Should You Build or Buy B2B Registration & Approval on Shopify?
Building B2B registration and approval wins for mid-market Shopify stores: a $5,000–$15,000 form-Flow-API workflow (Deploi estimate, illustrative) closes a real gap, since native B2B ships no auto-approve registration (July 2026 research). Approved applicants become companies with the right catalog and terms automatically, not ten copy-paste minutes each. Registration apps work, but many still approve buyers into tags, and tax documents land in a vendor's database. Buy only when a no-dev team is drowning in applications.
Your profile — see how the verdict shifts
- Confidence
- High — Small bounded workflow on sanctioned primitives, low lock-in both ways, and the auto-approve gap is documented — fit value is high for a 2–4 week build
- Reference scenario
- $20M–$100M GMV · 20–100 wholesale applications/month · agency dev bench
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under 10 applications/mo | WAIT | Manual company setup in the admin costs minutes a week; automation isn't the constraint at this volume. |
| 10–50 applications/mo | DEPENDS | Build if any dev window exists this quarter — the scope is two to four weeks. Buy to bridge a truly empty bench. |
| 50–200 applications/mo | BUILD | Reviewer minutes and applicant wait times now cost real money; auto-approve rules pay for the build fast. |
| 200+ applications/mo | BUILD | Intake is a pipeline at this scale; you want your own rules, your own data, and same-day activation. |
What B2B registration & approval Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — indirect | High | Every day an approved-in-principle buyer waits is a day their orders go to the incumbent supplier; same-day approval pulls the first PO forward. |
| Operational efficiency | High | Auto-created companies with catalog and terms assigned end the copy-paste-across-admin-screens loop — roughly ten manual minutes per applicant at volume. |
| Customer experience | Medium | Buyers judge a wholesale program by its front door; a real application flow with status updates reads as a supplier worth stocking. |
| Data & insight | Medium | Structured application data — channel, region, expected volume — lands in your metaobjects and feeds segmentation and sales follow-up. |
Spend ceiling: Registration is a front door, not a platform. Cap the build near $15,000 (Deploi estimate, illustrative) unless vetting itself is the business — past that you're building underwriting, not intake.
What buying enables (top apps)
- + A polished application form live in days with no dev time
- + Built-in review queues, applicant emails, and status tracking
- + Vendor-maintained templates for common vetting questions
What building additionally unlocks
- + Auto-approve rules on your own criteria — closing the documented native gap
- + Company creation with catalog and payment terms assigned in one motion via the Admin API
- + Tax IDs and resale certificates stored in your stack, not a vendor's database
- + Application data as metaobjects, feeding segmentation and follow-up without export walls
Find Your Verdict in 3 Questions
Do wholesale applications arrive more than about ten times a month?
Yes: Go to question 2.
No: Your verdict: WAIT — manual review in the admin covers this volume; revisit when applications pick up.
Is there any dev window in the next quarter — even two to four weeks?
Yes: Your verdict: BUILD — the form-Flow-API workflow ends the copy-paste loop and keeps applicant data yours.
No: Go to question 3.
Is application volume drowning the team right now?
Yes: Your verdict: BUY — install a registration app, confirm it creates companies rather than tags, and diary the build review.
No: Your verdict: BUILD — schedule it for the next dev window; a shared inbox bridges the gap.
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 | A registration app configures in a day or two; the form-Flow-API build is an estimated 2–4 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Apps bill monthly for the life of the wholesale program; the build's recurring cost is minor upkeep. | ||
| Maintenance & upgrades | Bounded surface on both paths: a form, a Flow, and one API integration rarely break, and the vendor patches its own. | ||
| Switching & exit | Approved companies live in Shopify either way; pending applications and uploaded documents sit in the app's database, and the build keeps them in your metaobjects. | ||
| Risk | |||
| Vendor risk | Registration apps are small vendors in a churning category; a form and a Flow have no vendor to lose. | ||
| Security & compliance surface | Tax IDs and resale certificates are sensitive business documents; the build keeps them out of a third party's database entirely. | ||
| Platform-deprecation exposure | Apps built on the pre-2026 tag-based wholesale model misfit native B2B companies; forms, Flow, and the Admin API are the sanctioned primitives. | ||
| Value | |||
| Fit to requirement | Your vetting questions, your segments, your auto-approve thresholds — intake rules are exactly the kind of logic templates flatten. | ||
| Time to market | Days versus two to four weeks — a real but small gap. | ||
| Performance & scale | A form is a form; neither path strains at wholesale application volumes. | ||
| Data ownership & AI-readiness | Structured applicant data — channel, region, expected volume — lands in your own metaobjects and feeds segmentation without export ceilings. | ||
| Focus & opportunity cost | Small enough scope that neither path distracts; a classic first Flow-plus-API build for a wholesale program. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Registration apps (category) | Category — Form-plus-approval apps; several predate native B2B companies, so confirm that approval creates companies rather than just customer tags | $10–$100/mo bands (illustrative) | A working intake queue this week with no dev hands |
| Native B2B company setup (manual) | Native — Company profiles, catalogs, and payment terms on every paid plan since 2026-04-02; intake and approval stay manual (July 2026 research) | Included with your Shopify plan | Low application volume a person can vet |
| Custom form + Flow + Admin API | Build lane — This page's verdict: themed application form, Flow review routing, and API company creation with auto-approve rules | $5,000–$15,000 one-time (Deploi estimate, illustrative) | Owning the front door and the vetting data behind it |
The Build Path
- Application form on your theme: A themed form capturing business identity, tax and resale numbers, channel, and region; submissions stored as metaobjects with status fields.
- Flow review routing: Shopify Flow notifies the right owner, chases stale applications, and moves statuses — the review queue lives where your team already works.
- Admin API company creation + auto-approve rules: On approval, the API creates the company and assigns catalog and payment terms in one motion; rule-passing applicants skip the queue entirely.
- Effort band
- $5,000–$15,000 one-time (Deploi estimate, illustrative) — the low half of the $10–25K contact-form band, often bundled with wider B2B setup
- Typical timeline
- 2–4 weeks (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate) — roughly $800–$3,000/yr (illustrative) for form tweaks, rule changes, and API version bumps. There is no subscription line.
- What you own — and what you take on
- You own: the vetting rules, the applicant data, and the documents. You take on: file-upload handling for certificates and the small upkeep above.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$500 (config) | $5,000–$15,000 |
| Years 1–3 (recurring) | $1,100–$3,600 | $2,400–$9,000 (upkeep) |
| 3-year total | ≈$1,100–$4,100 | ≈$7,400–$24,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: mid-band registration-app pricing held flat.
- † Build: form, Flow routing, API company creation, and auto-approve rules; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Tag-model mismatch: approval into customer tags means re-doing setup as companies to use native catalogs
- — Applicant documents — tax IDs, resale certificates — accumulate in the vendor's database
- — Per-submission or tier pricing creeps as the wholesale program grows
On the build path
- — File upload for certificates is the fiddly 20% — scope it explicitly
- — Auto-approve rules need a fraud-shaped review: ask who could game them
- — Upkeep runs ~15–20% of build cost per year (Deploi estimate)
- — Rejection and wait-list flows get forgotten in v1 scopes
What Merchants Say
Wholesale operators describe the same grind: applications arrive by email, someone copy-pastes company details across admin screens, and hot applicants wait days while the incumbent supplier keeps their orders.
Registration-app reviews flag a model mismatch: apps that approve into customer tags leave merchants re-doing setup as companies to use native catalogs and terms.
If You Change Your Mind Later
If you bought and outgrow it
Approved companies and customers live in Shopify, so the store keeps working after uninstall. Pending applications and uploaded documents live in the app — export them before the subscription lapses, and re-key any in-flight applicants. The cleanup is annoying but bounded; low lock-in is this category's one mercy.
If you built and want out
Applications live in your metaobjects and the workflow lives in Flow — both stay put through theme changes and redesigns. Retreating to an app later means pointing the form's URL somewhere new. Nothing is stranded, which is why the small build is easy to green-light.
When This Answer Changes
We're watching for:
- ▸ Shopify shipping native self-serve B2B registration or auto-approval rules — that would move this page toward WAIT (none as of July 2026 research)
- ▸ Application volume crossing ~50 a month — manual review time starts paying for the build by itself
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Does Shopify have a built-in wholesale registration form?
No. Native B2B ships company profiles, catalogs, and payment terms on every paid plan since April 2026, but no application form and no auto-approve workflow (July 2026 research). Someone on your team creates each company by hand. A custom form plus Shopify Flow plus the Admin API automates the intake-review-approve loop; registration apps cover it too, with the trade-offs this page scores.
How much does automated B2B registration cost to build?
An estimated $5,000–$15,000 one-time (Deploi estimate, illustrative): a themed application form storing submissions as metaobjects, Flow routing for review, and Admin API company creation with catalog and payment-terms assignment on approval. Timeline runs 2–4 weeks (Deploi estimate, illustrative). Registration apps rent the same loop for $10–$100 a month (illustrative).
Can wholesale applicants be approved automatically?
Yes, with rules you define. A build auto-approves applicants who pass your checks — a valid tax or resale number, a matching region, no competitor flags — then creates the company with the right catalog instantly. Shopify ships no native auto-approve rules (July 2026 research). Keep a manual review lane for edge cases; auto-approval works best on the clearly safe majority.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- List your vetting criteria and split them: auto-approvable checks versus human judgment calls
- Design the application form with sales — every field must earn its place
- Build the Flow routing: notify, remind, escalate stale applications
- Wire Admin API company creation with catalog and payment-terms assignment
- Track time-to-approval weekly — it's the number this build exists to shrink
If you're going with BUY
- Confirm the app approves into companies, not customer tags
- Check where uploaded documents are stored and how they export
- Map the app's approval statuses to your actual vetting steps
- Keep catalogs and payment terms native so the app stays swappable
- Diary a build review at 50 applications a month
Official Docs & Sources
- Shopify B2B — Shopify Help Center
- Apps and B2B — shopify.dev
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.
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.
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 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 automate your wholesale front door?
A small form-Flow-API build approves good buyers the same day and keeps their documents in your stack. We ship these in weeks, not quarters.
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.