ERP integration

ERP integration services that connect your store, CRM and warehouse to one ERP

We connect the ERP you run to the systems around it, decide which one owns each record and build the queue for what fails.

Scope your ERP integration
Trusted by the world's fastest-growing brands

What an ERP integration is

One system owns each fact, and the others read it

ERP integration services connect the system that holds your items, prices, orders and invoices to the store, the CRM, the warehouse and the EDI feeds around it. The build is a set of agreed rules about who owns each record and which way it travels.

Item 20417Louisville, KYSample Ironwood Trade SupplyHubSpot · quote$18.40Shopify store · product$18.40Business CentralOwnerDescription3/4 in. brass ball valveTrade price$18.40Available312

Ownership

A price, a credit limit or a stock count has one home. Everything else shows a copy and cannot overwrite it. The ownership map is written with you before the build, because two systems that both accept edits can disagree.

Direction

A flow runs one way, with a stated trigger: an order placed in the store creates a sales order in the ERP, a posted invoice updates the store. Where a record needs to travel both ways, we split it by field, so each field still has a single owner.

Proof

Connected systems can drift, through a missed delivery, a rejected record or a manual edit. A reconciliation compares counts between systems and lists the gaps. You see which records differ and why, in a log you can open any day.

Two ways to connect an ERP

A scoped integration, or a prebuilt connector

Both put data from one system into another. They differ in who decides ownership, how your own fields are handled and what is left when a record fails.

Prebuilt connector or marketplace appInstalled and configuredIntegration scoped to your flowsWritten, then built
Ownership rulesSet by the connector’s defaults, adjusted in its settingsWritten with you for each record before the build starts
Your own fieldsCovered where the connector has a matching fieldMapped one by one, including custom fields and your item numbering
Failed recordsShown in the connector’s log, in the connector’s own formatHeld in a queue you can read, with the reason and a named person
ReconciliationAdded separately if the connector offers oneA count comparison between systems, set up as part of the scope
Cost shapeA subscription for the connector, plus setup timeA quoted scope, flow by flow, plus the vendors’ own plans
When each one fits

A prebuilt connector fits when two systems have a connector with the flows you need and your data follows the vendor’s standard shape. A scoped integration fits when you have custom fields, customer-specific pricing, several systems around one ERP or an EDI feed, or when you want the failure handling written down.

What the sources say

Six vendor limits that shape the design

Each one comes from the vendor’s own documentation, with the page and the date we read it under the claim. We read the limits for your edition before we scope.

  1. Store limitsShopify, by plan

    Shopify sets the GraphQL restore rate by plan: 100 points a second on Standard and 2,000 on Shopify for enterprise.

    Advanced is 200 and Shopify Plus is 1,000. A single query may not exceed 1,000 points on any plan. We read your plan before scoping a stock or price push, and we size the batches to it.

  2. DuplicatesShopify webhooks

    Shopify’s webhook guidance says to ignore duplicate deliveries using the X-Shopify-Webhook-Id header.

    An order notice can arrive twice. If the integration creates a sales order each time, the warehouse picks the order twice. We store the delivery id and check it first, so a repeat is logged and dropped.

  3. Missed deliveriesWhy we reconcile

    Shopify says webhook delivery isn’t always guaranteed, and recommends reconciliation jobs that fetch data periodically.

    The same page says an app shouldn’t rely on receiving data from webhooks alone. So the design pairs each webhook with a comparison job that finds orders the notice never delivered.

  4. Request rateBusiness Central

    Business Central online allows 6,000 OData requests per user in a 5-minute sliding window, and answers with a 429 above that.

    Microsoft’s own page says an integration should already have retry logic with a cool-off period. We build the wait and the retry, and we count the calls a full item load needs before it is run.

  5. ConcurrencyBusiness Central

    Business Central allows 5 concurrent OData requests per user, and queued requests time out after 8 minutes with a 503.

    The page also lists a maximum of 100 operations in one $batch request. Microsoft suggests spreading a heavy workload across several users or service principals. That choice belongs to your administrator, and we raise it in the scope.

  6. Shared capacityNetSuite

    Oracle says a NetSuite account limits how many requests can be made to web services and RESTlets at once, and that part of it can be allocated to specific integrations.

    The store, the warehouse system and ours may all draw on that one account limit. We ask your administrator for a named allocation for the integration we build, so a busy import elsewhere does not starve it.

The scope

What ERP integration services produce

Six parts of one working integration. Each part is built in accounts you own and comes with a document describing it.

Company · HubSpotSplit by fieldOwned by HubSpotDeal stageQuote sentMain contactPurchasing managerRead by the ERPOwned by the ERPCredit termsNet 30Bill-to addressLexington, KYRead by CRM, store

The ownership map

We list each record the systems share, name the one that owns it and mark the others as read-only. Customer data is split by field where two systems need to edit. You receive: an ownership map showing, for each record, its owner and who reads it.

Field map · order line2 rulesStore SKUPX-050-B25Item lookupERP item no.31206Store quantity2 boxes of 25× 25ERP quantity50 each1 box of 25 posts as 25 each in the ERP.

Field mapping

We match each field in one system to its place in the next, including custom fields, units of measure and item numbering, and write the conversion rules in plain sentences. You receive: a field map with each source field, its target and any rule applied on the way.

Sync rule · itemsOne wayFlowItems and pricesDirectionBusiness Central to storeMatch onItem numberTriggerItem or price edited in the ERPFirst load: 4,200 items42 batches of 100

Sync rules

Each flow gets a direction, a trigger and the key that matches a record in both systems, so an order is found again instead of created twice. We also size the call volume against the vendor’s limits. You receive: a sync rule sheet listing each flow, its direction and its matching key.

Error queue7 heldUnmapped item3 ordersGoes toCatalog managerThenRetried once the item is mappedCredit hold2No tax certificate1Invalid ship-to address1429 replies wait, then retry

The error queue

A record that fails a rule, such as an unmapped item or a credit hold, goes to a queue with the reason attached and a named person to act on it. Rate-limit errors wait and retry. You receive: a list of error types, who handles each and what the retry does.

ReconciliationSample dayShopify storeBusiness Central212placed205sales orders7error queue205 + 7 = 212, counts agree

Reconciliation

We compare counts and totals between the systems, such as orders placed against sales orders created, and list each gap with its cause. The scope sets when the comparison runs. You receive: a reconciliation log showing the counts, the gaps and the reason for each.

Sandbox tests6 of 6 passedsandbox · Business CentralSame order notice delivered twiceItem number not mappedCustomer on credit holdERP answers 429 Too Many RequestsTax-exempt buyer, no certificatePrice changed in the ERPSwitch-onAfter your approval

Test plan and cutover

We run the integration against a sandbox copy of your ERP with test cases for the failures you fear most, then agree the switch-on with you. Sign-ins use accounts in your name. You receive: the test results, a cutover checklist and the access list showing who holds each login.

How it runs

From a tangle of systems to an integration you can audit

Each stage starts after you approve it and ends with a document for your files. The samples follow a fictional wholesale distributor, Sample Ironwood Trade Supply in Louisville, KY.

ownership-map.csv

Ownership map

Sample · Sample Ironwood Trade Supply, Louisville, KY
RecordOwned byRead by
Items and price listsBusiness CentralStore, CRM quotes
Bill-to address and credit termsBusiness CentralCRM, store
Contacts and deal stagesHubSpotBusiness Central, read only
Web order as placedShopify storeBusiness Central
Picks and shipmentsWarehouse systemBusiness Central
Invoices and paymentsBusiness CentralStore, CRM
Customer purchase ordersEDI providerBusiness Central
Five systems share these records: Business Central, the Shopify store, HubSpot, the warehouse system and the EDI provider. The customer is the one record with two owners, split by field: the ERP owns billing and terms, the CRM owns contacts and stage.

Our stack

The systems an ERP integration touches

The ERP is yours and so are these accounts. We read each system’s own documentation for its limits and pick the connection method by the job.

Shopify
Why Shopify

An online store platform with an Admin API, webhooks and a rate limit set by the store’s plan.

How we use it

We connect a trade or retail store to the ERP: orders go in, and prices, stock and invoice status come back. We read your plan’s limit first and keep a record of each webhook delivery.

Time to launchCheckoutFor D2C
ShopifyBuilt-in
WooCommercePlugin
CustomBuild

Questions

ERP integration services, answered

Start here

Get the flows and the price in writing

Tell us which ERP you run and what needs to connect first. You get a written scope with the flows, the owner of each record and the price, and you decide after reading it.