Offline-first, touch-oriented POS

Point of sale software built for the person behind the counter.

StamPOS keeps trading practical: big touch targets, local sales data, clear cash handling, receipt printing, event reporting and payment flows that do not pretend network failures are simple declines.

See the product View roadmap

Local SQLite data Touch-first JavaFX Linkly-first EFTPOS direction

Sales menu

No server requiredDesigned for local operation

Touch-first checkoutLarge operator controls

Payment-awareApproved, declined and unknown states

Event-readyX/Z reporting direction

Product showcase

The app is the marketing.

StamPOS is not trying to be a generic SaaS dashboard. The interface is built around real event hardware, fast operator decisions and keeping the queue moving.

SalesTouch menu

Large product tiles, visible totals and an obvious PAY action.

AdminLocal control

SKUNamePriceStatusWATERWater4.00ActiveCOFFEECoffee6.00ActiveMERCHMerch25.00Active

Products, transactions, employees, reports, receipts and payments stay on-terminal.

TechnicianReadiness

Storage OK · Database OK · EFTPOS simulator active

Separate maintenance tools keep normal event operation clean.

Built for actual trading

Small-business POS without unnecessary complexity.

Everything important is visible, touchable and grounded in the sale workflow: products, payment, receipt, reporting and the next customer.

Fast checkout

Touch-friendly product buttons and a focused sale flow for busy service periods.

Local sales data

SQLite storage on each POS terminal keeps core trading independent of a central server.

Receipt-ready

Simulator, Windows printer and direct network printer paths support practical setup and testing.

Admin controls

Manage products, prices, visibility, reporting periods, hardware and completed sales.

Technician tools

Readiness checks, diagnostics, storage snapshots and database housekeeping before event start.

Event reporting

Start reporting periods, close events with itemised Z reports and retain vendor records.

Cash demoSale total: $35.00

Tendered$0.00

Change due$0.00

Operator-first cash handling

Press notes the way customers hand them over.

For a $35 sale, the operator can press $20 twice, see $40 tendered, then return $5 change. No mental arithmetic required while the line is building.

Payments without guesswork

Linkly-first, provider-neutral EFTPOS direction.

StamPOS is shaped around a provider-neutral terminal workflow, with Linkly as the preferred first production path. The goal is clear operator feedback, persisted attempts and safe recovery when a terminal result is uncertain.

1Create local salePayment attempt is recorded first

2Send to terminalProvider-neutral transaction ID

3Persist outcomeApproved, declined, cancelled or unknown

4Receipt and reconcileStore references and receipt text

Operational confidence

Prepared for market stalls, pop-ups and event days.

StamPOS separates normal operator tasks from technician tools. Admin handles products, sales, payments and reporting. Technician tools support storage status, database health, diagnostics and pre-event readiness checks.

Admin

Create the administrator PIN, manage products and prices, review completed sales, configure payments and select receipt printing mode.

Technician

Run storage checks, database health checks, external archive support and pre-open readiness checks before trading begins.

Event flow

Zeroise/start an event reporting period, close with an itemised Z report and retain data for vendor records.

Explore StamPOS

Follow the product beyond the homepage.

Read the current product direction, development milestones and public design guidance as StamPOS progresses toward its first customer-ready release.

Growing

Taking on the big guys, one practical workflow at a time.

StamPOS is progressing through Linkly accreditation, documentation and release preparation while its private application source remains protected.

See what comes next