01
The approval packet
ERP = Business Central. Model = native extension. Clients = iOS/Android. Offline = device queue. Auth = user + device. We put the table on the integrations hub so you do not hunt the homepage.
02
What you are actually approving
ERP = Dynamics 365 Business Central. Model = native extension. Clients = iOS and Android. Offline = encrypted device queue against the live company. Auth = user plus device, with central revoke. There is no ESB to patch, no iPaaS meter, no integration VM at 02:00, and no replica to reconcile at month end. Your BC upgrade cycle stays yours.
- Reads and writes BC objects — does not replace the ERP
- Designed to support KVKK / GDPR duties; legal pages sit under locale privacy/KVKK
- Compatibility is confirmed against the company you actually run, including on-prem vs cloud
03
Questions that belong in the first architecture call
Conflict handling on the queue, max queue size, how a lost phone is revoked, which document types your company posts, and whether master data is clean enough for a one-week path. We put the table on the integrations hub so you do not hunt the homepage. If you need SAP, Logo, Netsis or a Shopify storefront, this is the wrong product.
04
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
05
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
01Who hosts the field client?
Representatives run iOS and Android apps against your Business Central company. Deployment shape is walked in the demo against your environment — we do not hide an integration server in the architecture diagram.
02Do 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.
03Is 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.
04What 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.