Keep the POS you already use.
Loyalty starts when the payment ends
An in-house CRM that receives payment records from a store's POS and turns them into loyalty points and repeat-visit management. When a payment completes, the staff tablet shows an alert, and the customer enters a phone number to earn points. It was installed at one pilot store and confirmed to work.
B2B SaaS, POS integration, loyalty CRM
Real screens.
Screens from a run with demo data. Select an image to enlarge it.
A POS records sales, but not who came back and how often.
Managing regulars means using one more tool besides the POS. At a busy counter, that extra step is where loyalty gets skipped.
We leave the POS untouched and read only the payment information.
A bridge program installed on the store PC reads POS payment records in read-only mode. It takes the amount, time, receipt number and cancellation status. It does not read card numbers or customer details. When a refund arrives, the matching points are revoked automatically.
The owner's admin covers customers, points, coupons, at-risk customers and sales analytics. Automated messages run on four kinds of rules, capped at 200 per store per day.
Stack.
.NET bridge
Reads POS payment records in read-only mode on the store PC and sends them to the server.
Node.js, TypeScript, PostgreSQL
Handles payment intake, customer matching, and point accrual and revocation.
Three Next.js apps
Split into owner admin, staff tablet and customer mini home.
SSE
Notifies the tablet as soon as a payment arrives.
Cloudflare Workers, AWS Lightsail
Screens deploy to Workers, and the server and database run on Lightsail.