Skip to main content
Talk to an expert
Shopify logo

Shopify integration for ecommerce

Shopify orchestrated with ERP, PIM and operational systems cleanly. Shopify is the commerce platform layer. iWeb defines the flows to ERP, PIM, payments, fulfilment, search, marketplaces and CRM so products, stock, pricing, orders and customers stay in step. Integrates with the ERP, PIM, OMS and operational systems commerce teams already run.

Also searched as: commerce platform, storefront, online store, shop platform, commerce engine.

Your systemsiWeb integration layerShopify
Talk to an expertSee the estate map ↓
Works with - SAP, NetSuite, Sage, Infor ERP (finance, invoicing, customer master) · Contentful, Salsify, Akeneo PIM (product catalogue, attributes, media) · Blue Yonder, Manhattan Associates OMS (order routing, inventory allocation) · Elastic Search, Algolia, Searchspring (search indexing, merchandising) · Stripe, Adyen, Square payment processor (payment authorisation, capture, refunds)
On this pageGet a brief reviewed
01 · What you get

What a Shopify integration gives you.

Product catalogue published cleanly

Products, attributes, media and taxonomies from PIM flow to Shopify without gaps, manual steps or data loss. Category trees, variant logic and asset links stay governed and consistent.

Stock and pricing always current

Shopify checkout reflects real-time stock from ERP or OMS and pricing from the source system. Overselling, stale pricing and customer-facing errors drop significantly.

Orders handed off reliably

Orders captured in Shopify reach ERP, OMS and fulfillment systems with full context - customer, items, addresses, payment status. Acknowledgements and fulfillment status flow back so both systems stay in sync.

Customer experience unified

Customers logging in, building carts, checking order status and receiving marketing all work against a single customer record shared with ERP and CRM. No duplicate accounts, lost orders or untracked refunds.

Operational visibility across systems

You know when Shopify, PIM, ERP or payment sync is broken before customers complain. Monitoring dashboards show data flow health, exception queues and drift so operations can act.

Multi-channel inventory controlled

Stock is allocated, reserved and synchronised across Shopify, branches, marketplaces and other channels without overselling. Shopify stays in step with true available inventory.

02 · When it's worth it

Where a Shopify integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Publish product catalogue, attributes and media from PIM to storefront in real time
Sync stock availability from ERP or OMS to checkout without overselling
Route orders from Shopify checkout into ERP, OMS or warehouse systems for fulfillment
Reflect pricing, promotions and customer-specific offers from ERP or pricing rules
Handle refunds, chargebacks and payment reconciliation back to finance systems
Ingest Shopify customer events into CRM, marketing platform or CDP for engagement
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Catalogue publishing requires manual structure mapping

Shopify's default product import does not enforce PIM taxonomy, completeness rules or asset transformation. You must define which PIM attributes map to Shopify product fields, which to metafields, and how to handle variants, bundles or options that Shopify's schema may not natively support.

Stock sync is not natively multi-location or reservation-aware

Shopify tracks simple inventory at the location level but does not natively handle ERP stock holds, allocated stock, serial number tracking or split fulfillment across multiple warehouses. The integration must manage that logic outside Shopify.

Order routing and split fulfillment require external logic

Shopify captures orders but does not natively route them to branch, warehouse or dropship locations based on inventory, cost or customer account rules. OMS or fulfillment integration layer must handle that decision and send dispatch instructions to the right system.

Pricing and promotion rules are storefront-only

Shopify's discount and pricing rules live on the storefront and do not sync back to ERP. If pricing changes in ERP or for a customer account, the integration must push those changes to Shopify; Shopify cannot reverse-sync that logic.

Customer account data is not natively ERP-linked

Shopify stores customer email and shipping address but does not natively link to ERP customer master records, credit limits, payment terms or account hierarchies. The integration must manage that mapping and keep records in sync bidirectionally.

Returns and refunds lack exception visibility

Shopify refunds are manual or rule-based but do not natively integrate with ERP credit-note workflows or WMS returns handling. The integration must route returns to the right system and reconcile refund status back to Shopify.

04 · The real work

The gap most teams miss is that Shopify owns the storefront experience and checkout, but does not own product truth, pricing source, stock authority or order finance - those live in neighbouring systems and must stay in sync deliberately.

05 · Where it sits

Where this integration sits in your estate.

Shopify is the commerce platform - the customer-facing experience, catalogue, checkout and account area. The iWeb integration layer wires it into the ERP, PIM, OMS, WMS and payments systems it depends on. The estate map helps agree ownership before anything is built.

Where the customer sees your business. Shopify depends on clean feeds from ERP, PIM and fulfilment to keep that view accurate.

Customer-facing commerce
Commerce platform
Shopify
Commerce platform and customer-facing storefront layer
  • Product catalogue and storefront merchandising
  • Shopping cart and checkout experience
  • Customer session and login state
  • Order capture at point of sale
iWeb integration layer
Systems behind the platform
Systems it depends on
SAP, NetSuite, Sage, Infor ERP (finance, invoicing, customer master)Contentful, Salsify, Akeneo PIM (product catalogue, attributes, media)Blue Yonder, Manhattan Associates OMS (order routing, inventory allocation)Elastic Search, Algolia, Searchspring (search indexing, merchandising)Stripe, Adyen, Square payment processor (payment authorisation, capture, refunds)Shopify Flow, Zapier middleware (lightweight workflow automation)Amazon, eBay, Faire marketplace connector (channel listing, order sync)HubSpot, Klaviyo CRM (customer events, email, segmentation)
  • Product detail page display and search results
  • Promotion and discount application at checkout
  • Customer account profiles and order history
  • Payment capture initiation
Connected neighbours
Integration layer
ERP
Source system for customer master, base pricing, stock, invoicing and finance reconciliation
Integration layer
PIM
Master product catalogue, attributes, taxonomy, descriptions, images and metadata
Integration layer
OMS
Order routing, inventory allocation, split fulfillment and order status orchestration
Integration layer
WMS
Warehouse operations, pick and pack, dispatch confirmation and stock movement
Integration layer
Payment processor
Payment authorisation, capture, refund settlement and reconciliation
Integration layer
CRM and marketing
Customer engagement, segmentation, email campaigns and behavioural analytics
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb wires Shopify into whatever ERP, PIM, OMS, WMS, payments and operational systems your estate already runs.

Systems behind the platform (examples)
  • SAP, NetSuite, Sage, Infor ERP (finance, invoicing, customer master)
  • Contentful, Salsify, Akeneo PIM (product catalogue, attributes, media)
  • Blue Yonder, Manhattan Associates OMS (order routing, inventory allocation)
  • Elastic Search, Algolia, Searchspring (search indexing, merchandising)
  • Stripe, Adyen, Square payment processor (payment authorisation, capture, refunds)
  • Shopify Flow, Zapier middleware (lightweight workflow automation)
  • Amazon, eBay, Faire marketplace connector (channel listing, order sync)
  • HubSpot, Klaviyo CRM (customer events, email, segmentation)
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into COMMERCE
←From COMMERCE
↔BOTH WAYS
Product and media publish: Product attributes, descriptions, images and variants flow from PIM into Shopify as the storefront catalogue
Updates to attributes, category trees or asset links trigger refreshes so storefront content stays in step with the master record.
Stock and pricing sync: Stock availability and base pricing flow from ERP or OMS into Shopify checkout
Promotion rules, tiered pricing or customer-specific discounts layer on top depending on the buyer or channel context.
Order ingestion into ERP or OMS: Orders captured in Shopify checkout are sent to ERP for invoicing, to OMS for routing and fulfillment, or directly to warehouse systems
Order acknowledgement and fulfillment status flow back to Shopify so customers see tracking and status updates.
Payment and settlement: Payment intent and authorisation flow from Shopify into the payment processor
Capture, refund and settlement events come back to Shopify and are reconciled against ERP for accounting.
Customer and behavioural events: Customer identity, consent, browse events, cart abandonment and purchase history flow from Shopify into CRM, marketing automation or CDP platforms for engagement, segmentation and personalisation.
Marketplace and channel listing sync: Shopify can serve as the source for marketplace listings on Amazon, eBay or other channels, or receive orders from those channels
Stock, pricing and product data synchronise bidirectionally to keep listings current.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Data mapping and transformation

    iWeb designs how PIM attributes, media and variants transform into Shopify product schema, metafields and options. You define the source rules; iWeb handles the technical pipeline.

  2. 02
    Stock and inventory governance

    iWeb builds the layer between ERP, OMS and Shopify so stock is published to checkout without overselling, respecting location, hold and allocation rules from the source system.

  3. 03
    Order routing and fulfillment handoff

    iWeb designs how Shopify orders are routed to the correct warehouse, branch, dropship partner or OMS based on inventory and business rules. Dispatch instructions, tracking and returns flow back cleanly.

  4. 04
    Customer and payment reconciliation

    iWeb ensures customer records in Shopify link to ERP accounts, that payment captures and refunds reconcile to finance, and that credit limits and pricing rules are respected.

  5. 05
    Monitoring and exception handling

    iWeb builds alerting so data flow gaps, sync failures, catalogue drift and order rejections are surfaced before launch. Exception queues are owned and cleared regularly.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataProduct catalogue, attributes, descriptions, media and variants
Source / ownerPIM
Maintained byProduct data team
NotesShopify receives the published catalogue; PIM owns the master copy and change control.
DataStock availability and allocation
Source / ownerERP or OMS
Maintained byOperations / warehouse
NotesShopify displays stock for checkout; ERP or OMS owns the true inventory state and allocation rules.
DataBase pricing and promotion rules
Source / ownerERP or pricing rules engine
Maintained byMerchandising / pricing team
NotesShopify displays prices and promotions; ERP or rules engine owns the source and change authority.
DataOrders and order detail
Source / ownerERP or OMS
Maintained byOrder management / operations
NotesShopify captures orders; ERP or OMS owns the order record for invoicing, fulfillment and finance.
DataCustomer accounts and credit limits
Source / ownerERP
Maintained byCredit / sales team
NotesShopify stores customer contact and session data; ERP owns account master, terms and credit rules.
DataPayment authorisation, capture and refund
Source / ownerPayment processor
Maintained byPayments team
NotesShopify initiates transactions; payment processor owns settlement and reconciliation back to ERP.
DataFulfillment status and tracking
Source / ownerWMS or fulfillment system
Maintained byWarehouse / logistics team
NotesShopify displays status to customer; WMS owns dispatch confirmation, tracking and returns.
10 · Experienced integrator

Built Shopify integrations at scale

iWeb has built hundreds of commerce integrations, including many where Shopify is the storefront and the operational estate includes ERP, PIM, OMS and payment systems. We understand how Shopify fits, what it owns and what must be connected outward, and we know the patterns that survive launch.

We know how product data from PIM transforms cleanly into Shopify products, metafields and variants without manual intervention or data loss.
We have integrated Shopify checkout with ERP systems so orders, customers, credit and invoicing stay synchronised, and stock never oversells.
We design order routing from Shopify into OMS and WMS so fulfillment is orchestrated correctly and tracking flows back to the customer.
We manage payment capture, refund reconciliation and finance handoff so accounting teams see the same truth as Shopify.
We build monitoring so you know when Shopify integration drifts and can resolve it before it breaks the customer experience.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify product attributes from PIM transform into Shopify products without data loss and images display correctly on storefront.
Confirm stock levels in Shopify checkout match ERP availability and update within 15 minutes of warehouse movements.
Test that orders placed in Shopify appear in ERP within 2 minutes with full customer, line item and payment status detail.
Validate that refunds issued in Shopify reconcile to ERP credit notes within 24 hours with correct amounts and tax treatment.
Check that pricing changes in ERP are published to Shopify product pages within 30 minutes and apply at checkout.
Confirm customer credit limits from ERP block orders over the allowed amount and that account-specific pricing applies.
Verify monitoring alerts fire when catalogue sync, stock sync or order flow stops and that exception queues are visible to operations.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Catalogue drift between PIM and Shopify

If the transformation pipeline breaks or is paused, Shopify catalogue becomes stale - missing products, wrong attributes, outdated images. Customers see incomplete or incorrect product data and conversion drops.

Overselling due to stale or mismatched stock

If stock sync lags or fails silently, Shopify shows items as available when ERP or warehouse inventory is exhausted. Orders are accepted but cannot be fulfilled, leading to customer refunds and operational chaos.

Orders lost or stuck between systems

If the order-to-ERP or order-to-OMS flow breaks, orders are captured in Shopify but never reach fulfillment. They sit in a queue with no acknowledgement, no dispatch instruction and no customer tracking.

Payment capture or refund mismatch

If payment authorisation succeeds in Shopify but capture fails silently, or refunds are issued in Shopify but not reconciled to finance, money is lost and accounting breaks.

Customer account linking fails or drifts

If Shopify customers do not link cleanly to ERP account masters, credit limits are not enforced and pricing does not apply correctly. High-value trade accounts may not see negotiated terms or may exceed credit.

Pricing and promotion rules become inconsistent

If ERP pricing changes are not pushed to Shopify, or promotional rules are edited in Shopify and not recorded in ERP, the storefront and invoicing show different prices to the customer.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Shopify integrations.

How does product data from PIM get to the Shopify storefront?

iWeb builds a data pipeline that transforms PIM attributes, descriptions, images and variants into Shopify product and metafield schema. Updates trigger automatically when PIM data changes. The mapping respects Shopify's product model so variants, options and media display correctly without manual steps.

Can Shopify show real-time stock from the ERP or warehouse?

Yes. iWeb syncs stock from ERP or OMS to Shopify so checkout always reflects true available inventory. The integration respects location rules, allocation logic and hold status so stock is never oversold. Stock updates when inventory moves in the warehouse.

What happens to orders placed in Shopify?

Orders are sent to ERP for invoicing and financial recording, and to OMS or WMS for fulfillment and dispatch. Shopify receives acknowledgement status and tracking updates so customers see order progress. Returns and refunds flow back through the same path for reconciliation.

How do we handle pricing in Shopify if the ERP is the source?

iWeb publishes base pricing from ERP to Shopify so product detail pages show the correct list price. Promotion rules, discounts and customer-specific pricing can layer on top in Shopify. If ERP pricing changes, the integration pushes the update to Shopify automatically.

Can a customer's ERP account link to their Shopify login?

Yes. iWeb maps Shopify customer email to ERP account master records so the right credit limit, payment terms and account pricing apply. This is especially important for B2B accounts or trade customers who need account-specific rules enforced at checkout.

What happens if the integration between Shopify and ERP breaks?

iWeb designs a fallback so Shopify can continue operating for a limited time with cached stock and pricing data. Meanwhile, a monitoring alert is raised so operations can investigate and fix the issue. Once restored, stock and orders reconcile and any gaps are resolved.

How do refunds and returns work between Shopify and the ERP?

When a customer requests a refund in Shopify, the integration sends a return event to OMS or WMS for handling, and a credit instruction to ERP for finance. Shopify receives confirmation so the customer sees the refund status. If the return is rejected, Shopify is notified.

Can Shopify orders go to different fulfillment locations?

Yes. iWeb works with OMS to route orders based on inventory, location proximity or business rules. Some orders may go to the warehouse, others to a branch or dropship partner. Shopify tracks the dispatch status for each shipment.

How is payment capture and reconciliation handled?

iWeb routes Shopify payments to the payment processor for authorisation, capture and settlement. Captured payments and refunds are reconciled against ERP finance records daily so accounting stays accurate. Failed captures trigger alerts.

Can Shopify feed customer events to a CRM or marketing platform?

Yes. iWeb sends customer identity, consent, purchase and behavioural events from Shopify to your CRM, CDP or marketing automation platform. This data is used for segmentation, email campaigns and personalisation. Suppression lists and unsubscribe status flow back to Shopify.

How do you monitor that Shopify integration is working?

iWeb builds monitoring dashboards showing catalogue freshness, stock sync health, order throughput, payment status and exception queue depth. You are alerted if a data flow degrades so you can investigate before customers see issues. Regular reconciliation reports compare Shopify against source systems.

What happens during a Shopify upgrade or platform change?

iWeb tests the integration against new Shopify versions before they are deployed to production. Extensions and custom fields are verified. If a breaking change occurs, the integration is paused and reworked so it continues to work with the new Shopify release.

14b · Same category

Other commerce platforms integrations.

Adjacent integrations in the same category. Same shape of work, different vendor.

Commerce platforms
Next step

Have a Shopify integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →