Custom software · POS systems

Custom POS software development for supermarkets and retail stores

Spatial Map is browser-based indoor mapping and 3D digital twin software, and it has no point-of-sale module. When a retailer needs a till, our team does custom POS software development as a client project: a checkout built around your products, barcode and RFID scanning, inventory sync, several branches and offline selling, with sales and stock shown on a live map of the store if you want that. It is never a ready-made product.

Spatial Map: no credit card for the trial, runs in the browser, Pro is $60/month for up to 4 facilities. Explore the live demo

Illustrations of device types — not vendor product photos.

Works with hardware from

Zebra, Chainway, SATO and Sanray are trademarks of their respective owners. Spatial Map is not affiliated with or endorsed by them; we integrate devices our clients own — or source for a project through normal channels — using the vendors’ SDKs and APIs.

What a custom POS usually includes

Every retailer’s counter works a little differently, so the scope is agreed per project. Most POS builds are made of the same parts:

  • Checkout screen — scan, change quantity, weigh loose items on a connected scale, hold and recall a basket, returns and voids behind the right permissions.
  • Barcode and RFID checkout — barcode scanners for untagged items; an RFID reader at the counter can read a whole basket of tagged items in one go, with the cashier confirming anything that does not match.
  • Prices and promotions — price lists per branch, discounts, bundles and multi-buy offers, entered as rules your own team maintains.
  • Payments — cash, split tenders and card terminals. The terminal takes the card; the POS talks to it through the terminal vendor’s SDK or your payment provider’s API and receives only the result.
  • Receipts, printers and drawers — receipt printers, cash drawers, customer displays and label printers connected through their documented interfaces.
  • Shifts and roles — cashier sign-in, shift open and close, cash-up, supervisor overrides and an audit trail of who did what.

Inventory sync, many branches, offline mode

A till is only useful if its numbers match the shelf. The POS is designed together with the stock side: each sale reduces stock for that branch, and receiving, transfers and RFID counts feed it back. Which system is the system of record — the POS, or your ERP or WMS — is decided in discovery, and the sync is built to match.

  • Multi-branch — one central catalogue, branch-specific prices and stock, transfers between branches, and head-office reports across all of them.
  • Offline mode — each till keeps the catalogue and prices on the device and keeps selling when the network drops. Sales queue locally, carry a unique sale ID so they cannot be posted twice, and upload when the connection returns.
  • What offline cannot do — some payment methods and gift-card checks need a live connection. The design decides what the till does then, and the cashier sees a clear message instead of a stuck screen.

Tax, receipts and e-invoicing: built to your local rules

Tax rates, rounding, receipt content, fiscal printers and e-invoicing submission differ from country to country, and they change. We build to the requirements you give us for your country and your business — typically the tax authority’s published specification and what your accountant confirms — and we keep those rules in configuration so they can change without a rebuild.

We make no compliance claim. Where your country requires approved software or a fiscal device, that has to be assessed against the rules there; we integrate the device or service you are required to use, and we do not certify anything on your behalf.

How we build it

A POS touches money and queues, so the project is staged and tested on real counters before it goes live:

  • Discovery — a walk through your checkout, returns, promotions and end-of-day process, the devices you own, and the systems the POS must talk to.
  • Design — cashier screens, roles, data model and integrations agreed on paper and in clickable mock-ups before code.
  • Build — the checkout, back office and sync service, built in stages so you can try each one.
  • Integrate — scanners, RFID readers, printers, payment terminals, your ERP or accounting system and, optionally, Spatial Map.
  • Hand-over — a pilot at one branch, training for cashiers and managers, documentation, and a support arrangement agreed in the proposal.

Connecting the POS to a live store map

The POS stays the system of record. It sends summary rows to Spatial Map through the table write API — HTTPS, a bearer key, bulk upsert, 60 requests a minute per key, so the service batches rows rather than sending every scan. If your POS already exposes an endpoint, REST polling is the other route.

  • Sales by department — value badges or coloured areas on the floor plan, updated through the day.
  • Till status — online or offline, open lanes and queue length as markers at each lane.
  • Shelf stock — zones that run low, from POS sales combined with counts, as coloured areas.
  • Loss prevention — exit-reader events next to sales, as in the Retail Mart demo and the anti-theft solution.

Hosting and what you own

Cloud or on-premises. The POS back end can run in your cloud account, in ours, or on a server in the store or head office; tills keep working locally either way. On the map side you can use the hosted Spatial Map app or, for a self-hosted setup, the open-source edition. See deployment options for the map itself.

Ownership is written into the proposal. The usual position is that you own the source code written for you, your data and the cloud accounts it runs in, with third-party components staying under their own licences. A Spatial Map subscription, if you use one, is separate.

Devices a POS project connects

Illustrations of device types, not vendor product photos. Hardware you own is reused; on request we can also source it, quoted per project — see hardware.

  • Barcode scanners and mobile computers

    Counter scanners and handheld units for price checks, queue busting and receiving.

  • RFID readers at the counter

    Read every tagged item in a basket at once for faster checkout.

  • Label and receipt printers

    Receipts, shelf labels and RFID labels, driven through the printer’s command language.

How it connects

How the pieces fit together

  1. 01

    Counter devices

    Scanners, RFID readers, scales, printers and card terminals.

  2. 02

    POS app

    Checkout, offline queue, shifts and roles on the till.

  3. 03

    Branch and head office

    Catalogue, prices, stock, transfers and reports across branches.

  4. 04

    ERP / accounting

    Item master and prices in; sales and stock movements out.

  5. 05

    Spatial Map

    Summary rows through the table write API → live store map and reports.

Custom POS development — frequently asked questions

No. Spatial Map is indoor mapping software and has no point-of-sale module. A POS is a custom project we build for one client, designed around that client’s products, devices and branches.

Yes. Barcodes cover untagged items and RFID reads tagged items in bulk. The cashier sees one basket and resolves any mismatch before payment. The RFID side needs readers at the counter — see hardware.

Tills keep selling from the catalogue and prices stored on the device, and queue each sale with a unique ID. When the connection returns, sales upload without duplicates. Payment methods that need a live approval behave as the card terminal and provider allow.

We build to the requirements you give us and keep tax rules in configuration, but we make no compliance claim. Where approved software or a fiscal device is required, you confirm that against local rules and we integrate what you are required to use.

Any device whose vendor publishes an SDK or documented interface. We confirm each one in the proposal after reading its documentation.

No. The map is optional; most clients add it because sales, queues and stock are easier to read on a floor plan. Tell us the workflow and we will say plainly whether the map belongs in it.

Scoped and quoted per project, from a written proposal with milestones, after we have seen your checkout process and systems. We do not quote before that.

Describe your checkout. We’ll scope the system around it.

Tell us your branches, the devices at the counter, the systems the POS must talk to and your country’s tax setup. We will reply with a scoped proposal — and a live map of your store if you want one.