What is a Sublocation?
Understanding sublocations and how they structure your business in Tiquo
Use sublocations to manage parts of your business independently within the same Tiquo organisation.
Sublocations make it possible to run simple single-venue setups as well as complex multi-brand, multi-entity operations without changing systems.
Definition of a sublocation
A sublocation represents a distinct operational unit within your organisation. This could be a physical space, a department, a venue within a venue, or a service area that needs its own configuration, reporting, or payment flows.
A sublocation can be configured for Products, Services, or Products & Services. Service sublocations include booking workflows. The enabled capabilities determine which configuration and operational tools are available. A sublocation that offers only one can add the other later from Sublocation Settings > General > Services & Products. See Services & Products.
A business can use a single sublocation, such as a standalone bar or café, or several sublocations within the same organisation.
Each sublocation can have its own:
- Products & Services: independent catalog and pricing
- Availability & Bookings: separate scheduling
- Orders & POS: dedicated order flows
- Staff Access: granular permissions
- Payment Routing: separate settlement
- Reporting: independent analytics
Sublocations always sit within an organisation and can be linked to the same or different legal entities.
Common sublocation examples
Examples of sublocations include:
When to use a sublocation
You should use a sublocation when part of your business needs:
- Its own products, services, or availability
- Separate operational workflows
- Independent reporting or performance tracking
- Distinct staff access or permissions
- Separate payment routing or settlement
If something needs to be configured, operated, or settled independently, it should usually be set up as a sublocation.
How sublocations affect pricing
Tiquo pricing is based on sublocations and the types of revenue enabled within them.
| Scenario | Billing |
|---|---|
| Single sublocation | Billed monthly |
| Multiple revenue types | Each revenue type billed separately |
| Products + Services | Both capabilities billed |
Core sublocation pricing depends on the enabled product and service capabilities. Marketing pricing is separate and depends on the total number of customers in your database. See Subscription & Fees.
How sublocations affect operations
With sublocations, teams can:
- Run products and services with dedicated workflows
- Control staff access at a granular level
- Route payments correctly across legal entities
- Track performance per sublocation or across the organisation
- Maintain consistency across brands and locations
Customers can interact with one or several sublocations as parts of the same business.