Shopify B2B Order Approval Workflows: Permissions, Draft Review, and Multi-Level Procurement

Map the four controls that merchants often call ‘approval’

Start by naming the event being controlled. Access approval decides whether a new wholesale company may enter the B2B buying environment. Customer permission decides what a person associated with an approved company location may see or change. Merchant draft review decides whether the seller accepts a submitted order before it becomes final. Buyer-side procurement approval decides whether the customer's own organization has authorized the spend before the seller should treat it as approved purchasing intent.

A distributor can need all four. A new contractor first requests wholesale access. Once approved, a purchasing employee receives ordering permission for one location. Every order from that location might still be submitted as a draft so the distributor can verify freight or stock allocation. Inside the contractor's own business, a large purchase may also need manager and finance approval. None of those controls is redundant merely because they all contain the word approval.

This map prevents a common implementation error: granting a user broader Shopify permissions because the business actually needed an internal spend-approval chain, or forcing every order into merchant review because the buyer organization lacked its own authorization process. Define the missing control before adding software.

Use Shopify customer permissions for access scope, not spending authority

Shopify currently documents two B2B company-customer permission levels. Ordering only lets a customer place orders for assigned company locations and view that customer's own order history. Location admin can also view the orders placed by all customers for that assigned location and edit billing and shipping addresses. These permissions determine what the customer can do in the company account context.

They should not be described as a purchase-approval hierarchy. A Location admin can have broader visibility and address-management capability without being the finance approver for a $50,000 order. Likewise, an Ordering only buyer can be perfectly authorized to prepare routine purchases even if larger orders must later move through an internal approval chain.

A practical permission design keeps Shopify access as narrow as the job requires. Give routine buyers the access they need to order for the correct locations. Reserve broader location administration for people who actually need cross-buyer order visibility or address control. Then solve spend authorization separately instead of trying to encode corporate policy by over-granting or under-granting account permissions.

Keep company-account approval separate from order approval

Shopify's company account request workflow is an onboarding gate. Current documentation says a submitted request can create a company, company location, and customer record for review. By default, companies created through that request flow cannot place orders or access B2B pricing until the merchant approves them. That is useful for deciding who qualifies for your wholesale channel.

Approval at this stage answers questions such as whether the applicant is a legitimate trade customer, which company locations should be activated, and which permissions should be assigned. It does not mean every future order is authorized by the buyer's own management, and it does not replace a merchant-side order review rule.

Treat onboarding approval as a durable account-state decision. Once a company is approved, its normal purchasing workflow should not require the sales team to repeat the same identity check on every order. If later orders need financial or operational review, build those controls at the order layer instead of turning company access into a recurring manual bottleneck.

Use native draft review when the merchant is the approver

Shopify lets a merchant configure a company or company location so orders are submitted as drafts for review. Current documentation says every order from that location is then created as a draft, no payment is collected at the initial checkout, and the merchant can review the order before confirming it. Shopify also points to Payment Customization Functions when only selected orders should be submitted as drafts based on criteria such as order value or cart contents.

This is a seller-side control. It fits a manufacturer that must verify production capacity, a distributor that needs to review freight or allocation, or a wholesaler that wants a manual check for unusually large baskets. The person making the approval decision is the merchant or merchant staff, not the buyer's manager or finance team.

Do not let the checkout wording create conceptual confusion. A buyer might see a submit-for-approval experience because the order is going to the merchant as a draft. That does not prove the buyer organization has completed its own internal authorization. If both organizations require approval, model both stages explicitly.

Use multi-level procurement approval when authorization belongs inside the buyer organization

B2B Procurement OS is designed for the internal purchasing chain that native merchant draft review does not represent. Its current Shopify App Store listing describes multi-level approval workflows with conditional rules based on order amount and gives Purchasing, Manager, and CFO as example approval steps. That makes the app relevant when an order should move through the customer's organization before it is treated as an approved procurement request.

Consider a hotel group. A site buyer can prepare a $1,200 housekeeping replenishment, while a $12,000 opening order should require a regional manager and finance. The products may come from the same Shopify catalog, but the purchasing authority is different. Amount-based multi-level approval is the control that matches that business problem.

Keep the boundaries honest. The verified App Store claim is multi-level approvals with conditional rules based on order amount. Do not assume unsupported department budgets, contract signatures, arbitrary ERP approval synchronization, or every possible policy rule. If your procurement policy depends on a condition not documented by the listing, verify that requirement before rollout.

Combine buyer approval and merchant review without creating a double-approval maze

Some stores need both sides to approve, but every approval should have a reason. A buyer may need internal authorization because the purchase exceeds a department limit, while the merchant may still need to review only orders that involve special freight or constrained inventory. If every order requires every approver on both sides, the workflow can become slower than the email chain it replaced.

A better design gives each control a trigger and an owner. Routine orders can pass the buyer's normal authorization and flow directly if the merchant has no reason to inspect them. High-value or unusual purchases can require buyer-side escalation. Merchant draft review can be reserved for accounts or criteria where the seller genuinely needs a gate. The result is layered control rather than duplicated control.

Write the stages in plain language before configuration: who prepares the basket, who authorizes the buyer's spend, when merchant review is required, when payment becomes due, and what happens after rejection or required correction. If staff cannot explain the workflow in one minute, the configuration is probably doing too much.

Connect approval to payment terms and credit exposure, but do not confuse those concepts

Shopify's native B2B payment terms define when payment is due. Current documentation supports no payment terms, net 7, net 15, net 30, net 45, net 60, and net 90 for company locations and individual draft orders, along with due-on-fulfillment and fixed-date options in the documented contexts. Those terms are about timing, not about how much financial exposure the merchant wants to extend.

B2B Procurement OS adds a different commercial control. Its listing says merchants can set per-company credit limits and net terms and automatically block over-limit or overdue orders. That matters because an internally approved purchase can still be commercially unacceptable if the account is already beyond the merchant's credit policy.

Design the sequence deliberately. Buyer approval establishes that the customer organization authorizes the purchase. Merchant credit rules establish whether the seller will extend the requested exposure. Payment terms establish when an accepted balance is due. One green approval status should never be used as shorthand for all three decisions.

Use a simple role matrix before configuring the workflow

A one-page matrix can prevent months of confusion. Put the people or roles down the left and the decisions across the top: prepare basket, see all location orders, edit company addresses, approve spend under threshold, approve spend above threshold, review merchant draft, resolve credit exception, and release fulfillment. Then mark who owns each decision.

For example, a buyer might have Ordering only access and prepare the basket. A location administrator might maintain addresses and view the location's full order history. A manager and finance approver might exist only in the procurement chain. The merchant's account manager might review exceptional drafts, while finance owns credit exceptions. The exact structure varies, but the separation is what makes the policy understandable.

This matrix also exposes unnecessary privileges. If a finance approver only needs to authorize large purchases, that requirement should not automatically make the person the Shopify Location admin. Likewise, broad location visibility should not be mistaken for permission to approve every level of spend.

Choose native Shopify or B2B Procurement OS based on the missing layer

Stay native when the real requirement is simple: approve companies before they get B2B access, give customers the correct company-location permissions, or hold orders as drafts so your own staff can review them. Those are documented Shopify capabilities, and adding procurement software merely to recreate them can add needless administration.

Choose B2B Procurement OS when the missing layer is buyer-side procurement depth. The current listing combines multi-level amount-based approvals with per-company credit limits and net terms, saved-list or CSV reordering, volume quote requests, and self-service editing of unfulfilled orders. That combination is more compelling when approvals are part of a broader purchasing process rather than a single checkout gate.

As of September 15, 2026, the official Shopify App Store listing shows Starter at $79 per month, Growth at $199, and Enterprise at $499, each with a 14-day free trial. Available in English. Compare that cost with the operational problem being solved. A store that only needs merchant draft review should keep the simpler native workflow. A store coordinating internal buyer approvals, credit rules, repeat orders, and quote exceptions has a stronger reason to add the procurement layer.

• Need to approve a new wholesale company: use company-account approval.
• Need to limit what a company customer can see or edit: use Shopify B2B customer permissions.
• Need your own team to accept an order before finalization: use merchant draft review.
• Need Purchasing, Manager, or CFO-style internal authorization: evaluate B2B Procurement OS.
• Need to control seller exposure: keep credit limits separate from payment-term timing.

Roll out one real account before standardizing the policy

Choose a customer whose process already contains at least one approval handoff. Map the real people, permission levels, value thresholds, merchant review triggers, payment terms, and credit rules. Then test ordinary and awkward cases on paper before making the workflow the default for every account.

Useful scenarios include a routine order by an Ordering only buyer, an address change by a Location admin, an order just above the buyer's approval threshold, an account that is overdue, a merchant-review draft with a saved card, and a rejected purchase that must be corrected and resubmitted. The goal is to find ambiguous ownership before the first large order gets stuck.

Measure operational clarity rather than inventing a revenue claim. Count how many manual handoffs remain, how often staff are unsure who must act next, whether approvals are being bypassed by email, and whether rejected or blocked orders have a defined recovery path. A strong B2B workflow makes authority visible. It does not merely add more approval screens.

Apps mentioned in this guide

Frequently asked

Are Shopify B2B customer permissions the same as purchase approvals?

No. Ordering only and Location admin control what a customer can do for assigned company locations. They do not by themselves create a multi-level purchasing authorization chain based on spend.

What does Shopify's native submit-for-approval flow actually approve?

When a company or company location is configured to submit orders as drafts, the merchant reviews the draft before confirming the order. That is seller-side review, not proof that the buyer company's manager or finance team approved the purchase internally.

Can Shopify approve a company before it gets B2B pricing and ordering access?

Yes. Shopify's company account request workflow lets merchants review new company requests, and companies created through that form cannot order or access B2B pricing by default until approved.

What does B2B Procurement OS add to approvals?

Its current App Store listing describes multi-level approval workflows with order-amount conditions, plus company credit limits and net terms, saved-list or CSV reorders, volume quote requests, and controlled editing of unfulfilled orders.

Is B2B Procurement OS available in English?

Yes. B2B Procurement OS is available in English. ShopRadar's shared App Store CTA uses the authentic b2b-procurement-os slug with locale=en.