Shopify product and SKU data: what a 3PL needs before go-live

Before a Shopify catalogue can be connected to a fulfilment warehouse, a 3PL typically needs a unique SKU for every sellable variant, a scannable barcode for every SKU, a clear definition of how bundles or kits are built from individual stock items, and confirmation of which Shopify stores and Markets share (or don't share) the same inventory pool. Messy or inconsistent product data — not the technical integration itself — is the most common reason a Shopify go-live is delayed.

The technical side of connecting a Shopify store to a warehouse management system is usually the fast part. What takes longer is making sure that every product, variant and bundle in the Shopify catalogue maps to exactly one, unambiguous location in the warehouse.

A warehouse operates on SKUs and barcodes, not on product titles. If two different physical products share a SKU, or one product has two different barcodes in circulation, the warehouse cannot reliably tell them apart — which shows up later as mis-picks, incorrect stock counts or orders that cannot be fulfilled automatically.

Shopify integration is available.

Requirements vary by provider and by warehouse management system, but most of the categories below come up in any Shopify-to-3PL onboarding.

Shopify variants let one product carry several sellable options — size or colour, for example — and each variant can have its own SKU, barcode, price and inventory count. For fulfilment, the practical question is simpler: does every variant that needs to be picked separately already have its own SKU and barcode in Shopify, or only the parent product?

Bundles raise a different question. A bundle can be treated as its own stock-keeping unit — received and picked as one item — or it can be assembled at pick time from its individual component SKUs, with each component's stock deducted separately. Both approaches work, but the warehouse and the brand need to agree on which model applies to which bundle before stock arrives, since the two models require different warehouse setup.

Brands running more than one Shopify store, or using Shopify Markets to present different storefronts for different regions, need to confirm whether those stores or Markets should draw from one shared fulfilment inventory pool or be kept separate.

Can multiple Shopify stores use the same fulfilment inventory? This depends on the store and inventory configuration. Vareya assesses multi-store requirements during qualification and onboarding before confirming the final setup.

Composite, anonymised example. It does not describe an identifiable current or former Vareya customer.

A cosmetics brand with roughly 80 Shopify products expected onboarding to take a few days. During data review, around a third of its variants turned out to share SKUs with discontinued products still visible in the product catalogue, and several best-selling variants had no barcode assigned at all — only the parent product did. Three bundles were configured as single Shopify products with no link back to their component SKUs.

Resolving this required relabelling the affected variants with unique SKUs, printing and applying barcodes to the previously unbarcoded stock, and agreeing with the warehouse that the three bundles would be assembled from components at pick time rather than received as pre-built units. Once that was done, inbound stock receipt and the first live orders processed without exceptions.

Lesson: the Shopify-to-warehouse connection itself was ready well before the product data was. Reviewing SKU and barcode data before sending the first inbound shipment avoids discovering these issues during receiving, when they are more disruptive to fix.

Mark each item ready, in progress, or not started:

This article combines approved Vareya claims from the Claims Register (v1.7) with public Shopify documentation. The onboarding example is composite and anonymised and does not describe an identifiable current or former customer.