An ecommerce storefront can accept orders around the clock, but the business still needs accurate inventory, pricing, customer records, fulfilment and financial data behind it. ERP and ecommerce integration connects the digital sales channel to the systems that run purchasing, stock, finance and operations. The right design reduces manual rekeying and gives teams a consistent view of what has been sold, promised, shipped and paid.
There is no single best integration platform for every retailer or distributor. A business with one Shopify store and a supported ERP connector has different needs from a multi-brand company running several storefronts, marketplaces, warehouses, payment providers and third-party logistics partners. Start with the data flows and operating model, then choose the integration approach.
What should an ERP and ecommerce integration handle?
Most projects involve several related data domains. Define the direction, frequency and business owner for each one.
| Data flow | Typical direction | Business control |
|---|---|---|
| Product catalogue and variants | ERP or PIM to ecommerce | SKU, descriptions, attributes, images, units and publication status |
| Pricing and discounts | ERP to ecommerce, sometimes bidirectional | Price lists, customer groups, currencies, promotions and effective dates |
| Inventory availability | ERP/WMS to ecommerce | Available-to-promise quantity, safety stock, locations and reservations |
| Customer and company records | Bidirectional where required | Identity matching, B2B accounts, addresses, tax details and credit terms |
| Orders and changes | Ecommerce to ERP | Order lines, shipping, tax, payment status, cancellations and fraud holds |
| Fulfilment and shipment | ERP/WMS/3PL to ecommerce | Pick, pack, tracking number, partial shipment and delivery status |
| Returns and refunds | Bidirectional | Return authorisation, restock decision, refund and credit note |
| Payments and settlements | Payment provider to ERP | Fees, payouts, reconciliation, chargebacks and cash application |
Not every organisation should make every flow bidirectional. For example, if the ERP owns product master data, allowing the storefront to overwrite core SKU attributes may create inconsistent records. Document the authoritative source for each field.
1. Choose the right integration architecture
Native ERP or ecommerce connector
A native connector is usually the first option to assess when your ERP and ecommerce platform have a supported integration. It can reduce implementation effort and provide a documented path for common objects. However, native does not automatically mean complete: check supported plans, regions, stores, B2B features, tax scenarios, returns, payment gateways, custom fields and error handling.
iPaaS or integration platform
An integration platform is useful when several applications must exchange data, such as an ecommerce platform, ERP, WMS, PIM, CRM, marketplace, tax service and 3PL. It can provide reusable mappings, orchestration, monitoring and retry controls. The trade-off is another subscription, operating layer and skill requirement.
Custom API or middleware development
Custom integration may be appropriate when business rules are distinctive, standard connectors do not support required workflows or performance and control requirements are unusual. It offers flexibility but transfers responsibility for version changes, authentication, monitoring, retries, support and documentation to your organisation or implementation partner.
| Approach | Best suited to | Primary risk to evaluate |
|---|---|---|
| Native connector | Standard workflows between supported products | Capability gaps and configuration limits |
| iPaaS | Multiple applications and reusable integration patterns | Platform cost, operational ownership and connector dependency |
| Custom API | Specialised workflows or unsupported business rules | Long-term maintenance and change management |
| Hybrid architecture | Standard core flows plus selected custom processes | Clear ownership and monitoring across multiple components |
2. ERP and ecommerce integration options to evaluate
The following are examples of product approaches and documented connector ecosystems, not a universal ranking. Availability and supported features vary by ERP edition, ecommerce plan, region and implementation design.
Microsoft Dynamics 365 Business Central with Shopify
Microsoft documents a Shopify Connector for Business Central. Its documented capabilities include synchronising products or items, inventory, customers and companies, sales orders, fulfilment information, transactions and payouts. The connector also supports multiple Shopify stores and background synchronisation through job queues. This is a sensible starting point for organisations whose requirements align with the standard connector; validate B2B pricing, tax, variants, locations and exception handling against your actual process.
Oracle NetSuite connectors
Oracle documents NetSuite connectors for ecommerce channels including Shopify, BigCommerce, Adobe Commerce and WooCommerce. Its connector overview describes flows involving products, pricing, inventory, orders, customer information and fulfilment status, with certain applications also supporting settlement, refunds, returns and cancellations. Confirm the precise connector and channel combination because coverage differs by application.
Acumatica commerce connectors
Acumatica documents commerce connectors for channels including Shopify, BigCommerce and Amazon. Its published capabilities cover product, pricing, inventory, customer and order synchronisation, with workflows for fulfilment and returns also described. This can be relevant to distributors and retailers that need connected inventory, warehouse, finance and commerce processes.
Integration platforms and specialist connectors
When a direct connector is insufficient, evaluate iPaaS and ecommerce-focused integration providers such as Boomi, Celigo, MuleSoft, Jitterbit, DCKAP Integrator, Patchworks or similar products against your exact ERP and storefront combination. Do not assume a vendor supports every ERP module or ecommerce feature simply because it advertises a connector. Ask for a working demonstration of your highest-risk transaction flows.
3. Build around order lifecycle, not just order creation
Importing an order into ERP is only one step. A complete workflow must handle payment authorisation, credit checks, inventory reservation, picking, partial shipment, tracking, invoicing, cancellation, returns and refunds. Agree the status model between systems so a customer does not see an order as shipped when only one line has left the warehouse.
For B2B commerce, additional rules may include customer-specific catalogues, negotiated price lists, purchase order numbers, payment terms, credit limits, account hierarchies and approval workflows. Confirm that the integration supports the required B2B data model rather than assuming a B2C connector will cover it.
4. Decide between real-time and scheduled synchronisation
Real-time events can be important for inventory availability, order acknowledgement and shipment updates. Scheduled batch processing may be sufficient for product enrichment, catalogue updates or less time-sensitive financial reconciliation. A hybrid approach is common.
Set a freshness requirement for each data domain. For inventory, estimate the cost of stale stock data and overselling. For product descriptions, a delay of several minutes may be acceptable. For financial settlement, a controlled reconciliation cycle may be more reliable than trying to process every event synchronously.
5. Design for failures and reconciliation
Integrations fail because of expired credentials, API limits, invalid addresses, missing SKUs, tax mismatches, duplicate events, unavailable services and unexpected data formats. A production design needs more than a success message on the first test order.
- Idempotency: repeated messages should not create duplicate orders, invoices or payments.
- Retries: transient errors should retry safely, with limits and backoff.
- Dead-letter handling: records that cannot be processed should be visible to an owner and recoverable.
- Monitoring: track failed jobs, queue depth, processing delay and records awaiting acknowledgement.
- Reconciliation: compare order counts, totals, inventory movements, refunds and payouts across systems.
- Audit trail: retain source identifiers, timestamps, status history and error details.
For example, if an ecommerce order is accepted but ERP import fails, the storefront should not silently treat the transaction as fully processed. Define how the customer, support team and operations team are notified and how the record is safely replayed.
6. Calculate total cost of ownership
Compare more than connector licence fees. The total cost can include:
- Native connector, iPaaS or middleware subscription.
- Implementation discovery, mapping and configuration.
- Custom API development and testing.
- Data cleansing, SKU rationalisation and customer deduplication.
- Additional environments, monitoring and security controls.
- Ongoing support, connector upgrades and API version changes.
- Internal effort from finance, ecommerce, warehouse, customer service and IT teams.
- Costs of failed orders, overselling, manual reconciliation and delayed fulfilment.
Use a representative transaction volume and peak-season scenario when sizing the platform. Include the cost of adding a second store, marketplace or warehouse, because an architecture that is inexpensive for one storefront may become costly as channels expand.
7. Questions to ask during a platform demonstration
- Can you demonstrate the complete order lifecycle, including partial shipments, cancellations and returns?
- How are product variants, bundles, kits, units of measure and customer-specific pricing mapped?
- How are inventory reservations and multi-warehouse availability calculated?
- Which B2B features are supported, including company accounts, purchase orders and payment terms?
- How are failed messages logged, retried, alerted and reconciled?
- What are the API rate limits, throughput assumptions and peak-volume constraints?
- Who owns custom mappings and how are they maintained after ERP or storefront upgrades?
- Can we export logs and integration configurations if we change providers?
Implementation checklist
- Map the order-to-cash process from storefront through finance and fulfilment.
- List all connected systems, data objects and system-of-record decisions.
- Document B2C and B2B requirements separately.
- Confirm native connector coverage and identify gaps.
- Define event timing, inventory freshness and order acknowledgement targets.
- Design error handling, idempotency, monitoring and reconciliation.
- Cleanse product, customer and pricing data before migration.
- Test normal, peak, exception, cancellation, return and refund scenarios.
- Train business owners and assign ongoing integration support.
- Measure order processing time, manual touchpoints, inventory accuracy and integration failure rate.
Conclusion
The strongest ERP and ecommerce integration is the one that supports the business’s actual order, inventory, fulfilment and finance processes with clear data ownership and operational controls. Start with a native connector when it meets the requirements, consider iPaaS when orchestration across multiple systems is needed, and use custom development only where the business case justifies the ongoing ownership.
For a broader view of integration architecture, see our ERP integration strategy. Businesses evaluating Business Central can also review our Business Central licensing before finalising the application and user model.
