CStoreNexus › How it works

How it works

The register writes files. We read them.

No API, no new hardware, nothing typed in. Here is the path a sale takes from the counter to your screen, and the rules that keep every number honest.

From the register to you

Four steps, every minute of the day.

Passport and Commander have no database to connect to — they write XML to a share on the store PC. A small agent on that PC watches the share, uploads what arrives, and never deletes a thing, so the store keeps its own backup.

Register Passport · Commander Collector the store PC Cloud built · every 20 min You web · phone every 1 min every 5 min live RegisterPassport · Commander Collectorthe store PC Cloudbuilt · every 20 min Youweb · phone every 1 min every 5 min live

Two kinds of file

Journals arrive in minutes. Day-close files are the record.

Journals (PJR)

Arrive within minutes and carry every transaction with its time. They feed Live Sales and Hourly Sales — the day in progress.

PJR_10001_20260913_163812.xml
Movement files

MSM, MCM, FGM and ISM arrive at day close and carry the register's authoritative totals. They build the shift report.

MSM · MCM · FGM · ISM
Never mixed up

They never agree to the penny, and every page says which one it used — and the date its data runs through.

data through Sep 13, 2026
Passport and CommanderRead through the XMLGateway share each register already exposes. A site that only hands over a journal is read from that.
Every day rolls at store closeNot at midnight. The day boundary is read from the file every time — the previous close, else the first sale.
Fuel prepay counted onceA prepaid fill's completion restates the whole sale. The original is dropped whole, basket included, so nothing is double counted.
Nothing is deletedThe files on the store PC stay put. Snapshots are kept before any rebuild, and you can see when each station last sent a file.
The operator's rule

Nothing counts until a person accepts it.

A shift is invisible to every report until it is accepted. An invoice's costs do not touch a margin until it is accepted. A price change is not on the register until the register's own acknowledgement says so.

ShiftsAccepted on the business date the register stamped — re-dating is a separate, deliberate step, never a side effect.
InvoicesRead, matched and gated by the invoice's own arithmetic; costs and margins move only when you accept.
RegistersA price change is written in the register's format and queued. Only the register's ACK counts as “on the till”.
Try accepting a shift report →
Honest by design

A confident number you cannot trace is worse than a dash.

Empty is honest

A station that sent nothing today says nothing received — never $0. A report with no accepted days says so instead of drawing a zero.

no journal for last Sunday to compare
Every page names its source

Journals or day-close files, and the date the data runs through. A Passport writes about 85% of inside sales to its journal, so the live figure is labelled the day in progress, and the shift report is the record.

data through Sep 13, 2026
Each location keeps its boundary

Cost, retail, margin and inventory are per store. An account dashboard adds the stores up; it never blurs them. Adding a store needs zero setup in the software.

one product ≠ one price

See it on your own stores.

Thirty minutes over a screen share, on one of your stores. $249 a store, month to month.

Book a walkthrough →Pricing