Offline Mobile App for Business Central

Your team keeps working — even without signal. Dynamics Mobile is built offline-first for Business Central: every action queued locally, synced to BC automatically when connectivity returns.

Full offline operation — scan, pick, deliver, sell without a data connection
Automatic background sync when connectivity returns — no manual retry
Deterministic conflict resolution — no double-posting or lost records
Works in warehouses, basements, rural routes, and dead zones
Native BC data — no third-party sync platform to maintain

Why Offline Matters for Business Central Mobile Users

An offline mobile app for Business Central is a mobile application that can execute warehouse, field, and delivery workflows without an active internet connection, storing all changes locally and synchronising to Business Central automatically when connectivity is restored. Without offline capability, a lost signal means a frozen screen, a lost transaction, or a driver who cannot complete a delivery — all of which have direct operational and financial consequences.

Dynamics Mobile is designed offline-first. It does not degrade to a read-only mode when offline. Your warehouse operative can pick 500 lines, a driver can complete 20 deliveries, and a field rep can raise 10 orders — all without a single data bar — and every record will be in Business Central before the end of their shift.

How Offline Sync Works

When Dynamics Mobile loses connectivity, the following happens automatically:

  1. Local queue — Every transaction (pick line, delivery confirmation, order, stock count) is written to an encrypted on-device queue in real time.

  2. Background reconnect detection — The app monitors network availability in the background. No user action is required to trigger a sync.

  3. Ordered sync — When connectivity returns, the queue is replayed to Business Central in the exact order the transactions occurred, preserving business logic (e.g., stock reservations are applied in sequence).

  4. Conflict resolution — If a BC record changed while the device was offline (e.g., a pick line was cancelled by the back office), configurable rules determine which version wins. Standard rules: field operations win during active routes; back-office wins for master data.

  5. Confirmation — Once sync completes, the user sees a sync status indicator. Any conflicts are surfaced as actionable notifications, not silent overwrites.

Offline Workflows Supported

  • Warehouse picking and put-away — Complete pick waves offline. Bin movements are queued and applied to BC in sequence when the device reconnects.

  • Stock counting — Count entire zones offline. Submit counts to BC in one batch — no connectivity required mid-count.

  • DSD route delivery — Load van stock in the morning, deliver all stops offline, settle the route at the end of the day. BC is updated with a single sync when the driver returns to depot range.

  • Van sales — Create cash sales, capture payments, and issue invoices offline. Inventory adjustments sync back to BC on return.

  • Field sales orders — Raise orders offline at customer premises. Orders land in BC as soon as the rep steps outside into coverage.

  • Proof of delivery — Capture signatures and photos offline. All POD data — including GPS — synced to BC sales shipments on reconnect.

Security of Offline Data

All data stored locally during offline operation is encrypted at rest using AES-256 on the device. Offline data caches are scoped to the authenticated user's Business Central environment — no data is accessible to other app users or visible outside the app. Remote wipe is supported: if a device is lost, the BC administrator can invalidate the user's session and purge the local cache on next sync attempt.

What About Large Data Sets?

Dynamics Mobile uses selective synchronisation — only the data needed for the current user's workflows (their pick wave, their route, their customer list) is downloaded to the device. Full BC catalogs are not stored locally. This keeps device storage requirements low (typically 50–200 MB depending on catalogue size) and initial sync times under 60 seconds on most LTE connections.

Frequently Asked Questions

What is an offline-first mobile app for Business Central?

An offline-first app is designed to work without internet connectivity as its primary mode of operation — not as a fallback. Dynamics Mobile stores all active workflow data on the device at the start of a shift and writes all transactions locally. Sync to Business Central happens in the background and does not block any user action.

How long can a device operate offline?

There is no fixed time limit. A device can operate offline for an entire shift (8–12 hours) without any issue. Data is queued indefinitely until connectivity is available. The only limitation is device storage — in practice, a shift's worth of transactions is typically under 5 MB.

What happens if the device battery dies before sync completes?

The local queue is written to persistent storage, not held in memory. If the device is powered off before sync completes, the queue is preserved. On the next app launch with connectivity, sync resumes from where it left off.

Can two users pick from the same bin offline simultaneously?

Yes — this is a common scenario in busy warehouses. Dynamics Mobile uses BC's reservation system to assign pick lines to specific users at the start of a wave, preventing two pickers from being directed to the same item. When both sync, BC processes their picks in order without conflict.

Is offline mode available on all device types?

Yes. Offline operation is available on all supported platforms: iOS (iPhone and iPad), Android smartphones and tablets, and ruggedised Android handhelds (Zebra, Honeywell, Datalogic). The offline behaviour is identical across all device types.

How does Dynamics Mobile handle offline differently from the standard BC mobile app?

The standard Business Central mobile app is a web-based interface — it requires a live connection to the BC service and does not queue transactions locally. Dynamics Mobile's offline capability is a native architectural feature, not a browser cache. It is designed for industrial use cases where connectivity gaps are expected, not exceptional.