Square Inventory Purchase Orders: Full Setup Guide

Square can create, send, and receive purchase orders — if you're on a paid plan. Purchase orders live in Square Dashboard under Items & services → Inventory management → Purchase orders, and they're included with Square Plus and Square Premium (in older account language, "Square for Retail Plus"; Square unified its plans in October 2025). You can pick a vendor, add items with quantities and unit costs, email the PO to the vendor from Square, and receive stock against it — including partial receiving — with unit costs saved and COGS tracked on a FIFO basis.

This guide walks through the whole Square purchase order workflow step by step, then covers the limits you'll want to know about before you build your ordering process on it — including the ones Square's own docs confirm.

Quick answer

To create a purchase order in Square:

In Square Dashboard, go to Items & services → Inventory management → Purchase orders and click Create
Choose the vendor (or create one inline), the delivery location, and the expected delivery date
Add items with quantity and unit cost — Square pulls per-vendor codes, SKUs, and costs if you've set them on the item
Click Create, or Save as Draft if you're not ready to commit
To send it, add the vendor's email, preview, and click Send — Square emails the PO directly, and you can keep a copy or export PDF/CSV
When the delivery arrives, open the PO and click Receive All, or Receive per line for partial deliveries — stock on hand and unit costs update automatically

That covers order creation and receiving. Below: the setup that makes it work well, and where the workflow ends.

Setting up vendors properly (do this first)

Purchase orders are only as good as the vendor records behind them. In Square Dashboard under Items → Vendors you can:

Create vendors, or add them inline while building an item or a PO
Assign a default vendor per item (bulk-assignable via item library export/import with the "Default Vendor Name" column)
Store vendor codes and SKUs per item, and edit unit costs per vendor — Square supports multiple vendors on the same item, each with their own cost
Deactivate vendors you no longer buy from; inactive vendors stop appearing in PO creation

If a vendor code includes a barcode, you can receive stock in the Retail POS app by scanning the vendor code — genuinely useful on a busy receiving day.

Low stock alerts and reordering

Square's reorder trigger is the low stock alert: in Dashboard, select items and use Actions → Update low stock alert to set a threshold per item, per location or across locations. Items at or below the threshold get flagged in your stock overview.

Two things to know:

Alerts are thresholds, not math. Square doesn't calculate the threshold for you from sales velocity, delivery lead time, or seasonality — you set a number per item and maintain it yourself. For a catalog of 50 items that's a Saturday chore; for 3,000 SKUs across two locations it's a job nobody actually does, which is why thresholds drift out of date and stockouts happen on items that technically had an alert set. (The math the threshold is standing in for is a reorder point.)
Auto-generated purchase orders are advertised but have been suspended. Square's marketing pages describe sending purchase orders automatically from stock forecasts, but Square staff confirmed in its seller community that auto-generated POs were disabled "while our team makes improvements to the feature," and we could find no announcement of the feature returning. Check the toggle in your own account before you plan a workflow around it.

So in practice, the Square reorder loop is: see flagged items → build the PO by hand → send. The awareness is automated; the ordering isn't.

Receiving, unit costs, and COGS

This is the strongest part of Square's PO workflow. When stock arrives:

Open the PO and click Receive All, Receive None, or Receive on individual rows for partial deliveries
Received quantities update stock on hand at the delivery location
Unit costs from the PO are saved automatically, and Square surfaces price, unit cost, and profit margin at receiving
Inventory value and cost of goods sold run on a FIFO basis, so receiving at accurate costs is what makes your COGS report mean something
Damaged or stolen items can be marked at receiving and are excluded from COGS

If you use Square POs, use them all the way through receiving — skipping the receive step is how the COGS report quietly becomes fiction.

The limits to know before you commit

These are factual, from Square's own documentation and seller community:

Whole numbers only. Purchase orders don't support decimal quantities for ordering or receiving. If you buy cheese by the pound, fabric by the yard, or produce by weight, Square POs can't represent your order accurately — a long-running seller-community complaint.
Editing a PO doesn't notify the vendor. If you change a PO after sending, Square does not automatically re-send it; you have to remember to use Send as Email again. The vendor's copy and your copy can silently diverge.
The PO is one email, one direction. Square can send the order out. It doesn't capture what comes back — a confirmation, a short, a substitution, a price change, a pushed delivery date. Whatever the vendor replies lands in your inbox, and the PO in Square stays exactly as you wrote it.
No suggested quantities. Even with alerts set, deciding how much to order — against sales velocity, lead time, pack sizes, and minimums — is manual.
Paid plan required. On Square Free you get basic item and stock tracking, but vendor and purchase order management starts at Square Plus.

None of this makes Square's POs bad — for a single-location shop with a modest catalog and reliable vendors, the native workflow is genuinely serviceable, and the receiving/COGS mechanics are better than most POS-native tools. The limits matter when order volume, SKU count, or vendor messiness grows past what one person can hold in their head.

Where the workflow actually ends

Notice the shape of the native loop: alert → build PO → email → receive. Everything between "email" and "receive" — the part where the vendor is involved — happens outside Square. That's the gap that grows with your business:

The vendor confirms 14 of 16 lines, subs one item, and raises a price. The Square PO still shows the original 16.
Receiving checks the truck against the original order, not the vendor-confirmed one — so a known short reads as a mystery variance.
The bookkeeper gets an invoice that matches neither, and reconstructs the story from your inbox.

For restaurants, Square's answer is the Square Restaurant Inventory add-on by MarketMan (launched April 2026, restaurants only, paid add-on to Plus/Premium) — a real inventory suite, and a sign Square knows the native tools stop short. For retail, and for anyone whose vendors reply by email, text, or portal, the missing piece is a procurement layer that keeps the PO alive after it's sent: a living purchase order that absorbs vendor replies as structured updates, lets receiving reconcile against the confirmed state, and hands accounting the finished story. That's the layer LineNow runs beside Square — Square stays the POS and the demand record; LineNow runs the vendor loop from suggested quantities through reply tracking to reconciled handoff. The deeper breakdown of that split is in Square Purchase Orders Are Not Enough.

Square Inventory Purchase Orders: Setup, Receiving, and the Limits to Know

Quick answer

Setting up vendors properly (do this first)

Low stock alerts and reordering

Receiving, unit costs, and COGS

The limits to know before you commit

Where the workflow actually ends

Sources checked

Square Inventory Purchase Orders: Setup, Receiving, and the Limits to Know

Quick answer

Setting up vendors properly (do this first)

Low stock alerts and reordering

Receiving, unit costs, and COGS

The limits to know before you commit

Where the workflow actually ends

Sources checked

Related