How to build a POS system
Follow these steps in Evonx to a point-of-sale app with catalogs, carts, and tender flows you can preview and ship. Pair with the POS template when cashiers need a fast starting layout instead of a blank prompt.
Step-by-step
Define catalog and locations
List SKUs, modifiers, tax rules, and store locations so register behavior matches retail ops.
Start from the POS template
Open the POS template in Evonx or describe products, carts, and payments explicitly.
Model tickets and inventory impact
Create orders, line items, payments, and stock decrements with idempotent sale completion.
Build cashier and manager screens
Ask for barcode-friendly product search, cart edits, voids with reasons, and end-of-day summaries.
Wire payment providers
Integrate card readers or Square/Stripe terminal hooks; never expose secret keys client-side.
Preview register flows
Walk refund, split tender, and offline-failure cases in preview before production merge.
Outcome
A POS repository with catalog, cart, tender, and inventory hooks you can preview and ship.
Related resources
FAQ
Is this guide for online checkout or in-store registers?
It targets in-store POS. For pure ecommerce checkout, start from order management and payment integration guides instead.
How do I keep inventory accurate across registers?
Model stock at location level and decrement on completed sales with clear void/refund reverse movements.
Can I reuse an existing product catalog?
Yes. Import the repo and map SKUs and modifiers into the POS entities this guide describes.
Build production software with Evonx
Start from a template or connect an existing repository. Evonx helps you ship real applications with preview, evolution threads, and pull-request delivery—not disposable demos.