Every register.
Every store.
One operating picture.
StorePad connects straight to your POS. Sales, the price book, departments and lottery flow up to the cloud every day — and approved changes flow back to the register in seconds. Reconciled to the cent.
- ✓ Direct Verifone Commander integration
- ✓ Two-way sync, human-approved
- ✓ Multi-store from day one
Net sales
$8,412.36+4.2% vs FriInside merchandise
$5,120.90+2.8%Fuel
$3,291.461,046 galCustomers
612−1.1%- Tobacco31%
- Beer & wine18%
- Grocery14%
- Lottery12%
- Fountain & coffee9%
- Other16%
- 3 Pending to POS staged, awaiting release
- 2 Changed at other stores Riverside · Hilltop
- ● Store agent heartbeat 20 s ago
- Price released · Marlboro Gold 20s → $9.49applied at register · 2.4 s
- PO-118 received · Core-Mark24 cases posted to Inv.
- Lottery count posted · 14 binsvariance $0.00
- Audit posted · Beer cave212 items counted
The platform
Structured exactly like the app.
24 modules, four groups, one sign-in.
These are the app's own module names and descriptions. What you see here is what your team opens tomorrow morning — nothing aspirational, nothing hidden behind a roadmap.
Every closed day and the open one, straight from the register.
For Owners & managers
- OverviewToday's sales, traffic & what needs attention
- LiveThe open business day, straight from the register
- Sales HistoryClosed days, day detail & product history
- Vendor SalesProduct sales by vendor, daily to monthly
- ReportsSales reports by period
- AnalyticsSales trends & price analytics
- TransactionsTransaction journal, live from the POS
- End of DayThe day's totals receipt
- FuelFuel prices, live from the POS
- TaxTax rates, live from the POS
How it works
From the register to your phone
— and back, on your say-so.
Most retail dashboards stop at reading exports. StorePad is wired to the register in both directions, with a human standing between the two.
- 01
Verifone Commander
The register
Nothing is installed on the POS itself. StorePad reads the price book, day reports, department configuration, fuel and tax exactly as the register publishes them.
- 02
On the store PC
The store agent
A small, self-updating agent runs on the PC that already sits in the back office. It collects nightly, streams the open day every few minutes, and applies released changes within seconds.
- 03
Per store, in the cloud
StorePad Cloud
Every store is its own scope. The same numbers feed dashboards, reports, purchasing, audits and lottery — there is one definition of net sales, not five.
- 04
Anywhere, any device
Your team
Owners, managers, staff and label printers each see the modules their role allows. Changes queue up as Pending to POS and go to the register only when a manager releases them.
Send to POS
Two-way with the register.
Never without a human.
Reading from a POS is table stakes. Writing to one is where most tools stop, because a wrong price on a live register costs real money. StorePad writes back — with a discipline built for that risk.
- Staged, released, applied — three states, one buttonEvery edit to a register field lands in Pending to POS as a staged row. A manager reviews the list and presses Send to POS. The agent applies the released rows and acknowledges each one back.
- Read-modify-write, one field at a timeThe agent echoes the register’s own record and changes exactly the intended field. Every write format was proven field-by-field on a live register before it shipped.
- Prices, departments, EBT flags, names, tax ratesOne change row carries every field you touched on an item. Department EBT eligibility is written the same careful way.
- You can always see the agentA heartbeat on every screen shows when the store agent last checked in — so a released change never quietly waits on a machine that is off.
| Item | Field | Change | Status |
|---|---|---|---|
| Marlboro Gold 20s | Price | $9.19 → $9.49 | applied |
| Red Bull 12oz | Price | $3.29 → $3.49 | sending |
| Monster Zero 16oz | Department | Grocery → Beverages | pending |
| Dept 12 · Snacks | EBT eligible | off → on | pending |
| Bud Light 12pk | Item name | “BL 12PK” → “Bud Light 12pk” | pending |
- 1 staged edited in the portal
- 2 released a manager pressed Send to POS
- 3 applied the agent wrote it and acknowledged
Multi-store
Built for the operator with a handful of stores
— and the platform running three hundred.
An item is the same item at every store only when it carries a genuine GTIN; a department is matched by name, never by the register’s internal number. Those rules are what make cross-store features safe.
| Item | Northgate | Riverside | Hilltop |
|---|---|---|---|
| Marlboro Gold 20s | $9.49 | $9.49 | $9.49 |
| Red Bull 12oz | $3.49 | $3.29 | $3.49 |
| Coke 20oz | $2.39 | $2.39 | $2.49 |
| Bud Light 12pk | $13.99 | $13.99 | $13.99 |
| Lays Classic 8oz | $4.99 | $4.79 | $4.99 |
- Compare stores
A parity report across every store you own. Same item, three prices? You see it in one row — and can look up any item or group across the network.
- Import from store
Copy groups, long item names and vendors from one store to another, or from “all stores together”. Prices and costs never cross unless you tick the box.
- Changed at other stores
When Riverside changes a price, Northgate’s manager sees it — and can Dismiss or Apply here. Applied changes still go through Pending to POS.
Daily operations
Not a dashboard on top of the store.
The store’s actual work.
The price book, as a grid
Every item on the register in one editable sheet. Tick rows, edit cells inline, or fill just the fields you want changed across a selection. Costs are dated — a cost change knows which days it reaches.
- Bulk edit
- Multi-fill
- Dated costs
- Inv. = stock in − sold
Purchase orders from the vendor’s own count sheet
Pick a vendor, count cases and loose units against their items, submit. Receiving checks the delivery in and posts units to inventory. A PO never touches the register.
- Vendor count sheet
- Cases + loose units
- Receive with variance
Guided physical counts
Scope a count by group, vendor or department. The sheet snapshots what the system expects; you count; posting corrects inventory for counted lines only.
- Snapshot vs counted
- Post to Inv.
- Never the register
Lottery that reconciles itself
A daily bin count with sold = end − start per pack, checked against the register’s own instant, online and payout figures. The difference is stored, not overwritten.
- Pack lifecycle
- Bin count
- Register reconciliation
- Ticket barcodes
Shelf tags over Bluetooth
Scan or search, queue tags, print straight from the browser to a Bluetooth label printer. Label-only staff get this page and nothing else — and print the same tag a manager would.
- Scan to queue
- Label presets
- Labeler role
The open day, live
Net sales so far, hourly transactions and fuel — streamed from the register every few minutes. Fuel prices, tax rates and Mix & Match promotions are read straight from the POS too.
- Live snapshot
- Fuel & tax
- Promotions
- End-of-day receipt
Accuracy & access
Software that can change a live register
has to earn it.
Reconciled to the cent
Every register-sourced number is checked against the POS day report line by line. Exact match is the bar; where lottery or cash accountability legitimately differ, the reconciliation says why.
Scoped to one store, always
Every request resolves to exactly one store, never by guessing. A user reaches only the stores they were granted — and nothing from another business, ever.
Human-gated writes
Send to POS is the only path to the register, and it is a person pressing a button. It cannot be automated or delegated to a role.
Access down to the module
Each person sees the modules their role allows and nothing more — the sidebar, the home screen and the data all agree. Label-only staff get the tag printer and no other page.
Revocable sessions
Sessions are records, not just cookies — they can be revoked. Store agents authenticate with an agent token, never with a user’s session.
A change log across stores
Register diffs, portal edits, imports and applied changes are recorded with their source. What changed, where, and who released it is always answerable.
Questions
Straight answers
before we connect anything.
Does StorePad replace our POS?
No. StorePad connects to the register you already run and works alongside it. Your cashiers keep ringing sales exactly as they do today; StorePad reads what the register publishes and, when a manager releases a change, writes that one change back.
Which registers does it connect to?
StorePad is built on a direct integration with the Verifone Commander, the controller behind most convenience and fuel registers. If you run something else, tell us what — the collection and write-back layer is designed to be extended.
Can it change prices on the register?
Yes — prices, departments, EBT eligibility, item names and tax rates. Every change is staged first and reaches the register only when a manager presses Send to POS. The agent then confirms each applied change back to the portal.
What does setup involve?
We set up your stores, you run a small agent on each store’s back-office PC, and it starts reporting on its next cycle. The agent keeps itself up to date; nothing is installed on the register.
How do you know the numbers are right?
Because we check. Register-sourced totals are reconciled line by line against the POS day report, and the reconciliation documents are part of how StorePad is built. Exact match is the standard.
We have several stores. Are they kept separate?
Yes. Each store is its own scope, and your business’s data is never visible to anyone else. Cross-store features — comparing prices, importing groups, alerts about changes elsewhere — work only across your own stores, and prices never cross stores unless you ask.
Does it work on a phone?
Yes, in the browser — the whole portal is responsive and used on phones on the shop floor today. A dedicated Android app is in development.
See StorePad running on a live store.
A demo is a live store’s numbers on screen — not a slide deck. Tell us how many stores and which POS, and we take it from there.
or write to hello@storepad.net