--- title: "Integrations — native Dynamics 365 Business Central | mCommerce365" description: "No middleware, no parallel database, no nightly batch. How mCommerce365 connects to Business Central, syncs offline, and runs on iOS and Android." lang: "en" canonical: "https://mcommerce365.com/integrations/" alternateMarkdown: "https://mcommerce365.com/integrations/page.md" lastModified: "2026-08-18" --- # Business Central is the system of record mCommerce365 is not an iPaaS, a CRM, or a second ERP. It is a native Dynamics 365 Business Central extension with an iOS/Android field client. If the answer is 'we copy items into a sidecar every night', stop. The pages below split native Business Central, offline sync, the no-middleware stance, and the clients field teams already carry. ## 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. ## Who this hub is written for - ERP owners who will be asked to approve an architecture, not a slide - Security reviewers who need device auth, revoke, and encrypted transport in one place - Anyone comparing this product to an iPaaS-plus-mobile-database stack - Project managers who need to know what we deliberately do not integrate ## The integration questions that actually matter If the answer is 'we copy items into a sidecar every night', stop. mCommerce365 reads and writes Business Central. Offline is a device queue against that company, not a warehouse replica. The pages below split native BC, sync, the no-middleware stance, and the iOS/Android clients. - Ask where the posted sales order lives — it must be the BC company finance already closes - Ask what happens to a lost phone: revoke is part of the security conversation - Do not budget an ESB or integration VM for this product — that is a different architecture ## Pages in this hub - [Microsoft Dynamics 365 Business Central](https://mcommerce365.com/integrations/dynamics-365-business-central/) — The only supported ERP. Orders, items, prices and customers are BC objects — not copies in a sidecar. - [Offline sync](https://mcommerce365.com/integrations/offline-sync/) — A device queue, not a warehouse replica. Status stays visible: in progress, waiting to sync, posted. - [No middleware architecture](https://mcommerce365.com/integrations/no-middleware/) — No ESB, no iPaaS meter, no integration VM. Fewer moving parts for the people who have to approve the project. - [iOS and Android](https://mcommerce365.com/integrations/ios-android/) — Phones and tablets the team already carries. Role-specific home screens, not a desktop website pinched onto glass. ## Questions buyers ask ### 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. ## Related pages - [Book a 20-minute demo](https://mcommerce365.com/contact/) - [mCommerce365](https://mcommerce365.com/) - [llms.txt](https://mcommerce365.com/llms.txt)