Short answer:Shopify B2B natively supports draft-order approval (an order holds until the merchant confirms it), order review rules that flag orders by criteria like size or category, and a buyer-side self-approve setting that lets a company approve its own team's orders. What it does not natively support is per-user spending limits or a multi-tier approval chain that routes an order to different approvers by dollar amount or cost center. For that, plan on a dedicated B2B approval app or a custom build with Shopify Functions and Flow.
For most of Shopify B2B's life, it was a Shopify Plus feature built for merchants big enough to have a dedicated ops team and, usually, a custom build to fill whatever the platform did not cover natively. That has changed. B2B commerce is now available well below Plus, and Shopify has been adding B2B-specific mechanics, order review rules and self-approve among them, that speak directly to how a real purchasing process works inside a manufacturer or wholesaler's customer base.
That is genuinely good news for smaller Atlantic Canada manufacturers and wholesalers who could never justify a Plus contract just to sell wholesale. It also creates a new kind of confusion: teams read that Shopify added order review rules and assume the whole approval problem is solved, then discover mid-build that spending limits and multi-step sign-off are not in the box. This guide separates the two clearly.
01. Why Order Approval Suddenly Matters for Shopify B2B
A consumer storefront never needs an approval step. A B2B storefront almost always does, because the person placing the order and the person accountable for the spend are frequently not the same person. A purchasing agent orders on behalf of a plant, a regional buyer commits a location's budget, a junior team member submits a request that a manager needs to see before it becomes a real commitment.
As B2B storefronts on Shopify spread past the Plus tier into the range of businesses AtlanticWorks typically works with, more of those buyers are hitting this gap directly on the platform rather than through a custom-built portal. Knowing exactly what Shopify covers, and where the edge is, is now a launch-planning question for almost any manufacturer or wholesaler moving wholesale online.
Here is the quick comparison, then the detail behind each row.
| Capability | Native in Shopify B2B | Needs an app or custom build |
|---|---|---|
| Submit order as draft for merchant review | Yes | Longstanding B2B mechanic |
| Order review rules (flag by size, category, etc.) | Yes | Added 2026 |
| Buyer company self-approves its own team's orders | Yes | Newer buyer-side setting |
| EDI purchase orders synced as draft orders | Yes | Via SPS Commerce, Crstl |
| Per-user or per-role spending limits | No | Third-party app or custom build |
| Multi-tier approval chains by dollar amount | No | Third-party app or custom build |
| Approvals tied to a specific cost center | No | Third-party app or custom build |
Why it matters: If you plan a launch assuming Shopify covers your full approval policy, a gap in spending limits or multi-tier routing surfaces after go-live, not before, when it is far more expensive to fix.
02. What Shopify Natively Handles Today
Three native mechanics cover a meaningful part of a typical wholesale approval need.
- Draft order submission. A company location can be configured so its orders submit as drafts rather than completing immediately. A staff member on the merchant side reviews the draft, adjusts if needed, and confirms it, or sends an invoice or payment request. This has been a core part of B2B since it launched.
- Order review rules. Shopify added configurable rules that flag an order for review when it meets conditions the merchant sets, a large order total or a regulated product category are the common cases. This is a merchant-side safety net, not a buyer-side approval chain, but it closes a real gap for sellers who previously had no automatic way to catch an outsized or sensitive order before it processed.
- Buyer-side self-approve.A newer setting lets the buyer's own company designate someone on their team to approve orders placed by other members of that company, without the seller getting involved in the buyer's internal sign-off. This shifts a piece of the approval burden to where it usually belongs, inside the purchasing organization, and it is the closest thing Shopify has shipped to a genuine buyer-side approval workflow.
Together, these three cover a common and legitimate case: one layer of review, on one side or the other, before an order is final. For a lot of manufacturers and wholesalers, that is genuinely enough.
Why it matters: If your purchasing policy needs exactly one review step, native Shopify B2B may cover the whole workflow with no app and no custom development at all.
03. What Still Requires an App or Custom Build
Where native Shopify stops is the part of the market this article is really about. Three requirements consistently push a build past what B2B ships with out of the box.
Common gaps that need an app or custom build:
- Per-user or per-role dollar limits on what a buyer can order without escalation.
- Multi-tier chains that route an order to different approvers depending on the amount.
- Approvals tied to a specific cost center, department, or project budget.
- Approval logic that spans multiple company locations under one parent account.
The Shopify App Store carries a small but growing set of apps purpose-built for B2B spending limits and approval chains, and they are usually the faster path if your policy is standard (a fixed dollar threshold that escalates to a named approver, for example). Where the policy is unusual, tied to your ERP's budget codes or a multi-location parent-child structure specific to your business, Shopify Functions and Shopify Flow give you the building blocks to encode that logic directly, at the cost of a real development project rather than an app install.
Why it matters: Choosing between an app and a custom build is a scoping decision you want to make deliberately, before launch, not a fallback you reach for after the native tools turn out to be short.
04. Draft Orders, Review Rules, and Self-Approve: How They Differ
These three native tools get used interchangeably in conversation, which causes real confusion when a team is scoping a build. They solve different problems and usually work together rather than as alternatives to each other.
Draft orders answer: does this order need a human on our side before it is real?
It is the broadest, simplest control, and it applies at the company-location level. Every order from that location holds as a draft until your team acts on it.
Order review rules answer: which specific orders deserve extra scrutiny?
Rather than holding every order, rules flag the ones that meet a condition you set, letting routine orders flow through while unusual ones get a second look. This is the tool for a merchant who does not want to review everything, only the outliers.
Self-approve answers: who inside the buyer's company gets to say yes?
This is the only one of the three that puts control in the buyer's hands rather than the seller's. It matters most for larger buyer accounts with their own internal purchasing hierarchy, where your sales team was never the right party to be approving another company's spend in the first place.
A well-designed setup often layers all three: draft orders as the baseline safety net, review rules to focus staff attention on the orders that actually need it, and self-approve turned on for buyer accounts large enough to want their own internal control. That layering connects directly to the wider question of what Shopify Flow can and cannot automate once the native approval tools are in place.
Why it matters: Treating these as three separate levers, not one feature, is what lets you match the tool to the actual policy instead of over-building or under-covering it.
05. Designing an Approval Workflow That Fits Your Business
Here is the order we work through this with a client before a single setting gets configured.
- 1. Write down the actual purchasing policy, not the ideal one. Who can order without sign-off, at what dollar amount does someone else need to approve, and does that threshold change by product category or by customer.
- 2. Decide whose side the review sits on. If it is your team catching outsized or unusual orders, that is review rules. If it is the buyer's own organization controlling its team, that is self-approve. Most businesses need some of both.
- 3. Count the tiers. One review step, native tools likely cover it. Two or more tiers by dollar amount, or limits tied to a role or a cost center, plan for an app or custom build from day one.
- 4. Check it against your EDI flow if you have one. Purchase orders synced in from SPS Commerce or Crstl land as draft orders too, so make sure your approval design covers that intake path, not just orders placed through the storefront.
- 5. Pilot with your highest-volume accounts first. They surface edge cases in the policy fastest, and getting the workflow right for the accounts that generate the most orders pays back the design time quickest.
Why it matters: This sequence keeps the build scoped to what your purchasing policy actually requires, rather than to every approval feature that sounds useful in the abstract.
06. Where This Fits If You Are Not on Shopify Plus
The approval tools covered here are not gated behind Plus. Shopify has extended core B2B functionality, companies, catalogs, net payment terms, and self-serve ordering, down to lower plan tiers, which is a meaningful shift for smaller manufacturers and wholesalers who previously had to either skip B2B on Shopify entirely or absorb a Plus contract to get it.
What does stay strongest on Plus is depth: the most granular staff permission controls and the largest catalog of B2B-focused apps still assume a Plus-level build. For a business evaluating whether it needs Plus at all, that is the real question to ask, not whether basic approval exists, since draft orders, review rules, and self-approve are now available well below it, but how much depth and customization your specific policy needs. That decision is worth working through in full alongside what Shopify B2B actually includes without Shopify Plus and how it compares to a self-serve wholesale portal built on Shopify B2B.
Why it matters: Plan tier is no longer the gate on getting a working approval flow live, which means the plan decision should be driven by depth and scale, not by whether approval exists at all.
07. Key Takeaways
- Shopify B2B natively covers draft-order approval, order review rules, and buyer-side self-approve. That is one full layer of review, on either the seller or the buyer side.
- Per-user spending limits and multi-tier approval chains by dollar amount are not native and require a third-party app or a custom build with Shopify Functions and Flow.
- EDI purchase orders from SPS Commerce or Crstl land as draft orders too, so they flow through the same approval step as manually placed B2B orders.
- B2B, and its native approval tools, are no longer gated behind Shopify Plus. Plan tier should be decided on depth and scale, not on whether basic approval exists.
- Map your real purchasing policy and count the approval tiers before you build, so you know from day one whether native tools cover it or an app and development budget belong in the plan.
08. Frequently Asked Questions
Does Shopify have native order approval for B2B orders?
Partly. Shopify B2B lets a company location submit orders as drafts that a merchant reviews and approves, and native order review rules flag orders based on conditions like order size or product category. A newer self-approve setting also lets a buyer company approve its own team's orders internally. Per-user spending limits and multi-tier approval chains are not native.
What is the difference between order review rules and B2B self-approve?
Order review rules are merchant-side and flag an incoming order for the seller to check before it processes. Self-approve is buyer-side and lets the purchasing company designate its own approver for orders placed by its team, without the seller reviewing every internal sign-off.
Can Shopify enforce spending limits or budget thresholds per buyer?
Not natively, as of 2026. There is no built-in setting for per-user or per-role dollar limits on B2B orders. Merchants who need that level of control add a third-party B2B approval app or build the logic with Shopify Functions and Shopify Flow.
Is Shopify B2B still limited to Shopify Plus?
No. Core B2B functionality, including companies, catalogs, and net payment terms, is now available on lower plan tiers including Grow, not only Plus. The deepest permission and approval controls remain strongest on Plus, but draft order approval works below it too.
How do EDI purchase orders fit into Shopify B2B approval?
EDI purchase orders from providers such as SPS Commerce and Crstl can sync directly into Shopify as draft orders, which then move through the same admin review and approval step as any other B2B draft order.
What should a manufacturer or wholesaler check before relying on Shopify's native approval tools?
Map how many approval tiers your purchasing process actually needs. One round of merchant-side or buyer-side review is likely covered natively. Dollar-based routing across multiple approvers or budget enforcement tied to a cost center needs a dedicated app or custom build planned from the start.
Sources
- Shopify, Shopify Winter '26 Edition: features that unify B2B operations
- Shopify Help Center, Shopify B2B features by plan
Related Resources
What B2B actually includes now on lower plan tiers, and where Plus still matters
Building a buyer-facing ordering portal that fits a wholesale sales motion
A full walkthrough of companies, catalogs, pricing, and payment terms
What Flow can automate around orders, and where it hits its limits
Building a B2B order approval workflow on Shopify?
AtlanticWorks builds Shopify B2B storefronts for Canadian manufacturers and wholesalers, including the approval logic that native tools do not cover. We map your real purchasing policy, configure what Shopify handles natively, and build the rest with Flow, Functions, or a purpose-built app so nothing gets discovered after launch.
Start the Assessment