Purchase orders in Shopify: what native covers, when apps help, and the 8 fields every PO needs

Yes, Shopify has native purchase orders — you can create a PO, track it from draft to ordered, and mark items received, which updates your inventory counts at the chosen location. Since the Stocky sunset on August 31, 2026, this native PO workflow is the default, and it covers the basics well. What it doesn't do is the thinking around the PO: suggested quantities, lead-time tracking per supplier, and order-by dates. This guide walks the native workflow step by step, shows exactly what updates in your inventory and when, and then draws the honest line between "native is enough" and "an app earns its price." (Behavior documented per the Shopify Help Center purchase order pages, accessed Oct 2026; Shopify can and does adjust the admin, so treat exact button locations as current as of October 2026.)

What native Shopify POs cover

As of October 2026, the admin includes:

• Creating purchase orders with a supplier, destination location, line items, quantities, and costs.
• Draft POs you can save, edit, and confirm later — useful for planning next month's buys without committing.
• Status tracking from draft through ordered, with receipt handling.
• Marking items received, which increases inventory at the selected location — partial receiving included, so a shipment that arrives half-full doesn't force an all-or-nothing update.
• Supplier records that a PO attaches to, so order history accumulates per supplier.
• Linked inventory transfers — the data model connects POs to the transfer objects that move stock (visible in Shopify's API documentation as well as the admin).

What's deliberately not there: automatic reorder quantities, lead-time measurement, minimum-order-quantity and case-pack logic, or sending the PO to your supplier from inside the admin — plan to deliver the document yourself (print, PDF, or paste into an email to the supplier). For small catalogs that's a non-issue; for a buyer placing dozens of POs weekly, it's where apps start earning money. One 2026 platform change matters for tooling: on September 17, 2026, Shopify shipped a Purchase Order Read API in the GraphQL Admin API (2026-10), letting apps read POs, line items, supplier snapshots, and linked transfers. It's read-only — the release notes state purchase order mutations are not included — which means apps can now build reporting on your native POs, but creating POs still happens in the admin or inside an app with its own PO records.

Creating your first purchase order natively

1. In the Shopify admin, go to Products → Purchase Orders and click to create one. (If you don't see it, your store's plan and permissions are fine — POs are standard admin features; check that the Products section isn't collapsed in your navigation.)
2. Pick the supplier. Choose an existing supplier record or create one — supplier name, contact, and reference go on the PO. Keep supplier records current; they're the spine of your ordering history now that Stocky is gone.
3. Pick the destination location — your warehouse, your retail store, or a 3PL location synced into Shopify. Inventory will land here when you receive.
4. Add line items. Search products and variants, set the quantity you're ordering, and enter the unit cost. The cost matters beyond this PO: it feeds your cost-per-item and profit reporting.
5. Add reference details — the PO number, expected arrival date, and any notes (payment terms, freight method). The expected date is optional in the form and indispensable in practice; more on that below.
6. Save as draft or confirm the order. Draft keeps it editable and out of your open-PO counts; confirming marks it ordered and puts it on the books.
7. Deliver it to the supplier yourself — print, save as PDF, or copy the line items into an email. The admin tracks the order; the correspondence is yours.

Time for a first PO: a few minutes. The real work — deciding what and how much — happens before you open the form, which is why the discipline section below matters more than the click path.

The PO → receiving → inventory flow

Understanding what updates when prevents the classic "my counts are wrong" support ticket:

Two implications worth internalizing:

Receiving is the moment of truth. The received quantity should be what physically arrived, not what the PO says. Suppliers short-ship, substitute, and mispack constantly. If you mark 120 received when 112 showed up, your counts — and every reorder calculation built on them — are now wrong until a count catches it. Counting discipline (cycle counts vs. full stock takes) is covered in the Shopify inventory counts guide; the one-line version for POs: verify at the box, not at the desk.

The gap between ordered and received is invisible to your storefront. While 200 units sit "on order," Shopify still shows your current on-hand — and if that's 3 units, you're one good day from selling out with stock en route. This is why open-PO visibility (next section) and backorder handling matter; the overselling guide covers the storefront side of that gap.

When native is enough — and when a PO app earns its price

Native is enough if:

• You place a handful of POs a month and compute quantities yourself.
• Your suppliers are few and reliable, and lead times live in your head (accurately).
• You don't need PO reports beyond what the admin shows.

An app earns its price when one or more of these is true:

• Lead-time tracking. Native POs record what you ordered, not how long the supplier actually took. If you reorder based on a quoted 30 days while the supplier averages 38, your reorder dates are systematically late — the "quoted 30, delivered 41" problem. Apps like Stockroom (free) and Stockie ($59.99 tier) track supplier history per PO.
• Auto-suggested quantities. Any standing reorder logic — forecasting, min/max per SKU — lives in apps, not the admin. Native has ABC analysis for segmenting your catalog, but no suggestion engine.
• Multi-supplier catalogs where one variant comes from different suppliers at different costs.
• MOQ and case-pack handling. Suppliers don't sell in units of 1; if you must order in cases of 12 with a 120-unit MOQ, native POs will happily let you order 37. Apps with MOQ/case-pack logic round correctly — and the ones that don't will inflate your order.
• PO documents at volume. Emailing, PDF-ing, and tracking dozens of POs weekly is workflow software territory.

Price-check before you install: Stockroom covers unlimited POs and receiving free; Stockie gates POs and barcode receiving behind its $59.99 tier; Sumtracker ($59+) bundles POs with multichannel sync. If the only gap is knowing what to order, a planner or buying-list tool is cheaper than a full PO suite. (Verified pricing, October 2026, from each app's App Store listing.)

PO discipline that keeps you from running out

A PO system records decisions; it doesn't make them. Three habits do most of the preventive work:

1. Order-by dates from lead times, written on every PO. For each SKU, the reorder point is demand during lead time plus safety stock. Worked example: your cedar trail sock sells 3.2 units/day. Your supplier quotes 30 days but has averaged 38 — use the actual, which is why lead-time records matter. Safety stock to cover a typical delay: 25 units. Reorder point = (3.2 × 38) + 25 = 147 units. When on-hand drops to 147, the PO must go out that day — not when you "notice it's low." The full math, including how stockouts poison the velocity number you feed it, is in the reorder point formula guide.

2. Keep open-PO visibility as a standing view. Before you place any PO, check what's already incoming for that supplier — double-ordering is the expensive twin of stockouts, and it happens most when three people place orders from three tabs. Native shows your POs in list form; apps add per-supplier "on order" rollups. Either way, make "what's already on order?" the first question of your buying routine.

3. Receive accurately, every time. Receiving is where your inventory data quality is won or lost, and it's the cheapest moment to catch a supplier error. Verify counts physically, record shortages as shortages (not silent shrinkage), and reconcile against the PO before closing it. Repeat offenders — the supplier that's short twice in a row — deserve a conversation and a safety-stock bump.

This is also where a buying-list workflow plugs in. Tools that produce a weekly list of what to reorder and by when — whether that's a spreadsheet, Tallyfold's restock plan ($5), or the weekly Buying List in our app InventoryX (in development, no published price, intended to turn each week's list into draft native POs, opt-in) — exist to make step 1 mechanical instead of memory-dependent. The PO form was never the hard part; knowing today was the day was.

The 8 fields every purchase order needs

Whether you use the native form, an app, or a template, a purchase order that omits any of these will eventually cost you an argument with a supplier:

1. PO number — unique, sequential, quoted on every related email and invoice. Without it, "that order from March" is unprovable.
2. Supplier name and billing/contact details — the legal entity, not the sales rep's name.
3. Ship-to location — the exact Shopify location receiving the stock, so receiving updates the right counts.
4. Line items with SKU, quantity, and unit cost — SKUs, not product titles; titles drift, SKUs are the contract.
5. Order date and expected delivery date — the expected date is your early-warning trigger: when it passes with no delivery, you chase. (If it's blank, you can't be early.)
6. Payment terms — Net 30, deposit, COD. Prevents the "we thought you prepaid" dispute.
7. Shipping method and freight responsibility — who pays, which carrier, FOB terms if applicable.
8. Case-pack and MOQ notes — "ordered in cases of 12; 120-unit MOQ met." When the invoice doesn't match the PO, this line explains it.

That list doubles as a review checklist: any PO in your system missing one of the eight is a future dispute. Shopify's own Help Center provides a purchase-order template for the document format (Shopify Help Center, accessed Oct 2026); the fields above are what make any template work.

For the email side of ordering — what to send the supplier and why confirmations matter — see how to email a purchase order.

Common questions

Does Shopify have purchase orders? Yes — POs are native to the admin as of October 2026. You can create a PO with a supplier, destination location, line items, and costs, save it as a draft, confirm it, and mark items received (partially, if needed), which updates inventory at the chosen location. What native doesn't do: suggested quantities, lead-time tracking per supplier, or emailing the PO to your supplier.

How do I create a purchase order in Shopify? Products → Purchase Orders → create. Pick the supplier and destination location, add line items with quantities and unit costs, add the PO number and an expected delivery date, then save as draft or confirm. You'll deliver the document to the supplier yourself — print, PDF, or paste into an email. The first PO takes a few minutes; the deciding-what-to-order part happens before you open the form.

Does receiving a PO automatically update inventory in Shopify? Yes. When you mark items received, the received quantity is added to inventory at the PO's destination location — partial receiving included. Until you receive, your on-hand number doesn't move, which means stock "on order" is invisible to your storefront: if on-hand is 3 with 200 inbound, you're one good day from selling out.

Do I need a purchase order app for Shopify? Not if you place a handful of POs a month and compute quantities yourself. Apps earn their price for lead-time tracking per supplier, auto-suggested quantities, multi-supplier catalogs, MOQ and case-pack logic, or PO documents at volume. Since the September 17, 2026 PO Read API, apps can also build reporting on your native PO history — read-only, so PO creation stays in the admin or inside an app.

Can I send a purchase order to my supplier from Shopify? No, as of October 2026 — the admin tracks the order but doesn't email it. Download the PDF, print it, or paste the line items into an email yourself. That's also why the eight fields above matter: your PO document is the contract the admin never sends.

The next step

Place your next three POs with an expected delivery date filled in and an order-by date calculated from your supplier's actual lead time — then track whether the supplier hit it. Three data points per supplier is enough to know whether your reorder math has been running on fiction; the supplier lead time guide shows how to build that record without new software.