--- title: "Field order lifecycle to Business Central — mCommerce365" description: "Follow every field order from tap to posted Dynamics 365 Business Central document — including the offline queue." lang: "en" canonical: "https://mcommerce365.com/digital-transformation/order-lifecycle/" alternateMarkdown: "https://mcommerce365.com/digital-transformation/order-lifecycle/page.md" lastModified: "2026-08-18" --- # Order lifecycle into Business Central Instant post when online. Secure store and automatic send when not. Status: in progress, to sync, completed. ## Takeaways - In progress / to sync / posted — visible to managers - Queue when offline, post when coverage returns - Not a merge of two master-data editors ## Status is an operations control If nobody can see the offline backlog, managers invent stories. Visible state is how you run a fleet of phones as a process, not a rumour. ## Status is how you run a fleet of phones Instant post when online. Encrypted store and automatic send when not. Visible states — in progress, waiting to sync, posted — stop managers inventing stories about the offline backlog. The happy path is capture, park if needed, post to Business Central. We are not merging two master-data editors. Edge cases belong in the demo with your ERP owner. - Managers see backlog instead of guessing - Posted documents keep a visible sync state - Queue size is sized against your route reality in implementation ## The happy path is capture, park, post Online posts immediately. Offline stores encrypted and sends on reconnect. Visible states stop managers inventing stories about the backlog. Queue sizing is an implementation conversation against your route — we will not print a fake maximum document count on this page. Collision handling is posting into Business Central, not merging two master-data editors. ## 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 ### What if two updates collide? Sync is designed around posting field orders into Business Central, not merging two master-data editors. We walk the edge cases with your ERP owner in the demo. ### 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 - [Digital transformation](https://mcommerce365.com/digital-transformation/) - [Real-time inventory and price control](https://mcommerce365.com/digital-transformation/real-time-inventory-pricing/) - [Customer portfolio in the field](https://mcommerce365.com/digital-transformation/customer-portfolio/) - [Field product catalogue](https://mcommerce365.com/digital-transformation/product-catalogue/) [Book a 20-minute demo](https://mcommerce365.com/contact/)