--- title: "No middleware, no parallel database — mCommerce365" description: "Why mCommerce365 refuses a second database and nightly batches for field sales on Business Central." lang: "en" canonical: "https://mcommerce365.com/integrations/no-middleware/" alternateMarkdown: "https://mcommerce365.com/integrations/no-middleware/page.md" lastModified: "2026-08-18" --- # No middleware architecture No ESB, no iPaaS meter, no integration VM. Fewer moving parts for the people who have to approve the project. ## Takeaways - Nothing to babysit at 02:00 - Month-end has one truth - IT reviews an extension, not an estate ## The usual failure mode Middleware projects slip. The mobile app shows yesterday's price. Finance does not trust the number. mCommerce365's answer is architectural: do not create the second truth. ## Fewer moving parts for the people who approve Middleware projects slip. The mobile app shows yesterday's price. Finance does not trust the number. mCommerce365's answer is architectural: do not create the second truth. No ESB, no iPaaS meter, no integration VM, no nightly batch that becomes someone's on-call. Month-end has one company: Business Central. IT reviews an extension, not an estate. - Nothing to babysit at 02:00 - If you were quoted an integration server, you were quoted a different architecture ## What IT is actually asked to approve An extension into the Business Central company finance already closes — not an integration VM, an ESB, or a replica that needs its own backup. Your BC upgrade cycle stays yours. If someone is selling you a field app that needs a second database, you are buying month-end theatre. We say that before the twenty minutes, not after. ## 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 ### What if we already have an iPaaS? You can keep it for other systems. This product does not need it to post field orders into Business Central. Mixing a replica mobile database back in would recreate the month-end diplomat. ### What 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. ### 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 - [Integrations](https://mcommerce365.com/integrations/) - [Microsoft Dynamics 365 Business Central](https://mcommerce365.com/integrations/dynamics-365-business-central/) - [Offline sync](https://mcommerce365.com/integrations/offline-sync/) - [iOS and Android](https://mcommerce365.com/integrations/ios-android/) [Book a 20-minute demo](https://mcommerce365.com/contact/)