For growing ecommerce or omnichannel stores, there’s no shortage of technology and systems available to streamline, monitor and improve every aspect of your business. Shopify might sit alongside an ERP, warehouse management system (WMS), product information management (PIM) platform, customer relationship management (CRM) system, third-party logistics provider (3PL), and maybe a dedicated order management system (OMS). 

Connecting them already seems complicated, but it’s only really half the job. The real work comes when deciding which system creates, owns, updates, and consumes each piece of data. This matters because a Shopify unified commerce architecture with eight connected platforms can work extremely well when every system has a clearly defined responsibility, but can fail spectacularly if a source of truth isn’t defined or data isn’t pushed in the right direction. 

The fix? Aim for one authoritative system per data domain.

Shopify increasingly positions its platform as a unified commerce operating system spanning DTC ecommerce, retail, and B2B, while still supporting integrations with ERP, PIM, CRM, logistics, and other enterprise systems. Shopify also describes its native order-management capabilities as including multichannel order capture, distributed inventory, order routing, returns, and coordination across stores, warehouses, and 3PLs. 

So, where should everything else fit? In this blog, we’ll break down where to even begin when it comes to outlining your Shopify integration architecture across three reference examples,  depending on whether you’re primarily DTC ecommerce with a warehouse or 3PL, you’re a retailer with multiple stores and warehouses, or you’re Hybrid B2B and B2C on Shopify.

Forget Integrations, Unified Commerce Architecture Needs to Start with Ownership

The questions that lead to the big operational questions aren’t about the direction your data moves or how everything is linked. Instead, they’re considerations like:

1. Who owns a SKU?

2. Who can change the sellable inventory quantity?

3. Does Shopify or the ERP decide which warehouse fulfils an order?

4. What happens when a customer returns an online purchase in a retail store?

5. Should the WMS send tracking information to Shopify directly or through the ERP?

6. If a B2B customer has negotiated pricing, does that price originate in Shopify or the ERP?

These all relate to data ownership and orchestration, rather than integration. Shopify also makes this distinction: it recommends assigning ownership to individual data domains rather than treating every connected application as equally authoritative. This means that there’s one simple rule you should follow when building your Shopify ecommerce architecture and unified commerce tech stack: 

One source of truth per data domain, instead of one software system for everything.

Unified commerce vs. omnichannel: what's the difference?

“Omnichannel” describes the customer experience of interacting with a retailer across connected channels, while “unified commerce” goes further by addressing the infrastructure underneath those channels.

For example, a retailer might appear omnichannel because customers can shop online and in stores, while still operating two separate commerce platforms, two customer databases and an integration that periodically synchronizes inventory between them. A unified commerce architecture, however, aims to reduce those channel-specific silos.

With Shopify and Shopify POS, for example, online and retail orders can exist within the same commerce platform, inventory can be centrally managed while remaining tracked by location, and stores and warehouses can participate in shared fulfilment workflows.

What do Shopify, POS, ERP, OMS, PIM, WMS, CRM, and 3PL actually do?

Here’s a quick explainer on all the systems you might want to add to your ecommerce tech stack as your business grows and you start needing more sophisticated or complex systems to handle increasingly complicated problems or needs. 

1. Shopify: Storefront, checkout, commerce orders, Shopify customer profiles, selling locations, channel availability, promotions, native routing and fulfilment workflows

2. Shopify Point of Sale (POS): In-store selling and operational workflows, while using the underlying Shopify commerce, order, customer, and inventory records

3. Enterprise Resource Planning (ERP): Finance, procurement, accounting, costs, suppliers, purchasing, enterprise inventory records, invoicing and operational reporting

4. Order Management System (OMS): Cross-channel order orchestration, allocation, distributed order management, advanced routing and fulfilment exceptions

5. Product Information Management (PIM): Enriched product information, attributes, descriptions, taxonomy, localization and channel-ready product content

6. Warehouse Management System (WMS): Warehouse inventory movements, receiving, bins, picking, packing and warehouse execution

7. Customer Relationship Management (CRM): Account relationships, sales activity, customer-service or marketing context and enriched customer data

8. Third-Party Logistics Provider (3PL): Physical storage and fulfilment performed by an external logistics provider, often exposing inventory, shipment and tracking information back to the commerce stack

PIM vs. ERP: dividing product data by how it behaves

Let’s get the most complicated distinction out of the way early: product data is often the area where the term “single source of truth” becomes complicated or even misleading. Your ERP might own the SKU, supplier, cost, and unit of measure, while your PIM might own product titles, specifications, ingredients, materials, dimensions, descriptions, translations, taxonomy and ecommerce attributes.

Both feed into Shopify, which then consumes the information necessary to merchandise and sell the item. The separation between these tools looks like this: 

• ERP: Is this SKU an active item? What did it cost? Who supplies it? How many were purchased?

• PIM: What should shoppers know about it? Which attributes, images, descriptions, translations and category data should each channel receive?

• Shopify: How should the product be presented, merchandised and sold in this commerce experience?

This is especially important for merchants with large catalogues, multiple languages, many sales channels or complex product specifications.

OMS vs. ERP vs. WMS: where order responsibilities diverge

Your ERP records what happened financially/operationally, your WMS tells warehouse employees what needs to happen on the floor, and your OMS decides how an order should move between channels, inventory pools, and fulfillment centers. 

You could also think of it this way:

• OMS: order orchestration

• ERP: broad enterprise operations

• WMS: warehouse execution

For merchants with relatively straightforward fulfilment and routing requirements, Shopify’s built-in order management and Order Routing capabilities may remove the need for a separate OMS, reducing both cost and integration complexity. A dedicated OMS can still make sense when fulfilment requires more advanced distributed order management, cross-channel inventory orchestration, complex allocation rules, or sophisticated exception handling.

Which system should own inventory in Shopify?

“Inventory,” as a concept, is too broad to give a simple answer. At a minimum, it encompasses four separate concepts:

1. Physical on hand: What is physically at the location?

2. Committed: What has already been promised to orders?

3. Unavailable: What exists physically but shouldn’t currently be sold?

4. Available to sell: What can actually be offered to a shopper?

The authoritative physical quantity should normally originate as close to the stock movement as possible. For a distribution centre, that's commonly the WMS, while for a 3PL, it's usually the 3PL's inventory platform. A retail store using Shopify POS without a separate store-inventory system might prefer Shopify itself as the operational inventory source.

The available-to-promise quantity is different, however. An OMS or Shopify might need to convert physical inventory into a sellable value based on reservations, fulfilment eligibility, safety stock and routing logic.

Reference architecture 1: DTC ecommerce with a warehouse or 3PL

For our first scenario, let’s look at a primarily direct-to-consumer brand selling through Shopify, with one warehouse or 3PL, an ERP and potentially a PIM and CRM.

Your architecture might look like:

ERP → PIM → Shopify → WMS/3PL

With:

Shopify ↔ ERP

and:

Shopify → CRM

Product data

For product data, the ERP creates or validates the operational item record and SKU. Product information is passed to the PIM, where teams enrich attributes, descriptions, taxonomy and other channel-facing content. The PIM then publishes approved product content to Shopify.

Fast-changing information like inventory and potentially base pricing can bypass the PIM and travel directly from the operational system to Shopify. 

Inventory

If the 3PL or WMS knows what is physically sitting on the warehouse shelf, it should normally be the source for physical on-hand inventory at that location. That, however, doesn’t mean that the WMS owns the quantity that Shopify offers customers. For example, you could have 100 units on hand, but 20 are already committed to existing customers, 10 are damaged, and 5 are safety stock. 

Shopify itself distinguishes between on-hand, available, committed, unavailable and incoming inventory states. Available inventory represents the quantity that can actually be sold rather than simply everything physically present at the location.

For that reason, merchants should define available-to-promise inventory separately from physical inventory.

Orders and fulfillment

For orders and fulfillment, Shopify captures the checkout and creates the order. Then, the ERP receives it for financial and operational processing, while the WMS or 3PL receives the fulfillment request and handles picking, packing, and shipping. 

Next, shipment and tracking information should flow back to Shopify so that order status is visible to customers and customer service teams can access it if needed. Once Shopify records fulfilment and tracking events, it can also trigger relevant customer notifications and configured Shopify Flow workflows, depending on the event and the merchant’s settings.

Shopify can treat integrated fulfilment apps, including many third-party logistics services, as locations within its inventory and fulfilment model, allowing inventory and orders to be associated with external logistics providers alongside merchant-operated stores and warehouses.

Reference architecture 2: Shopify POS with multiple stores and warehouses

Next, let’s look at a retailer operating ecommerce, Shopify POS, several retail stores, a distribution centre and possibly a 3PL. In this scenario, Shopify POS ERP integration, real-time inventory, BOPIS architecture, ship-from-store and distributed order management become concerns.

Your architecture could resemble:

ERP/PIM → Shopify

with Shopify operating:

Online Store + Shopify POS + Customers + Orders + Commerce Inventory

and fulfillment connecting:

Shopify → OMS or Shopify Order Routing → Store / WMS / 3PL

Stores should be fulfilment nodes, not disconnected sales systems

Shopify locations can represent stores, warehouses and certain third-party logistics services. Inventory is tracked independently by location, and Shopify can use those locations to determine where online orders should be fulfilled.

This enables retail stores to participate in fulfillment instead of just functioning as isolated POS endpoints.

Buy online, pick up in store (BOPIS)

Shopify supports in-store pickup for online orders. At locations using Shopify POS Pro, staff can prepare pickup orders in Shopify POS, notify customers that orders are ready and mark them as collected. Shopify can also support transfers into a pickup location when the chosen store doesn’t currently have the necessary inventory, depending on the merchant's configuration.

Ship-from-store

Shopify POS Pro also supports ship-from-store workflows. Participating locations can fulfill shipping orders through POS, including packing slips, shipping labels, tracking and shipment processing. Shopify requires the participating retail locations to be configured as fulfilment locations and uses order-routing rules to determine where orders should be fulfilled.

Where should order-routing logic live?

As we mentioned earlier, Shopify can handle a lot of order-routing logic natively. Its default routing strategy can minimize split shipments, favour locations within the destination market and prioritize the closest eligible location. Merchants can also rank locations or use location metafields as routing criteria.

The need for an OMS outside your ecommerce platform comes when routing decisions need to incorporate more advanced variables such as store labour capacity, carrier cut-off times, promised delivery dates, fulfilment costs, inventory ageing, warehouse backlog, store opening hours, backorders, dropship suppliers or inventory reservations across several external sales channels.

There isn’t necessarily a right answer as to where order routing logic needs to live, just that you choose one orchestration authority and stick to it. 

Reference architecture 3: Hybrid B2B and B2C on Shopify

Our final scenario looks at hybrid businesses where the same product may have different customers, prices, payment terms and order workflows depending on who is buying.

Shopify supports selling B2B and DTC through the same store or through separate stores. Its B2B model includes companies, company locations, catalogues, customer-specific commerce experiences and integrations with ERP and other external systems.

A hybrid B2B/B2C architecture could resemble:

ERP → PIM → Shopify B2B + DTC

With:

CRM ↔ Shopify Companies/Customers

Shopify → OMS → WMS/3PL

Shopify ↔ ERP

Product information

Your PIM can remain the enrichment hub for both your B2B and B2C operations.  Rather than maintaining duplicate product descriptions and specifications, the PIM can publish the appropriate attributes into Shopify and other channels.

B2B customers might receive additional technical information, case-pack details or specifications, while DTC shoppers receive more merchandising-oriented content.

Companies and customer accounts

Individual buyers can exist as Shopify customer records, while B2B buyers are associated with companies and company locations. Shopify also provides external company IDs specifically to support synchronization with systems such as an ERP.

For an organization with a mature CRM, the CRM or ERP can remain the enterprise authority for account identity while Shopify stores the commerce representation necessary for purchasing.

B2B pricing

When it comes to pricing ownership, you need to make an explicit decision: Shopify B2B catalogues can control which products and prices a customer can access, including catalogue assignments to B2B markets and, on Shopify Plus, direct assignments to companies or company locations.

…but that doesn’t mean Shopify absolutely must originate the price. For businesses that maintain negotiated pricing in the ERP, those values can be synchronized into the Shopify catalogue structure, but for organizations whose teams directly manage B2B price lists in Shopify, Shopify might be authoritative instead. 

B2B fulfillment

B2B also strengthens the case for separating order capture from fulfilment orchestration: A B2C order for two units could ship immediately from the nearest warehouse, but a B2B order for 250 units might require credit approval, a delivery appointment, palletization, partial shipment rules or fulfilment from a specific distribution centre.

Shopify can remain the commerce and order-capture layer while the ERP, OMS and WMS manage the operational processes that extend beyond checkout. The platform also supports integrations that synchronize B2B products, companies, customers, orders, inventory, pricing and other information with ERP and external business systems.

Conclusion

A successful Shopify unified commerce architecture gives every system a clearly defined job and decides which one is authoritative for each type of data. Whether Shopify is working alongside an ERP, OMS, PIM, WMS, CRM, 3PL, or all of the above, the most important principle remains the same: one source of truth per data domain, rather than one software system for everything.

That’s why the best place to start isn’t with an integration diagram. Instead, start by asking who creates each record, who can change it, which system makes the operational decision, and what happens when something goes wrong. Once those responsibilities are clear, integrations become significantly easier to design, maintain and scale.

If your Shopify ecosystem has reached the point where POS, ERP, PIM, WMS, OMS, or 3PL integrations add unnecessary complexity, Blue Badger can help design and implement a unified commerce architecture that gives every platform a clear role while keeping Shopify at the centre of the customer experience. Get in touch with us today to learn more.