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 shipped company profiles, locations, buyer permissions and net terms to every paid plan on April 2, 2026 (per Shopify's rollout, July 2026 research). Adopt the native core first and cancel overlapping app spend. Customize the named gaps (registration auto-approval, buyer self-service edits, RFQ) with small disposable builds, and re-open the app question only against a confirmed gap list.
Your profile — see how the verdict shifts
- Confidence
- Medium — The frontier moved in April 2026; native release notes keep closing gaps and app vendors are mid-reposition, so any named-gap list goes stale fast
- Reference scenario
- $20M–$100M GMV · blended DTC + wholesale · 50–500 company accounts · agency dev bench
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Light wholesale (under ~25 companies, single-location buyers) | WAIT / native | Native company profiles, buyer permissions and net terms cover this outright; enable them and cancel any overlapping app. |
| Growing (25–150 companies, first multi-location accounts) | WAIT, then CUSTOMIZE | Run native for a quarter; registration approval is usually the first gap that earns a build, and the ticket log will tell you. |
| At scale (150–500+ companies, tiered catalogs, approval rules) | CUSTOMIZE | Registration workflow, buyer self-edit gaps and the 3-catalog cap (off Plus) bite here; close them with targeted builds on the native core. |
| Rep-managed books, RFQ-heavy or ERP-driven permissions | DEPENDS | Apps still earn a fee where reps quote daily; a custom portal on native objects wins where the ERP owns the account truth. Score your real workflow. |
What Company accounts & permissions Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Company accounts gate the wholesale channel itself: without account structure, B2B orders route through email and spreadsheets, and some never get placed at all. |
| Operational efficiency | High | Buyer permissions and location-scoped ordering move order entry to the customer's own team, deflecting the rep emails and finance chasing that manual account management burns. |
| Customer experience | High | B2B buyers now expect DTC-grade self-service; the right buyer ordering against the right location and terms without a phone call is table stakes. |
| Data & insight | Medium | Company-level records tie buyers, locations and orders into one account view, the substrate for account-based pricing, credit decisions and demand forecasting. |
| Retention & LTV | Medium | Approved buyers with saved terms and catalogs reorder with less friction, and switching suppliers means re-onboarding an entire buying team. |
Spend ceiling: Native now covers the core account model on every paid plan, so the ceiling sits at your named gaps. Budget for the one or two gaps that generate weekly tickets (registration, self-service edits), not for re-buying what's included.
What buying enables (top apps)
- + Native (included, no license): company profiles, locations, buyer permissions, catalogs, volume pricing and net terms on every paid plan since April 2, 2026
- + App suites package registration forms, vetting and approval workflows that native still lacks
- + Rep dashboards and sub-account tooling beyond native's buyer-permission model, maintained and supported
- + One subscription covering several small gaps at once, sensible when you genuinely hit three or more
What building additionally unlocks
- + Approval logic that encodes your actual credit policy: trade references, tax-exempt vetting and auto-tagging wired through Flow and the Admin API
- + Buyer self-service edits (PO numbers, addresses) built as account and checkout extensions, closing native's ticket-generating gap
- + Permissions synced from your ERP so buyer roles, locations and credit limits mirror the system that owns the account truth
- + RFQ on the draft-orders API shaped to how your reps actually negotiate
Find Your Verdict in 3 Questions
Do your wholesale accounts fit native's model today: companies with locations, buyer permissions, up to three catalogs off Plus, and standard net terms?
Yes: Your verdict: WAIT — enable native company accounts, migrate your wholesale list, and cancel overlapping app spend.
No: Go to question 2.
Are your gaps specifically registration auto-approval, buyer self-service edits, or quick-order UX?
Yes: Your verdict: CUSTOMIZE — adopt the native core and close each gap with a small Flow, Functions, or extension build.
No: Go to question 3.
Do rep-managed books, RFQ-heavy negotiation, or ERP-driven permissions run your wholesale day?
Yes: Your verdict: DEPENDS — score an app suite against a custom portal on native objects; your workflow decides, not a vendor's feature chart.
No: Your verdict: WAIT — run native for a quarter and write the gap list from real support tickets before spending anything.
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 company accounts are already in your paid plan; enabling them plus a gap build or two costs less than migrating your account base onto a suite. | ||
| Recurring fees | Account suites bill monthly for company profiles and permissions Shopify now includes; the native core adds no fee line at all. | ||
| Maintenance & upgrades | Shopify maintains the native core; your gap builds carry roughly 15–20% of build cost per year in upkeep (Deploi estimate). | ||
| Switching & exit | Company records, buyer lists and price lists accumulate inside an app's data model, and migrating them out later is real work that deepens every quarter. | ||
| Risk | |||
| Vendor risk | Post-native, account-app vendors face a shrinking moat; the ecosystem's consolidation pattern keeps repeating, while native objects have no vendor to lose. | ||
| Security & compliance surface | Company data, credit terms and buyer identities sit in fewer third-party hands on the native path. | ||
| Platform-deprecation exposure | Native company objects ride Shopify's roadmap; extensions use first-class primitives (Flow, Functions, checkout and account extensions) rather than deprecated surfaces. | ||
| Value | |||
| Fit to requirement | Suites still package registration vetting and rep tooling today; native plus small builds matches your permission rules exactly instead of a vendor's model. | ||
| Time to market | Native is effectively instant since it ships with your plan; suites install in days; gap builds run weeks each. | ||
| Performance & scale | Native has documented ceilings (3-catalog cap off Plus, no buyer-side edits); map where they bind before promising portal UX. | ||
| Data ownership & AI-readiness | Company, location and buyer-permission data in native objects stays queryable through the Admin API and portable to whatever you build next. | ||
| Focus & opportunity cost | The cheapest move is subtraction: adopt what's included, cancel overlap, and spend dev weeks only on gaps confirmed by real tickets. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify native B2B company accounts | Live — The baseline. Company profiles, locations, buyer permissions, catalogs and net terms on every paid plan since April 2, 2026; partial payments and deposits stay Plus-only (July 2026 research) | Included in plan | The default starting point for every merchant on a paid plan |
| PortalSphere | Live — Post-native positioning: wholesale upsell/AOV features beyond the native core (July 2026 research) | Tiered | Named gaps you've confirmed after native adoption, not instead of it |
| BSS B2B | Live — Breadth-for-price positioning (July 2026 research) | Tiered | Several small confirmed gaps where one suite beats three point apps |
The Build Path
- Registration & approval workflow: Custom trade-application form plus Flow and Admin API auto-tagging; closes native's most-cited gap (no auto-approve) in a small build.
- Buyer self-service edits: Customer-account and checkout extensions let buyers fix PO numbers and addresses themselves instead of raising tickets.
- Permission sync from ERP: Admin API sync so buyer roles, locations and credit limits mirror the system that actually owns the account.
- RFQ / quoting: Draft-orders API plus a light request flow; the recognized pattern for negotiation before a PO.
- Effort band
- Gap builds typically land in the $10–25K contact-form band each (Deploi estimate, illustrative); ERP-driven permission architectures range into the $25–75K band
- Typical timeline
- 2–6 weeks per gap build (Deploi estimate, illustrative); ERP permission sync runs longer
- Maintenance, honestly
- The native core is Shopify's to maintain. Your gap builds carry roughly 15–20% of build cost per year in upkeep (Deploi estimate): API version bumps and release-note tracking as native closes gaps. There is no subscription line.
- What you own — and what you take on
- You own: your registration policy, your permission rules, and account data in native objects any future stack can read. You take on: watching native B2B's release notes, because a gap you built may become a feature you delete.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $1,000–$4,000 | $12,000–$35,000 (two gap builds) |
| Years 1–3 (recurring) | $7,200–$21,600 | $5,400–$21,000 (upkeep at ~15–20%/yr) |
| 3-year total | ≈$8,200–$25,600 | ≈$17,400–$56,000; a WAIT with zero builds rounds to $0 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy path: a mid-tier B2B account suite retained for three years; native-plus-extensions path: included core plus two gap builds. A pure WAIT (native only, zero builds) costs near zero and isn't charted.
- † Canceled overlapping app spend not modeled; it usually improves the native path further.
What the Sticker Price Hides
On the buy path
- — Paying a suite for company profiles and permissions Shopify now includes; the April 2026 rollout stranded exactly this overlap
- — Company records and price lists accumulate in the vendor's data model, and every quarter deepens the eventual migration
- — Post-native, account-app vendors carry elevated repositioning and consolidation risk (the ecosystem's repeating pattern)
- — Suite pricing often tiers on company count, so growth in accounts becomes growth in fees
On the build path
- — Native's release notes move fast; a gap you build this quarter can ship natively next quarter, so keep each build small and disposable
- — Plus-only gates (partial payments, deposits) can force plan-upgrade math you didn't budget
- — Permission edge cases multiply: location-scoped approvals and rep hierarchies deserve a written matrix before any scoping call
What Merchants Say
The recurring at-scale question: what breaks past 500 wholesale accounts? The catalog cap, missing registration auto-approval, and rep workflow gaps come up again and again.
Buyers can't fix their own PO numbers, addresses or quantities after ordering, so every small correction becomes a support ticket. It's the gap merchants feel daily.
If You Change Your Mind Later
If you bought and outgrow it
Plan the native-migration window before you sign: export formats for companies, buyers and price lists vary by vendor, and the account base you accumulate makes every quarter's exit more expensive. The frontier is moving toward native either way.
If you built and want out
Each gap build is small and independently disposable: if native ships registration auto-approval or buyer self-edits, you delete a Flow workflow or an extension, not a platform. Your account data already lives in native objects, so nothing is stranded.
When This Answer Changes
We're watching for:
- ▸ Native closing its named gaps (registration auto-approve, buyer self-service edits, RFQ, the 3-catalog cap); each closure shrinks the app case further
- ▸ Shopify Editions announcements touching B2B and customer accounts
- ▸ Account-app vendors repositioning or consolidating post-native
Verdict change log:
- 2026-04-02BUYWAITShopify shipped native company profiles, locations, buyer permissions, catalogs and net terms to every paid plan; the app-first default for company accounts died that day. Apps now compete on named gaps only: RFQ, registration auto-approval, buyer self-service edits.
Common Questions
What can't native Shopify B2B company accounts do yet?
As of the July 2026 research: no RFQ or quoting workflow, no automatic approval of buyer registrations, and no buyer-side edits to orders or certain account records, so corrections become support tickets. Partial payments and deposits stay Plus-only, and non-Plus plans carry a 3-catalog system-wide cap. Re-verify at reading time; this list keeps shrinking.
Should I cancel my B2B account app now that native shipped?
Map the app's features against what your paid plan now includes: company profiles, locations, buyer permissions, catalogs, volume pricing and net terms. Cancel when the overlap covers your real usage, and keep paying only for named gaps you've confirmed you hit, like registration workflows or rep tooling. A quarter of native-first running usually settles the question.
How do buyer permissions work in native Shopify B2B?
Native company accounts give each company one or more locations, with buyers assigned per location and permissions controlling who orders there; catalogs, payment terms and checkout rules follow the location (per Shopify's rollout, July 2026 research). What native doesn't yet let buyers do is edit their own records after purchase; that gap is what a small extension build closes.
Your Next Steps
If you're going with WAIT(matches your selected profile)
- Enable native B2B on a pilot set of wholesale companies and mirror their current terms
- Map your account app's features against the native checklist (companies, locations, buyer permissions, catalogs, terms)
- Cancel confirmed overlap; this is the rare next step that's pure subtraction
- Log every account-management support ticket for a quarter; that log is your gap list
- Subscribe to the verdict-change alert and re-assess in Q4 2026
If you're going with CUSTOMIZE
- Write the gap list from real tickets and order workflows, not a vendor comparison chart
- Scope the registration approval workflow first; it's the most-cited native gap and the smallest build
- Verify which needs are genuinely Plus-gated before any plan-upgrade decision
- Sequence gap builds smallest-first so each ships in weeks and stays disposable
Official Docs & Sources
- Companies and customers in B2B — Shopify Help Center
- Shopify B2B — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Do You Still Need a B2B App Now That Shopify Does B2B Natively?
Most Shopify merchants should pause B2B app spending: native B2B shipped to every paid plan on April 2, 2026.
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.
Build or Buy a Blended DTC + B2B Storefront on Shopify?
Native B2B made the blended storefront the default architecture; the build is theme conditionality, and the real fork is one store or two.
Should You Build or Buy MOQs & Order Rules on Shopify?
MOQs and order rules are a narrow build: native B2B catalogs carry quantity rules, and one validation Function enforces the floors and logic they can't.
Should You Build or Buy Your NetSuite Integration on Shopify?
NetSuite integration is the honest DEPENDS: buy a connector for standard flows, build middleware when the flows are the business.
Ready to map your company-account gap list?
We'll audit your wholesale accounts against native B2B, name the app spend to cancel, and scope the one or two permission gaps actually worth building.
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.