Shopify's Native Net Terms: Is Your B2B App Now Redundant?
Summer Editions 2026 did what Editions releases always do: it took a feature merchants were paying an app for and made it part of the platform. This time it was wholesale's turn. Net payment terms, automated invoicing and payment reminders are now native to Shopify B2B, and every DTC brand running a wholesale side channel through a dedicated B2B app has a pricing decision to make.
We have spent the weeks since the release fielding the same question from clients: can we drop the app now? The honest answer is that it depends — but it depends on fewer things than your app vendor would like you to believe.
What follows is the framework we use in those conversations. What native actually covers, where dedicated apps still earn their fee, how to decide based on your numbers rather than your nerves, and what the cutover looks like if you choose to leave.
$4,000+
What a dedicated B2B suite typically costs per year across the mid-market stores we audit, once you add the subscription tier, transaction fees and the developer hours spent keeping the integration upright.
What native B2B now covers
Shopify B2B has supported company profiles, locations and price lists for a while. What Summer Editions 2026 added is the financial plumbing that used to justify a dedicated app: payment terms that actually enforce themselves, invoices that send without manual draft-order wrangling, and reminders that chase late payers so your team doesn't have to.
Net payment terms
Net 15, 30 and 60 terms assignable per company location. Due dates track against the order, outstanding balances surface in admin, and approved buyers check out on terms automatically.
Automated invoicing
Invoices generate and send automatically when a B2B order is placed or fulfilled. No more converting draft orders by hand or bolting an invoicing app onto your order webhooks.
Payment reminders
Scheduled reminders before and after the due date, with the outstanding amount and a payment link included. Configurable cadence, no app, no spreadsheet of who owes what.
The three capabilities Summer Editions 2026 moved into core Shopify B2B.
Two caveats before you draft the uninstall ticket. First, Shopify B2B remains a Plus feature, so if you are on a standard plan the question changes shape entirely — it becomes whether your wholesale volume justifies the Plus upgrade at all, which we worked through in our breakdown of whether Shopify Plus is worth it. Second, this was one announcement among many; the same release reshaped subscription primitives too, and we covered those separately in our Summer Editions 2026 review.
Where dedicated apps still earn their fee
Native gets you the eighty per cent case. The remaining twenty per cent is exactly where wholesale gets expensive, and it is worth being honest with yourself about whether you live there. Four capabilities still sit firmly on the app side of the line.
Credit limit management
Native terms have no concept of total exposure. A good app caps a buyer's outstanding balance and blocks new orders past the threshold. Native will happily let a slow payer keep ordering.
Invoice-level dunning
Native reminders are polite nudges on a schedule. Apps run escalation logic per invoice: tone that hardens over time, account holds, copying in the buyer's finance contact at day 14 overdue.
Multi-entity buyers
A parent company ordering through several legal entities, with consolidated statements and different terms per entity. Native models companies and locations; it does not model corporate groups.
Customer-specific catalogs
Native price lists handle who pays what. They do not handle who sees what at SKU level, with minimum order quantities, case-pack multiples and contract-specific ranges per buyer. Apps still own that.
The four jobs that still justify a dedicated B2B app in mid-2026.
If none of those four made you wince, you are probably paying for capability you do not use.
The decision framework
Two variables settle this for almost every brand we audit: how much of your revenue is wholesale, and how complex your wholesale orders actually are. Across our client base, somewhere around twenty per cent wholesale share is typically where finance operations start demanding proper tooling. Complexity means any of the four capabilities above; simplicity means single-entity buyers, standard terms and pricing that fits in a price list.
Wholesale revenue share × order complexity
Drop the app
Single-entity buyers on standard terms, pricing covered by price lists. Native now does everything you use. Schedule the migration this quarter and bank the fee.
Simplify first
At this share, the complexity probably isn't earning its keep. Standardize terms, consolidate catalogs, then go native. The app is often masking a process problem, not solving one.
Native, plus finance tooling
Run terms and invoicing natively, and put credit control where it belongs: in your accounting stack, not a storefront app. Cheaper, and your finance team already lives there.
Keep the app
Multi-entity buyers, credit limits and contract catalogs at meaningful volume: the app fee is cheap insurance against receivables chaos. Revisit at every Editions release.
Zerglo's net-terms decision matrix: wholesale revenue share against order complexity. The thresholds are guides drawn from our audits, not laws.
A supplements brand we worked with last year sat squarely in the first quadrant without realising it. They were paying for a full B2B suite to serve eleven stockists — all single-entity, all on net 30, all priced off one trade discount. When we mapped actual usage against the app's feature list, they used four features out of roughly forty, and three of the four are now native. That conversation takes ten minutes once the numbers are on the table.
The quadrant that catches people out is the second one. Brands with small wholesale arms accumulate bespoke arrangements one stockist at a time, and the app quietly absorbs the mess. Before you renew, ask whether each special case is revenue you would fight to keep.
The hybrid case: subscriptions plus wholesale
The configuration we see most at Zerglo is not a pure wholesaler. It is a DTC subscription brand adding wholesale as a second channel: the coffee roaster picking up cafés, the pet food brand supplying groomers, the skincare label landing its first salon chain. For these brands, the net-terms question collides with an existing selling plan setup, and that collision deserves more care than it usually gets.
The two systems are different machinery. A selling plan bills a vaulted payment method on an interval. A net-terms order defers payment against an invoice. They happen to live in the same admin, but they make opposite assumptions about who pays, when, and how — and trying to weld them into a "wholesale subscription" produces the worst of both: recurring orders your finance team can't reconcile and invoices your subscription app doesn't know exist.
"A selling plan bills a card on a schedule. A net-terms order is a promise against an invoice. The moment you make one do the other's job, both channels get worse."
Wholesale buyers do not want a subscription; they want a reorder.
So keep the channels cleanly separated. Your B2B catalogs should exclude the purchase options that carry selling plans, so company buyers never see subscribe-and-save widgets priced against the wrong list. Recurring wholesale demand belongs in scheduled draft orders or reorder flows, not in selling plans with net terms bolted on. And discount logic should never be shared between channels, because a stacked trade discount plus subscription discount is margin you will not get back. Attaching selling plans to products they were never designed for is already one of the most common selling plan mistakes we see in audits; adding payment terms to the mix multiplies the failure modes.
In our experience, the hybrid brands that run wholesale well treat it as a separate business that shares inventory, nothing more. Separate catalogs, separate pricing, separate payment expectations. Native net terms make that separation easier to maintain, not harder, because the financial machinery no longer lives in a third-party app with its own opinions about your data model.
The migration checklist
If the matrix says go native, treat the cutover as a small replatform rather than an uninstall — the same sequencing discipline as a full Shopify migration, in miniature. The order of operations matters because the app's data leaves with it.
-
Export every open invoice and balance first. Pull an aged-receivables report from the app before anything else. Outstanding invoices are money, and the app's records disappear when you uninstall.
-
Map terms per company. Recreate each buyer's net 15, 30 or 60 assignment on their company location in native B2B. Native supports a fixed set of terms, so decide now how you handle the one stockist on net 45.
-
Rebuild pricing as price lists and catalogs. Then spot-check against last quarter's actual invoices, not against what the app's settings claim. Pricing drift between app and reality is common and embarrassing to discover post-cutover.
-
Recreate the reminder cadence and test it on yourself. Set up native payment reminders to match your current dunning rhythm, then place a test order on terms and watch the full sequence land before any buyer does.
-
Run both systems in parallel for one billing cycle. New orders go through native; existing invoices wind down inside the app. Cutting over with open invoices in flight is how receivables go missing.
-
Uninstall cleanly. Strip the app's theme code, snippets and webhooks, and re-point your accounting integration at native B2B order data. An orphaned wholesale snippet rendering broken prices is the classic post-uninstall surprise.
The direction of travel
Editions releases compound. Wholesale functionality that was app-only territory two years ago became native-with-gaps last year and is genuinely usable now. The sensible bet is that the remaining gaps — credit limits and multi-entity support most obviously — are roadmap candidates rather than permanent moats. App vendors know this, which is why the better ones are already repositioning around workflow depth instead of feature exclusivity.
The practical posture for a DTC brand with a wholesale arm: put the B2B line item on review at every Editions cycle, and make the vendor tell you what they do that Shopify doesn't. A vague answer is itself an answer.
And if you are not sure which quadrant you sit in, the fastest route to clarity is putting real numbers against the matrix: wholesale share, actual feature usage, and what each manual workaround would genuinely cost your team. That is precisely the kind of question an outside audit answers quickly, because the data already exists in your admin — someone just has to read it without a renewal incentive.