One agent, only the products that are theirs
Restrict each user to the products or collections of their location, without touching permissions or creating a separate account per brand.
Multi-location chains
Granular roles, large catalogs and real isolation between brands: every team sees only what’s theirs, and you see everything, without asking anyone for a separate spreadsheet.
Several brands, several currencies, several teams: the same engine keeps them apart without ever losing sight of the whole picture.
Restrict each user to the products or collections of their location, without touching permissions or creating a separate account per brand.
Sales, support, the gate, finance: each with exactly the permissions it needs, out of more than 25 possible ones, not one more.
Every product has its own currency and timezone, so price and booking cutoff are calculated where the experience happens, not at one central location.
Every change to price, availability or tax is logged: who, what and when, kept indefinitely to settle any dispute.
A Monday with ten locations open
Five steps that repeat exactly the same way at every location, without anyone having to replicate anything by hand.
A new product inherits the collection setup already assigned to each agent. No one has to reconfigure access by hand.
Each location sells in its own currency and timezone, with price and tax resolved where the experience actually happens.
An agent only sees, edits and cancels what their product scope allows, even if the organization has thousands of products.
Any price or availability adjustment gets logged with who made it, the previous value and the new one, no exceptions.
Sales by location, by currency and by channel, available from one panel, without asking every manager for a CSV.
The same API your checkout uses
The same calendar call resolves the final price in that location’s currency and the booking cutoff in its own timezone, with no central location having to translate anything.
{
"date": "2026-09-03",
"location": "Ciudad de México",
"timezone": "America/Mexico_City",
"currency": "MXN",
"is_open": true,
"slots": [
{
"start_time": "11:00",
"remaining_capacity": 24,
"price_display": "$450.00"
},
{
"start_time": "17:30",
"remaining_capacity": 9,
"price_display": "$520.00"
}
]
}The detail almost no one tests
If an admin removes a permission or a product scope while the user’s session is still open, the change is revalidated on the next sensitive action, not on the next login. A revoked access stops working immediately, not the next day.
Yes, by restricting their access to that location’s product collections. Add a new product to that collection and the agent sees it automatically, no reconfiguration needed.
As many as you need, combining up to 28 independent permissions: from managing users and rotating API keys to redeeming a single ticket at the gate.
No. Every report is grouped by currency; a reference total with cached exchange rates can optionally be shown, always flagged as an estimate.
Its products stop being available immediately in the API, for both public traffic and existing keys, and its staff loses panel access instantly.
Yes. The audit trail keeps who, what changed, the previous value and the new one, indefinitely, for prices, availability and tax.
Tiqory keeps availability, pricing, payments and access working together as your operation grows. Tell us where you are headed; we’ll show you how to get there without starting over.