Shopify B2B Purchase Order Number Workflow: Checkout, Draft Orders, Corrections, and Approval

Define what the PO number means in your buyer relationship

Do not begin by making the field mandatory for everyone. First identify which accounts actually use formal purchase orders and what their number represents. For one buyer it may authorize a department to spend up to a stated amount. For another it may simply be a reference used by accounts payable to match an invoice to a receiving record. Those are different controls even though both produce a string such as PO-48217.

Write down three ownership questions: who creates the PO on the buyer side, who is allowed to place the Shopify order against it, and who can correct the reference if it was typed incorrectly. Then decide which changes are clerical and which require a new commercial approval. A corrected digit in a reference is not the same thing as doubling quantity or changing the destination address.

A PO number is not proof that the buyer's organization approved the purchase unless that is actually how the buyer's internal system works. Treat the number as a reference carried with the order, not as a universal substitute for an approval workflow.

For self-service orders, let the authenticated B2B buyer enter the PO at checkout

Shopify requires B2B customers to use customer accounts for the B2B experience. In Shopify's documented checkout flow, the signed-in buyer selects the company location, adds products, proceeds to checkout and has the option to enter a purchase order number. If the location uses net terms, the buyer can submit the order without immediate full payment according to those terms; if the location is configured for draft review, the checkout can instead be submitted for merchant approval.

After checkout, Shopify says the purchase order number is visible on the order status page when one was entered. That matters because the buyer can confirm the reference attached to the order rather than discovering a mismatch weeks later when accounts payable receives an invoice.

Operationally, teach purchasing teams where the field belongs and what format their own organization expects. Do not invent a universal PO syntax. Some companies use one number per order, others reuse a project reference, and others encode department or fiscal-year information. Your storefront should preserve the buyer's agreed process rather than impose a pattern that has no business reason.

For phone or email orders, add the PO to the B2B draft order instead of keeping it in an inbox

Sales-assisted wholesale orders often begin outside the storefront. Shopify documents creating a B2B draft order for a company that sends an order by email or phone. After selecting the B2B customer and company location, the merchant can add a purchase order number in the draft order's PO number section before collecting payment, sending an invoice or applying payment terms.

That is cleaner than leaving the PO only in an email thread because the reference travels with the Shopify order object used by operations. It also keeps the sales-assisted path closer to the self-service path: whether the buyer typed the PO at checkout or the merchant entered it while building a draft, the business has one place to reconcile the final order reference.

If the salesperson is transcribing a PO supplied verbally or from a PDF, add a human verification step before the draft becomes an order. The risk here is not exotic software failure; it is a transposed digit that causes the buyer's invoice to fail matching later.

Decide when a PO correction is clerical and when the order needs review again

Corrections are where a simple field becomes a procurement-control problem. B2B Procurement OS advertises self-service editing of unfulfilled orders for quantity, shipping address, PO number and cancellation. The unfulfilled boundary is important: the listing does not promise unlimited edits after fulfillment, and an operation that has already shipped should not be treated as if it were still a flexible shopping cart.

Create a change matrix. A PO-number typo with no commercial change may be clerical. A quantity increase changes spend. A shipping-address change may alter freight, tax or receiving expectations. A cancellation changes the commitment entirely. Your policy should say which changes can proceed as corrections and which should return to an approval or merchant-review step.

Do not claim that a specific edit automatically triggers re-approval unless the product explicitly documents that behavior for your configuration. B2B Procurement OS separately advertises multi-level approval workflows with conditional rules based on order amount and self-service order editing. If your requirement is 'every material edit must automatically restart approval,' verify that exact sequence in your implementation before relying on it.

Use approval rules for spend authority, not merely for the presence of a PO number

A buyer can enter a syntactically perfect PO number and still lack authority for a large purchase. Conversely, an authorized buyer may place an urgent order while the formal PO is generated moments later under the buyer's own process. The presence of text in a PO field therefore should not become your only procurement control.

B2B Procurement OS lists multi-step approval examples such as Purchasing, Manager and CFO, with conditional rules based on order amount. That is the more appropriate layer when the buyer's organization wants spend authority to change as the order becomes larger. The PO reference can remain attached to the order while the approval chain answers a different question: who is allowed to commit the company to this spend?

For a practical example, a purchasing coordinator might prepare a $3,000 restock using the correct PO reference, while a $40,000 expansion order requires manager and finance review. The same PO field can exist in both orders; the approval requirement comes from policy, not from the formatting of the reference.

Keep merchant review separate from the buyer's internal approval

Shopify can be configured so a company location submits orders as draft orders for merchant review. In that checkout mode, the B2B customer sees a submit-for-approval action and the order remains a draft until the merchant accepts it or the customer completes payment after an invoice is sent. That is useful when the seller needs to check inventory, freight, negotiated terms or another condition before accepting the order.

The wording can be confusing because the buyer may also have its own internal approval chain. Keep the two gates separate in your process map. Buyer-side procurement approval answers whether the customer's organization authorizes the spend. Merchant-side draft review answers whether the seller accepts the proposed order. One does not automatically prove the other occurred.

A reliable record therefore has at least the commercial order, the PO reference when the account uses one, the buyer's required approval state, and the merchant acceptance state when seller review is enabled. That structure makes disputes easier to reconstruct than a shared inbox full of 'approved' messages with no indication of which approval they refer to.

Design the invoice-matching handoff before the first order goes live

Ask the buyer's accounts-payable team what they need to match. The PO number may need to appear on documents they use for reconciliation, but a successful match can also depend on supplier name, bill-to entity, line-item description, quantity, delivery evidence or another field. Do not assume the PO reference alone guarantees payment acceptance.

Shopify's native documentation confirms that buyers can enter the PO at checkout and merchants can add it to B2B drafts. B2B Procurement OS confirms self-service PO-number editing for unfulfilled orders. Those are useful capture and correction capabilities; neither should be described as a complete external ERP or accounts-payable integration unless you have separately verified that integration.

For the first few accounts, reconcile one finished order from buyer request through Shopify order and payment record. Confirm that the PO survives the path your staff actually use, that corrections are visible to the people who need them, and that the buyer's finance team can identify the order without asking sales to reconstruct the history.

Choose B2B Procurement OS when the PO field is part of a larger procurement workflow

If your only requirement is to capture a PO number on ordinary B2B checkout or a sales-created draft order, Shopify's documented native features may already cover the core job. Add a procurement app when the reference sits inside a more demanding process: multiple approvers, company credit limits, net terms, repeat ordering, quote requests or controlled edits before fulfillment.

B2B Procurement OS is designed around that broader job. Its current listing combines multi-level approvals, per-company credit limits and net terms, saved-list or CSV reordering, volume quote requests and self-service editing of unfulfilled orders including PO number. That combination is more relevant to a purchasing department than a standalone custom field because it keeps the reference next to the controls governing the order.

As of September 15, 2026, the official listing shows Starter at $79/month, Growth at $199/month and Enterprise at $499/month, each with a 14-day free trial. B2B Procurement OS is available in English. Start with a real account whose PO process currently creates email back-and-forth; if the only friction is initial PO capture, keep the simpler native path. If corrections, approvals and credit checks repeatedly spill outside Shopify, the broader procurement layer is easier to justify.

• Define who creates, enters and may correct a PO number for each account.
• Use authenticated B2B checkout for buyer-entered PO references when the account orders self-service.
• Put emailed or phoned-in PO references on the B2B draft order rather than leaving them only in correspondence.
• Separate clerical PO corrections from commercial changes that alter quantity, address or commitment.
• Do not treat the existence of a PO number as proof of buyer-side approval.
• Keep buyer procurement approval and merchant draft review as distinct states.

Apps mentioned in this guide

Frequently asked

Can Shopify B2B customers enter a purchase order number at checkout?

Yes. Shopify's current B2B customer-account documentation says signed-in B2B customers have the option to enter a purchase order number during checkout, and the number is shown on the order status page when provided.

Can I add a PO number to a Shopify B2B draft order?

Yes. Shopify documents a PO number section when a merchant creates a B2B draft order for a company, including orders received by phone or email.

Does a PO number prove the buyer approved the order?

Not necessarily. A PO number is a reference whose business meaning depends on the buyer's process. Approval authority should be modeled separately when the buyer requires manager, finance or other procurement sign-off.

Can B2B Procurement OS let buyers correct a PO number?

Its current Shopify App Store listing advertises self-service editing of unfulfilled orders including quantity, shipping address, PO number and cancellation. Define your own re-approval policy for material changes and verify any automatic re-approval behavior your process requires.

Is B2B Procurement OS available in English?

Yes. B2B Procurement OS is available in English. ShopRadar links to the official b2b-procurement-os App Store slug with locale=en.