Integrations
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.
4 pages
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
The only supported ERP. Orders, items, prices and customers are BC objects — not copies in a sidecar.
ERP: Dynamics 365 Business Central only
Read the page →Offline sync
A device queue, not a warehouse replica. Status stays visible: in progress, waiting to sync, posted.
Automatic send on reconnect
Read the page →No middleware architecture
No ESB, no iPaaS meter, no integration VM. Fewer moving parts for the people who have to approve the project.
Nothing to babysit at 02:00
Read the page →iOS and Android
Phones and tablets the team already carries. Role-specific home screens, not a desktop website pinched onto glass.
Smartphone and tablet
Read the page →
Questions buyers ask
01Do 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.
02Is 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.
03What 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.
Next step
Book a 20-minute demo
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.