Choose a purchase-order workflow for a company store when purchasing needs to approve a defined commitment before the supplier starts work. Choose company-card payment when an authorized buyer can approve and pay for the order in the same step. Use a hybrid when recurring employee orders and large campaign purchases need different controls. The deciding factor is not which checkout looks easiest. It is whether the buying process can reliably connect spending authority, payment and production release.
A PO number field alone does not establish that connection. Neither does a successful card charge. Before launch, agree exactly what lets a merchandise order move into production, who can authorize it and what happens when that authorization changes.
Publisher perspective: Brand Sauce provides company-store services. This is our recommended buying-process framework, not a promise that a specific payment method, credit term or purchasing integration is included in every Brand Sauce store. Confirm the proposed configuration and commercial terms in writing. Platform examples below come from current official documentation checked October 7, 2026.
Separate four decisions that checkout can hide
Merchandise purchasing involves four questions: is this person allowed to request the item, has the business approved the expense, how will the supplier be paid, and may production begin? Treat these as separate decisions even if one person handles all four.
An employee may be entitled to choose a welcome gift without authority to commit the company to any product in the supplier’s range. A department manager may approve a budget without being an authorized cardholder. Accounts payable may have the invoice without the artwork approval. None of those situations is inherently a problem; the problem is allowing the order to advance without the missing decision.
| Decision | Evidence to retain | What it does not prove |
|---|---|---|
| Recipient eligibility | Campaign eligibility or approved request | Permission to spend above the program limit |
| Spending approval | Approved PO, delegated limit or named approval | Supplier acceptance of payment terms |
| Payment arrangement | Agreed billing terms and payment reference when paid | Artwork, sizes or delivery details are final |
| Production release | Named release owner and dated acceptance record | Shipment or delivery has occurred |
For ongoing programs, the authority may be established in advance rather than individually for every shirt. Document the scope of that standing approval: permitted products, eligible recipients, period, destination rules and spending ceiling. Our department-budget guide addresses allocation; this guide addresses the gate between that authority and a supplier order.
Choose the route by how purchases are authorized
| Route | Good operational fit | Main tradeoff |
|---|---|---|
| Authorized company card | A named buyer can approve a bounded order and pay immediately | Payment can happen before a separate approval unless checkout prevents it |
| PO-backed ordering | Purchasing must approve supplier, amount and scope before commitment | Orders can stall while references, changes or terms are resolved |
| Review before release | Artwork, freight, scope or funding requires a final check | Someone must actively work the review queue |
| Hybrid by program | Routine gifts and larger custom buys have different approval needs | Routing rules and reporting must stay explicit |
Card-first is useful when the authorization really is simple. A marketing buyer ordering a small, approved event replenishment may not need a second purchasing workflow. Set the allowed scope and transaction limit, identify who handles a declined charge, and keep the order confirmation with the internal approval. Do not build the process around an employee lending a personal card while waiting for someone to resolve company funding.
PO-backed ordering is useful when the commitment needs a purchasing record. A uniform rollout with specified garments, decoration and destination may benefit from an agreed quotation attached to an approved PO. Confirm that the supplier accepts the arrangement before recipients order. Request any credit approval, deposits, invoice instructions and payment terms early; a buyer’s internal approval does not establish supplier terms.
Review-first is useful when the final order is not yet complete. A request can collect intended quantities and choices while still waiting for a freight quote or artwork decision. Make the recipient-facing status honest: “submitted for review” is different from “in production.” Shopify’s B2B checkout documentation, for example, describes draft-order review separately from payment-method and payment-term options. That illustrates the distinction; it does not verify any other provider’s workflow.
Decide what the PO field actually checks
Ask a vendor to demonstrate what happens after someone types a number into the PO field. Is the value merely saved as text, checked against a list, matched to a purchasing system or reviewed by a person? A required field can prevent a blank entry while still accepting the wrong reference.
For a PO-controlled program, use a small approval register or an agreed system record. It should connect the reference to the supplier, buying entity, approved scope, currency, period, ceiling and owner. If the store cannot check those conditions itself, identify the human review step that will. Describe that as manual control, not automation.
Decide whether the PO covers one purchase, a campaign or a stream of releases. A one-off jacket order should not accidentally become the reference for unrelated gifts six months later. If the business permits a continuing PO, specify which orders consume its available amount and which charges require separate approval.
Do not make employees interpret purchasing policy at checkout. If their only job is selecting an eligible gift, keep PO assignment with the administrator where the supported workflow permits. If a manager must choose a department reference, show only the appropriate choices and test an invalid selection.
Write one production-release rule
Use a sentence the store administrator, supplier and purchasing team can all apply. For example: “Release an order only after its funding route is accepted, its total falls within the approved scope, and its product, artwork and delivery details are final.” Then state who records that decision and where.
For card purchases, specify whether a successful payment is required before release and how failures are handled. For PO-backed purchases, specify the accepted reference and any supplier conditions. For review-first requests, name the reviewer and escalation route. There should be no permanent queue that everyone assumes someone else monitors.
Payment timing needs its own written definition. Shopify’s payment-terms documentation distinguishes immediate payment, net periods, due-on-fulfillment and fixed-date arrangements. Its net periods start when the order is placed, and it states that payment is not automatically captured when terms expire. Deposit requirements have a Shopify Plus plan requirement. These are Shopify-specific details—not universal definitions or Brand Sauce terms.
The practical lesson is to ask for the actual due-date trigger and collection process, not just the label “net 30.” Also confirm what starts the production clock. Waiting for purchasing approval should not silently consume a promised manufacturing window that assumes the order is already released.
Reserve approval capacity before the invoice arrives
A continuing purchasing limit needs visibility into accepted commitments, not only invoices already received. Otherwise several orders can individually appear affordable while collectively exceeding the approved amount. Have the purchasing owner define when an order consumes capacity and when a canceled request restores it.
Illustrative example—not prices, accounting advice or measured customer results: assume a program has a $12,000 purchasing ceiling. Accepted commitments total $8,000, including $2,000 already invoiced. The proposed next release is $3,400, and the team reserves another $300 for a pending delivery adjustment under its approval policy.
- Remaining capacity before the new release: $12,000 − $8,000 = $4,000.
- Capacity needed for the proposed release and reserve: $3,400 + $300 = $3,700.
- Remaining unallocated capacity: $4,000 − $3,700 = $300.
Do not subtract the $2,000 invoice again: it is already inside the $8,000 of commitments. Conversely, looking only at that invoice would hide the other accepted orders. This is a purchasing-capacity example, not a method for recognizing expenses. Finance should define accounting treatment separately.
Use the same currency and charge scope throughout the check. If the approved limit includes freight and tax, merchandise-only totals cannot establish that an order fits. When a charge is unknown, obtain the quote or use a reserve specifically accepted by the purchasing owner. Do not invent a favorable estimate to pass the gate.
Design the exceptions before launch
A requested change increases the amount. Hold the affected release until the appropriate owner approves the revised scope. Keep the old and new amounts linked to the same request. The order-change and cancellation guide covers production-stage limits; purchasing approval alone does not make a physical change feasible.
The PO expires while an order is awaiting approval. Route it to the purchasing owner. Do not substitute another department’s reference to keep it moving. Decide in advance how existing accepted orders and newly requested orders are treated when an authorization period ends.
A card payment fails. Notify the authorized buyer through the established support route and keep the recipient informed about the hold. Avoid repeatedly creating new orders while retrying payment. Keep one request reference so the release owner can see whether a replacement attempt is actually the same purchase.
The supplier asks for a deposit. Record the deposit requirement, remaining balance and collection responsibility separately. An approved PO and a paid deposit are different facts. Verify whether the order can start after the deposit and what triggers the balance; do not infer either from a checkout label.
An invoice is sent before payment. That may be the intended payment request, not evidence of settlement. Shopify’s draft-order documentation describes invoices with secure checkout links for completing payment. Keep “invoice sent,” “payment received” and “released” distinguishable in the operating record.
Payment route and production model are separate choices
On-demand production can suit uncertain, ongoing employee demand, but many small orders still need a supported funding and approval route. A standing approved scope may be more practical than asking purchasing to review each individual gift. Confirm how cumulative limits and exceptions will be handled.
Bulk can be the better fit for a known campaign quantity, consistent decoration and a shared delivery deadline. One approved buy may simplify the purchasing gate, although storage and later distribution remain separate responsibilities. A hybrid can use bulk for a planned rollout and on-demand replenishment for later hires.
Do not force both streams into the same rule merely because they share a storefront. Give them identifiable order types and document whether they use the same purchasing ceiling. The payment method does not tell you which production model is cheaper or more reliable; those decisions require the actual product, decoration, destination and service quote.
Run a six-case acceptance test
Before launch, ask the proposed provider to walk through these cases in a test environment or documented demonstration, without creating live manufacturing commitments:
- Valid request: correct approval reference, permitted item and supported funding route. Show who releases it.
- Wrong reference: a plausible-looking but invalid PO. Show the rejection or review step.
- Over limit: an order that fits the merchandise allowance but exceeds the approved total after delivery charges.
- Concurrent requests: two orders that each fit the remaining capacity alone but not together. Show how overcommitment is prevented or caught before release.
- Changed request: an approved order increases in amount. Show renewed approval without creating a duplicate purchase.
- Unavailable approver: the usual reviewer is absent. Show the backup owner and the recipient-facing status.
Retain the results with a one-page launch decision: selected route, approval owner, payment terms, release trigger, exception owner and reporting references. After ordering starts, use the separate invoice-reconciliation process to match charges to the approved activity.
Frequently asked questions
Does accepting a PO number mean the supplier offers credit?
No. Confirm payment terms and any required credit approval directly with the supplier. A reference field can simply record the buyer’s purchasing identifier.
Can a store use both card payment and PO-backed orders?
Potentially, but the proposed configuration must support it. Define which buyers and order types use each route, then test the routing. Do not assume a generic checkout feature implements your internal approval policy.
Should employees need a purchasing card to receive a company gift?
For a company-funded gift, design an administrator-owned funding route so eligible recipients can focus on selection. If that is not supported, settle the operational workaround before inviting employees—not after someone reaches a payment screen.
What should we ask Brand Sauce to quote?
Provide the purchasing route, expected order pattern, required approval checks, billing references and production-release rule. Ask which steps are supported natively, which need manual service and which require additional work. Request the relevant product and program quote; payment terms and implementation scope should not be assumed.
