Build my booking setup

Every location thinks it’s the only one. The panel knows it isn’t.

Set up brands, currencies and teams once. Tiqory keeps everything separate where it should be and consolidated where you need it, with no spreadsheet bridging locations by hand.

See all capabilities

Multi-location chains

Ten locations. One panel that knows which is which.

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.

  • 28 permissions independent building blocks for exactly the role each team, location or brand needs
  • Unlimited locations and product collections per organization, without duplicating configuration
  • Indefinite is how long the audit trail is kept: who changed which price, and when

The problems you already know. Solved without a call per location.

Several brands, several currencies, several teams: the same engine keeps them apart without ever losing sight of the whole picture.

01

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.

02

Roles built for each team

Sales, support, the gate, finance: each with exactly the permissions it needs, out of more than 25 possible ones, not one more.

03

Every location, its own currency

Every product has its own currency and timezone, so price and booking cutoff are calculated where the experience happens, not at one central location.

04

An audit trail that never forgets

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

Here’s the operation, from the gate to the report

Five steps that repeat exactly the same way at every location, without anyone having to replicate anything by hand.

  1. 1

    New location

    A new product inherits the collection setup already assigned to each agent. No one has to reconfigure access by hand.

  2. 2

    Local sale

    Each location sells in its own currency and timezone, with price and tax resolved where the experience actually happens.

  3. 3

    Restricted access

    An agent only sees, edits and cancels what their product scope allows, even if the organization has thousands of products.

  4. 4

    Audited change

    Any price or availability adjustment gets logged with who made it, the previous value and the new one, no exceptions.

  5. 5

    Consolidated report

    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

Every location, its own schedule and its own currency

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.

GET /api/v1/products/rooftop-tasting-experience/calendar
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12
  13. 13
  14. 14
  15. 15
  16. 16
  17. 17
  18. 18
  19. 19
{
  "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"
    }
  ]
}
200 Availability resolved

The detail almost no one tests

Revoking a permission mid-session works mid-session

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.

Frequently asked questions

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.

More bookings. More channels. The same calm.

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.