Make sale states explicit
Cover code scanning, search, quantity changes, discounts, parked baskets and completion. Weighted, bundled and marked items may require different checks. Order creation, payment, fiscal documents and handover are distinct events. After a partial failure, the cashier must know what completed and which next action is safe.
Shifts, returns and permissions
Agree shift opening and closing, cash movements, full or partial returns and correction. Available operations depend on the existing checkout and payment environment. A merchandise return does not automatically confirm a refund. Assign discount, cancellation and reporting permissions with an audit trail; do not delete closed-shift history.
Verify payment and fiscal providers
Terminal, online payment, fiscal-device and fiscal-data-operator integration require an actual local provider, documentation, contractual access and a sandbox. Building an interface does not establish legal compliance. Confirm applicable procedures with the provider and customer specialist. Retries must not create second payments or receipts; uncertain outcomes require reconciliation.
Inventory, devices and connectivity
Receive products and prices centrally and return sales with stable identifiers. Define reservations, rounding and price-conflict rules. Verify actual scanner, scale, printer and terminal models, drivers and protocols. Allow offline operations only where the provider and agreed workflow permit them. Avoid unnecessary payment-data storage and exposed credentials.
Pilot one checkout
Map sale exceptions, test a prototype with cashiers and connect provider test environments. On actual equipment, simulate post-payment outages, print failures, double clicks and partial returns. Reconcile accounting and document uncertain-status procedures before production access is enabled.
- Reproduce basket totals from agreed rules.
- Prevent duplicate sales on repeated clicks.
- Separate payment, receipt and handover states.
- Link returns to original operations.
- Show a safe response to device failure.
Project questions
Is this automatically a certified fiscal checkout?
No. We develop software and integrations; the selected provider must confirm fiscal status, permitted modes and required procedures.
Can an existing terminal be integrated?
Only after checking its model, protocol, acquiring agreement and access. A USB or Ethernet port does not establish support.
Will it sell without internet?
That depends on operations, devices and provider rules. Uncertain payments cannot be treated as successful without confirmation.
Illustrative image