Cash management has been rebuilt on both POS devices and Admin (POS channel). New register extension targets and APIs have also been added. With register sessions, reason codes, and the new cash drawer / ledger model, cash can now be tracked, controlled, and reconciled.
Records the breakdown of payments and cash movements per session. Even when and by which staff member the drawer was opened is logged.
Reason codes are required for cash operations outside of orders. Whether the drawer auto-opens can also be controlled per device.
View opens, closes, and expected balances in Admin's Register sessions tab. Filtering and export speed up accounting and reconciliation.
Each register session's summary is shown clearly on the device. You get improved cash tracking, a payment breakdown, andwhen and which staff member opened the drawer, with fine-grained visibility into cash activity.
Opening or adjusting the drawer andany non-order cash operation can be required to have a reason code. Enable and customize codes from the POS channel to keep the audit trail you need.
Control whether the deviceautomatically opens the cash drawer after an order. Useful for staff using mobile devices on the sales floor.
A dedicated tab has been added to Admin showingopen and closed sessions, along withexpected cash balances across locations and per locationFilters and exports have been improved, making accounting and reconciliation faster.
Even when running multiple stores, cash open/close and balances are consolidated on a single screen.per storeandoverallYou can check expected balances at both granularities, providing a starting point for reconciliation work.
Multiple devices cancontribute to a single cash drawerGoing beyond "1 device = 1 session," sessions spanning multiple devices are rolled up into a single drawer through an updated data model and API.Payment reports remain per-device,Cash reports are aggregated across contributing devicesand the ledger provides complete auditability of all cash events.
With new POS targets, apps canhook into open/close procedures,display alerts when balances exceed float / min / max thresholds, and extend session details with custom logic or reports.
Using the API, you canopen and close sessions programmatically,create cash drawers and reason codes,assign devices to drawers,and retrieve custom reports. Integration with back-office and accounting systems, and automation of routine close-out processes, are within reach.
| Item | Previously | New cash management foundation |
|---|---|---|
| Terminals and sessions | 1-to-1 1 terminal = 1 session | Many-to-1 Multiple terminals consolidated into 1 drawer |
| Cash operations outside of orders | Sparse records | Reason codes required Audit trail secured |
| Drawer operation logging | Unclear who opened it and when | Fine-grained logging Down to staff and timestamp |
| Cash reports | Closed at the terminal level | Aggregated across contributing terminals (payments remain per-terminal) |
| Reconciliation in Admin | Tends to be scattered | Dedicated tab Open/close, expected balance, export |
| Automation / extensions | Not specified | API + POS extension targets for open/close, assignment, reports, and alerts |
Sessions occur per terminal, but they roll up into a single drawer.Payments = terminal-level granularity,Cash = drawer-level granularityDesign your aggregation logic on the premise of this two-layer structure.
Opening/closing sessions, creating drawers/reason codes, assigning terminals to drawers, and retrieving custom reports are all available via API. Closing procedures and accounting integrations can be put on batches/workflows.
Alerts for when the balance exceeds float/min/max are injected by apps via POS extension targets. In-house logic such as prompting cash pickups or detecting theft can be hooked into the open/close procedures.
By requiring reason codes for cash operations outside of orders, the ledger retains "why the money moved." Design the code taxonomy (deposits, withdrawals, adjustments, change replenishment, etc.) on the POS channel side.
This article is a feature overview. Specific API schemas, the list of available POS extension targets, and supported plans/countries areNot specified in the article body. Verify against the developer changelog and the POS UI extension targets documentation before implementing.