One stock number, online and at the counter.
Point of sale and ecommerce sharing a single source of truth, on hardware that keeps trading when the internet does not. The gap between the shelf and the website is where most retail software falls over.
- 4 – 6 weeks
- scope to live
- Fixed price
- against a written scope
- Offline first
- trading continues in an outage
Who this is for
You probably need this if…
01
You oversold something you did not have
It sold in store and online within the same hour. One customer is getting an apology email, and the stock figure was never wrong on purpose.
02
The internet goes down and trading stops
A cloud-only till means an outage at somebody else's data centre becomes a queue of people at yours who cannot pay.
03
Each location does it differently
The printer was configured by hand at one site and nobody wrote down how. The second site has never produced a correct receipt.
What we build
The work, in detail.
POS terminal software
Built for a counter: fast, touch-first, and usable by somebody who started yesterday with six people waiting in front of them.
Unified inventory
One stock record behind the till and the storefront, with reservations and conflict rules agreed before anybody hits a conflict.
Offline trading
A full local store with queued operations, so the till keeps working through an outage and reconciles cleanly when it returns.
Peripherals
Receipt and label printers, barcode and QR scanners, cash drawers, scales and customer-facing displays, tested on the real hardware.
Payments at the counter
Certified card readers, tips, split payments and refunds, including what happens when a reader disconnects mid-transaction.
Reconciliation
Daily comparison of till, storefront, processor and ledger, naming the transactions that disagree rather than counting them.
Storefront
A customer-facing store on your own domain, or an integration with the Shopify or WooCommerce shop you already run.
Multi-location
Per-site configuration, staged updates and reporting across every location, without anybody driving between them.
Practice areas
The disciplines behind it.
You buy this as one engagement at one price. Underneath, it draws on 4 of our practice areas, and the same people cover all of them.
Devices & Edge
Software for the hardware on a counter, in a stockroom or on a wall.
- POS terminal software
- Peripheral integration
- Card reader integration
- Kiosk & self-service
Payments & Commerce
Taking money reliably, and being able to prove where it went.
- Checkout & payments
- Subscriptions & billing
- Invoicing & receipts
- Marketplace payouts
Systems Integration
Making two systems agree that were never designed to talk to each other.
- POS & retail platforms
- Payment routing
- Identity federation
- Third-party orchestration
Data & Sync
Getting the same number in two places, and keeping it there.
- Schema & modelling
- Delta sync
- Reconciliation
- Migration & backfill
How it runs
Four weeks, in order.
Week 1
Scope
A day in the shop watching how selling actually happens, your exact hardware models confirmed, and a written specification you sign off. No code until then.
Week 2
Build
The core selling flow and the inventory model, running on the real terminal with a real printer attached. Friday demo you can ring a sale on.
Week 3
Build
Payments, offline queueing, the storefront link and reconciliation. Second Friday demo, including pulling the network cable to prove offline works.
Week 4
Ship
Pilot site live with the old process still available, staff training, then rollout to the remaining locations once the pilot is quiet.
What you get, concretely
- POS software running on your confirmed hardware
- One inventory record shared by counter and storefront
- Offline trading with queued sync and conflict reporting
- Daily reconciliation across till, processor and ledger
- Per-site configuration and staged update rollout
- Staff training at the pilot location, recorded
- 30 days of post-launch fixes at no additional cost
Typical engagement
Fixed price · four to six weeks
Number of locations and how much peripheral hardware is involved move the figure more than anything else. A single till with a printer is a small job; six sites with scales, label printers and an existing storefront sits near the top.
Technology
What we build it with.
Defaults, not requirements. If you already run something else and have a team who knows it, we work in yours.
- Devices
- Android & iOS terminals, Star and Epson printers, Zebra scanners
- Payments
- Stripe Terminal, Square, certified card readers
- Local data
- SQLite, local-first sync, queued operations
- Commerce
- Shopify, WooCommerce, custom storefronts
Proof
We have built this before.
Not a reference we cannot name. Systems we designed, shipped and still operate, with the decisions written down.
Questions
What people ask before signing.
- Do we have to buy new hardware?
- Usually not. Most current terminals, printers and scanners are supported. We confirm your exact models in week one, before anybody commits to buying anything.
- What actually happens in an outage?
- Trading continues. Sales are written locally and queued, then sync when the connection returns, with reconciliation reporting anything that conflicted while you were offline.
- Can we keep our existing online store?
- Yes. Integrating with a Shopify or WooCommerce store you already run is common and usually cheaper than replacing it.
- Who handles payment certification?
- We build against certified readers from the processor, which keeps the certification burden with them rather than with you. That is deliberate and much the cheaper path.
- How do you roll out to several sites?
- One pilot location first, running long enough to be boring, then staged rollout. A bad update across an entire fleet at once makes for a very long day.
- What about card data?
- It never reaches your servers. Tokenisation and certified readers keep you in the simplest compliance category, and your acquirer confirms the specifics.
Related reading
Written on this, by us.
Data & Integration · 6 min read
Idempotency: The One Word That Stops You Charging Someone Twice
The most common serious bug in payment code is not fraud or a failed gateway. It is a retry that creates a second charge, and it is entirely preventable.
Engineering · 7 min read
Offline-First Is Not a Feature, It Is a Decision You Make on Day One
Software used in a stockroom, a basement or behind a fridge will lose its connection. Retrofitting offline support is one of the most expensive changes in mobile development.
Data & Integration · 8 min read
What POS Integration Actually Costs a Multi-Location Restaurant
Online ordering that doesn't talk to your POS costs you ninety minutes a night and a food cost number you can't trust. Here's what the integration involves and what it's worth.
Tell us what you sell, and where.
How many locations, what hardware is on the counter, and what you sell online. We confirm your exact models before anything is quoted.
Phone
+1 (407) 796-2376Reply time
One business day, from an engineer
Based in
Orlando, Florida · serving the United States
What happens next
- A reply within one business day, from an engineer
- A thirty-minute call, with no qualifying call before it
- A written scope and a fixed number, if it fits