Use cases
The same app, different jobs
Field reps, managers, IT, finance and your customers do not share a screen. These pages describe the job each role actually finishes with mCommerce365.
Pick the role that will sit in the demo. Bring the person who currently re-keys paper and the person who will revoke a lost device. Native posting, a device queue, role screens — if those two agree the architecture is boring, the project usually survives.
5 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.
Five jobs, one Business Central company
Field representatives who need the customer, stock and price on one phone screen
Sales managers who cannot wait for last month's export to coach this week
IT / ERP teams who will own the extension after go-live
Finance, operations, and B2B customers who need a screen instead of a support queue
Pick the role that will sit in the demo
The homepage cannot show five jobs at once. These pages do. Bring the person who currently re-keys paper, plus the person who will revoke a lost device. If those two agree the architecture is boring — native posting, device queue, role screens — the project usually survives.
- Start with the field-rep page if your pain is the visit itself
- Start with IT if the blocker is architecture approval
- Read customer self-service last — it is a panel for accounts you already sell to, not a public shop
Pages in this hub
Field sales representatives
Customer card, last orders, live stock, contract price, tap to post — one screen, including offline.
One-tap reorder from recent documents
Read the page →Sales managers
Coverage, volume per visit and who needs coaching — this week, not last month's export.
Live team performance
Read the page →IT and ERP teams
Approve an extension, not an integration estate. No middleware to patch, no replica to reconcile.
No ESB / iPaaS / integration VM
Read the page →Finance and operations
Cleaner orders, fewer credit notes, a full audit trail from tap to posted document.
Field document posts as the BC document — no second typing pool
Read the page →Customer self-service
Buyers track their own orders. Support volume drops because 'where is my order?' has a screen, not a queue.
Fewer 'where's my order' calls
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.