Permits and reservations
Connecting parking permits and reservations
A permit grants an entitlement under a policy. A reservation may also allocate capacity for a particular period. They can produce similar access rights, but they are not automatically the same record or business process.
The decision
Decide which system owns each fact
Identify the source for the customer, booking dates, payment status, permit eligibility and vehicle details. Define how those facts become an access right at the lane.
Lexoh’s parking-permit workflows and documented API can support an integration project. Compatibility with a particular booking system requires a review of its available interfaces, permissions and data model.
Specify the whole change lifecycle
Creating a new arrival is only the first case. Include changed dates, cancellations, refunds, no-shows, vehicle substitutions and a booking moved between sites. State when each change should affect access.
A refund does not necessarily cancel a stay, and a cancelled stay should not leave an active credential unnoticed. Write the mapping explicitly rather than relying on similarly named fields in two systems.
On a narrow screen, scroll the table horizontally to see every column.
| Record | What it establishes | Decision to document |
|---|---|---|
| Permit | Eligibility for a zone and period | Who approves, renews and revokes it |
| Reservation | A booking for an agreed period | Whether it reserves a stall, a zone or only admission |
| Payment | A transaction and its status | Which payment changes affect the booking or access |
| Access right | Permission recognized at an entrance | Credential, entrances, validity and update confirmation |
Choose a transfer method the team can maintain
Manual entry can suit low volumes if staff have a reconciliation procedure. File imports need validation and a clear schedule. An API integration needs ownership, error handling and monitoring.
Ask the project team to demonstrate how a new booking, a change and a cancellation reach the entrance. Confirm whether a supported connector exists or a custom integration is needed, and name who will maintain it. Include configuration, testing and ongoing support in the proposal.
Test duplicates, delays and failures
Send the same booking more than once and verify that it does not create duplicate rights. Test changes arriving out of order, a disconnected destination and recovery after a failed update.
Document how staff recognize an unsynchronized record and resolve it. During an outage, a controller may continue using stored rights where supported, while a new cancellation or arrival has not yet reached it.
Keep capacity and access aligned
A valid credential does not necessarily guarantee an available stall. If the reservation sells a space, define how capacity is allocated, how permits consume it and whether the guarantee applies to a specific stall or a zone.
Before launch, compare a sample of bookings, permits and access rights with the reception team. The acceptance criterion is a correct customer journey through changes and exceptions, not merely a successful first import.
Questions
Practical questions
Does a refund automatically remove access?
Not necessarily. A refund, a cancelled booking and a revoked access right are separate changes. Define which event changes the right, when it takes effect and how staff confirm it reached the entrance. Test partial refunds as well as complete cancellations.
Can seasonal permits and short-stay reservations use the same entrance?
They can be planned around the same entrance if the selected system and equipment support both workflows. Define each group’s zones and validity, whether it consumes shared capacity, and what happens when the lot is full. Test both credentials with the actual lane equipment.
Does an API mean the booking software is already integrated?
No. The interfaces, mappings, permissions, update process and support responsibilities must be designed and tested.
Can a permit guarantee a parking space?
Only if the operating policy and capacity management explicitly provide that guarantee. Access eligibility alone does not reserve capacity.
References and further reading
- Digital parking permits
Lexoh product or project reference.
- Lexoh API reference
Lexoh product or project reference.
Your project
Scope the booking-to-access integration
Share the booking platform and change scenarios with Lexoh for a technical review.
Discuss the project