One truth, every system.

We connect your store to NetSuite, SAP Business One, Odoo or Dynamics 365 so orders, stock, prices, invoices and returns agree everywhere, without anyone exporting a spreadsheet.

  • 4–8 wksFor a full two-way store and ERP sync.
  • DailyReconciliation report you can check line by line.
  • 0 exportsNo spreadsheets passed between teams.
  • RESTERP interface
  • 2-waysync direction
Use cases

Where syncs usually start

  • Order to sales order

    Each store order lands in the ERP with the right customer, items, tax and location.

    OrdersCustomersTax
  • Stock and prices out

    The ERP stays the source of truth; the store and marketplaces follow it.

    StockPricesMarketplaces
  • Refunds and returns

    A return in the store creates the credit note and restocks the right location.

    RefundsRMAsCredit notes
  • B2B accounts

    Company accounts, payment terms and price lists kept in step with the ERP.

    B2BTermsPrice lists
  • Finance close

    Invoices, payouts and fees matched so month-end does not start with a spreadsheet.

    PayoutsFeesInvoices
Explained

What ERP integration involves for a store

Your online store is good at selling. Your ERP is good at knowing things: what you have in stock, what each trade customer pays, what’s been invoiced and what’s been paid. ERP integration is the plumbing that lets each system rely on the other, so nobody has to carry numbers between them by hand.

In practice that means a handful of flows. Orders go from the store into the ERP as sales orders. Stock levels and prices come back the other way. Shipments, refunds and invoices close the loop. A B2B store adds customer accounts, credit limits and price lists to the list.

Read the detail: What ERP integration involves for a store

The question that matters most: who owns what?

Every field needs exactly one owner. If the store and the ERP can both change a price, sooner or later they’ll disagree and nobody will know which is right. So before any code, we write down a short ownership table: the ERP owns stock, cost and trade prices; the store owns product descriptions, images and retail promotions; customers are created in the store but their credit terms live in the ERP. It’s dull work, and it prevents most of the arguments you’d otherwise have in month three.

Real-time or scheduled?

Not everything needs to be instant. Orders should flow within a minute or two, because the warehouse is waiting. Stock usually needs to update every few minutes on a busy store, and immediately when a line sells out. Prices and product data can often sync hourly or nightly. Matching the timing to the job keeps you inside API limits and keeps hosting costs sensible.

The ERP-specific details, like which API we use and the quirks we plan around, are on each platform page: NetSuite, SAP Business One, Odoo, Dynamics 365 Business Central and Acumatica.

ERPs we integrate

Pick your ERP for the details

Each page covers what we sync, the interface we use and the gotchas we plan for.

What’s included

Everything a sync needs to stay right

Every ERP project ships with the same eight things, so the numbers still match a year from now.

  • Field mapping

    Every field, status and code mapped in writing before a line is built.

  • Two-way sync

    Orders and refunds in, stock and prices out, in near real time.

  • Queues + retries

    Rate limits and outages absorbed; records wait in a queue until they go through.

  • Daily reconciliation

    A report comparing store and ERP totals, line by line.

  • Least-privilege access

    Integration users with only the permissions the sync needs.

  • Version control

    Workflows and mapping files in your repository.

  • Replay tools

    Any failed record can be fixed and replayed without duplicates.

  • Hand-over

    Documentation and a recorded walkthrough for your team.

Decision guide

Connector app, integration platform or custom integration?

There are three common ways to connect a store to an ERP. We’ll happily recommend a ready-made connector when it fits; it often does for simple catalogues.

A rough comparison. Connector features and pricing vary widely, so we check the specific options for your ERP during the audit.
OptionFits whenBreaks down whenRunning cost shape
Off-the-shelf connectorStandard products, one store, one warehouse, and you’re happy to work the way the connector expects.Bundles, B2B pricing, multiple locations or custom fields. Changes wait on the vendor’s roadmap.Monthly subscription, often tiered by order volume.
Workflow engine with custom mappingMost mid-sized stores: standard flows with your own rules, built on an automation engine with the mapping kept as a readable file.Very high volumes or complex logic, where a dedicated service is cheaper to run.Build cost, then hosting or engine plan plus optional monitoring.
Custom integration serviceThousands of orders an hour, several storefronts and ERPs, or strict data residency requirements.Small stores, where the build cost won’t pay back.Higher build cost; low cloud running cost at scale.

Not sure which engine fits? Workflow automation explains how we choose between low-code platforms, Shopify Flow and custom code.

Under the hood

Mapping you can read and review

Most sync problems are mapping problems. We write the mapping down as a file you can review, version and change.

  • Mapping as a fileEvery field mapping is a reviewed file in your repository, where anyone can read it.
  • Idempotent writesThe store order ID travels with every record, so a replay never doubles an order.
  • Respectful of limitsCalls are queued and paced to each ERP’s concurrency and rate limits.
  • Reconciled dailyTotals compared every morning; differences listed before anyone asks.
mapping/order-to-sales-order.yml (excerpt)
# store order -> ERP sales order
source: shopify.order
target: netsuite.salesOrder
key: externalId = order.id
fields:
  entity:     customer.match(email) or create
  location:   map(order.fulfillment_location)
  items:      line_items -> item by SKU
  taxcode:    map(tax_lines[0].title)
  memo:       "Store order " + order.name
on_error:   hold + alert #ops
retry:      3 x exponential

Works with

NetSuiteerpSAP Business OneerpOdooerpDynamics 365 BCerpAcumaticaerpBrightpearlerpCin7erpShopifystoreShopify PlusstoreAdobe CommercestoreWooCommercestoreBigCommercestoreAmazonmarketplaceeBaymarketplaceShipStationshippingShipBob3plStripepaymentsQuickBooksfinanceXerofinanceSlackalerts
The plan

Your ERP sync, week by week

  1. Week 0

    Audit call

    30 minutes on where the numbers disagree today.

    Gap list
  2. Weeks 1–2

    Mapping

    Every field, status and code agreed in writing.

    Mapping file
  3. Weeks 2–5

    Build

    Syncs built in a sandbox ERP, demoed weekly.

    Staging demo
  4. Weeks 5–7

    Parallel run

    Old and new process side by side until totals match.

    Signed-off recon
  5. Week 8+

    Run

    Monitoring, daily reconciliation and a monthly report.

    Monthly report
Where syncs go wrong

Four ERP integration problems, and how we handle them

These come up on almost every project. The difference between a sync you trust and one you check by hand every morning is whether they were planned for.

Problem

SKUs that don’t match

The store sells “Blue Mug, 2-pack”. The ERP has two separate items and a kit record. Orders arrive and nobody knows what to pick.

How we handle it

A SKU map agreed in the mapping phase, bundles split into components, and any unknown SKU held and flagged for a person to check.

Problem

Overselling between syncs

Stock updates every 30 minutes. A flash sale sells 200 units in ten. You now owe customers 60 items you don’t have.

How we handle it

Event-based stock updates for fast movers, a safety buffer on low-stock items, and a near-real-time push when a line hits zero.

Problem

Tax and rounding differences

The store calculates tax per line, the ERP per order. Totals differ by a cent and finance can’t close the month.

How we handle it

One agreed rule for where tax is calculated, test orders across every tax case, and a daily reconciliation that flags any mismatch.

Problem

The ERP is down or slow

Maintenance window, an upgrade, or just a busy month-end. Orders keep coming in.

How we handle it

Orders queue safely, retry with growing waits, and post as soon as the ERP is back, in order and without duplicates.

Pricing

Priced per sync, not per seat

Typical ranges. Your fixed quote follows the free audit, and nothing is billed before you agree it.

One direction

Order sync

$8,000+Orders into the ERP, 4 weeks

  • Order to sales order
  • Customer match or create
  • Error path and alerts
Scope order sync
Most chosen

Two-way sync

$12k–$20kOrders in, stock and prices out

  • Orders, refunds, stock, prices
  • Daily reconciliation report
  • Two months monitoring included
Scope two-way sync
Ongoing

Managed

from $350/moSized to your syncs

  • Five-minute failure alerts
  • Mapping changes included
  • Monthly written report
Talk monitoring
Glossary

ERP integration terms you’ll hear

A short list of the words that come up in mapping sessions, so the first meeting doesn’t feel like a different language.

Source of truth the owner
The one system allowed to change a particular field. Everything else reads it. Deciding this per field is the single most useful thing we do in week one.
Field mapping
The written list of which field in the store becomes which field in the ERP, and how values are converted.
Two-way sync
Data flowing in both directions: orders in, stock and prices out.
Reconciliation
A scheduled check that totals in both systems still agree, with differences listed.
Parallel run
Running the new sync alongside the old process for a week or two, comparing results before switching over.
iPaaS
Integration platform as a service: hosted tools for building connections between systems.
Kit or bundle
One sellable item made of several stock items. A frequent cause of picking errors when mapped badly.
Questions

About ERP integration

Anything else, ask on the audit call.

Ask an engineer

Not answered here? Ask on the free 30-minute audit call. An engineer replies within one business day.

Quick facts

  • Based in Delhi, India Working across time zones, with written weekly updates.
  • Fixed quote first Nothing is billed before you agree it.
  • You own it The code, workflows and accounts are yours.
  • Stores and ERPs Shopify, BigCommerce, WooCommerce and Adobe Commerce, with NetSuite, SAP Business One, Odoo and Dynamics 365.
See all questions
Why not use an off-the-shelf connector?

Sometimes you should. We recommend a ready-made connector when your process is standard; we build custom syncs when you have custom fields, multiple locations, B2B terms or rules a connector cannot express.

Which ERPs do you integrate with?

We most often work with NetSuite (SuiteTalk REST and SuiteQL), SAP Business One (Service Layer), Odoo (JSON-RPC and XML-RPC) and Microsoft Dynamics 365 Business Central (OData v4 APIs), plus Acumatica, Brightpearl and Cin7.

Which system is the source of truth?

Usually the ERP for stock, prices and customers, and the store for new orders. We agree this field by field in the mapping file before anything is built.

What happens if the ERP is down?

Records queue and retry with growing waits. Nothing is lost; once the ERP is back, the queue drains in order and the daily reconciliation confirms the totals match.

Will you work with our ERP partner?

Yes. We work alongside your ERP partner or admin, use an integration user with only the permissions it needs, and share the mapping file for review.

How long does an ERP integration take?

Usually four to eight weeks for the core flows: orders, stock, prices and fulfilment. B2B rules, several warehouses or a very customised ERP add time. The parallel run at the end typically takes one to two weeks.

How much does it cost to integrate Shopify with an ERP?

Typical ranges run from about $8k to $20k for the core flows, plus hosting and an optional monitoring plan. The main cost drivers are the number of flows, how customised the ERP is, and how clean your product and customer data is. The fixed quote follows the audit.

Can you sync B2B prices and credit limits?

Yes. Customer-specific price lists, payment terms and credit limits usually live in the ERP and are pushed to the store’s B2B features.

Do you replace our ERP partner?

No. Your ERP partner looks after the ERP itself. We build and run the connection to the store and other systems, and we work with them on fields, custom records and test environments.

What if we change ERP later?

Because the mapping is written down as a file and the store-side logic is separate, switching ERP means rebuilding the ERP side of the connection rather than starting from scratch.

Can we see what the sync is doing?

Yes. Every run is logged, failures alert your team and ours, and a daily reconciliation report lists any differences. Many clients also add an operations dashboard on top.

Where do your numbers
disagree today?

Tell us the store, the ERP and the report nobody trusts. An engineer replies within one business day.

We save what you type here so we can follow up if you get interrupted.
One file, up to 10 MB: PDF, Word, Excel, CSV, text, PNG or JPG.

An engineer replies within one business day.

What happens next

  1. An engineer replies Within one business day, by email.
  2. A free 30-minute audit On a call with an engineer.
  3. A fixed quote It follows the audit. Nothing is billed before you agree it.
All services

Get a quote. One form, one real reply.

Tell us what you are building or fixing. An engineer reads every request and replies within one business day, with a fixed scope, price and dates once we have talked.

Direct
[email protected]
Response time
Within one business day
Cost of asking
Nothing. The first 30-minute audit is free.

An engineer replies, not a form queue.