Skip to main content
Release note· Updated August 12, 2026· Mathias Nielsen

Dialog-free refund, authentication, and product commands now available

Final POS now processes refunds (including gift card and partial payment refunds), user authentication, and product catalog changes — create, edit, delete, and inventory receiving — through programmatic commands. No modal dialog boxes appear during any of these workflows. Structured error codes are returned on failure instead of fallback dialogs.

What changed

Refund processing, user authentication, and product catalog management on Final POS terminals no longer rely on modal dialog boxes. All three workflows now execute through dedicated programmatic commands — the action runs in the background, and the terminal updates without interrupting the cashier's session.

What's new

Refund commands

  • Standard refunds — Dispatch a refund command against a transaction and the return completes without a refund dialog appearing on screen.

  • Gift card refunds — A dedicated gift card refund command credits the return directly to the card. No prompt modal, no manual entry step.

  • Partial payment refunds — For split-tender transactions, a partial refund command accepts a specific amount and processes exactly that amount — no interactive dialog required.

Authentication commands

User login no longer triggers an authentication dialog. Credentials are processed silently through a dedicated auth command, and the session state updates in the background. The cashier flow continues uninterrupted.

Product commands

  • Create — Add a new product record to the catalog programmatically.

  • Edit — Update an existing product's details without opening a UI form.

  • Delete — Remove a product record. If the product is currently attached to an active cart, the command aborts and returns a descriptive error rather than deleting mid-transaction.

  • Receive inventory — Increment a product's stock count when a shipment arrives, directly from a command — no manual form entry needed.

How commands execute

Every command follows the same pattern: the action is dispatched with a typed payload, executes in the background, and returns a structured status result. If something goes wrong — a gateway timeout on a gift card refund, invalid credentials on an auth command, or an over-limit amount on a partial refund — the system returns a structured error code. There is no fallback to a dialog box.

What's not included yet

Batch product updates and multi-location inventory rebalancing are not part of this release. Those are planned for a future phase.

Who this affects

Any POS terminal running refund, authentication, or product management workflows. No action is required on your end — the commands are available now.