Do You Still Need a B2B App Now That Shopify Does B2B Natively?
Most Shopify merchants should pause B2B app spending: Shopify shipped native B2B — company profiles, catalogs, volume pricing, payment terms — to every paid plan on April 2, 2026 (per Shopify's rollout, July 2026 research). Adopt native first, close specific gaps like the 3-catalog cap, buyer registration workflows, and RFQ with targeted customization, and re-assess remaining apps once your gap list is real rather than assumed.
Your profile — see how the verdict shifts
- Confidence
- Medium — Frontier moved 4 months ago; app vendors are still repositioning and native limits are still being mapped in the wild
- Reference scenario
- $20M–$100M GMV · blended DTC + wholesale · agency dev bench
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Light wholesale (few accounts, simple tiers) | WAIT / native | Native company profiles + 3 catalogs + net terms cover it. Cancel overlapping app spend. |
| Growing wholesale (catalog tiers, registration flow) | CUSTOMIZE | Native core + targeted builds: registration/approval workflow (Flow + Admin API), MOQ rules (Functions), quick-order UX. |
| 500+ wholesale customers / multi-tier pricing | DEPENDS | The 3-catalog system-wide cap (non-Plus) and rep workflows bite here — score Plus upgrade vs. app vs. custom against your real gap list. |
| Distributor → wholesaler → retailer chains | BUILD (architecture) | Native can't model multi-tier distribution (community-documented); this is an architecture engagement, not an app install. |
What B2B & wholesale apps Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Wholesale is a revenue CHANNEL, not a feature — the capability unlocks orders that can't otherwise be placed. |
| Operational efficiency | High | Self-service ordering, catalogs and net-terms automation deflect the rep hours and finance chasing that manual wholesale burns. |
| Customer experience | High | B2B buyers now expect DTC-grade self-service — a clunky portal quietly costs reorders to whoever's portal isn't. |
| Data & insight | Medium | Company-level records unify buyer behavior across locations and buyers — the substrate for account-based pricing and forecasting. |
Spend ceiling: Channel-revenue proximity justifies real spend — but native B2B now covers the core on every paid plan, so the budget belongs to your NAMED gaps only, not to re-buying what's included.
What buying enables (top apps)
- + Native (included, no license): company profiles, catalogs, price lists, volume pricing and net terms on every paid plan since April 2, 2026
- + App suites: rep dashboards, advanced registration and quoting flows packaged, maintained and supported
- + One subscription covering several small gaps at once — sensible when you genuinely hit three or more
What building additionally unlocks
- + Registration/approval, MOQs and quick-order flows encoding YOUR wholesale policy exactly — each a small, disposable Functions/Flow build
- + RFQ and quoting on the draft-orders API, matched to how your reps actually negotiate
- + ERP-connected ordering (inventory-aware, account-aware) that app suites can't reach
- + Checkout behavior tuned per company tier — deposits, terms and payment rules where the platform allows
Find Your Verdict in 3 Questions
Are you on any paid Shopify plan today?
Yes: Native B2B is already included in your plan (since April 2, 2026) — go to question 2.
No: Plan selection comes first; native B2B ships with every paid plan.
Do your wholesale needs fit within 3 catalogs and standard net terms?
Yes: Your verdict: WAIT / adopt native — enable it, migrate accounts, cancel overlapping app spend.
No: Go to question 3.
Are your gaps specifically registration workflow, MOQs, or quick-order UX?
Yes: Your verdict: CUSTOMIZE — native core plus targeted builds (typically weeks each, independently disposable).
No: DEPENDS — 500+ wholesale accounts, partial payments, or multi-tier distribution needs a scored architecture decision. Talk it through.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | Native is already in your plan; targeted customization beats both re-platforming onto an app suite and a ground-up build. | ||
| Recurring fees | B2B app suites bill forever for features Shopify now includes; the April 2026 rollout stranded a lot of overlapping spend. | ||
| Maintenance & upgrades | Native features are maintained by Shopify; small Functions/Flow customizations carry light upkeep. | ||
| Switching & exit | Migrating wholesale accounts and price lists off an app is real work — another reason not to add app dependency now. | ||
| Risk | |||
| Vendor risk | Post-native, B2B app vendors face a shrinking moat — repositioning and consolidation risk is elevated (the pattern the ecosystem keeps repeating). | ||
| Security & compliance surface | Wholesale pricing and terms in fewer third-party hands. | ||
| Platform-deprecation exposure | Native B2B rides the platform roadmap; customizations use first-class primitives (Functions, Flow, checkout extensions). | ||
| Value | |||
| Fit to requirement | Apps still win specific gaps today (rep portals, advanced registration); the question is whether YOUR gaps justify a suite. | ||
| Time to market | Apps install fast; native is faster still (it's already on); gap customizations run in weeks. | ||
| Performance & scale | Native B2B has hard documented ceilings (3 catalogs system-wide on non-Plus; no buyer-side order edits) — know them before promising wholesale UX. | ||
| Data ownership & AI-readiness | Company, catalog and terms data in native objects stays queryable and portable. | ||
| Focus & opportunity cost | The cheapest move is subtraction: cancel overlap, customize the two gaps that matter, revisit in two quarters. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify native B2B | Live — The baseline. All paid plans since April 2, 2026; some features remain Plus-only; 3-catalog system-wide cap on non-Plus (July 2026 research) | Included in plan | The default starting point for everyone |
| PortalSphere | Live — Post-native positioning: wholesale upsell/AOV features beyond the native core (July 2026 research) | Tiered | Named gaps after native adoption, not instead of it |
| BSS B2B | Live — Breadth-for-price positioning (July 2026 research) | Tiered | Multiple small gaps where one suite beats three point apps |
The Build Path
- Registration & approval workflow: Custom form + Flow + Admin API auto-tagging — the most-cited native gap, and a small build.
- MOQs & order rules: Cart/checkout validation Functions encode your wholesale policy exactly.
- Quick-order UX: A dense, SKU-first order form as a custom storefront component.
- RFQ / quoting: Draft-orders API + a light request flow — the recognized pattern for negotiation before a PO.
- Effort band
- Gap customizations typically land in the $10–25K contact-form band each (Deploi estimate, illustrative); multi-tier architecture engagements range higher
- Typical timeline
- 2–6 weeks per gap (Deploi estimate, illustrative)
- Maintenance, honestly
- Light: Functions and Flow ride platform versioning; the native core is Shopify's to maintain.
- What you own — and what you take on
- You own: wholesale policy encoded in your store, not a vendor's roadmap. You take on: tracking native B2B's fast-moving release notes — which is exactly what this page's watch triggers do.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $1,000–$4,000 | $10,000–$30,000 (two gap builds) |
| Years 1–3 (recurring) | $7,200–$21,600 | $3,000–$9,000 (light upkeep) |
| 3-year total | ≈$8,200–$25,600 | ≈$13,000–$39,000 — minus cancelled overlap |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy path: a mid-tier B2B app suite retained for 3 years; Wait/Customize path: native core + two gap builds.
- † Plus-upgrade economics excluded here — scored separately when the catalog cap binds.
What the Sticker Price Hides
On the buy path
- — App suites still bill for features Shopify now includes — the April 2026 rollout stranded a lot of overlapping spend
- — Migrating wholesale accounts and price lists OFF a suite later is real switching cost — every month deepens it
- — Post-native, B2B app vendors carry elevated repositioning/consolidation risk
On the build path
- — Tracking native B2B's fast-moving release notes becomes your job (or this page's watch triggers do it)
- — Plus-only gates (partial payments, deposits) may force plan-upgrade math you didn't budget
- — Unscoped gap-builds creep — write the gap list from real workflows before scoping
What Merchants Say
What breaks operationally once we cross 500 wholesale customers? The 3-catalog cap, lack of partial payments, and sales-rep gaps come up again and again.
Does Shopify B2B support buyer-facing post-purchase editing — quantity changes, address corrections, PO updates — or does everything become a support ticket? (It becomes a ticket.)
Does Shopify natively support quoting/RFQ workflows, or do we need a bolt-on for any negotiation before a PO is confirmed? (Native has no RFQ — this is a real gap.)
If You Change Your Mind Later
If you bought and outgrow it
If you keep an app suite now, plan a native-migration window anyway — the frontier is moving toward native, and account/pricing data accumulating in a vendor's model makes every quarter's exit more expensive.
If you built and want out
Functions and Flow customizations ride first-class platform primitives — each one is small and independently disposable. If native later covers a gap you built, you delete a Function, not a platform.
When This Answer Changes
We're watching for:
- ▸ Native B2B closing its named gaps (RFQ, auto-approve registration, buyer-side edits, 4th+ catalog) — each closure shrinks the app case further
- ▸ Shopify Editions announcements touching B2B (next: verify current cycle)
- ▸ B2B app vendors repositioning or consolidating post-native
Verdict change log:
- 2026-04-02BUYWAITShopify shipped native B2B (company profiles, catalogs, volume pricing, payment terms) to every paid plan — the app-first default died that day.
Common Questions
What are native Shopify B2B's hard limits?
As of the July 2026 research: a 3-catalog system-wide cap on non-Plus plans, no RFQ/quoting workflow, no automatic buyer registration approval, no buyer-side post-purchase order editing, and partial payments/deposits gated to Plus. Re-verify at reading time — this list is shrinking.
Should I cancel my wholesale app?
Map your app's features against what native B2B now includes; cancel when the overlap covers your actual usage. Keep (or add) apps only for named gaps you've confirmed you hit — not gaps a vendor's comparison chart says you might.
When does Shopify Plus enter this decision?
When native limits start binding: the 3-catalog system-wide cap, partial payments and deposits, or deeper B2B checkout customization. At that point score the Plus upgrade against app suites and targeted custom builds — it's the same Total Cost of Capability exercise with a third column, and the honest answer depends on your wholesale mix.
Your Next Steps
If you're going with WAIT(matches your selected profile)
- Map your current app's features against the native B2B checklist (company profiles, catalogs, net terms)
- Cancel confirmed overlap — this is the rare next-step that's pure subtraction
- Enable native B2B on a pilot set of wholesale accounts
- Subscribe to the verdict-change alert; re-assess against your gap list in Q4 2026
If you're going with CUSTOMIZE
- Write the gap list from real order workflows — not from a vendor comparison chart
- Scope the registration/approval workflow and MOQ rules first (highest ticket-volume payback)
- Verify which needs are genuinely Plus-gated before any plan decision
- Sequence gap builds smallest-first; each should ship in weeks
Official Docs & Sources
- Shopify B2B — Shopify Help Center
- Catalogs and pricing in B2B — Shopify Help Center
- Companies and customers in B2B — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
PortalSphere vs. a Native B2B Portal: Rent or Build It?
A B2B buyer portal belongs on native rails: customer-account extensions on native B2B beat renting a hosted portal layer once a dev bench exists.
Wholesale Gorilla vs. Native B2B: Time to Switch?
Native B2B has covered core wholesale on every paid plan since April 2026; Wholesale Gorilla keeps a lane only where the 3-catalog cap or cart rules bind.
SparkLayer vs. Native B2B: Is the App Still Worth It in 2026?
Native B2B covers core wholesale on every paid plan since April 2026; SparkLayer earns its fee when the 3-catalog cap binds or ordering UX must ship now.
Should You Build or Buy B2B Catalogs & Price Lists on Shopify?
Native catalogs carry B2B price lists until the 3-catalog cap bites; past it, customize with API-generated catalogs instead of renting a parallel pricing database.
B2B Company Accounts on Shopify: Buy an App, Build, or Go Native?
Company accounts and permissions no longer justify an app for most Shopify merchants: native B2B covers the core on every paid plan since April 2, 2026.
Ready to map your real B2B gap list?
We'll audit your wholesale flows against native B2B, name what to cancel, and scope the two customizations that actually matter.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.