Paid customer stays
Compare rate rules, exit validation and transaction follow-up.
Explore parking revenue controlShopping centre parking
Parking systems for shopping centres and retail sites
A retail parking system must distinguish a shopping visit from employee parking, a delivery or unrelated long-stay use. Define those journeys and the customer payment policy first. Lexoh can connect the selected access and payment equipment to the rules approved for the property.
Start with the operation
Decide what counts as a customer visit
A free period, a merchant validation and a paid stay are different policies. Specify the trigger, maximum duration and exceptions for each. A camera or barrier alone cannot determine whether someone shopped at a tenant’s business; the project needs an explicit validation process where that distinction matters.
| Arrival or user | Policy to define | Design consequence |
|---|---|---|
| Customers | Is parking free, time-limited or paid? | Define entry records, grace periods and departure instructions. |
| Merchant validation | Who can grant it and what does it change? | Confirm the selected payment workflow and accountability. |
| Employees | Which area should long stays use? | Separate recurring staff rights from customer benefits. |
| Deliveries | Are service lanes physically separate? | Coordinate vehicle size, loading hours and authorized access. |
From policy to the lane
Keep the customer journey clear
Choose the control model
Compare a gated entrance with an open site and a defined verification process. Consider queues, pedestrian crossings and delivery paths. The right operating model depends on the layout and the policy, not simply on adding a barrier.
Make validation auditable
Define which merchants can validate, the permitted benefit and how exceptions are recorded. Confirm the exact feature and payment configuration during scoping. Train tenant staff on the same rule that the exit equipment will apply.
Test the difficult departures
Include an unread credential, a disputed duration and an unsuccessful payment in acceptance testing. State who can assist and when. A customer should not discover the help procedure only after blocking the exit.
Lexoh software and physical equipment
Connect retail parking rules to the equipment
Payment kiosks and merchant validation
Choose where customers pay: before returning to the vehicle or at an exit equipped for payment. Specify how the selected kiosk or payment interface identifies the parking session and applies any approved free period or merchant discount. Ask for a demonstration using a valid discount, an expired validation and a failed payment before selecting the configuration.
Readers, vehicle detection and barriers
For controlled entrances, match the credential reader and barrier to the lane layout, vehicle detection and pedestrian crossings. Give employees a defined credential and permitted area. An open car park needs a separate method for checking parking use; adding a camera does not by itself establish purchase validation or enforcement.
Operator records and customer assistance
The illustrated Lexoh Security Center device view shows entry events, camera context and barrier commands. Specify the separate payment and validation records needed to investigate a disputed stay, including who granted the benefit and which transaction it affected. Confirm operator permissions, available exports and assistance hours for the proposed configuration.
Planning exampleSee the documented Scotiabank installation →
A shared lot serves shops and an evening venue
Consider a retail property whose shops close before an on-site evening venue. A daytime free period may be unsuitable for the later event. Define the event entitlement, the transition time and employee areas separately. Test a vehicle arriving before the policy change and leaving afterward. If the site uses merchant validation, agree which business bears the parking charge and how the operator reviews the record.
Prepare the scope
Give tenants and operations the same rules
The site plan, pedestrian crossings, loading routes and observed peak arrival and departure periods.
Customer duration rules, merchant validation authority, employee allocation and event exceptions.
The payment journey, help coverage and records required to investigate disputed parking sessions.
Retail parking questions
Questions to settle before selecting the equipment and configuration.
Yes, the operating policy may include free parking. Specify how the period is established and what happens after it ends, then confirm how the selected system applies that rule. Free parking does not automatically require payment equipment.
It can control entry against configured rights. It does not by itself determine how a vehicle is used after entry or verify a purchase. Define the evidence and follow-up process needed for the property’s policy.
That depends on the approved validation and payment configuration. Define merchant roles, the benefit granted and reporting needs, then request a demonstration of the complete workflow before selecting it.
Traffic layout, the number and placement of payment points, merchant validation and employee access all affect the design. Include customer signage, payment configuration, civil work and operating support in the estimate. Define how the free period starts and ends; add merchant validation only if a purchase changes the parking entitlement.
Lexoh combines cloud management with offline operation through a mesh network that lets site devices communicate locally. Access equipment still needs power and locally available permissions. Payment authorization and merchant-validation services have their own connectivity requirements. Define and test the customer exit and assistance procedure when one of those services is unavailable.
Design parking around the retail visit
Bring the customer policy, tenant needs and lane plan so we can review access, payment and operational follow-up.