![Working through a client's systems](/_astro/working.Dc18osKj_1Q1BEc.webp) # Three storefronts, one ERP, one 3PL, no re-keying [Vlad Leonov](https://www.linkedin.com/in/vodyl/) 8/17/26 9/9/26 2 min read **Three storefronts can give customers three distinct shopping experiences. Behind the scenes, finance and fulfilment still need the orders to tell one consistent story. For one multi-brand consumer-goods group we work with, that meant connecting Shopify, Dynamics 365 Business Central and a third-party logistics provider, or 3PL. The aim was an order flow that did not depend on someone copying information between systems**. ## [The setup](#the-setup) Each brand had its own Shopify storefront. Business Central held finance and stock, while the 3PL handled fulfilment. The brief was practical: orders arriving in the ERP without re-keying, reliable stock information and less manual reconciliation across the group. This case is anonymised. We name clients only with their sign-off. ## [What we built](#what-we-built) We connected the storefronts to Business Central, and Business Central to the 3PL. Orders, stock and fulfilment updates move between those systems without manual re-entry as part of the normal flow. That last part matters. An order arriving in the ERP is one handover; getting it through to fulfilment and bringing the updates back completes more of the picture. The value is in **connecting the whole route**, rather than leaving someone to carry the information across the final gap. The integrations run as code the group owns, inside the secure boundary we operate. Kori, our AI Integration Support Engineer, helps investigate issues and reports findings in the shared chat. When something needs attention, the conversation sits alongside the people responsible for the work. ## [The lesson that became policy](#the-lesson-that-became-policy) This client had also experienced integrations that depended on one person, and the difficulty of carrying on when that person moved on. Connecting the systems was not enough; the knowledge needed to stay with the business too. That experience helped shape our [continuity approach](/our-approach#continuity): documented operating instructions and code the client owns. A working integration should come with a way for someone else to understand and maintain it. ## [Sound familiar?](#sound-familiar) If your setup looks like this, follow one order from checkout to despatch. Where does a person have to move the information, and where would you look if it stopped? We can start there in [a free one-hour conversation about your systems and integration plans](/talk). You do not need to have the solution mapped out before we talk. [Case studies](/blog/categories/case-studies) [Case study](/blog/tags/case-study) [shopify](/blog/tags/shopify) [business-central](/blog/tags/business-central) [Integration](/blog/tags/integration) ## Table of contents [‐To the beginning](#start)[‐The setup](#the-setup)[‐What we built](#what-we-built)[‐The lesson that became policy](#the-lesson-that-became-policy)[‐Sound familiar?](#sound-familiar) ## Share it: [](mailto:?subject=Have a look at this article&body=https%3A%2F%2Fwww.inite.co%2Fblog%2Fthree-storefronts-one-erp-one-3pl)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.inite.co%2Fblog%2Fthree-storefronts-one-erp-one-3pl)[](http://news.ycombinator.com/submitlink?u=https%3A%2F%2Fwww.inite.co%2Fblog%2Fthree-storefronts-one-erp-one-3pl&t=Three storefronts, one ERP, one 3PL, no re-keying)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fthree-storefronts-one-erp-one-3pl)[](https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fthree-storefronts-one-erp-one-3pl)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fthree-storefronts-one-erp-one-3pl&title=Three storefronts, one ERP, one 3PL, no re-keying)[](https://t.me/share/url?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fthree-storefronts-one-erp-one-3pl)[](https://x.com/intent/post?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fthree-storefronts-one-erp-one-3pl)[](https://api.whatsapp.com/send?text=https%3A%2F%2Fwww.inite.co%2Fblog%2Fthree-storefronts-one-erp-one-3pl) ## Continue reading: [Meet Kori, our AI Integration Support EngineerOur newest team member doesn’t sleep. Meet Kori: investigating integration issues, keeping answers in the open and helping our team move fixes forward.4 min read](/blog/meet-kori) [Keeping a manufacturer's systems talking, long-termConnecting a food manufacturer’s ERP is not just a go-live job. An ongoing NZ engagement shows why ownership and support belong in the plan from the start.2 min read](/blog/keeping-a-manufacturers-systems-talking) ## Table of contents [‐To the beginning](#start)[‐The setup](#the-setup)[‐What we built](#what-we-built)[‐The lesson that became policy](#the-lesson-that-became-policy)[‐Sound familiar?](#sound-familiar)