How to sync online and offline inventory without losing a scan. How offline-first apps store, queue and sync field transactions, how conflicts resolve, and what to demand from a vendor. Field locations are offline by default: plan for it.
The signal dies exactly where the stock is
Walk the places where field inventory actually lives. Hospital basements. Plant rooms behind two fire doors. Metal-clad warehouses that swallow every bar of 4G. Remote substations. Motorway lay-bys where an engineer counts trunk stock between jobs. None of these locations care about your network plan. Most of them are offline by default.
That is the problem with most inventory software. It assumes a connection. The app that demos perfectly in a boardroom freezes in a basement. So the question teams end up asking is simple: how do you sync online and offline inventory without losing a single scan? This piece answers it in plain words. How offline-first apps like Ventory store, queue and sync every movement. How conflicts get resolved. And what to demand from any vendor before you sign. If offline work is your daily reality, start with the working offline use case.
Why offline capability decides your inventory accuracy
Coverage maps flatter reality. Per Ofcom's Connected Nations 2024 report, 4G coverage from at least one operator reaches 95% of UK landmass. That leaves 5% of the country with no signal from any network at all. And the figure is measured outdoors. Step inside a concrete stairwell, a server room or a steel warehouse and coverage drops again. Hospitals add another layer: guest wifi is restricted, locked down or simply forbidden for third-party devices.
Now map that against where stock sits. Engineer vans. Forward stocking locations. Consigned implants in hospital storerooms. Loaner kits in transit. The inventory that matters most lives in the worst-connected places you operate.
An online-only app fails there in a predictable sequence. The scan hangs. The technician waits, then gives up. Counts move to paper or memory. Someone retypes the paper into the ERP two days later, or never does. Every skipped scan becomes a phantom record: the system says five units, the shelf holds three. Phantom records drive emergency shipments, failed jobs and write-offs. Ventory was built around the opposite assumption: no signal is normal, and real-time tracking means real-time on the device, synced the moment a connection returns.
How to sync online and offline inventory: the mechanics
Offline-first is an architecture, not a feature toggle. Four parts do the work.
- A local store on the device. The app keeps its own database on the phone or scanner: the catalogue, locations, stock levels, open tasks. Every scan writes to that local store first. The device never asks the network for permission to record a movement.
- A queue for every transaction. Each scan, count, pick or transfer becomes a timestamped record in an outbound queue. Scan 40 items in a basement and the queue holds 40 entries, in order, stored on the device until delivery is confirmed.
- Sync when signal returns. The moment the device sees a connection, even a weak one, the queue uploads in the background. The user does nothing. No sync button, no export, no retyping. Transactions arrive at the server in the order they happened.
- A referee for conflicts. Two people can touch the same stock while both are offline. On reconnect, the server compares timestamps, applies the transactions in sequence and recalculates the balance. Because each record is a movement (take 2, add 5), not an overwrite of a total, most "conflicts" resolve themselves as simple arithmetic. True clashes, like two users claiming the last unit, get flagged for review instead of silently dropped.
One more layer matters in an enterprise stack: the system of record. Your ERP stays the referee of financial truth. The field inventory layer validates and sequences field transactions, then posts clean, deduplicated movements to SAP, Oracle, Dynamics or NetSuite. The ERP never sees the mess of reconnection. It sees an ordered ledger. That separation is what lets barcode scanning in the field stay fast while the back office stays consistent.
Online-only vs offline-first: what to demand from a vendor
Many vendors say "works offline" and mean "caches a product list". That is not the same thing. The difference shows up in five situations you will hit in week one.
| Situation | Online-only app | Offline-first app |
|---|---|---|
| Basement or plant room | First scan hangs; team reverts to paper | Every scan saves locally; the count continues |
| Remote site with no coverage | No counting possible on site | Full stock take on the device; uploads on the drive home |
| Hospital with restricted wifi | Stalls against network policy; data gaps | No connection needed during the count |
| Sync after reconnect | Someone retypes paper notes into the ERP | Queued scans upload automatically, in order |
| Risk of lost scans | High: anything unsent is gone | Near zero: every transaction stored until the server confirms |
In a basement or plant room, an online-only app hangs on the first scan and pushes the team back to paper. An offline-first app saves every scan locally and the count continues. On a remote site with no coverage, online-only means no counting at all; offline-first means a full stock take that uploads on the drive home. In a hospital with restricted wifi, online-only apps stall against network policy, while an offline-first app needs no connection during the count. After reconnect, online-only workflows depend on someone retyping paper notes; offline-first queues upload automatically and in order. And the risk of lost scans: high for online-only, because anything unsent when the app closes is gone; near zero for offline-first, because every transaction is stored until the server confirms it.
So put these questions in your RFP, verbatim:
- Can a user complete a full count, pick and transfer with the radio off? Ask for a demo in airplane mode, not a slide.
- Where does an unsent scan live, and for how long? The answer should be: on the device, encrypted, until delivery is confirmed.
- How are conflicting offline edits resolved? You want timestamps, transaction ordering and a flagged exception list, not "last write wins".
- What does the ERP receive after a messy reconnect? One ordered, deduplicated ledger of movements.
- How many days can a device stay offline before data ages out? Days, not hours.
This is the standard Ventory holds itself to as the field inventory layer between your ERP and your field teams. Offline is not an edge case in the product. It is the default state it was designed for.
The proof: counted offline, accurate everywhere
A national ambulance service runs consumable stock across a 100-vehicle fleet. Crews count between calls, often in parking bays and station basements with no usable signal. Every scan lands in the local store, queues, and syncs when the vehicle is back in coverage. The result: 99.76% rolling stock accuracy across the fleet, with field adoption above 95%, because the app never blocks a crew mid-count.
The pattern repeats beyond ambulances. Across 450+ field locations, teams using an offline-first layer report up to 70% fewer stockouts and 35% less excess stock, because the numbers in the system finally match the shelf. Accuracy is not a reporting exercise. It is what happens when no scan is ever lost to a dead zone.
Getting started
- Map your dead zones. List the locations where staff already complain about signal: basements, plant rooms, remote sites, vehicles. These are your first candidates.
- Test in airplane mode. Take your current app to the worst location on the list and try a full count with the radio off. Record what breaks.
- Start a focused first scope at 3-5 locations. Pick the sites with the weakest coverage, not the easiest ones. If the system holds there, it holds anywhere.
- Connect the ERP once. Field devices sync to the field inventory layer; the layer posts clean movements to the ERP. One integration, not one per site.
- Go live and measure. Deployment runs 4-8 weeks. Track scan completion, sync failures and stock accuracy from day one.
See your own dead zones fixed: book a demo.
Field notes
- 5% of UK landmass has no 4G from any operator, and the Ofcom figure is outdoors only: plan for offline, not around it.
- 99.76% stock accuracy on a 100-vehicle ambulance fleet was counted largely offline, in basements and bays.
- Teams that stop losing scans report up to 70% fewer stockouts, because the system finally matches the shelf.
Frequently asked questions
How do you sync online and offline inventory?
Each device keeps a local database and writes every scan to it first. Transactions queue on the device as timestamped records and upload automatically when a connection returns. The server applies them in order, resolves conflicts, and posts one clean ledger of movements to the ERP. Users never press a sync button.
Can inventory apps work without internet?
Yes, if they are built offline-first. The full workflow, scanning, counting, picking and transfers, runs against the local store on the device, so no internet is needed during the work itself. A connection is only required later, to sync. Apps that merely cache a product list are not offline-capable in any useful sense.
What happens if two people edit the same stock while offline?
On reconnect, the server acts as referee. It orders both users' transactions by timestamp and applies them in sequence. Because records are movements rather than overwritten totals, most overlaps resolve as simple arithmetic. A genuine clash, like both users taking the last unit, is flagged for a person to review instead of being silently overwritten.
How long can a device stay offline?
Days or weeks, not hours. Queued transactions stay encrypted on the device until the server confirms delivery. Practical limits come from device storage and your own data-freshness policies, not from the architecture. Ask vendors for a specific retention figure during evaluation.
Does offline inventory data still reach the ERP?
Yes. The field inventory layer validates and sequences synced transactions, then posts deduplicated movements to the ERP as the system of record. SAP, Oracle, Dynamics, Sage and NetSuite all receive the same ordered ledger, whether the scans happened online or three days offline.
About Ventory
Ventory is the field inventory layer for regulated, high-stakes industries. We give MedTech, 3PL, Aerospace, Energy and FMCG leaders real-time visibility and control over inventory outside the four walls, in hospitals, ambulances, trunk stock, consignment locations, and field service vans. Ventory is ERP-agnostic (SAP, Oracle, Dynamics, Sage, NetSuite) and trusted by a global medtech manufacturer, a national ambulance service, global logistics and consumer-goods operators. See how it works →
Ten questions. You get a field readiness score, a gap tier and the three fixes worth doing first.
Ventory is the field inventory layer between your ERP or WMS and the teams working outside the warehouse: engineer vans, forward stocking locations, consigned stock and loaner kits.
About Ventory
