evonx
Log in
App template

Point of sale template for retail and cafe counters

Take orders, apply modifiers, and close shifts with cash reconciliation that matches how a counter actually runs. This POS template is built around tickets, tenders, and inventory decrements—not a spreadsheet of SKUs with a checkout button bolted on.

Get started freeBrowse templates
pos.acme.storeFront counter
Open tickets

Ring up sales, manage open tickets, and reconcile end-of-day cash and card totals.

Tickets today186
Avg ticket$24.10
Open shifts3
  • Table 4 — brunchOpen · $68.40
  • Walk-up #412Paid card · Tip $4
  • Catering pickupHold · Due 12:30

What's included

Ring up sales, manage open tickets, and reconcile end-of-day cash and card totals.

Intended users

  • Store managers
  • Cashiers
  • Owners

Suggested stack

  • PostgreSQL
  • Next.js
  • Card reader SDK

Core features

Fast ticket entry with modifiers

Split tenders and tips

Shift open/close reconciliation

Inventory decrement on sale

Receipt reprint and voids

Main workflows

Ring a sale

Add items and modifiers, take tender, print receipt.

Void line item

Require manager PIN, log reason, restore stock.

Close shift

Count drawer, compare expected, submit variance notes.

Database model / entities

Distinct domain entities — not a renamed generic CRUD list.

TicketOpen or closed sale with line items and tenders.
Catalog itemSellable SKU with price, tax, and modifiers.
ShiftCashier session with opening float and closing count.
TenderPayment method applied to a ticket with amount.

User roles

  • Owner
  • Store manager
  • Cashier

Possible integrations

Applications built from this template can connect to these services via their APIs.

  • Stripe Terminal
  • Square
  • Resend
  • Twilio

Example prompt

Copy this into Evonx to start from a production-shaped brief instead of a blank canvas.

Build a POS with tickets, catalog items, modifiers, shifts, and tenders. Support split payments, tip capture, manager voids, inventory decrement, and end-of-day reconciliation. Use PostgreSQL with cashier and manager roles.

How Evonx customizes this template

Start from the domain model above, describe the workflows your team needs, and Evonx generates a working preview you can refine. For teams with an existing codebase, the same agent can extend repositories instead of starting from a blank project.

Related resources

Build POS with AIOperators evaluating POS software with AI should expect repository-backed catalogs, carts, and tender flows. Use this paCRM templateTrack leads, accounts, and pipeline stages with activities your team can evolve in production. This template maps a B2B SaaS templateLaunch a multi-tenant product skeleton with auth, settings, and billing integration points.Admin dashboard templateCentralize configuration, user management, and monitoring for internal operators.Customer portal templateLet customers view orders, tickets, documents, and profile data without emailing your team.Inventory management templateTrack SKUs, warehouses, adjustments, and low-stock signals for fulfillment teams.

FAQ

Does the POS template support split tenders on one ticket?

Yes. A ticket can take multiple tenders—cash plus card, or gift balance plus card—before closing.

How are voids controlled on the floor?

Void and discount actions can require a manager role or PIN and always write a reason into the audit log.

Can inventory update when a sale completes?

Closed tickets decrement on-hand quantities for stocked catalog items so the back room stays closer to reality.

Is this only for restaurants?

No. The same ticket/catalog/shift model works for retail counters and cafes; customize modifiers and tax rules per venue type.

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.

Get started freeSee AI for existing software