Operator help center

Open Locations, create the location, and enter its public name, address, timezone, and operating details. Add zones or spaces when the location needs capacity tracking or separately managed areas.

Choose a memorable shortcode and generate QR codes from the QR codes area. A QR code is simply a link, so anyone who has the link can open it. Unlisted locations are omitted from ParkTab location search and shortcode discovery; unlisting cannot prevent a previously shared direct or QR link from being used.

Assign the intended pricing group, confirm that at least one active base rate applies, and use the pricing tester for representative arrival times and stay lengths. Also check taxes, service fees, maximum stay, and payment options.

Publish only after the driver flow is complete. Test the public link in a signed-out browser and scan the real printed QR code before installing signage.

A pricing group owns rate plans, and locations receive pricing by being assigned to groups. Each plan is a versioned pricing document. Base plans are matched automatically; access plans are reached through a pinned link or other controlled entry path. Lower priority numbers are considered first.

Use bucket pricing when the sign gives one total price for each stay-length band. Use progressive pricing when charges accumulate over time. Use a package when one price includes parking until a stated exit deadline. Add schedule windows, stay limits, day boundaries, overage behavior, caps, taxes, and modifiers only when the posted rules require them.

Saving a pricing change creates a new immutable version. Keep useful gaps between priorities, such as 10, 20, and 100. Leave a draft or inactive plan out of live quoting until it has been tested.

Use the pricing tester with times just before and after schedule boundaries, the minimum and maximum stay, overnight stays, grace periods, vehicle or service modifiers, taxes, and overage. Compare the rendered summary and total with the physical sign before activation.

Use Sessions to search by plate, location, status, or date. A session record is the operational source for its vehicle, quoted price, payment, timestamps, extensions, and related activity.

A driver may be quoted before payment is complete. Do not treat a browser confirmation alone as proof of payment; use the session and payment status shown in ParkTab. Payment methods can include cards and supported wallets through the configured processor.

Drivers can retrieve receipts from their account or receipt link when available. Before making a correction, confirm the location, plate, amount, timestamps, and payment identifier so a similarly named session is not changed by mistake.

Only authorized operator staff should issue a refund. Confirm the amount and reason, explain that bank posting time varies, and keep the ParkTab reference for follow-up. ParkTab does not promise an exact bank settlement date.

Open Get paid and complete the processor onboarding steps for the operator account. Required business and bank information is collected by the payment provider. Payout availability depends on the provider account being verified and enabled.

Reports and payment views help reconcile sessions, gross charges, fees, refunds, and payouts. Date ranges and operational timestamps can differ from the processor payout date, so use the same basis on both sides of a comparison.

Invite users from Users & Roles and assign the least access they need. Review roles when responsibilities change, and remove access promptly when someone leaves the organization.

A ParkTab role controls what a teammate can do in the product. Payment-provider verification controls whether money can be processed or paid out. Fix the system that owns the blocking status.

Valet operations track vehicle intake, ticket or claim identity, vehicle status, requests, and return. Staff should advance the vehicle through the actual operational stages so the driver-facing status stays accurate.

When a driver requests their vehicle, verify the claim path before releasing it. Use the current request and vehicle record rather than relying only on a name or verbal description.

Use Enforcement to check whether a plate has an applicable active session or authorization. Confirm the plate, location or zone, and effective time before taking action. A typo or wrong zone can make a valid stay appear unauthorized.

Citations and payment records are separate from ordinary parking sessions. Record the evidence and identifiers required by the operator policy, and use the citation-specific flow for review or payment.

Create location and access-plan QR codes from QR codes. The encoded value is a URL, so print tests should be scanned at the intended size and distance. Replacing signage is necessary if its destination must no longer be shared.

Supported payment hardware must belong to the correct operator and location context. Confirm network connectivity, processor registration, and the selected location before troubleshooting an in-person transaction.

ParkTab integrations use authenticated APIs, including GraphQL operations and realtime subscriptions where provided. ParkTab does not currently promise arbitrary outbound HTTP webhooks, so integrations should use the documented interfaces rather than assuming webhook delivery.

Store API credentials only in approved secret storage, grant the narrowest permissions possible, and rotate credentials that may have been exposed. Never place a server secret in browser or mobile client code.