Build or Buy Pick-Path and Slotting Optimization on Shopify?
Pick-path and slotting optimization on Shopify is a CUSTOMIZE: your WMS routes the pick, and a velocity analysis from Shopify order data decides where each SKU sits. The analysis is a $5,000–$15,000 one-time build (Deploi estimate, illustrative). No Shopify app reads your orders and tells you how to re-slot shelves. ShipHero is the one listed WMS documenting slotting controls, pricing unpublished. Buy dedicated slotting software only above roughly 20,000 SKUs or several DCs.
Your profile — see how the verdict shifts
- Confidence
- Medium — Checked the App Store for slotting and pick-path listings: ShipHero is the one Shopify-listed app whose own help center documents slotting types (static vs. dynamic) and pick routing by location priority, and its plan pricing is unpublished. FORTNA OptiSlot DC (formerly Optricity) is real DC-slotting software sold direct, quote-only, with no Shopify integration on its site. No app reads Shopify order data to produce a re-slot plan; that step is a data job the merchant runs.
- Reference scenario
- $20M–$100M GMV · one owned DC of 10,000–40,000 sq ft · 2,000–10,000 active SKUs · a WMS or ShipHero already running · agency or in-house dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Fulfilled by a 3PL | WAIT | Slotting is your 3PL's problem, and their pick rate is priced into your per-order fee. Ask for their re-slot cadence and pick-rate trend in the quarterly review; buy and build nothing. |
| Own DC, under ~2,000 SKUs, shipping app + native inventory | BUILD | A velocity analysis from Shopify order-line data plus a bin-location column is the whole solution: $5,000–$15,000 (Deploi estimate, illustrative) and a weekend of moving shelves. A WMS just for slotting is overkill here. |
| Own DC, 2,000–20,000 SKUs on a WMS | CUSTOMIZE | Your WMS routes the pick by location priority; feed it velocity classes from Shopify data each season, or use ShipHero's own slotting controls if ShipHero is the WMS. The analysis is yours, the routing is theirs. |
| Multiple DCs or 20,000+ SKUs | BUY | Dedicated slotting software such as FORTNA OptiSlot DC earns its quote at this size, running off WMS data rather than Shopify. The Shopify-side question shrinks to whether your order feed into the WMS is clean. |
What Pick-path and slotting optimization Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | Walking is the largest share of pick labor in a manual DC; placing A-class and high-affinity SKUs near pack-out removes the double traverse per order that the trigger describes. FORTNA's own marketing claims 10% productivity gains from optimized slotting (vendor claim). |
| Customer experience | Medium | Shorter pick cycles let you hold a later same-day cutoff and clear peak-day backlogs before carrier pickup, which shoppers experience as orders shipping the day they were placed. |
| Data & insight | Medium | Velocity classes, affinity pairs and cube-per-SKU are the same data that improves replenishment and pack-size decisions; the analysis pays twice. |
| Revenue — indirect | Low | A later order cutoff and fewer peak-day misses lift conversion at the margin; the direct win is cost per order, not sales. |
Spend ceiling: Size the spend to your pick labor bill, not to software. A DC picking 2,000 orders a day saves real money when each order loses a minute of walking; a DC picking 200 doesn't, and a spreadsheet re-slot is the right tool there.
What buying enables (top apps)
- + Live pick routing by location priority across every picker and shift, maintained by the WMS vendor
- + Static or dynamic slotting modes documented and supported, so the warehouse team isn't inventing method
- + At FORTNA's scale, algorithmic slotting across multiple DCs with digital-twin modeling of the floor
What building additionally unlocks
- + Shopify-only demand signals (pre-orders, launches, bundles, promo calendars) shaping the slot plan before the volume hits
- + A velocity and affinity model you keep and reuse for replenishment and pack-size decisions
- + Re-slot cadence on your calendar, timed to the quiet week before each peak
- + Zero switching cost when you change WMS or graduate to dedicated slotting software
Find Your Verdict in 3 Questions
Do you run your own DC rather than a 3PL?
Yes: Go to question 2.
No: Your verdict: WAIT — slotting is the 3PL's job and it's priced into your per-order fee; ask for their re-slot cadence and pick-rate trend instead.
Does your WMS already have slotting and pick-routing controls (ShipHero documents both)?
Yes: Your verdict: CUSTOMIZE — turn on location priorities in the WMS and feed it velocity classes from Shopify order data each season.
No: Go to question 3.
Are you running several DCs or more than roughly 20,000 SKUs?
Yes: Your verdict: BUY — dedicated slotting software such as FORTNA OptiSlot DC, fed from WMS data; the Shopify side is just a clean order feed.
No: Your verdict: BUILD — a velocity analysis from Shopify order lines plus a location map is the whole solution; re-slot quarterly.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A WMS with slotting is a months-long, quote-priced implementation; the velocity analysis is a $5,000–$15,000 data job (Deploi estimate, illustrative) that runs against order data you already have. | ||
| Recurring fees | ShipHero and FORTNA both publish no price, so the subscription is whatever the sales call produces; the analysis re-runs quarterly at the cost of a few dev hours. | ||
| Maintenance & upgrades | The WMS vendor maintains its routing logic; a custom analysis needs its SKU-velocity thresholds and cube data refreshed each season, roughly 15–20% of build cost a year (Deploi estimate). | ||
| Switching & exit | Slotting rules configured inside a WMS leave with the WMS; a velocity model built on Shopify order data outlives any warehouse system you run it against. | ||
| Risk | |||
| Vendor risk | One Shopify-listed WMS documents slotting (ShipHero, 4.3★, 115 reviews, verified Sep 2026) and the alternative is enterprise software with no Shopify presence; a single-vendor category is a real risk. | ||
| Security & compliance surface | A WMS holds order, customer and address data by design; the analysis touches only order lines and SKUs, and a physical shelf move has no data exposure at all. | ||
| Platform-deprecation exposure | Order-line reads through bulk operations are a stable Admin API surface; both paths sit far from the checkout and theme changes that break other categories. | ||
| Value | |||
| Fit to requirement | WMS slotting uses the WMS's velocity view of the world; a custom analysis adds Shopify-only signals such as pre-orders, bundles and promotion calendars that change what will be fast next month. | ||
| Time to market | A first re-slot list from Shopify order history takes 2–3 weeks (Deploi estimate, illustrative); a WMS implementation with slotting configured is a quarter or more. | ||
| Performance & scale | Real-time pick routing across multiple DCs is what a WMS is for; a periodic analysis scales in SKU count but never routes a live pick on its own. | ||
| Data ownership & AI-readiness | Velocity classes, affinity pairs and cube-per-SKU are yours in the build path and feed forecasting and replenishment too; inside a WMS they're viewable but rarely exportable in bulk. | ||
| Focus & opportunity cost | The analysis is a bounded, repeatable data job; the physical re-slot is warehouse labor either way, and neither path pulls your dev bench off revenue work for long. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| ShipHero Inventory & Shipping | Live — 4.3★, 115 reviews. Not a kitting app: a full warehouse platform whose help center documents Kits, kit creation and editing, and Work Orders for build-to-order assembly at pick and pack time. Free to install, with additional charges applying. | Pricing not listed; the listing directs you to book a demo with sales (verified Sep 2026) | Merchants already on or moving to ShipHero as their WMS, who get slotting controls with it |
| FORTNA OptiSlot DC | Live — Off-platform enterprise DC-slotting software (formerly Optricity); no App Store listing and no Shopify integration mentioned anywhere on its site. Runs off WMS data. Publishes productivity claims but no price | Quote-based; schedule a demo, no public pricing (verified Sep 2026) | Multi-DC or 20,000+ SKU operations where slotting is a full-time discipline |
| Order-management and 3PL connector apps | Category — The listings that surface when you search the App Store for warehouse terms. They sync orders and inventory between Shopify and a warehouse or 3PL; none models shelf positions, pick paths or velocity-based slotting | Varies by vendor; not the capability on this page | Getting orders to the floor, not deciding where SKUs live on it |
| Velocity-based slotting analysis (custom) | Build lane — A data job over Shopify order lines: velocity classes, co-pick affinity, cube-per-SKU and current bin locations produce a ranked re-slot list, re-run each season and written back to the WMS as location priorities where an API exists | $5,000–$15,000 one time, $15,000–$40,000 with WMS write-back (Deploi estimate, illustrative) | Any owned DC that has velocity data in Shopify and no slotting module in its WMS |
The Build Path
- Velocity and affinity analysis from order lines: Pull 90–180 days of order lines through the bulk operations API, classify SKUs A/B/C by picks per week, and compute co-pick pairs so items that ship together sit near each other.
- Golden-zone slotting plan: Rank pick locations by distance from pack-out and ergonomic height, then assign A-class and high-affinity SKUs to the nearest, waist-height slots, respecting cube and weight limits per shelf.
- Pick-path sequencing: Order pick lists by a fixed walking sequence of locations (serpentine or return path) so a picker never doubles back; the WMS does this natively if it has location priorities, otherwise the pick list generator does.
- Optional: WMS write-back and seasonal re-run: Where the WMS exposes an API, push new location priorities directly; schedule the analysis before each peak so the re-slot happens in the quiet week, not during it.
- Effort band
- $5,000–$15,000 for the analysis and re-slot plan; $15,000–$40,000 with automated WMS write-back and seasonal scheduling — Deploi estimate (illustrative); lands in the $10–25K or $25–75K contact-form band
- Typical timeline
- 2–3 weeks to a first ranked re-slot list; 6–10 weeks with WMS write-back (Deploi estimate, illustrative); the physical move itself is a weekend of warehouse labor
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $1,000–$8,000/yr (Deploi estimate, illustrative), mostly refreshing velocity thresholds, cube data and the location map when racking changes. There is no subscription line.
- What you own — and what you take on
- You own: the velocity model, the affinity pairs, the location map and the re-slot history. You take on: keeping cube and weight per SKU current, and the discipline of actually moving the shelves each season.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $10,000–$40,000 (WMS implementation, illustrative) | $15,000–$40,000 |
| Years 1–3 (recurring) | $18,000–$90,000 (subscription, illustrative) | $7,000–$24,000 (maintenance) |
| 3-year total | ≈$28,000–$130,000 | ≈$22,000–$64,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: an illustrative WMS-with-slotting subscription band, since ShipHero and FORTNA publish no prices; implementation billed once, subscription held flat.
- † Build path: the analysis with WMS write-back, re-run quarterly; three-year horizon with upkeep at 15–20% of build cost per year.
What the Sticker Price Hides
On the buy path
- — Neither ShipHero nor FORTNA publishes a price; the slotting feature you want is priced inside a WMS or DC-software contract you can't compare from the listing
- — WMS slotting runs on the WMS's velocity view, so Shopify-only signals (pre-orders, bundles, promotion calendars) never reach the slotting logic unless someone feeds them
- — Implementation is months, and the first re-slot waits for the WMS to go live; the walking problem continues through the whole project
- — A single Shopify-listed vendor documenting slotting means the exit is a WMS migration, not an app swap
On the build path
- — The analysis is easy; the physical move is labor, and re-slots that nobody schedules never happen
- — Cube and weight per SKU are wrong or missing for a third of catalogs; cleaning them is the unglamorous half of the first run
- — Pick-path sequencing needs a location map that matches the floor; racking changes silently break it
- — ~15–20% of build cost per year in upkeep (Deploi estimate)
What Merchants Say
Pickers walk the whole floor for a two-line order because the two SKUs that always sell together sit at opposite ends; nobody re-slotted after the first season's velocity data came in.
The 1–2★ theme on WMS listings: onboarding runs for months and the price arrives only after a sales call, so the slotting features you wanted sit behind a contract you couldn't price from the listing.
If You Change Your Mind Later
If you bought and outgrow it
Slotting rules and location priorities live inside the WMS and leave with it; a WMS migration means re-deriving the slotting plan from scratch. Export your location map and velocity classes on a schedule so the next system starts from data, not from an empty floor.
If you built and want out
The velocity model and location map are plain data you keep; they port to any WMS, to dedicated slotting software when you outgrow the analysis, or to a spreadsheet if the dev bench disappears. The exit cost rounds to zero, which is a large part of why the build lane wins at this size.
When This Answer Changes
We're watching for:
- ▸ ShipHero publishing plan pricing on its listing (unlisted as of September 2026)
- ▸ Any slotting vendor shipping a Shopify order-data connector; FORTNA OptiSlot DC shows none as of September 2026
- ▸ Shopify adding shelf or bin position fields to native inventory; locations today are facilities, not shelf positions
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Does any Shopify app tell you how to re-slot your warehouse?
No Shopify app reads your order data and produces a re-slot plan. ShipHero's help center documents static and dynamic slotting and pick routing inside its WMS, but the slotting decision runs on the WMS's own data, and the listing publishes no price. FORTNA OptiSlot DC has no Shopify integration at all. A velocity analysis built from Shopify order lines costs $5,000–$15,000 (Deploi estimate, illustrative) and fills that gap.
What Shopify data does a slotting analysis need?
A slotting analysis needs 90–180 days of order lines (SKU, quantity, timestamp) to classify velocity, plus SKU co-occurrence within orders for pick affinity, and cube and weight per SKU from the product record. Add the current bin location per SKU from your WMS or a metafield, and a map of pick locations ranked by distance from pack-out. Shopify's bulk operations API pulls the order lines in one job.
How often should a mid-market DC re-slot?
Re-slot quarterly, and always in the quiet week before a peak, so the A-class SKUs for the coming season sit in the golden zone before volume arrives. Velocity shifts with promotions, launches and seasonality, and a slotting plan built on last winter's data is wrong by summer. A 2,000–10,000 SKU DC moves a few hundred SKUs per re-slot, which is a weekend of labor, not a project.
Your Next Steps
If you're going with CUSTOMIZE(matches your selected profile)
- Time-study one week of picks: walking distance per order is the baseline number the whole project is measured against
- Pull 90–180 days of order lines through bulk operations and classify SKUs A/B/C by picks per week
- Map pick locations by distance from pack-out and shelf height; mark the golden zone
- Load velocity classes and affinity pairs into the WMS as location priorities, or generate the re-slot list for a manual move
- Re-run before each peak and re-measure walking distance per order; the delta is the ROI
If you're going with BUY
- Get written confirmation of which slotting and pick-routing features sit in the tier you're quoted
- Ask how velocity data enters the slotting logic and whether Shopify-side signals can be loaded
- Confirm bulk export of location maps and slotting rules before signing; it's your exit path
- Schedule the first re-slot for go-live week, not a quarter later
Official Docs & Sources
- Inventory — Shopify Help Center
- Locations — Shopify Help Center
- Bulk operations (queries) — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Build or Buy Assortment Planning and Open-to-Buy on Shopify?
Stocky ended 2026-08-31 with no native open-to-buy replacement, and the apps that name OTB carry 12, 0 and 7 reviews. Build the planning model on data you own.
Build or Buy Inbound PO Email and PDF Capture on Shopify?
Two young apps parse emailed and PDF purchase orders into Shopify draft orders, capped near 100 a month. Above that, buy extraction and build the mapping layer.
Build or Buy Kitting at the Pick Face on Shopify?
No dedicated kitting app exists on Shopify. Assemble-to-order lives inside a WMS, and Shopify Bundles tracks component stock overall, not by location.
Build or Buy Order Merge and Consolidation on Shopify?
Two Built for Shopify apps merge same-customer orders for a few dollars per merge; nothing native does. Buy, and build only a hold window ahead of your 3PL feed.
Should You Build or Buy Your NetSuite Integration on Shopify?
NetSuite integration is the honest DEPENDS: buy a connector for standard flows, build middleware when the flows are the business.
Ready to stop paying pickers to walk?
We'll build the velocity and affinity analysis from your Shopify order data, rank your pick locations, and write the result back to your WMS so the next re-slot is a schedule, not a project.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.