Ecommerce ERP: connect product, stock and orders
An ERP comparison for retail product, purchasing, inventory and financial records, with clear ownership of each connection to the storefront.
- Published
- Last updated
Ecommerce ERP integration connects your online store to the system that manages purchasing, stock and financial records. Give each field an owner before choosing a connector. The right connection carries a sale through to fulfilment and accounting without creating a second version of the order.
You need an ERP when several channels or teams need shared operational records and your existing tools cannot keep those records consistent. A smaller retailer can keep a storefront, inventory application and accounting package if their connections cover the actual workflow.
What an ERP adds to an online store
Enterprise resource planning (ERP) brings business processes and their records into a shared system. For a retailer, that can include suppliers, purchasing, inventory, sales and the financial ledger.
The commerce platform runs the catalogue, basket and checkout your customers use. An inventory application controls quantities and locations. An order management system routes orders through fulfilment. An ERP can include some of those functions, but buying one does not settle which application owns each task.
Consider a retailer selling the same products online, through shops and to wholesale accounts. Purchasing needs supplier costs, the warehouse needs available quantities and finance needs posted invoices. Shared records help when those teams otherwise enter the same transaction repeatedly.
A single-store retailer with straightforward stock can have a smaller connected setup. Keep it when staff can reconcile orders and receipts, stock updates arrive within the selling window and exceptions have an owner. Add an ERP for an operational requirement, such as purchasing across warehouses, rather than a connector’s list of logos.
Give each record one source
Assign ownership at field level, because one universal master rarely fits every record. Your ERP can own the item number while your merchandising team owns the storefront description.
A retail record map
| Record | Suggested authority | What crosses the connection | Exception owner |
|---|---|---|---|
| Product identity | ERP or existing product register | Stable item number, stock keeping unit (SKU), variant and destination ID | Catalogue manager |
| Descriptive content | Storefront or product information management application | Approved title, images and customer-facing attributes | Merchandising team |
| Price | ERP price list or storefront, by selling context | Currency, tax basis, customer tier and effective price | Commercial manager |
| Availability | Inventory authority | Sellable quantity by location, with reservations and safety stock applied | Stock controller |
| Order | Storefront at checkout, then ERP for processing | Order ID, lines, discounts, tax and payment reference | Order operations |
| Tax and posted accounts | Finance system | Tax codes, invoice totals and posted document references | Finance team |
| Refund | Payment provider for money movement, finance for the credit | Refund ID, amount, original transaction and credit reference | Finance team |
These are design choices for your implementation, not defaults shared by every connector. Wholesale prices might come from ERP customer agreements while storefront promotions own a separate discount. Define their precedence so both systems do not overwrite the final selling price.
Keep a mapping between the ERP item ID and the storefront’s product and variant IDs. A SKU helps staff recognise the item, but it must remain unique within the agreed scope. A reference joins the records without copying supplier costs or internal warehouse notes into the public catalogue.
Record the destination ID when an item is created. If staff rename its SKU later, update the mapping deliberately. Treating the new SKU as a new product can split stock and leave the original listing available for sale.
Choose the integration method
Choose the connection that supports your edition and required data flows, then assess how it handles failed updates. A bidirectional connection can send different objects in different directions. It does not mean every field can safely be edited at both ends.
Connection methods compared
| Method | Objects and direction | Timing | Access | Failure handling |
|---|---|---|---|---|
| Supported connector | Its documented product, stock and transaction objects | Events, scheduled jobs or manual runs | Authorised application and system permissions | Connector logs, queues and supported recovery |
| Middleware | Mapped objects across several applications | Per-flow schedules or events | Separate credentials for each endpoint | Central retries, routing and alerts |
| Custom application programming interface (API) connection | Only the endpoints and fields you implement | Polling or events within rate limits | Scoped API credentials | Your team builds duplicate protection and recovery |
| Controlled file transfer | Agreed import/export fields | A scheduled batch or supervised transfer | Restricted file location and import rights | Validation, rejected-row report and reconciliation |
An ecommerce integration platform is the connection layer. It maps fields, orders dependent steps and monitors delivery. The ERP owns the business records and posting rules. Middleware can repair an awkward connection without replacing an ERP that still meets your operational needs.
Choose middleware when a sale needs coordinated updates across several systems or the supported connector cannot express the mapping. Keep a direct connector when it already covers the workflow and staff can diagnose its exceptions. Budget for monitoring in either case.
Documented ERP and connector options
The matrix separates product editions and connection methods. Where a vendor describes a product family without release numbers, use its named edition for selection and put exact installed builds in the implementation contract. A family-level listing is insufficient evidence for a particular release pair.
| ERP edition or family | Store and method | Product and stock flow | Order and accounting flow | Timing and boundary |
|---|---|---|---|---|
| Dynamics 365 Business Central online | Shopify, Microsoft Shopify Connector | Configurable item direction; inventory from Business Central to Shopify | Shopify orders, transactions and refund information into Business Central; fulfilment back | Job queue and order notifications; on-premises Business Central is excluded |
| Dynamics 365 Finance and Supply Chain Management | External store through a selected connector or data-entity integration | Map released products and inventory through the chosen interface | Map sales documents separately | Entity and connector dependent; Business Central’s connector does not cover these applications |
| Dynamics NAV, GP or AX | Existing installation with a version-matched partner or custom connection | Define supported item and quantity endpoints for the installed release | Specify order creation and posting objects separately | Do not apply Business Central online instructions to these products |
| MYOB AccountRight | WooCommerce, MYOB Integration extension | MYOB product and quantity updates to WooCommerce | WooCommerce orders create MYOB orders or invoices and customer records | Inventory polling frequency is configurable; variable-product support needs care |
| MYOB Acumatica, formerly MYOB Advanced | Shopify for MYOB Acumatica, listed by MYOB | Scope product, price and stock entities for this connector | Scope order and financial-document entities separately | A different connection from AccountRight; edition and enabled entities decide the project |
| MYOB EXO or MYOB Business | Select a connection for that named product | Specify item and stock scope independently | Specify invoice, payment and tax scope independently | AccountRight or Acumatica compatibility does not establish EXO or Business compatibility |
| NetSuite ERP | Shopify or Shopify Plus, Oracle NetSuite Connector | Full product or price/quantity mappings from NetSuite | Store orders into NetSuite; fulfilment information back | Connector sync mechanisms and enabled flows apply; payment processing is a separate decision |
| SAP Business One | Shopify, Business One Integration Hub | Map the hub’s item and stock objects for the installed combination | Shopify order data into Business One | Use the Integration Hub guide and its supported patch combination; do not substitute ECC instructions |
| SAP ECC, S/4HANA or Business ByDesign | A separately selected store connector or API design | Specify materials/products and stock by that SAP product | Specify sales and accounting objects by that SAP product | Business One hub support grants no compatibility for these systems |
| Sage 100 / 100cloud | Shopify or WooCommerce through CertiPro E-Link | Product, price and inventory mapping | Customer and order mapping through E-Link | Sage marketplace describes near-real-time two-way integration |
| Sage 300 | CertiPro E-Link, with the contracted storefront mapping | Scope the product and stock flows for Sage 300 | Scope orders and account fields for Sage 300 | CertiPro lists Sage 300 compatibility; do not copy the Sage 100 release assumptions |
| Odoo 19 | Odoo eCommerce, integrated application | Odoo product catalogue and inventory settings | Sale, delivery and invoicing within Odoo | This is Odoo’s own store; Shopify and WooCommerce require separately selected connectors |
| Cin7 Omni | Shopify, Omni integration | Product download/upload, stock and price upload | Sales, refunds and customers download; transaction status upload | Automatic options depend on the integration settings; Cin7 Core has separate documentation |
| Pronto Xi | Pronto Xi eCommerce or Avenue by Pronto Woven | Integrated inventory, product and pricing information | Online order and customer-account workflows | Pronto describes real-time data sync; specify the Xi and commerce releases together |
| Priority ERP | WooCommerce via WooToERP or another Priority marketplace connector | Contract the connector’s product and stock scope | Contract order and accounting scope | A marketplace listing establishes the named option, not every version or object |
| SYSPRO | Shopify or WooCommerce through Modern Retail’s integration | Use the selected integration’s stock and product mapping | Define the supported sales-order and return flow | Partner connection; agree supported SYSPRO build and schedule before implementation |
| Jiwa 7 | Jiwa eCommerce integration or REST API connection | Map Jiwa item and stock records to the chosen store | Define order and debtor-document handling | Jiwa documents ecommerce and API routes; a Shopify or WooCommerce project still needs its own mapping |
| Intact iQ | Experlogix Digital Commerce through its REST interface | Regular active-product import, pricing and stock information | Online sales orders; account history, invoices and credit notes | Customer pricing can use a web-service call; requires Intact’s System Administrator API licence |
| Unleashed | Shopify through Unleashed’s integration | Product synchronisation and available quantity export | Shopify orders into Unleashed reduce availability | Stock export is periodic when enabled; retain a separate accounting connection where needed |
Microsoft’s Shopify Connector overview describes the Business Central objects and job queue. Its technical compatibility guidance confines that connector to Business Central online. Match your Business Central release to the connector’s supported Shopify API version.
For WooCommerce ERP integration, the extension is part of the operating setup. WooCommerce’s MYOB Integration documentation identifies AccountRight and warns about variable-product import and sync. Its detailed sync guide describes additional variation handling. Use a representative variant in acceptance testing instead of assuming the broader description covers your catalogue.
For MYOB ecommerce integration, first identify AccountRight, Business, EXO or Acumatica. Their names are not interchangeable. The Shopify and MYOB integration guide covers that narrower connection decision.
Oracle distinguishes full-product mappings from price/quantity mappings. A retailer can keep merchandising content in Shopify while updating stock and price from NetSuite. Connecting NetSuite to a payment gateway is another flow: map authorisation, capture, refund and settlement references without mistaking an imported order for cleared money.
A broad Zoho request also needs the product name first. Zoho Inventory, Books and Commerce have different responsibilities. Name the application and the WooCommerce objects it needs before selecting an extension. AI agents in an ERP do not establish a storefront connection or change who owns posted records.
Food distribution needs a more detailed stock map
For food distribution, map the selling unit separately from the stocking unit. A case of twelve and a single bottle need an explicit conversion. Identify which system allocates the batch and checks expiry before committing a delivery.
Decide whether the storefront needs individual batch data or only a sellable quantity that already excludes unavailable stock. Test mixed units and an expired batch against the selected connector’s actual fields. Inventory support alone does not prove that batch numbers, expiry dates or variable-weight quantities cross the connection.
Keep the buying journey consistent
Carry each authoritative change through to the storefront before customer-facing systems promise its result. A successful update in the ERP proves only that the source changed.
After a stock receipt, the inventory authority calculates sellable quantity and the connector sends it to the mapped storefront location. Customer-support answers must use that updated availability. If the update fails, staff need a visible exception and a rule for suppressing an unsafe stock promise.
When a customer places an order, preserve the storefront order ID as the ERP creates its processing document. Carry tax, shipping and discount values with the lines. Record the payment transaction separately so a pending authorisation does not become a statement that the invoice is paid.
For a refund, join the payment provider’s refund reference to the original order and the accounting credit. A returned item becomes available again only after the stock authority accepts it for resale. A refund alone does not establish that the item is back on the shelf.
A repeated order notification must resolve to the same imported order. A delayed stock message must not replace a newer quantity. A changed SKU must still identify the original variant. These failures can otherwise cause duplicate orders or false availability and payment answers.
Scope and verify the implementation
Price the connection against a written record and channel scope. Name stores, warehouses, currencies, tax treatments, price lists and the objects moving between them. Include the expected order volume and update frequency.
Separate ERP and storefront subscriptions from connector licences. Cost migration and catalogue cleaning as project work. Add ongoing monitoring, API upgrades and staff time for reconciling exceptions. A low connector fee can leave those operating costs with your team.
A Business Central and Shopify handover
This fictional example applies Microsoft’s documented item mapping and order/refund settings. The identifiers and quantities are illustrative. It describes an acceptance exercise, not an observed customer implementation.
The retailer chooses Business Central online as the item and stock authority. Shopify owns the merchandising description and checkout. Item LAMP-42 maps to Shopify variant 90042 through the SKU mapping. The stock controller owns inventory exceptions and finance owns posting differences.
- Export or map LAMP-42, then compare the saved Shopify variant ID with the Business Central item. Disable description overwrites in the agreed mapping so merchandising text stays intact.
- Start with ten sellable units at the mapped location. Run inventory sync and compare Shopify’s saved quantity with the selected Business Central stock calculation.
- Place illustrative order S-204 for two units at $55 each, including tax. Import it and compare the $110 total, line quantities and payment reference. Finance checks the tax calculation before posting.
- Confirm the imported order maps to one Business Central sales document. Reprocess the same notification and inspect the linked documents. The acceptance result must remain one order, without another stock deduction or payment request.
- Refund one unit for $55 through the agreed payment workflow. Import the refund using the configured return/refund mode. Compare the credit with the original line and confirm whether the returned unit qualifies for restocking.
- Run stock sync again and inspect the storefront record and customer-support answer. A resellable return restores one unit only after the stock record reflects it.
Microsoft’s sales order and refund workflow separates importing refund information from automatically creating credit memos. Its tax guidance also explains that Business Central recalculates tax when creating sales documents. A matching storefront total must therefore be checked before finance posts the transaction.
Run the handover first in isolated test environments with non-production payment methods. Add a deliberately failed update, then repair and replay it. Record who sees the failure and who can approve recovery. Grant the connection only the permissions its chosen objects require.
Compare saved records after each step, including after a reload, and keep the source and destination references together. Agree a rollback and reconciliation procedure before opening the connection to live orders. If order routing is the unresolved problem, use the ecommerce order management software guide to settle that responsibility before buying another system.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.