01
The job
Field selling dies when the phone shows 'no service' and the rep writes the order on paper. Paper is re-typed later, prices drift, and warehouse picks the wrong pack. Offline mode is not a nice-to-have for wholesale routes — it is the difference between a posted order and a callback.
- Works in coverage gaps without a parallel database
- Queue is encrypted on the device
- Posted documents keep a visible sync state
02
What the rep does
Open the customer card, pick lines, confirm. If the radio is down, the order stays on the phone with a clear 'to be synchronised' state. When the van hits a mast, the same document posts into Business Central — no inbox of photos of notebooks.
03
What IT should ask
There is no second database to reconcile at month end. Offline is a device queue against the live Business Central company. Ask us about conflict handling, max queue size, and how a lost phone is revoked.
04
Where this is not optional
Industrial parks, basements, rural agriculture and building-materials jobsites are the routes that still run on paper because the laptop ERP client dies with the radio. A device queue against live Business Central is how the visit continues. Status stays visible: in progress, waiting to sync, posted. There is no evening inbox of notebook photos.
05
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
06
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
01Can reps create invoices offline?
The product is built for order capture that posts to Business Central. Exact document types depend on your company setup — we confirm this in the demo against your BC configuration.
02What if two updates collide?
Sync is designed around posting field orders into BC, not merging two master-data editors. We walk through the edge cases with your ERP owner.
03What 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.
04Do 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.
05Is 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.
06What 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.