--- title: "Offline sync to Business Central — mCommerce365" description: "How field orders survive no-signal zones and post automatically when connectivity returns." lang: "en" canonical: "https://mcommerce365.com/integrations/offline-sync/" alternateMarkdown: "https://mcommerce365.com/integrations/offline-sync/page.md" lastModified: "2026-08-18" --- # Offline sync A device queue, not a warehouse replica. Status stays visible: in progress, waiting to sync, posted. ## Takeaways - Automatic send on reconnect - Encrypted store on the handset - Managers see backlog instead of guessing ## Sync is a posting problem We are not merging two master-data worlds. The happy path is: capture the order, park it if needed, post it to BC. Edge cases belong in the demo with your ERP owner. ## A queue against live Business Central Offline should not invent a warehouse you reconcile in Excel. The device stores the encrypted document, shows a clear state, and posts automatically on reconnect. Building-materials sites and agriculture routes are the usual stress tests. Paper is also 'offline' — teams already sell without signal; they just pay later in credit notes. A device queue is the same behaviour with an audit trail. - Automatic send on reconnect — no evening inbox of notebook photos - Encrypted store on the handset - Visible backlog for managers ## What managers should see while the van is still out A queue nobody can see becomes a rumour. In-progress, waiting to sync, posted — those states are how you coach a fleet instead of guessing who still has paper in the glovebox. Building-materials basements and rural agriculture are the usual places we walk this in the demo. We will not invent an uptime percentage for a telecom SLA you do not own. ## What a useful demo needs from you We walk a flow that looks like yours — not a generic grocery catalogue. Twenty minutes is enough if the brief is honest. Sales replies from app@icitech.com.tr. - Which Business Central deployment you run (cloud / on-prem) and who owns it - How many field representatives and whether they already carry iOS or Android - Must-have document types: order, quote, return — we confirm against your company setup - One painful route: basement, industrial park, rural site, or a counter that cannot wait ## Limits we state on purpose mCommerce365 is a B2B field sales surface on top of Business Central. It is not a consumer storefront, an iPaaS, or a second ERP. Named customer logos stay unpublished unless the customer has approved them. We do not invent visit counts or league-table rankings on this site. - Operator: ICI Tech Teknoloji A.Ş. Sales mailbox: app@icitech.com.tr. - Microsoft, Dynamics 365 and Business Central are trademarks of Microsoft Corporation. Reference does not imply endorsement. - Anonymous role-attributed notes live under References. They are not a promise that your route will move by the same percentage. ## Questions buyers ask ### How large can the queue grow? Depends on device and document mix. We size it against your route reality in implementation, not a generic cap on this page. ### What should we bring to the demo? Your Business Central deployment (cloud / on-prem), must-have document types, one painful route, and a named ERP owner. We walk a flow that looks like yours — twenty minutes from app@icitech.com.tr. ### Do you support ERPs other than Business Central? No. mCommerce365 is built as a native Dynamics 365 Business Central extension. If you do not run BC, this product is the wrong fit — we say that so you do not waste a demo. ### Is one week a contractual SLA? It is the typical path when Business Central is healthy and the scope is field order capture. Unclean items, missing owners, or a company still being redesigned add days. We scope that before kickoff — it is not printed as a guarantee on this website. ### What happens when there is no signal? The representative keeps capturing the order. The document stays on the device with a visible 'to be synchronised' state and posts to Business Central when the van hits coverage. There is no evening re-keying and no parallel warehouse database. ## Product facts - **ERP:** Dynamics 365 Business Central only. Not SAP, Logo, Netsis, or a second mobile database. - **Offline:** Orders continue with no signal. The device queues the document and posts it to Business Central when coverage returns. - **Go-live:** Typical path is about a week: install the extension, check master data, test, train. Dirty items stretch the calendar — we say that on the first call. - **Clients:** iOS and Android phones and tablets. Role screens, not a desktop website pinched onto glass. Five languages on this site: EN, TR, DE, FR, ES. ## Related pages - [Integrations](https://mcommerce365.com/integrations/) - [Microsoft Dynamics 365 Business Central](https://mcommerce365.com/integrations/dynamics-365-business-central/) - [No middleware architecture](https://mcommerce365.com/integrations/no-middleware/) - [iOS and Android](https://mcommerce365.com/integrations/ios-android/) [Book a 20-minute demo](https://mcommerce365.com/contact/)