General Settings
Use this guide to prepare site information, capacity, session rules, receipt details and customer messages for your Lexoh parking deployment. Work with an authorized administrator in the general settings area. Available fields, labels and device behaviour depend on the installed version and enabled modules; record the original values before changing an operating site.
Basic Settings
Configure the fundamental settings that define your parking facility's identity and tax handling.
Site Name
Enter the facility or organization name, then check how it appears in each enabled output:
- Parking tickets and receipts
- Customer emails and notifications
- System dashboard header
- Reports and administrative documents
Use Taxes
Configure tax handling from the values approved by the person responsible for your accounting. If the deployment offers separate tax fields, confirm which taxes apply and whether prices include or exclude them.
Tax Configuration
For each applicable tax, enter the approved rate, display name and registration number. The two groups below illustrate the information to prepare; use the fields available in your deployment.
Tax 1
| Tax Percent: | Approved rate, in the format requested by the field |
|---|---|
| Tax Name: | Display name (e.g., "GST", "Sales Tax") |
| Tax Number: | Official tax registration number |
Tax 2
| Tax Percent: | Approved second rate, where applicable |
|---|---|
| Tax Name: | Display name (e.g., "PST", "Local Tax") |
| Tax Number: | Registration number required for that tax |
QST: 9.975% of the same price before taxes, excluding GST.
For a taxable $100 amount before taxes, the rounded total is $114.98. Check exemptions, registration and rounding with your accounting contact. See Revenu Québec’s calculation guidance.
Parking Configuration
Manage your parking facility's capacity, current occupancy, and grace period settings.
Parking Capacity
Set the operating capacity agreed for the site. Validate how the configured capacity is used by each connected function:
- Entry decisions when the configured limit is reached
- Remaining-space information on connected signs or applications
- Capacity alerts, where configured
- The capacity used as the denominator in occupancy reports
Vehicles Inside
Treat the displayed count as a system estimate based on recorded events. Check the counting rules before relying on it for entry decisions:
- Which detection or access event increments the count
- Which confirmed exit event decrements the count
- Who may correct the count and how the reason is recorded
- What a reset changes, including its effect on open sessions
Grace Period
Define the free-entry interval separately from any time allowed to exit after payment. The examples below are policy choices, not Lexoh defaults. Test the charge just before and after the selected threshold.
| Grace Period | Use Case |
|---|---|
| 0 minutes | Example: no free interval at entry |
| 15 minutes | Example: a short drop-off or pickup allowance |
| 30 minutes | Example: a short-visit allowance |
| 60+ minutes | Example: a longer allowance approved by the operator |
System Behavior
Review these operating rules with the site administrator and installer. Test each enabled rule with controlled scenarios before changing live traffic or billing.
Maintenance Mode
Before using a maintenance setting, document its actual effect on the installed system:
- The entry and exit lanes that remain available, and who controls them
- Whether payment and ticket issuance continue or require an alternative process
- How operators are informed that maintenance is in progress
- The messages actually displayed on connected kiosks
- The effect on integrations and the steps to restore normal operation
Auto-Close Entries
If automatic session closure is enabled, verify its rules before activation. Closing a record does not establish that the vehicle has left.
- Confirm the configured execution time and site time zone
- Confirm the age threshold and exclusions for long stays or permits
- Test the effect on charges, payment status and later exit attempts
- Check whether occupancy changes and reconcile it against the physical count
- Confirm how an operator can identify, explain and correct a closed record
Disable Vehicle Limit
A capacity override changes an entry rule. Before using one, confirm the operating plan and the exact behaviour of the installed lanes:
- Verify whether each lane still requires an authorized credential or ticket
- Identify the approved overflow area and how vehicles reach it
- Keep occupancy monitoring active and account for the overflow area
- Check signs and alerts independently; do not assume the override updates them
Allow Exit Without Entry
Define the exception workflow for a vehicle with no matching entry record. Confirm each part of that workflow:
- How the vehicle or credential is identified before an exit decision
- How vehicles already on site are handled during migration
- How the operator provides assistance when an entry record is missing
- Which event and operator actions are recorded for reconciliation
- Which charge or lost-ticket policy applies; a missing entry does not imply a free exit
Branding & Visual Identity
Customize the visual appearance of your parking system to match your organization's brand identity.
Logo for Coupons & Receipts
Upload your company logo to appear on printed parking tickets and receipts:
- File format: Use a format accepted by the upload field and the connected printer.
- Dimensions: Fit the printable width without stretching the logo.
- File size: Respect the limit shown in the upload field.
- Color Mode: RGB (for color printers) or grayscale-friendly
- Validation: Print a sample ticket and receipt from each relevant device.
Logo for Emails
Upload a logo optimized for email communications sent to customers:
- File format: Use an accepted format and test it in the email clients your customers use.
- Dimensions: Keep the logo legible on desktop and mobile email layouts.
- File size: Respect the upload limit and avoid unnecessarily large images.
- Color Mode: Full color RGB
- Validation: Send test receipts, credential messages and notifications that are enabled for the site.
Branding Color
Choose the brand colour, then verify where the deployment applies it:
- Administrative buttons, headings and accents included in the theme
- Customer kiosk screens that use the site theme
- Enabled email and receipt templates
- The colour format accepted by the field, including any alpha value
- For a six-digit RGB field, #2196F3 is an example; do not assume an eight-digit field uses the same channel order
- Select the approved colour using the available controls
- Check that a typed value is accepted without changing its meaning
- Test contrast against the actual background if transparency is supported
- Review the saved result on each affected interface
Customer Messages
Prepare matching French and English messages for the ticket and email templates enabled at the site. Check the language selected by each customer workflow.
Parking Coupon Messages
These messages appear at the bottom of printed parking tickets issued at entry gates and payment kiosks.
Coupon Text (French)
Purpose: Closing message in French for French-speaking customers
Length: Follow the field limit and verify that the complete message prints.
Appears On: Bottom of parking tickets when French is selected
Coupon Text (English)
Purpose: Closing message in English for English-speaking customers
Length: Follow the field limit and verify that the complete message prints.
Appears On: Bottom of parking tickets when English is selected
Email Messages
Customize the introduction and closing text for automated emails sent to customers, such as access card confirmations and digital receipts.
Email Intro (French)
Purpose: Opening message that appears after the greeting
Use Case: Welcome customers and provide context
Appears On: Top section of automated emails
Email Intro (English)
Purpose: Opening message in English
Use Case: Welcome customers and provide instructions
Appears On: Top section of automated emails
Email Outro (French)
Purpose: Closing message and call-to-action
Use Case: Thank customers and provide contact information
Appears On: Bottom section of automated emails
Email Outro (English)
Purpose: Closing message in English
Use Case: Professional sign-off with contact details
Appears On: Bottom section of automated emails
Message Writing Best Practices
- Keep messages concise and friendly
- Include customer support contact information if needed
- Use professional yet welcoming language
- Test readability on actual tickets and email clients
- Ensure French and English messages convey the same meaning
- Test French accents, apostrophes and symbols with the printer’s supported encoding
- Include website URL for additional information
Saving Your Configuration
How to Save Settings
- Record the original values and the reason for each planned change
- Edit the intended fields and check any validation messages
- Use the save control provided by the installed version
- Wait for confirmation, then reopen the settings to verify the stored values
- Test the affected device, transaction or message; a saved value does not prove it has reached every component
Unsaved changes
Do not treat a modified field or a visible save button as confirmation that settings are stored. Finish the save operation and verify the result before leaving the page.
Important Notes
- Always save your changes before navigating away from the page
- Verify uploaded logos in an actual test print and received email
- Check branding changes in each affected interface after saving
- Confirm when tax changes take effect and how existing sessions, refunds and receipts are handled
- Confirm the actual state of each lane before beginning maintenance
Quick Reference
Use these checks after saving each type of change.
Change facility name
- Setting Section
- Basic Settings → Site Name
- Acceptance check
- Read the name on a test receipt
Enable/disable taxes
- Setting Section
- Basic Settings → Use Taxes
- Acceptance check
- Reconcile a test calculation and receipt
Update parking capacity
- Setting Section
- Parking Settings → Capacity
- Acceptance check
- Test the configured full-lot scenario
Set free parking time
- Setting Section
- Parking Settings → Grace Period
- Acceptance check
- Test both sides of the time threshold
Enable maintenance mode
- Setting Section
- System Behavior → Maintenance Mode
- Acceptance check
- Confirm lane and kiosk behaviour
Upload company logo
- Setting Section
- Branding → Logo (Coupon/Email)
- Acceptance check
- Inspect a print and a received email
Change brand color
- Setting Section
- Branding → Branding Color
- Acceptance check
- Inspect each affected screen
Customize ticket messages
- Setting Section
- Messages → Coupon Text
- Acceptance check
- Read a complete sample ticket
Troubleshooting Common Issues
Logo not displaying on tickets
- Verify that the upload accepts the chosen image format
- Check the file-size and dimension limits shown in the field
- Use the available save control, then reopen the settings to verify that the logo was saved
- Test print a sample ticket to verify appearance
- For thermal printers, use high-contrast images
Vehicle count inaccurate
- Compare open sessions with the physical count; do not enable automatic closure solely to hide a discrepancy
- Perform physical count during off-peak hours
- Have an authorized operator correct the count and record the reason
- Check barrier sensor functionality (entry/exit detection)
- Review recent entry/exit logs for missing events
Taxes not calculating correctly
- Verify "Use Taxes" is enabled in Basic Settings
- Check the field format, decimal precision, tax base and rounding against the approved calculation
- Ensure tax names and numbers are properly configured
- Confirm the effective date and the treatment of existing sessions before changing rates
- Test with a sample transaction to verify calculations
Branding color not applying
- Save the selected colour, then reopen the settings to verify the stored value
- Refresh browser cache (Ctrl+Shift+R or Cmd+Shift+R)
- Verify color format is valid hex code (e.g., #FF0000)
- Check color contrast meets accessibility standards
- Check synchronization and cached screens if a saved colour is not yet visible
Backup & Maintenance
Backup responsibilities
- Confirm who backs up the configuration for this deployment and how to request recovery
- Protect backup access and keep copies according to the approved hosting policy
- Schedule a controlled restore test and record its outcome
- Agree on retention and recovery requirements; do not assume a fixed retention period
Maintenance planning
- Routine operations: Monitor device status and actionable alerts.
- Periodic review: Investigate missing events and check backup status.
- Planned service: Follow each manufacturer’s cleaning, inspection and battery instructions. Apply approved, compatible firmware during a planned window.
- Access review: Review administrative permissions when staff or responsibilities change.
- Site review: Agree on an inspection schedule with the operator and installer.