Build or Buy Wave and Batch Picking for Your Shopify Warehouse?
Wave and batch picking on Shopify is a BUY for merchants running their own warehouse above roughly 500 orders a day, and the thing you buy is a WMS, not an app. ShipHero is the one App Store listing that documents batch picking, and it publishes no price. Below that volume, a built pick-list layer grouping fulfillment orders into waves costs $15,000–$40,000 (Deploi estimate, illustrative). If a 3PL picks for you, its WMS does this.
Your profile — see how the verdict shifts
- Confidence
- Medium — Checked both App Store listings the verification flagged: ShipHero's help center documents batch-picking and order-sorting configuration, while Deposco's listing (0 reviews) confirms pick, pack and ship workflows but not wave or batch picking. Extensiv's App Store app is Extensiv Order Management, not its 3PL Warehouse Manager WMS, which has no listing. ShipHero publishes no price, so the buy-side math rests on a sales call
- Reference scenario
- $20M–$100M GMV · own warehouse · 500–3,000 orders a day at peak · one fulfillment node · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| 3PL-fulfilled, any volume | WAIT | Your 3PL's WMS (Extensiv 3PL Warehouse Manager, Deposco or similar) already releases waves and batches picks; your only job is a clean order and inventory sync, so nothing here is yours to buy or build. |
| Own warehouse, under 500 orders a day | BUILD | A batched, bin-sorted pick list on fulfillment orders is enough; a $15,000–$40,000 layer (Deploi estimate, illustrative) buys two or three peak seasons before a WMS is worth its onboarding. |
| Own warehouse, 500–3,000 orders a day | BUY | Batch picking is now one of a dozen WMS functions you need (bin locations, cycle counts, scan-to-pack); ShipHero is the App Store route and direct-contract WMS vendors are the other, and both are quote-only. |
| Own warehouse, 3,000+ orders a day or multi-node | BUY | Wave planning by carrier cutoff, zone picking and put walls are enterprise WMS territory; evaluate Extensiv, Deposco and ShipHero on a direct contract and treat any Shopify listing as the connector, not the product. |
What Wave and batch picking Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | One picker collecting items for a dozen orders in a single pass replaces a dozen trips through the aisles, and orders released in waves match carrier cutoffs instead of arrival order. |
| Customer experience | Medium | Orders released by ship-by date and carrier cutoff leave the building on the day promised, which is what peak-season delivery estimates depend on. |
| Revenue — indirect | Medium | Throughput per picker-hour sets the daily order ceiling you can promise during peak; every order above it becomes a shipping-date slip or an overtime shift. |
| Data & insight | Medium | Wave timing, picks per hour and pick-path length become measurable once picking is batched, and those are the inputs to labor standards and slotting decisions. |
Spend ceiling: Spend against the peak-day ceiling. If a batched pick list clears your peak with the crew you have, waiting on the WMS is free; the moment overtime or missed cutoffs appear, the WMS pays for itself in one season.
What buying enables (top apps)
- + Scanner-guided batch picking with sort-to-order and pack verification, configured on ShipHero's platform rather than built
- + Wave release by carrier cutoff and zone, plus bin locations, cycle counts and receiving in the same system
- + Vendor-maintained carrier, printer and API integrations your ops team never touches
What building additionally unlocks
- + Wave rules written for your warehouse: your carrier cutoffs, your zones, your peak staffing, without a WMS cutover
- + Pick and wave logs in your own database, feeding labor-standard and slotting analysis
- + A bridge that runs two or three peak seasons before the WMS decision, with nothing to migrate when you make it
Find Your Verdict in 3 Questions
Does a 3PL pick and pack your orders?
Yes: Your verdict: WAIT — the 3PL's WMS runs waves and batches; keep your order and inventory sync clean and leave picking to them.
No: Go to question 2.
Do you exceed roughly 500 orders a day for more than a few peak weeks a year?
Yes: Your verdict: BUY — a WMS; ShipHero is the App Store route (quote-only), Extensiv and Deposco are direct contracts, and batching is the least of what you now need.
No: Go to question 3.
Do your pickers already work from bin locations you could store on each variant?
Yes: Your verdict: BUILD — a wave and batch pick-list layer on fulfillment orders, $15,000–$40,000 (Deploi estimate, illustrative), covers the next two or three peaks.
No: Your verdict: BUILD — but slot the warehouse first; a bin-location metafield per variant is the prerequisite for any batched pick list, bought or built.
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 onboarding bin-maps the warehouse, retrains pickers and cuts over, typically 6–12 weeks on a quoted contract; the pick-list layer ships in 4–8 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | ShipHero publishes no price and bills beyond the free install; direct-contract WMS vendors publish nothing either; the build carries upkeep only. | ||
| Maintenance & upgrades | The WMS vendor ships scanner, carrier and API updates for you; the layer needs roughly 15–20% of build cost per year (Deploi estimate) for API versions and printer or tablet changes. | ||
| Switching & exit | Leaving a WMS means re-mapping every bin and retraining the floor; the layer's wave rules and bin metafields stay in your own Shopify data. | ||
| Risk | |||
| Vendor risk | One 115-review listing is the App Store's whole wave-picking market; the direct-contract vendors are healthier but sit outside Shopify's billing and review surface. | ||
| Security & compliance surface | A WMS holds every order, address and inventory count; the layer reads fulfillment orders through scoped API access and stores wave assignments and pick logs only. | ||
| Platform-deprecation exposure | Both depend on the fulfillment orders API; quarterly versions with a 12-month support window are the shared exposure, and the WMS vendor absorbs it on your behalf. | ||
| Value | |||
| Fit to requirement | A WMS batches, sorts to order, scan-verifies and reslots; the layer batches and prints, which is the 80% peak season actually asked for. | ||
| Time to market | A WMS cutover before peak is a 6–12 week project nobody starts in October; the layer lands in 4–8 weeks (Deploi estimate, illustrative) and needs no floor re-map. | ||
| Performance & scale | Wave planning by carrier cutoff, zone picking and put walls scale to thousands of orders a day; a pick-list layer starts straining around 500 a day. | ||
| Data ownership & AI-readiness | Pick-path, picker-rate and wave-timing data live in the WMS vendor's database; the layer writes its wave and pick logs to a store you own. | ||
| Focus & opportunity cost | Warehouse software is not your differentiator; the build earns its slot only as a bridge to a WMS decision you are not yet ready to make. | ||
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) | Own-warehouse merchants who want scanner-guided batch picking without leaving the Shopify App Store |
| Deposco Fulfillment | Live — flagged — 0 reviews on a listing launched 2022-10-14; automated pick, pack, ship and receive workflows are on the listing, but wave and batch picking is not confirmed as a feature of this app; an August 2026 announcement added Shopify POS inventory visibility, positioned partly as a Stocky replacement path | Free with License; the WMS license itself is a direct contract, pricing not listed (verified Sep 2026) | Merchants already on Deposco's WMS through a warehouse partner; not a first pick from the App Store |
| WMS platforms sold outside the App Store | Category — Extensiv 3PL Warehouse Manager and Deposco's core WMS run wave, batch and zone picking but have no merchant-installable Shopify listing; Extensiv's App Store app is Extensiv Order Management, an order and inventory sync, not the WMS. You reach these through a direct contract or through your 3PL | Direct contracts; pricing not listed | 3PL-run fulfillment, where the warehouse's WMS already does this and your job is the order sync |
| Wave and batch pick-list layer | Build lane — A custom app that groups open fulfillment orders into waves by carrier cutoff, ship-by date or zone, prints consolidated pick lists sorted by a bin-location metafield, and drives a sort-to-order step on a tablet; an honest bridge, not a WMS | $15,000–$40,000 one-time plus ~15–20% a year in upkeep (Deploi estimate, illustrative) | One warehouse, seasonal peaks under roughly 500 orders a day, no WMS budget yet |
The Build Path
- Wave release on fulfillment orders: A scheduled job groups open fulfillment orders into waves by carrier cutoff, ship-by date, zone, or single-line versus multi-line, and holds the rest until the next release.
- Consolidated pick list by bin location: A bin-location metafield on each variant sorts a wave's combined pick list into one aisle path; the picker collects quantities for a dozen orders in a single pass.
- Sort-to-order on a tablet: A simple put-wall screen assigns each picked item to its order slot and flags shorts, replacing the second trip a miss would otherwise cause.
- Optional: barcode scan confirmation: Scan-to-confirm on pick and on pack, logged to your own database, so pick accuracy and picks per hour are measurable before you ever sign a WMS contract.
- Effort band
- $15,000–$40,000 build — Deploi estimate (illustrative); lands in the $10–25K or $25–75K contact-form band depending on scan confirmation and put-wall scope
- Typical timeline
- 4–8 weeks (Deploi estimate, illustrative); start no later than August for a November peak
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $2,500–$8,000/yr (Deploi estimate, illustrative) for API version bumps, printer and tablet changes and new wave rules. There is no subscription line.
- What you own — and what you take on
- You own: the wave rules, the bin-location data, the pick and wave logs and the put-wall UI. You take on: slotting discipline (a wrong bin metafield breaks the pick path) and the eventual WMS migration, which the logs make easier.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $8,000–$25,000 (WMS onboarding, bin mapping, training) | $15,000–$40,000 |
| Years 1–3 (recurring) | $36,000–$108,000 (illustrative WMS subscription) | $7,500–$24,000 (maintenance) |
| 3-year total | ≈$44,000–$133,000 | ≈$22,500–$64,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: a mid-market WMS subscription held flat at an illustrative mid-band; ShipHero publishes no price, so the figure is a placeholder for your quote.
- † Build path: wave release plus bin-sorted pick lists plus tablet sort-to-order; three-year horizon.
What the Sticker Price Hides
On the buy path
- — ShipHero's listing is free to install with additional charges and no published tiers; the real price arrives on a sales call, so budget from the quote, not the listing
- — A WMS cutover re-maps every bin and retrains every picker; scheduled in Q4 it collides with the peak it was meant to fix
- — Deposco's App Store listing carries 0 reviews and does not confirm wave or batch picking; the WMS behind it is a direct contract
- — Extensiv's App Store app is order management, not the 3PL Warehouse Manager WMS that actually runs waves
On the build path
- — Slotting discipline is the hidden dependency: one wrong bin-location metafield sends a picker the wrong way for the whole wave
- — Sort-to-order without scan confirmation trades mis-picks for speed; add scanning before volume, not after
- — ~15–20% of build cost per year in upkeep (Deploi estimate)
- — The layer tops out around 500 orders a day; plan the WMS decision before you hit it, not the week you do
What Merchants Say
Warehouse leads describe the same peak-season moment: single-order picking held until the day volume doubled, and the fix they wanted was one picker collecting for a dozen orders per aisle pass, not a full WMS project in October.
The WMS-app complaint shape: the connector installs free, then the onboarding, the per-order fees and the training surface on the contract, and reviewers say the listing gave no hint of the total.
If You Change Your Mind Later
If you bought and outgrow it
Leaving a WMS mid-contract means re-mapping bins, exporting pick and inventory history in whatever format the vendor allows, and retraining the floor; schedule it for February, never October. Your Shopify order data stays intact, because the WMS reads it rather than owning it.
If you built and want out
Nothing is stranded: bin-location metafields and the wave and pick logs stay in your store and feed the WMS onboarding when you outgrow the layer. Most WMS vendors import bin locations from a CSV, so the slotting work carries over intact.
When This Answer Changes
We're watching for:
- ▸ ShipHero publishing plan tiers on its Shopify listing (none as of September 2026)
- ▸ Extensiv or Deposco listing their WMS products, rather than their sync apps, on the Shopify App Store
- ▸ Shopify adding wave or batch pick lists to native fulfillment (nothing first-party as of September 2026)
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Is there a Shopify app for wave and batch picking?
One. ShipHero Inventory & Shipping (4.3★, 115 reviews) is the only Shopify App Store listing that sits on a WMS documenting batch-picking and order-sorting settings, and it publishes no price. Deposco Fulfillment lists pick, pack and ship workflows but does not confirm wave or batch picking and has 0 reviews. Extensiv's App Store app is order management, not its warehouse WMS.
What does it cost to add wave and batch picking to a Shopify warehouse?
Wave and batch picking costs either a WMS contract or a built pick-list layer. ShipHero and the direct-contract WMS vendors publish no prices, so budget from a quote. A built layer that groups fulfillment orders into waves and prints bin-sorted pick lists runs $15,000–$40,000 one-time (Deploi estimate, illustrative), plus 15–20% a year in upkeep (Deploi estimate). Below roughly 500 orders a day, the build is the cheaper bridge.
Do I need wave picking if a 3PL fulfills my Shopify orders?
No. A 3PL's WMS, such as Extensiv 3PL Warehouse Manager or Deposco, already releases orders in waves and batches picks across its clients. Your responsibility ends at a clean order and inventory sync into their system. Ask the 3PL for its peak-day throughput and its carrier cutoff times instead; those 2 numbers decide whether your delivery promises hold in November.
Your Next Steps
If you're going with BUY(matches your selected profile)
- Measure your peak-day ceiling: orders per picker-hour and the number of missed carrier cutoffs last season
- Book the ShipHero demo and at least one direct-contract WMS demo (Extensiv, Deposco); ask each for total first-year cost in writing
- Slot the warehouse before onboarding: bin locations on every variant
- Schedule cutover for the quietest quarter and run two weeks of parallel picking
- Keep the Shopify listing as the connector and negotiate the WMS contract on its own terms
If you're going with BUILD
- Store a bin-location metafield on every variant and audit it against the floor
- Define wave rules: carrier cutoffs, ship-by dates, single-line versus multi-line orders
- Ship the consolidated, bin-sorted pick list first; add tablet sort-to-order second
- Log picks per hour from day one; that number tells you when the WMS conversation starts
Official Docs & Sources
- Locations — Shopify Help Center
- Order routing — Shopify Help Center
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 clear peak without a WMS project?
We build the wave and batch pick-list layer on your fulfillment orders, and we'll tell you honestly when it's time for a WMS instead.
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.