--- title: "IT approval for a BC field sales app — mCommerce365" description: "Native Business Central extension, encrypted transport, role-based access, upgrade-safe. Specs IT actually asks for." lang: "en" canonical: "https://mcommerce365.com/use-cases/it-erp-teams/" alternateMarkdown: "https://mcommerce365.com/use-cases/it-erp-teams/page.md" lastModified: "2026-08-18" --- # IT and ERP teams Approve an extension, not an integration estate. No middleware to patch, no replica to reconcile. ## Takeaways - No ESB / iPaaS / integration VM - Device auth + central revoke - Designed to support KVKK/GDPR duties ## 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. ## 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 ## 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. ## 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 ## 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 ### Who 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. ### 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. ## 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. ## Related pages - [Use cases](https://mcommerce365.com/use-cases/) - [Field sales representatives](https://mcommerce365.com/use-cases/field-sales-representatives/) - [Sales managers](https://mcommerce365.com/use-cases/sales-managers/) - [Finance and operations](https://mcommerce365.com/use-cases/finance-operations/) - [Customer self-service](https://mcommerce365.com/use-cases/customer-self-service/) [Book a 20-minute demo](https://mcommerce365.com/contact/)