Guide
Vehicle vs Accommodation Operations
Vehicle rental and accommodation differ operationally because a vehicle leaves and returns physically changed, while an accommodation unit stays in place, only changing between occupied and ready.
What problem this solves
A vehicle rental business needs condition documentation and fee logic because the vehicle is out of sight during the rental; an accommodation business needs readiness control and a daily rhythm because the unit never leaves — a shared model would apply the wrong emphasis to both.
Why the alternative is insufficient
Modeling both domains as one generic 'return an asset' process with different labels would either force odometer and fuel fields onto accommodation, which has neither, or drop the readiness-state concept for vehicles, which has no equivalent.
How Kasura handles it
A vehicle return captures odometer, fuel level, damage and fee decisions before resolving the deposit; an accommodation check-out ends occupancy and moves the unit into a readiness state (ready, dirty, cleaning) instead.
What this does not mean
That vehicle return and accommodation check-out are the same process with different labels; a vehicle return has odometer, fuel and damage capture with no readiness state, while check-out has a readiness-state transition with no odometer, fuel or vehicle-condition component.
Related concepts
Part of: Vehicle Rental Operations, Accommodation Operations
Related glossary terms
Related guides
Principles: PR-01, PR-11 · Rationale: WHY-04, WHY-13 · Product Truth: T13, T14, T15
← Back to Guides