Activate or disable a register
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Control register availability while respecting open-shift protection.
What this guide helps you do
Control register availability while respecting open-shift protection. 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 “Activate or disable a register”. 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
- Guide focus: Control register availability while respecting open-shift protection.
- 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 and limits
- 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.
Check 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.
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.
