ERP integration

ERP integration services for teams that re-key orders between systems.

We connect your ERP to your web store, marketplaces, CRM and accounting, so orders, stock and invoices move on a schedule instead of by hand. You get a free written fit check first and a fixed quote before any build. On a NetSuite replacement we built, 16 scheduled jobs keep five outside tools in sync, and Shopify stock updates from the ERP every 10 minutes.

Connect, fix or replace

When to connect your systems, and when to fix or replace first.

Connect if

Orders are typed in twice

Someone re-keys web-store and marketplace orders into the ERP. We pull them in on a schedule, with the customer, line items and payment attached.

Connect if

Stock counts disagree

The store, each marketplace and the ERP keep their own counts, and you oversell. One system, usually the ERP, should hold the count they all read and push it to every channel on a schedule.

Connect if

Sales can’t see orders in the CRM

Reps work in HubSpot while order history and credit sit in the ERP. We sync the fields they need, one way or both ways, and agree which system wins each field when the two disagree.

Connect if

Invoices are retyped into accounting

Someone copies invoices and payments from the ERP into QuickBooks Online. We connect the two so those records reach accounting on a schedule. Our NetSuite replacement is connected to QuickBooks Online.

Fix first

The connector you have keeps breaking

Orders go missing without an error, duplicates appear or orders get stuck. We read the logs, repair the sync and add a check that shows when the counts drift, before we build anything new.

Audit an integration someone else built

Replace if

The ERP itself is the problem

If your team keeps spreadsheets beside the ERP to get through the day, connecting more tools adds more workarounds. A better-fitting ERP is the fix, and the fit check says so in writing.

Custom ERP development
Delivery examples

Two systems we connected, both in use today.

The figures come from the two projects’ code repositories, compiled in October 2026.

NetSuite replacement · US wholesale business

A sync layer around a new ERP

A US wholesale business moved off NetSuite in July 2026. The ERP we built is now its system of record, and a sync layer keeps its other tools in step with it.

  • 16 scheduled jobs sync NetSuite, eBay, AfterShip (shipment tracking), Klaviyo (email marketing) and HubSpot (CRM).
  • Shopify stock pushed from the ERP every 10 minutes: 213 SKUs on the first full run in July 2026.
  • Connected to QuickBooks Online for accounting.
  • Stripe card payments and EasyPost shipping labels run inside the operations app.
  • Before every release, a script checks that on-hand stock equals the open FIFO cost layers, with zero drift allowed.
  • The July 2026 release passed 2,397 automated tests. Sandbox and production databases are separate.

    Reporting and CRM · US consumer-health brand

    Distributor and Sage 100 data in one place

    A consumer-health brand kept its retail and distributor numbers in vendor exports and hand-kept workbooks. We built one database and web app that pull those feeds in every week.

    • Weekly scheduled jobs refresh the outside data sources.
    • Distributor purchase lines matched to the outlets they ship to, with duplicates merged.
    • 121 tables and about 1.24 million rows, measured in September 2026.
    • A reorder-prediction CRM built on the brand’s Sage 100 data.

      We do not name either client in public. Screens we share use synthetic data, never their customers, products or prices. Across all our work, we have delivered 300+ projects since 2019.

      Leaving NetSuite as well? See how we replaced NetSuite for a wholesale business.

      Get a free written fit check
      The sync map

      Before we build, every record gets an owner.

      The sync map lists each record type with the system that owns it, which way it flows, how often it moves and which side wins a conflict. We also agree how missed or duplicate records are found and fixed. The rows below are a sample with example settings, except the 10-minute Shopify stock push, which is how our NetSuite replacement runs.

      Stock
      Owned by the ERP. Pushed to Shopify every 10 minutes and to each marketplace on a schedule. On a conflict, the ERP count wins.
      Orders
      Created in the store or marketplace. Pulled into the ERP on a schedule with the customer, line items and payment. After that, changes are made in the ERP.
      Customers
      Billing and credit owned by the ERP, contact details by the CRM. Synced both ways, field by field, with the owner of each field named.
      Invoices and payments
      Created in the ERP and sent to accounting on a schedule. Accounting never writes back to the invoice.
      Shipments
      Labels made in the ERP. Tracking status read back from the tracking tool on a schedule.
      How we know it works

      A check that stops the release when the counts differ.

      These are the checks on our NetSuite replacement. Yours are agreed in the sync map.

      • Before every release, a script compares on-hand stock with the open FIFO cost layers. If they differ, the release stops.
      • The July 2026 release passed 2,397 automated tests.
      • Changes run on a sandbox with its own database before they are promoted to production.
      • During the move off NetSuite, we repaired 27,667 sales-rep attribution records and checked them against live NetSuite queries.
      Systems we connect

      ERP integration for Shopify, HubSpot, QuickBooks Online and NetSuite.

      What we have connected so far, system by system, plus a CRM we built on Sage 100 data.

      Shopify and marketplace integration

      The ERP keeps the stock count and pushes it to Shopify and your marketplaces, and channel orders can come into the ERP on a schedule. On our NetSuite replacement, Shopify stock updates every 10 minutes (213 SKUs on the first full run), and eBay is part of the scheduled sync.

      HubSpot CRM integration

      Reps who work in HubSpot need order history and credit status without opening the ERP. We sync the fields they use and name the system that owns each one. On our NetSuite replacement, HubSpot is part of the scheduled sync, and reps also see each customer’s order history in the ERP’s call queue.

      QuickBooks Online integration

      QuickBooks Online has a public API for invoices, payments and customers, so the ERP can send those records on a schedule in place of CSV exports. Our NetSuite replacement is connected to QuickBooks Online.

      Sage 100 data

      Sage 100 is Sage’s ERP for small and midsize businesses. We built a reorder-prediction CRM on one brand’s Sage 100 data. Tell us which Sage 100 modules you run, and the fit check says what a link to them would take.

      NetSuite

      On our NetSuite replacement, NetSuite is one of the five tools in the scheduled sync, and since the July 2026 switch it has been kept read-only for history. If you are staying on NetSuite and only need it connected to another tool, the same sync map applies.

      Payments, shipping, tracking and email

      Stripe card payments and EasyPost shipping labels run inside the operations app of our NetSuite replacement. AfterShip shipment tracking and Klaviyo email marketing are part of its scheduled sync.

      Three ways to connect

      Point-to-point, middleware or a custom sync layer.

      We pick per system, by how many tools you run and what has to happen to a record on the way across.

      Point-to-point
      One system calls the other’s API directly. Quick for two systems, though every new tool adds another link to look after.
      Middleware or iPaaS
      A hosted integration platform sits between the systems and runs the flows. Suits many standard tools and teams that want to configure flows without code. You pay for the platform.
      Custom sync layer
      Scheduled jobs you own, in your repository. Suits records that need business rules on the way across. Our NetSuite replacement uses one.
      How we connect it

      Run the sync beside the old process until the counts match.

      01

      Free written fit check

      Tell us which systems you run, roughly how many orders, products and customers move between them, and what breaks today. Within one business day we reply in writing: what we would connect first, the approach for each system and what discovery costs.

      02

      A sync map, then a fixed quote

      In discovery we draw the sync map: for each record type, the system that owns it, which way it flows, how often, and what happens on a conflict. You get the map, a fixed quote and a schedule before any build starts.

      03

      Build on a sandbox, then switch on

      We build on a sandbox, run the sync beside your current process and compare the counts. It goes live when they match, with a check that stops a release when they differ. Later changes or support run on a care plan or by quote.

      Tell us which systems you run.

      Name the ERP, the tools it has to talk to and roughly how many orders you handle a month. That is enough for the fit check.

      Get a free written fit check
      What you get

      What you get at each step.

      • A written fit check within one business day, including when connecting is the wrong fix
      • A sync map with the owner, direction, frequency and conflict rule for each record type
      • A fixed quote and schedule before the build
      • Automated tests and a sandbox for every change
      • Code in your repository, on servers you control, with handover documentation
      Who it is for

      Teams whose ERP has to talk to a store, a CRM or accounting.

      Wholesale, distribution and multi-channel ecommerce teams in the US, UK, EU and Australia. Our integration work covers Shopify, eBay, HubSpot, QuickBooks Online and NetSuite, and we have built a CRM on Sage 100 data. We have not built SAP or Microsoft Dynamics integrations, so if you run one of those, the fit check will say whether another team suits you better.

      Need a new ERP rather than a link? See custom ERP development and its build-or-buy test.

      Changing ERP before you connect anything? See ERP data migration services for how records move and get checked before the switch.

      Selling wholesale through several channels? See what an ERP for wholesale distributors has to cover.

      Did another developer start the sync and stop halfway? We can take over a half-built sync instead of starting again.

      Connector stuck on an old PHP or Node.js version? See PHP and Node.js upgrades.

      Want to see what we have built? Browse our selected work.

      FAQ

      Questions we get before people start.

      What do ERP integration services include?

      Mapping which system owns each record, building the sync, testing it on a sandbox, and the checks that show when two systems disagree. With us you also get the sync map in writing and a fixed quote before the build.

      What are the three approaches to ERP integration?

      Point-to-point, where one system calls the other’s API directly; middleware or an iPaaS platform that runs the flows between systems; and a custom sync layer of scheduled jobs you own. We pick per system. Our NetSuite replacement uses a custom sync layer: 16 scheduled jobs sync five tools, and Shopify stock updates every 10 minutes.

      What is API integration with an ERP?

      The ERP and the other tool exchange records through their APIs, on a schedule or when something changes, in place of file exports and manual imports.

      Can a CRM be integrated with an ERP?

      Yes. On our NetSuite replacement, HubSpot is part of the scheduled sync, and reps see each customer’s order history from the ERP in their call queue. We agree which system owns each field before we build.

      Can you connect QuickBooks Online to an ERP?

      Yes. QuickBooks Online has a public API, and our NetSuite replacement is connected to it. For your setup, the sync map sets which records go across and how often.

      Is Sage 100 an ERP, and can you work with its data?

      Yes, Sage 100 is Sage’s ERP for small and midsize businesses. We built a reorder-prediction CRM on one brand’s Sage 100 data. The fit check names what a link to your Sage 100 setup would take.

      What is an example of ERP integration?

      Stock pushed from the ERP to Shopify every 10 minutes. On our NetSuite replacement, the first full run in July 2026 pushed 213 SKUs.

      How much does ERP integration cost?

      The fit check is free, and the build gets a fixed quote after discovery. The cost depends on how many systems you connect, how many record types move, whether they sync one way or both ways, and how much history comes across.

      Next step

      Find out what connecting your systems takes.

      Free written fit check within one business day. Sync map and fixed price agreed before any build.