![New Zealand from above: the businesses we build for](/_astro/auckland.Bfa4URxP_ZUEdpU.webp) # Keeping a manufacturer's systems talking, long-term [Vlad Leonov](https://www.linkedin.com/in/vodyl/) 8/16/26 9/9/26 2 min read **Getting an integration live is a milestone. In manufacturing, the next working day matters just as much. Orders, production and distribution depend on information reaching the right place. When a handover needs attention, the team needs to know who will pick it up, not start a search for whoever built it. ## [The setup](#the-setup) Our ongoing engagement with a New Zealand food manufacturer covers both parts of that job: connecting the ERP to the systems around it and keeping those connections running**. This is an anonymised engagement. We name clients only with their sign-off. ## [How it runs](#how-it-runs) The work sits under a standing agreement, rather than ending at the first successful transfer. The integrations are delivered as **code the client owns**, with support arranged so it does not depend on one person’s availability. Those are practical choices. Ownership gives the manufacturer control over what has been built. Ongoing support gives the connections somewhere to go when they need attention. Neither should be an afterthought once production is relying on them. The lesson for another manufacturer is straightforward: when you scope a connection, ask about the working life of it as well as the delivery date. Who handles an exception? Who keeps the knowledge current? What stays with the business if the people involved change? ## [Sound familiar?](#sound-familiar) If your team is filling gaps between the ERP and the systems around it, start with the handover that causes the most chasing. [Our free assessment](/talk) is a one-hour conversation about your systems and future integration plans, including what needs to happen after go-live. [Case studies](/blog/categories/case-studies) [Case study](/blog/tags/case-study) [Integration](/blog/tags/integration) ## Table of contents [‐To the beginning](#start)[‐The setup](#the-setup)[‐How it runs](#how-it-runs)[‐Sound familiar?](#sound-familiar) ## Share it: [](mailto:?subject=Have a look at this article&body=https%3A%2F%2Fwww.inite.co%2Fblog%2Fkeeping-a-manufacturers-systems-talking)[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.inite.co%2Fblog%2Fkeeping-a-manufacturers-systems-talking)[](http://news.ycombinator.com/submitlink?u=https%3A%2F%2Fwww.inite.co%2Fblog%2Fkeeping-a-manufacturers-systems-talking&t=Keeping a manufacturer's systems talking, long-term)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fkeeping-a-manufacturers-systems-talking)[](https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fkeeping-a-manufacturers-systems-talking)[](https://www.reddit.com/submit?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fkeeping-a-manufacturers-systems-talking&title=Keeping a manufacturer's systems talking, long-term)[](https://t.me/share/url?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fkeeping-a-manufacturers-systems-talking)[](https://x.com/intent/post?url=https%3A%2F%2Fwww.inite.co%2Fblog%2Fkeeping-a-manufacturers-systems-talking)[](https://api.whatsapp.com/send?text=https%3A%2F%2Fwww.inite.co%2Fblog%2Fkeeping-a-manufacturers-systems-talking) ## Continue reading: [Three storefronts, one ERP, one 3PL, no re-keyingThree Shopify storefronts, shared finance and stock, one fulfilment partner. How we connected the order flow, with ownership and continuity built into the work.2 min read](/blog/three-storefronts-one-erp-one-3pl) [When an order stops halfway: Cloudflare Workflows adds rollbacksPayment taken, stock reserved, shipment not booked. Cloudflare Workflows adds a way to handle unfinished processes, provided the recovery rules are designed first.2 min read](/blog/cloudflare-workflows-saga-rollbacks) ## Table of contents [‐To the beginning](#start)[‐The setup](#the-setup)[‐How it runs](#how-it-runs)[‐Sound familiar?](#sound-familiar)