Did Shopify already replace Stocky with native purchase orders?

Native POs exist, but merchant threads still report missing retail price on receive, cost write-back, label printing, reorder suggestions, supplier MOQ, and landed cost. Those operational loops are app-sized, not theme-sized.

Is Shopify Plus B2B enough without apps?

Plus adds company accounts, catalogs, and a B2B checkout. Multi-step approvals, credit-limit holds, VIES reverse-charge notes, and pack-size ordering are still commonly custom or missing.

Why vote on a Shopify app draft instead of installing a suite?

Suites often resell ERP, PIM, or full wholesale portals. A DraftPlugins proposal is a single job you can reject or waitlist before anyone writes production code.

Shopify App Gaps Worth Building After Stocky

Native Shopify purchase orders, Plus B2B, and Flow still leave receiving, credit holds, variant metafields, and non-Plus automation to spreadsheets. Those jobs are the right size for vote-to-build App Store drafts.

Shopify already sells the checkout. The apps worth voting on in 2026 sit in the loops Shopify still treats as “bring a spreadsheet or Plus plus a partner.” After Stocky leaves the App Store and native purchase orders remain a blank form with a receive button, retailers who scan hundreds of units a week are saying the same thing in the community: receiving is slower, retail price is missing from the receiver, cost does not reliably write back, and nothing turns a low-stock alert into a draft PO at supplier MOQ.

That is not a theme problem. It is not a page-builder problem. It is an operations desk that belongs in the admin next to Products and Orders, with a screenshot that looks like Shopify — not WordPress.

Where native Shopify stops

Inventory quantities per location, basic transfers, and low-stock notices are native. Lot numbers, expiry, serials, FEFO, bill of materials, and a purchasing loop with lead times are not. Plus B2B added companies, catalogs, net terms, and a wholesale checkout. It did not add multi-step procurement approval, credit-limit enforcement against an outstanding balance, or EDI. Flow is powerful on Plus and awkward for custom actions on cheaper plans. Variant metafields still fight the bulk editor. Those gaps are documented in merchant threads, partner blogs, and Shopify’s own Stocky sunset notes — they are not invented keywords.

App-sized jobs, not another OS

A useful Shopify App Store draft on DraftPlugins names one trigger (a PO arrives, a B2B cart is submitted, a variant metafield must change on 400 SKUs) and one owner (receiving, finance, merchandising). It states what the first release will not become: an ERP, a full WMS, or a replacement for Shopify Functions. Voters can tell whether the workaround they run this week — CSV to Dymo, a Plus-only Flow, a second inventory SKU — would actually go away.

Browse the Shopify hub, vote on the desks that match a store you operate, and join the waitlist. Nothing here is listed on the live App Store until the community threshold is met and a release ships.

Shopify App Gaps Worth Building After Stocky and Native B2B

Where native Shopify stops

App-sized jobs, not another OS

Frequently asked questions