Build or Buy Inter-Store Inventory Transfer and Replenishment?
Inter-store inventory transfer and replenishment on Shopify is a WAIT under 8 locations: native transfers move stock between stores with in-transit status, partial receipts and Sidekick suggestions, included with the plan. Stocky, the first-party app that used to do this, shut down 2026-08-31. Buy Cin7 Core ($349–$1,199/mo, verified Sep 2026) when replenishment must link to purchasing; build rule-based rebalancing at $8,000–$20,000 (Deploi estimate, illustrative) when it doesn't.
Your profile — see how the verdict shifts
- Confidence
- High — Shopify's help docs confirm native transfers between store locations and suppliers with in-transit status, partial receipts, multi-shipment batches and Sidekick-created transfers, with no plan tier named as a requirement. The brief's verifier found the Stocky listing still resolving (3.2★, 201 reviews), but Shopify's own transition page records Stocky's hard sunset on 2026-08-31, so it's carried here as Sunset, not Live. Cin7 Core (49 reviews, still at the legacy dear-inventory handle) lists stock transfer without spelling out store-to-store scope; Veeqo is positioned on shipping and warehouse sync.
- Reference scenario
- $20M–$100M GMV · 3–8 retail stores plus online · Shopify POS · one weekly rebalancing rhythm · agency dev bench available but not required
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| 1–2 locations | WAIT | The two-store case is a phone call and a native transfer record with in-transit tracking. Nothing to buy or build; the process is the whole solution. |
| 3–8 stores plus online | WAIT | Native transfers with partial receipts and multi-shipment batches, Sidekick's transfer suggestions and a weekly stock-balance review cover it. Stocky's shutdown on 2026-08-31 changes nothing here; native inventory absorbed the transfer job. |
| 8–20 stores, weekly rebalancing by SKU | CUSTOMIZE | Deterministic min/max rules per store per SKU in a nightly job that creates the transfers costs $8,000–$20,000 (Deploi estimate, illustrative), against Cin7 Core at $349–$1,199/mo (verified Sep 2026) for a system you'd use a tenth of. |
| 20+ locations or purchasing-linked replenishment | BUY | Cin7 Core ties replenishment to purchase orders, supplier lead times and forecasting across a warehouse and many stores. Confirm store-to-store scope on the demo; the listing doesn't spell it out and carries 49 reviews (verified Sep 2026). |
What Inter-store inventory transfer and replenishment Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | A bestseller in stock at the store where the shopper is standing is a sale; the same unit three miles away is a markdown. Systematic transfers turn surplus into sell-through. |
| Operational efficiency | Medium | In-transit tracking, partial receipts and multi-shipment batches on the native transfer object replace the spreadsheet, the phone call and the mystery box that arrives uncounted. |
| Customer experience | Medium | Fewer 'we're out, try our other location' conversations, because the stock moved before the shopper walked in. |
| Data & insight | Medium | Transfer history by store pair shows which locations chronically over- and under-buy, which is the input to better initial allocations next season. |
Spend ceiling: Native transfers cost nothing, so spend only on the decision layer: the rules that say what moves where. Size that to the markdown dollars you take on stock stranded at the wrong store, not to the software category.
What buying enables (top apps)
- + Native, included: transfers between locations and suppliers, in-transit status with tracking, partial receipts, multi-shipment batches and Sidekick-created transfer suggestions
- + Cin7 Core: replenishment tied to purchase orders, supplier lead times and forecasting across a warehouse and many stores, from $349/mo (verified Sep 2026)
- + Veeqo: free multi-channel shipping and warehouse inventory sync when the network includes a fulfillment site
What building additionally unlocks
- + Deterministic min/max or days-of-cover rules per store per SKU, visible and auditable, instead of an AI suggestion
- + Nearest-surplus routing that prefers the sister store three miles away over the warehouse, with store roles respected
- + Transfers created automatically overnight for the sending store to confirm at open
- + A transfer performance view: lead time, fill rate and stranded-stock markdowns by store pair
Find Your Verdict in 3 Questions
Are you moving stock between fewer than ~8 locations on a weekly rhythm?
Yes: Your verdict: WAIT — native transfers with in-transit tracking, partial receipts and Sidekick suggestions cover it; add a fixed weekly stock-balance review.
No: Go to question 2.
Does replenishment need to link to purchase orders and supplier lead times, not only store-to-store moves?
Yes: Your verdict: BUY — Cin7 Core from $349/mo (verified Sep 2026); confirm store-to-store scope on the demo and weigh the 49-review listing.
No: Go to question 3.
Do you want deterministic min/max rules creating transfers automatically, with a dev bench to own them?
Yes: Your verdict: CUSTOMIZE — a nightly rebalancing job on native transfers at $8,000–$20,000 (Deploi estimate, illustrative).
No: Your verdict: WAIT — keep native transfers and the weekly review; revisit when the store count outgrows the habit.
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 | Native transfers are already in your admin; Cin7 Core is a configured implementation measured in weeks, and a rule-based rebalancing job runs $8,000–$20,000 (Deploi estimate, illustrative). | ||
| Recurring fees | Cin7 Core starts at $349/mo and reaches $1,199/mo (verified Sep 2026); native transfers are included with the plan, and a custom job's upkeep is 15–20% of build cost a year (Deploi estimate). | ||
| Maintenance & upgrades | Cin7 maintains its Shopify sync and rule engine; a custom job needs an API version bump each year and a rule review whenever assortments or store roles change. | ||
| Switching & exit | Replenishment rules and history configured inside Cin7 leave with Cin7; transfers created natively stay in Shopify no matter what runs on top of them. | ||
| Risk | |||
| Vendor risk | Cin7 Core is a real vendor with 49 reviews on a listing still parked at its acquired predecessor's handle (verified Sep 2026); Stocky's shutdown on 2026-08-31 is the reminder that even first-party apps end. | ||
| Security & compliance surface | An ERP-grade app reads every order, customer and stock movement; a rebalancing job reads inventory levels and writes transfers, and touches nothing about shoppers. | ||
| Platform-deprecation exposure | Native transfer objects are the first-party surface Shopify just expanded to replace Stocky; an app and a custom job both build on the same foundation. | ||
| Value | |||
| Fit to requirement | Cin7 Core brings replenishment linked to purchasing and forecasting; a custom job encodes your own store-by-store min/max rules and nothing else, which is the exact requirement under 20 stores. | ||
| Time to market | Native is live today; Cin7 Core is a multi-week implementation and the rebalancing job takes 3–6 weeks (Deploi estimate, illustrative). | ||
| Performance & scale | An ERP scales to warehouses, suppliers and dozens of stores; a nightly rules job scales in SKU and store count but never becomes a purchasing system. | ||
| Data ownership & AI-readiness | Stock movement history lives in Shopify on every path; the rules, thresholds and velocity signals you own in a build also feed forecasting and buying decisions. | ||
| Focus & opportunity cost | A weekly review of stock balances is a merchandising habit, not a project; the build earns dev time only once the habit can't keep up with the store count. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Native inventory transfers | Native — First-party, included with the plan; the help docs name no tier requirement. Create, track and receive transfers between store locations or to and from suppliers, mark them in transit with tracking, receive full or partial quantities across multiple shipments, and let Sidekick analyze stock balances and create transfers automatically | Included with the plan | Every retailer under roughly 8 locations; the mechanism is done, the weekly review is yours |
| Cin7 Core | Live — 4.6★, 49 reviews; listed under its legacy DEAR Inventory slug; no Built for Shopify badge | Standard $349/month (5 users, 2 integrations, 6,000 sale orders a year, unlimited locations), Pro $599/month (10 users, 4 integrations, 24,000 orders, material requirements planning), Advanced $1,199/month (15 users, 6 integrations, 120,000 orders, advanced warehouse management); annual billing saves 8%; 14-day free trial (verified Sep 2026) | Retailers whose replenishment must link to purchase orders, supplier lead times and forecasting |
| Veeqo Shipping and Inventory | Live — 4.0★, 125 reviews; Built for Shopify; Amazon-owned. Positioned on multi-channel shipping and warehouse inventory sync; store-to-store transfer fit is weaker and less explicit than Cin7 Core or native transfers | Free to install; order and shipping management always free, charges only for shipping labels and optional added services (verified Sep 2026) | Networks with a fulfillment warehouse where shipping and stock sync matter more than store-to-store moves |
| Stocky | Sunset — First-party Shopify app; delisted 2026-02-02, sunset 2026-08-31; read-only data export for at least 90 days | Free to install; core features were included with a Shopify POS Pro subscription (verified Sep 2026); no longer available after the sunset | Nothing new; export any remaining history before the read-only window closes |
| Rule-based rebalancing job (custom) | Build lane — A nightly job that reads inventory by location, applies min/max or days-of-cover rules per store per SKU, prefers the nearest surplus store, and creates the transfer in Shopify for the sending store to confirm at open | $8,000–$20,000 one time; $20,000–$45,000 with a transfer performance dashboard (Deploi estimate, illustrative) | 8–20 stores that want deterministic, auditable rules rather than AI suggestions or an ERP |
The Build Path
- Before you build: native transfers plus a weekly review: A stock-by-location report, Sidekick's transfer suggestions and a fixed weekly rebalancing slot cover most retailers under 8 stores; the transfer object tracks in-transit quantities, partial receipts and multiple shipments for you.
- Rule-based rebalancing job: A nightly job reads inventory levels per location, applies min/max or days-of-cover thresholds per store per SKU from recent sell-through, picks the nearest store holding surplus, and creates the transfer in Shopify for the sending store to confirm.
- Flow alerts at the reorder point: Shopify Flow fires when a location's quantity for a SKU drops below its threshold and notifies the store team or the buyer; Flow raises the flag, the job or a human does the cross-location math.
- Optional: transfer performance dashboard: Lead time from created to received, fill rate against requested quantity, and markdown dollars on stock stranded at the wrong store, by store pair; the numbers that tell you which locations chronically over- and under-buy.
- Effort band
- $8,000–$20,000 for the rebalancing job with rules and automatic transfer creation; $20,000–$45,000 with a transfer dashboard and per-store notifications — Deploi estimate (illustrative); lands in the $10–25K or $25–75K contact-form band
- Typical timeline
- 3–6 weeks for the rebalancing job; 8–12 weeks with the dashboard (Deploi estimate, illustrative); native transfers and the weekly review start today
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $1,500–$9,000/yr (Deploi estimate, illustrative), covering an annual API version bump and a rule review each season. There is no subscription line.
- What you own — and what you take on
- You own: the thresholds, the surplus-routing logic, the transfer history and the performance numbers. You take on: keeping store roles and thresholds current as the assortment changes, and confirming transfers at the sending store each morning.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $5,000–$15,000 (implementation, illustrative) | $8,000–$20,000 |
| Years 1–3 (recurring) | $12,600–$43,200 (Standard to Advanced tiers) | $3,600–$12,000 (maintenance) |
| 3-year total | ≈$17,600–$58,000 | ≈$11,600–$32,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: Cin7 Core between the Standard and Advanced tiers held flat, plus an implementation engagement; the native lane, at no additional cost, is the verdict for the reference scenario and sits at zero on both axes.
- † Build path: the rebalancing job without the dashboard, three-year horizon, upkeep at 15–20% of build cost per year.
What the Sticker Price Hides
On the buy path
- — Cin7 Core's $349/mo Standard tier (verified Sep 2026) is the entry price to a system you may use a tenth of; the implementation weeks are the larger cost
- — The listing doesn't state whether stock transfer covers store-to-store or warehouse-to-store only; get it in writing before signing
- — A listing parked at an acquired predecessor's handle (dear-inventory) is a small sign of how much attention the Shopify channel gets
- — Veeqo is free, but free for shipping and warehouse sync; it isn't a store replenishment tool and shouldn't be installed as one
On the build path
- — Thresholds set once become wrong by the next season; rule reviews need a calendar slot or the job quietly moves the wrong stock
- — Transfers created overnight that nobody confirms at open pile up as in-transit ghosts; the confirmation step is part of the design
- — Nearest-surplus routing needs store roles (flagship, outlet, seasonal) encoded, or it strips the flagship to feed an outlet
- — ~15–20% of build cost per year in upkeep (Deploi estimate)
What Merchants Say
The bestseller sells out at one store while the location across town holds six weeks of it; the transfer happens when a manager notices, not when the numbers say so.
After Stocky's shutdown, the recurring theme is trust: Sidekick's transfer suggestions get questioned on data fidelity, and managers want to see the rule behind a suggestion before they move stock.
If You Change Your Mind Later
If you bought and outgrow it
Leaving Cin7 Core means the replenishment rules, forecasts and purchasing links leave with it; the transfers themselves stay in Shopify's history. Export rule definitions and supplier lead times before you cancel, so the next system or the native lane starts from your numbers.
If you built and want out
Nothing is stranded: the job writes native transfers, so switching it off leaves you exactly on the WAIT lane with full history intact. The thresholds and routing rules are plain data that an ERP can import if you later graduate to one.
When This Answer Changes
We're watching for:
- ▸ Shopify adding deterministic min/max or days-of-cover replenishment rules to native inventory, beyond Sidekick's AI suggestions (none as of September 2026)
- ▸ Cin7 Core moving its listing off the legacy dear-inventory handle or spelling out store-to-store transfer scope on the listing
- ▸ Your location count passing 8 stores or a warehouse joining the network; both move the verdict off WAIT
Verdict change log:
- 2026-08-31Shopify's Stocky app shut down (delisted 2026-02-02, hard sunset 2026-08-31), retiring the first-party stock-transfer and replenishment app bundled with POS Pro. Native inventory transfers with in-transit tracking, partial receipts, multi-shipment batches and Sidekick-created transfers absorbed the transfer job, which is why the verdict is WAIT on native rather than 'use Stocky'. Rule-based replenishment across many stores is the piece left to buy or build.
Common Questions
Does Shopify natively transfer inventory between stores?
Yes. Shopify's native inventory transfers move and track stock between your store locations, or to and from external locations such as suppliers, with no plan tier named as a requirement. You can mark a transfer in transit with tracking, receive full or partial quantities, split it across multiple shipments, and let Sidekick analyze stock balances and create transfers automatically. Stocky, the first-party app that used to do this for POS Pro, shut down on 2026-08-31.
Do I still need Stocky or POS Pro for store-to-store transfers?
No. Stocky shut down on 2026-08-31 and its stock transfer and replenishment features moved into native inventory, which every plan gets. POS Pro (+$89 USD/month per location, verified Sep 2026) still matters for returns and exchanges at any location, richer customer profiles and per-register cash tracking, but creating and receiving transfers doesn't depend on it. Export any remaining Stocky history before its read-only window closes.
When is Cin7 Core worth paying for replenishment?
Cin7 Core earns its $349–$1,199/mo (verified Sep 2026) when replenishment has to link to purchase orders, supplier lead times and demand forecasting across a warehouse and 20 or more stores. Under that, native transfers plus a rule-based rebalancing job at $8,000–$20,000 (Deploi estimate, illustrative) covers store-to-store moves for less. The listing carries 49 reviews at the legacy dear-inventory handle and doesn't spell out store-to-store scope, so confirm that on the demo.
Your Next Steps
If you're going with WAIT(matches your selected profile)
- Set a fixed weekly rebalancing slot and run the stock-by-location report before it
- Create transfers natively with in-transit status and tracking; receive partially when shipments split
- Review Sidekick's transfer suggestions in that slot and note which ones you overrode and why
- Export any remaining Stocky history before its read-only window closes
- Diary a re-decision at 8 stores or when a warehouse joins the network
If you're going with CUSTOMIZE
- Define min/max or days-of-cover thresholds per store per SKU from the last 90 days of sell-through
- Encode store roles so surplus routing never strips a flagship to feed an outlet
- Build the nightly job to create transfers in Shopify for the sending store to confirm at open
- Add Flow alerts at the reorder point for the SKUs that can't wait for the nightly run
- Measure lost-sale and markdown dollars by store pair before and after; that delta is the ROI
Official Docs & Sources
- Inventory transfers — Shopify Help Center
- Transitioning from Stocky — Shopify Help Center
- Locations — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Build or Buy Cash Management and Till Reconciliation on Shopify?
POS Pro reconciles each register natively. Nothing rolls sessions up across stores or flags repeated shortages, and no app does. Write the SOP; build the roll-up.
Build or Buy Clienteling for Shopify POS Store Associates?
POS Pro already shows purchase history at the register; associate outreach, wishlists and tasks are the gap. Endear is the one app, with 17 reviews.
Build or Buy In-Store Returns of Online Orders (BORIS) on Shopify?
POS Pro already processes returns and exchanges of online orders at any location. Buy Loop only for policy automation; build only P&L attribution for store managers.
Build or Buy Loyalty Redemption at the Shopify POS?
Two well-reviewed apps already redeem points at the Shopify register. This is one of the cleanest buy decisions in retail, and the build case is narrow.
Build or Buy POS–Ecom Coherence on Shopify?
POS and ecom coherence on Shopify is native: one store, one catalog, one inventory pool, one customer record — the sync problem disappears.
Ready to move stock before the sale is lost?
We'll set up the weekly rebalancing rhythm on native transfers first, and build the min/max rules that create transfers overnight only if your store count needs them.
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.