Commerce Advisory · Systems Integration

eCommerce ERP Integration Built Around One Customer Record

We map how orders, inventory, products and customers move between your store, ERP, PIM, CRM and OMS, decide which system owns each piece of data, and write integration specs your developers or integrator can build without guesswork.

  • ERP, PIM, CRM & OMS
  • Middleware chosen to fit
  • Specs your team can build

Signs the systems don't talk

Integration gaps show up as profit leaks, not error messages

Disconnected systems rarely crash. They cost a little every day, in ways that look like operations problems. Our Commerce Advisory team traces each one to its data flow.

Overselling

Wholesale, marketplace and DTC orders draw from the same stock, but inventory syncs late or one way.

Manual order entry

Someone retypes orders into the ERP, and every retyped order is a chance for a wrong SKU or address.

Product data in five places

Specs, images and claims live in spreadsheets, the store and the feed, and they disagree.

Three versions of a customer

Store, email platform and CRM each hold a different profile, so LTV and segments can't be trusted.

The systems we connect

What each system should own, and what it shouldn't

ERP: inventory, cost and financials

Systems such as NetSuite, Microsoft Dynamics 365 Business Central or Acumatica usually own stock levels, product cost, purchase orders and the financial record of each order. Product cost matters for us: it is what makes contribution margin by order possible.

  • Inventory from ERP or warehouse to store, as close to real time as volume requires
  • Orders, refunds and partial shipments from store to ERP

The integration map

One system of record per type of data

DataSystem of record (example)Flows toSync timing
Product content and attributesPIMStore, product feeds, marketplacesOn publish
InventoryERP or warehouse systemStore, marketplaces, OMSNear real time
Prices and B2B termsERPStore catalogs and price listsOn change
Orders and refundsStore, then OMS and ERPEmail platform, CRM, analyticsReal time
Customer profile and consentStore and email platformCRM, ad platformsReal time
Cost and financialsERPReporting and margin modelDaily

Illustrative. Your map depends on the systems you run and the volume you ship.

How we run it

From whiteboard to a monitored integration

  1. Map

    Draw the current flows

    Every system, every connection, every spreadsheet and every manual step, including the ones people only mention when asked.

  2. Own

    Name a system of record per data type

    Product, inventory, price, order, customer and consent each get one owner. Everything else reads from it.

  3. Choose

    Pick the integration pattern

    Native connector, middleware such as Celigo or Boomi, or a custom API integration. We choose on volume, edge cases, monitoring and who maintains it.

  4. Spec

    Write the build spec

    Field mappings, triggers, error handling, retries and alerts, written so your developers, ERP partner or integrator can build and test against it.

  5. Test

    Test the awkward orders

    Bundles, partial refunds, split shipments, subscription renewals, B2B orders on terms and edited addresses. The easy orders always work.

  6. Monitor

    Alert on failures

    Failed syncs alert a named owner, with a daily reconciliation of orders and stock until the numbers stay matched.

One customer record

Clean customer data is what makes LTV and segmentation real

Cohort LTV, Value × Intent segments and predictive timing all depend on one profile per customer, with orders and consent attached. We decide where that profile lives, whether a customer data platform is justified or your email platform is enough, and how consent travels with the profile to every tool. The event side is built by our Data Layer Engineering team.

  • Email as the main identity key, with phone and customer ID as fallbacks
  • Consent status synced with the profile, never stored only in one tool
  • B2B buyers linked to their company account, not duplicated as consumers

FAQ

Systems integration questions

What is eCommerce ERP integration?

eCommerce ERP integration connects your online store to the system that runs inventory, purchasing and finance. Orders and refunds flow from the store to the ERP, and stock levels, prices and B2B terms flow back. Done well, nobody retypes orders, stock stays accurate across channels and product cost is available for margin reporting by order.

Should we use a native connector or middleware?

Use a native connector when it covers your edge cases and offers monitoring. Choose middleware when several systems need to share data, when you need custom mapping or logic, or when you want one place to watch failures. Custom API work makes sense for a few high-volume flows. We compare options on volume, edge cases and who maintains it.

Do we need a PIM?

Not always. With a modest catalog and one or two channels, your store admin plus a clean spreadsheet process may be enough. A PIM earns its place when you manage many SKUs, sell across several channels or marketplaces, run separate B2B catalogs or need one approved source for regulated product claims.

Which platforms do you plan integrations for?

Shopify and Shopify Plus most often, plus WooCommerce and Magento / Adobe Commerce. Integrations often come up during a replatforming project, because every connection has to be rebuilt, and in AI and automation work, which depends on clean data.

Do you build the integrations yourselves?

We own the plan, the integration map, the specs and the testing. Lighter connections, such as tracking, email platform and CRM syncs, our team can set up. For ERP and OMS builds, we work alongside your developers, your ERP partner or a specialist integrator, and stay on to QA the build against the spec.

Get your systems agreeing on the numbers

Start with the free audit for a quick read on where your store leaks profit, or book a call to map your current systems with us.

Free Profit Audit