The Shopify Purchase Order Workflow That Doesn't Need an ERP

The Five Jobs a PO Workflow Has to Do

Strip away the vendor category names and every purchasing system, from a clipboard to NetSuite, is trying to do the same five things:

An ERP does all five plus accounting, manufacturing, demand planning, and a dozen other modules. If you only need the five, you're paying for a lot of surface area you'll never open.

What Shopify Now Covers Natively (Updated June 2026)

This is the part a lot of "Shopify can't do purchase orders" advice is out of date on. Purchase orders and inventory transfers moved into the Shopify admin as Stocky was retired, and in June 2026 the two were connected: when you receive a purchase order, it now creates a transfer. Per Shopify's own changelog, that brings with it:

That is a legitimately usable version of jobs 2, 3, and 5. If you were budgeting for an ERP mostly because you needed a PO record and partial-receipt tracking, re-evaluate — you may already have it. (If you're still on Stocky, note that it stopped working permanently on August 31, 2026; our Stocky migration guide covers what to export.)

Where the Native Workflow Still Leaves You Typing

The gap isn't the purchase order object. It's everything on either side of it.

Your suppliers don't send CSVs. Native PO line-item import expects a CSV. Most independent distributors — auto parts, liquor, pet, hardware, apparel wholesale — send a PDF invoice attached to an email, sometimes a scan of a printed one, occasionally an Excel file with a layout that changes when they update their system. Getting that into a CSV is the manual data entry you were trying to eliminate. It just moved one step upstream. We broke down the tradeoffs between the three ingestion routes in CSV vs PDF vs barcode receiving .

New SKUs stop the line. A distributor adds a product line; three invoice lines reference SKUs that don't exist in your catalog yet. A PO can't receive against a product that isn't there, so receiving pauses while someone builds products — title, description, type, variants, price, cost — before the rest of the shipment can post.

Cost autofill is not weighted-average cost. Autofilling from the last purchase price is helpful, but it's the last price, not a blended one. If you bought the same SKU at three prices across a quarter, your margin reporting only tells the truth if cost per item is recalculated as a weighted average on every receipt. That's the difference between a cost field and real COGS tracking , and it compounds quietly.

The Middle Path: Close the Gaps, Keep the Platform

The workflow that works for most 200-to-5,000-SKU stores keeps Shopify as the system of record and adds invoice parsing on the front end and reorder signals on the back end. In practice, using Smart Restock , a week looks like this:

Nothing here replaces Shopify. Products, locations, and orders stay exactly where they are, and your accountant's export doesn't change. You've closed jobs #1 and #4 and taken the manual typing out of #3.

Watch the Receiving Step

Here's the part that replaces the CSV-building: uploading a supplier invoice and letting the line items extract automatically.

What the Two Paths Actually Cost

This is usually the deciding factor, so it's worth being concrete about the shape of it.

Mid-market inventory and ERP platforms — Cin7, Brightpearl, NetSuite and their peers — mostly sell on custom quotes rather than published rates, and the realistic all-in number for a small retailer includes three things merchants underestimate: the subscription, the implementation or onboarding project, and the internal time to migrate data and retrain staff. Industry write-ups routinely put small-to-mid retail deployments in the four-figures-per-month range once implementation is amortized, and NetSuite's own retail pricing is quoted per user on top of a platform fee. Whatever the exact figure for your store, it's a procurement decision with a timeline, not a checkbox.

Smart Restock is an app-level cost. Starter runs $9.99/month with a 14-day free trial, Lite is $19.99/month, and Unlimited Plus — the plan that includes AI product generation for high-volume catalogs — is $59.99/month, with metered overage rather than a forced tier jump when a heavy month lands. Setup is measured in minutes, not a quarter. Full details are on the pricing page .

The honest framing isn't "apps are cheaper." It's that an ERP prices in a lot of capability, and if you're buying it to solve invoice data entry and cost accuracy, you're paying for a warehouse-management and financials suite to get a receiving workflow.

When You Actually Do Need the ERP

Being fair about this matters, because the wrong call in either direction is expensive. Go get the ERP quote if:

If none of those describe you, the honest read is that you have a receiving and costing problem wearing an ERP-shaped costume. Solve the receiving problem, and revisit in a year with better data than you have now — which is, incidentally, one of the better arguments for closing the cost-accuracy gap first. An ERP migration goes far better when the inventory and cost history you're migrating is accurate.

Try it before you sit through another ERP demo

Run your next real supplier invoice through it during the 14-day free trial on Starter and see what's actually left over.

Close the gap without the migration

Keep Shopify as your system of record. Add the invoice parsing and cost accuracy an ERP was going to charge you five figures for.