Create a POS location
Follow this guide to add a tenant-scoped operating location with name, code, address and timezone. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goEnterprise POS → Locations or Enterprise POS → Shifts
What you’ll accomplish
Add a tenant-scoped operating location with name, code, address and timezone. This section covers physical/operational locations, registers and shift-controlled selling.
Follow these steps
- Go to Enterprise POS → Locations or Enterprise POS → Shifts and open the workflow that matches “Create a POS location”. Confirm the page or record context before making a change.
- Create or verify an active location.
- Create a register assigned to that location.
- Verify the register is active.
- Go to a shift with a non-negative opening float.
- Take sales through that register.
- Close the shift with a blind count and handover reason.
- Check expected, counted and variance values.
Fields and options to review
- Guide focus: Add a tenant-scoped operating location with name, code, address and timezone.
- Location name, code, address, timezone and active status
- Register name, code, location and active status
- Opening float
- Blind counted amount
- Close reason or handover note
- Expected cash and variance
- Current shift relation
Rules the system enforces
- Codes are uppercased and limited to A–Z, 0–9 and hyphen.
- Location and register codes are unique per tenant.
- A register belongs to a tenant location.
- Only one open shift can exist for a register.
- A register with an open shift cannot be disabled.
- Opening and counted amounts must be non-negative.
- Shift close data is signed with HMAC evidence.
How to confirm it worked
- The specific outcome described by this guide is visible and remains tenant-scoped.
- Active registers are available for shift opening and POS selection.
- A cashier can sell only against an open shift.
- Closed shift history records expected cash, counted cash and variance.
Safety checks and troubleshooting
- Use the correct timezone for each operational location.
- Do not share a staff login for shift accountability.
- Investigate variances through orders/payments and audit evidence; do not rewrite closed records.
Stay within the supported module flow
Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.
