Pixi WMS + Shopify 2026: When You Need It, When You Don't

Pixi is a full barcode-driven WMS. Three things decide the pixi-vs-native question:

MHD and batch/lot management. Pixi records best-before dates (MHD) and batch numbers at goods receipt, enforces FIFO/FEFO at picking, and gives you full batch traceability through shipping and returns — if a supplier recalls lot 4711, you can list every order that contained it. Shopify natively has nothing here: no expiry dates, no lots, no FEFO. For food, supplements, cosmetics, and anything under EU traceability rules (Regulation 178/2002 for food, the Cosmetics Regulation (EC) 1223/2009 with its batch-number and traceability obligations for cosmetics), this single feature is often the entire business case.

Pick path optimization. Pixi computes bin-level pick routes and drives them through a barcode scanner app, with multi-order (batch) picking. Descartes' own positioning starts at about 200 orders/day, with reference customers shipping 500–10,000 packages a day. Shopify's admin gives you a picking list at best — the walking order through your warehouse is your problem. At 30 orders/day that costs you nothing; at 500 orders/day an unoptimized pick path is one or two extra warehouse employees.

Multi-warehouse with real logic. Pixi manages multiple physical warehouses with per-bin stock, replenishment between zones, and returns processing per site. Shopify's locations model stock per location and (since the order-routing rules shipped) can prioritize which location fulfills — but it has no concept of bins, no replenishment logic, no goods-receipt workflow with scanning.

On top: carrier integration (DHL, DPD, GLS, Post AT and a few dozen more), returns management, and packing-table workflows. If you read that list and thought "I need two of those, badly" — keep reading. If you thought "none of those are my problem", Shopify native plus a shipping label workflow is very likely all you need, and you can stop at the cost section.

As of mid-2026 there are three realistic integration paths, and they are not equal:

1. Pixi's built-in Shopify interface. Pixi has maintained a native Shopify connection for years — orders flow from Shopify into pixi, stock and tracking flow back. This is the path most existing pixi merchants run. It is configured during the implementation project by Descartes or a pixi partner (Latori and maexware are the names you'll meet in DACH), and its scope is the classic one: orders in, aggregate stock and fulfillment status out.

2. The "Descartes Pixi WMS Connect" app from the Shopify App Store. Launched May 2025, free to install (the pixi license itself is the cost). Honest status report: as of July 2026 the app has exactly one review — one star, from a German merchant complaining that return numbers from pixi don't reach Shopify. One bad review is thin evidence, but it matches what we see in projects: the app covers the standard sync and stops at the edges. Treat it as a convenience wrapper around path 1, not as a richer integration.

3. Custom glue code against both APIs. Pixi exposes a documented API (pixi* API), Shopify's Admin GraphQL API is excellent. A middleware layer between them can do what neither standard path does: per-location stock instead of aggregate, MHD data pushed into Shopify metafields so the storefront can show "mindestens haltbar bis", batch numbers written back onto the order for customer-service lookups, or routing rules that respect carrier cutoff times per warehouse. This is the same pattern we described for JTL + Shopify: the standard connector carries 80%, custom code carries the 20% your operation actually differentiates on.

The practical recommendation: run path 1/2 first. Only build path 3 when you can name the specific field or workflow the standard sync drops — never speculatively.

Shopify's native inventory is better than its reputation in the DACH WMS community, and it is included in the plan price you already pay. The current state:

• Locations: 10 active locations on Basic, Grow, and Advanced; 200 on Shopify Plus. Fulfillment apps and deactivated locations don't count against the limit.
• Order routing: rule-based location priority — ship from the closest or preferred warehouse, with fallbacks. Native, free.
• Transfers and adjustments: stock transfers between locations, inventory states (incoming, committed, available, damaged), and adjustment history.
• Stocky is on its way out: Shopify's own inventory-planning app is being sunset in 2026, so purchasing/forecasting needs a replacement app or spreadsheet either way — don't count Stocky in your plan.

What native Shopify does not have, and — based on the platform's direction — will not have soon: expiry dates, batch/lot tracking, bin locations, pick path logic, barcode-driven goods receipt, and returns processing at warehouse level.

The blunt rule of thumb we give merchants: single warehouse, under ~100 orders/day, no MHD/batch requirement → Shopify native is enough. Adding a WMS at that size is the wrong default for DACH stores; it adds €12K+/year and an implementation project to an operation a good picking list already covers. The trigger points that genuinely justify a WMS are regulatory batch traceability, a second physical warehouse with real routing needs, or pick labor becoming a measurable cost line.

The realistic 2026 price picture for a DACH Shopify store, all prices net and as published or estimated in mid-2026:

Descartes pixi: quote-only pricing. Third-party estimates: roughly $1,000–$2,050+/month, plus an implementation project (partner day rates apply; realistic projects land in the five figures). Descartes' own claim is that implementation and running costs amortize on average within less than 12 months — their number, treat it accordingly; plausible at 300+ orders/day, not below.

Pickware for Shopify: the most direct DACH competitor since Pickware (originally Shopware-only) released its Shopify version. ERP module from €99/month — including 1,000 orders/month, then €0.20 per extra order (Advanced €299 with 1,500 included, Professional €599 with 2,000, extra orders €0.15). WMS at €199/month per scanner device, POS at €149/month per license (prices as of July 2026, monthly billing; annual −10%). Includes MHD/batch management. For one warehouse with 2 pick stations you're at ~€500/month plus overage above 1,000 orders/month — a fraction of pixi, with a smaller feature ceiling.

Xentral: the ERP-shaped alternative — from €349/month (Starter), €649/month Business, €849/month Pro after the spring-2025 pricing overhaul, plus a Launch tier at €99/month base (24-month term) + €0.30/order, capped at 1,200 orders/year and €500K annual revenue, with a one-time €1,990 partner onboarding. You get merchandise management + warehouse features + accounting export in one system, but warehouse depth (pick paths, MHD granularity) below pixi's.

Billbee: the small-store answer: €9/month base plus a volume-based per-order fee on the order of 6–9 cents (billbee publishes a calculator, not a flat rate). At 1,000 orders/month that's roughly €80–€100/month for order processing, invoicing, and basic stock sync — no real WMS features, but that's the point. Note the per-order pricing model, the exact pattern we dissect in hidden per-order fees: fine at 500 orders/month, a growth tax at 10,000.

Shopify native: €0 additional. Ten locations, routing rules, transfers — already in your plan.

The comparison merchants skip: at 50 orders/day, pixi costs more per year than the wage share of the picking hours it saves. At 500+ orders/day with batch requirements, it can genuinely be the cheapest option on the list. Volume decides, not features.

The decision tree we actually use in projects:

Stay on Shopify native if you run one warehouse, under ~100 orders/day, and sell nothing with expiry dates or lot numbers. Spend the money you saved on nothing — that's the win. If your only pain is purchasing/forecasting after the Stocky sunset, a planning app at €50–€100/month fixes that without a WMS.

Pick Pickware or Billbee if you need barcode picking or MHD handling at small-to-mid volume. €99–€500/month buys you the 20% of pixi you'd actually use. This is the right call for most DACH stores between 50 and 300 orders/day — and yes, that means the SaaS subscription is the correct answer here. Keep it.

Pick pixi if you run 300+ orders/day, multiple warehouses or a fulfillment provider setup, and hard batch/MHD traceability requirements. At that scale its pricing stops being scary and the pick-path savings are real, measurable hours.

Build custom glue code in exactly two situations. First: you already run pixi (or Pickware, or Xentral) and the standard Shopify sync drops the one field your operation needs — per-location availability on the storefront, MHD shown at the product page, batch numbers on the order for support. That's a €3K–€8K fixed-price build, not a system migration. Second: your "WMS requirement" is actually one workflow — say, FEFO allocation across two locations for 40 SKUs. A targeted app against Shopify's APIs can cover that for less than one year of any WMS subscription, and the code is yours. What custom code should not do is replace a WMS wholesale: rebuilding scanner-driven warehouse logistics is exactly the kind of project where buying beats building.

The break-even math, with the numbers from the cost section: a single targeted app is an €8K–€15K fixed-price build (complex multi-warehouse middleware runs €20K–€40K), plus €60–€180/month hosting. Against pixi at €12K–€25K/year it pays back inside the first year — if one narrow workflow really is all you need from a WMS. Against a Pickware setup at ~€500/month plus €0.20 per order above the included 1,000, the crossover sits around 3,000 orders/month: below that, keep the subscription — the SaaS is cheaper and someone else maintains it. Above it, the SaaS bill climbs past €900/month and keeps scaling with your volume, while the custom app's cost stays flat — and what you bought is yours: source code ownership, no per-order fees, no per-device licenses.

If returns are the process that actually hurts — pixi handles warehouse-side returns well, but the customer-facing part (portal, labels, refund logic) is a separate problem we cover under returns management.

If you want this decision made against your actual numbers instead of our thresholds: we run a 30-minute app-stack audit — order volume, current stack, the one workflow that hurts — and you leave with a fixed-price quote or an honest "keep the SaaS". Book it here.