Should You Build or Buy Per-Shipment B2B Invoicing on Plus?
Native wins for per-shipment B2B invoicing on Plus: Shopify's B2B plan table lists payment requests per fulfillment as Plus only, so each shipment of a split order carries its own request (verified Sep 2026). No app does this. Balance is the nearest listing at 0 reviews and documents no per-fulfillment feature. Below Plus, split the bill in your accounting system. On Plus, build only the ERP invoice sync, at $8,000 to $20,000 (Deploi estimate, illustrative).
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's B2B plan-features table on 2026-09-05: payment requests per fulfillment, partial payments and deposit requirements are all Plus only, while net payment terms exist on every plan. Browsed five App Store categories the same day: Selling products > Payments, Pay later, Pricing, Orders and shipping > Orders, and Inventory and ERP. The pay-later category is entirely consumer cash-on-delivery apps. The B2B pricing category is large and well reviewed, with BSS B2B Wholesale Pricing at 1,146 reviews and Wholesale Pricing Discount B2B at 723, but those apps do quoting and discounting rather than invoicing, and none advertises splitting one order's bill across fulfillments. Fetched Balance directly: free to install, 0 reviews, net terms for B2B buyers, and no documented per-shipment feature (verified Sep 2026). No other B2B payments listing checked documents the mechanic. The market is adjacent, not a fit, and the native feature is the answer on Plus.
- Reference scenario
- $20M–$100M GMV · Shopify Plus · wholesale orders shipped in 2–4 waves over weeks · net 30 terms per company · 100–300 shipments a month · receivables tracked in an ERP or accounting system · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Not on Plus | BUILD | Payment requests per fulfillment and partial payments don't exist on Basic, Grow or Advanced, and no app fills the gap. Issue one invoice per shipment from your accounting system, or split the order into one draft order per shipment and send each invoice, until Plus is justified by more than this. |
| Plus, orders split into 2–3 shipments, buyers pay from the request | WAIT | Fulfill the portion, send the payment request for that fulfillment, and let the company's terms do the rest. Nothing to buy and nothing to build; the plan already covers the mechanic. |
| Plus, ERP or accounting owns receivables and expects one invoice per shipment | CUSTOMIZE | Finance reconciles invoices, not Shopify orders. Sync each fulfillment's payment request and its payment to the ERP as its own invoice so AR aging matches what the buyer received. |
| Project supply: 4+ shipments over months with a deposit up front | CUSTOMIZE | Native deposits, per-fulfillment requests and net terms are all Plus features that stack. What's missing is the follow-through: payments aren't automatically captured when terms expire, so add an overdue report by company and shipment. |
What Per-Fulfillment B2B Payment Requests Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Billing each shipment as it leaves pulls cash forward by the weeks between the first and last pallet, and removes the buyer's objection to paying for goods they haven't received. |
| Operational efficiency | High | A request generated per fulfillment is an invoice nobody builds by hand, and with the ERP sync, a reconciliation nobody performs at month-end. |
| Customer experience | Medium | Purchasing departments match invoices to receipts; a bill per shipment matches how their three-way match already works, and one order with staged requests is easier than three orders. |
| Data & insight | Medium | Days-to-pay per shipment and per company become measurable when each fulfillment carries its own due date and payment rather than sharing one order-level status. |
Spend ceiling: On Plus, spend nothing on the mechanic; it's included. Spend on the ERP sync only when finance reconciles invoices in another system, and cap it at $8,000–$20,000 (Deploi estimate, illustrative). Below Plus, the ceiling is a process change, not a purchase, until a second Plus-only need makes the plan worth $2,300 USD/month (verified Sep 2026).
What buying enables (top apps)
- + Net terms for B2B buyers with credit risk underwritten by the provider rather than carried on your books (Balance, free to install, verified Sep 2026)
- + A unified set of business payment methods at checkout, which is the part of B2B collections most stores get wrong
- + Wholesale pricing, quoting and portals from a mature app category, useful even though none of it touches per-shipment billing
What building additionally unlocks
- + One ERP invoice per fulfillment, created from the Shopify event with order and fulfillment IDs on it, so AR aging matches what the buyer received
- + Daily reconciliation that catches a missed webhook before it becomes a missing invoice
- + An overdue report by company and shipment, because native requests bill but never chase
- + Below Plus, a documented split process that costs hours rather than a plan upgrade
Find Your Verdict in 3 Questions
Are you on Shopify Plus?
Yes: Go to question 2.
No: Your verdict: BUILD — payment requests per fulfillment are Plus-only and no app fills the gap; invoice each shipment from accounting or split the order into per-shipment draft orders until Plus is justified.
Does an ERP or accounting system own your receivables and expect one invoice per shipment?
Yes: Your verdict: CUSTOMIZE — use the native request per fulfillment and sync each one to the ERP as its own invoice with daily reconciliation ($8,000–$20,000, Deploi estimate, illustrative).
No: Go to question 3.
Do more than about 30 payment requests a month go past their due date?
Yes: Your verdict: CUSTOMIZE — keep the native requests and add an overdue report by company and shipment, because Shopify never captures a payment when terms expire.
No: Your verdict: WAIT — fulfill the portion, send the payment request, and let the company's terms do the rest; there's nothing to buy or build.
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 | There's nothing to install: the native feature is on with Plus; the ERP invoice sync and overdue report run 3–5 weeks (Deploi estimate, illustrative), and a net-terms platform adds onboarding and underwriting time. | ||
| Recurring fees | Balance is free to install with its fees billed by the vendor and not published (verified Sep 2026); the native feature is included with Plus and the sync carries upkeep only. | ||
| Maintenance & upgrades | A 0-review platform's roadmap is unknown; the sync needs an API version bump inside Shopify's 12-month window and a re-map when the ERP changes an invoice field. | ||
| Switching & exit | Leaving a net-terms platform brings receivables back onto your books mid-relationship; native payment requests and their payments stay on the Shopify order whether or not the sync runs. | ||
| Risk | |||
| Vendor risk | The only adjacent listing showed 0 reviews and documents no per-fulfillment feature (verified Sep 2026); the native mechanic is Shopify's own and the sync has no vendor. | ||
| Security & compliance surface | A payments platform sits in the money path of your largest orders; a first-party sync moves invoice records between two systems you already control. | ||
| Platform-deprecation exposure | Payment terms, partial payments and per-fulfillment requests are current B2B primitives on Plus; the sync depends on fulfillment and order webhooks, which are stable but never guaranteed to deliver. | ||
| Value | |||
| Fit to requirement | Billing each shipment as it leaves is precisely what the native feature is; a net-terms platform solves a different problem, and the sync adds the ERP fit native lacks. | ||
| Time to market | Native is live the day you're on Plus; the sync is about a month; a payments platform's underwriting sets its own calendar. | ||
| Performance & scale | A per-shipment request scales with fulfillments, not headcount; 300 shipments a month generate 300 requests without anyone building an invoice. | ||
| Data ownership & AI-readiness | Each shipment's request, due date and payment sit on the Shopify order and, with the sync, as an ERP invoice; a platform's ledger of what it collected is its own. | ||
| Focus & opportunity cost | The sync is small and bounded, a good first B2B automation; below Plus, the accounting-side split is a process decision more than an engineering one. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify B2B payment requests per fulfillment | Native — First-party Shopify, Plus only. Listed on the B2B plan-features table alongside partial payments and deposit requirements, all Plus only, while net payment terms run on every plan. Payments aren't automatically captured when the payment terms expire, so collection still needs an owner (verified Sep 2026). | Included with Shopify Plus, which starts at $2,300 USD/month (verified Sep 2026) | Billing each shipment of a split B2B order as it leaves, on Plus, with no app in the path |
| Balance | Live — flagged — 0 reviews; the listing reads 'No reviews yet'. Free to install. A real B2B payments product covering business payment methods, full ACH support and processing, and digital trade credit with underwriting, and it references offering net terms. The listing gives no specifics on credit-limit thresholds or automatic order holds for past-due accounts, so treat enforcement as unconfirmed until a vendor puts it in writing. | Free to install; underwriting and processing terms quoted by the vendor (verified Sep 2026) | Handing net-terms credit risk to an underwriter, which is a different decision from this one |
| B2B pricing and wholesale apps | Category — A large, well-reviewed category: BSS B2B Wholesale Pricing at 1,146 reviews and Wholesale Pricing Discount B2B at 723 (verified Sep 2026). These apps do quoting, tiered pricing and discounting. None advertises splitting one order's bill across multiple fulfillments, and the pay-later category next to them is entirely consumer cash-on-delivery apps. | Not priced here; the category doesn't cover invoicing | Wholesale pricing and portals, not the billing mechanic this page is about |
| ERP and accounting invoicing | Category — Platform integration; no App Store listing for the mechanic itself. Shopify's B2B integrations page names direct App Store integrations for NetSuite, Microsoft Dynamics 365, Fulfil and QuickBooks Online, iPaaS providers such as Pipe17, Patchworks and OmnifiCX, and custom API-based integrations. The accounting system can already issue one invoice per shipment on any plan; the work is keeping Shopify's order and the ERP's invoices in step. | Your existing ERP or accounting subscription; connector pricing varies by vendor (verify on the listing) | Splitting the bill below Plus, and owning AR aging above it |
The Build Path
- Use the native request per shipment on Plus: Fulfill the portion that's leaving, send the payment request for that fulfillment, and let the company's terms set the due date. Pair it with a deposit requirement on companies that need cash up front. Because payments aren't automatically captured when terms expire, give each request an owner or a report; the feature bills, it doesn't chase.
- Sync each request to the ERP as its own invoice: Finance reconciles invoices, not orders. On the fulfillment event, create the matching invoice in the ERP with the Shopify order and fulfillment IDs on it, and on payment mark it paid. Shopify's B2B integrations page offers three routes: direct App Store integrations for select ERP, accounting and PIM systems, iPaaS intermediaries, and custom API-based integrations. Reconcile daily, because webhook delivery isn't guaranteed and a missed event is an invoice that never existed.
- Below Plus, split in the system that can: Issue one invoice per shipment from your accounting system and record each payment against the Shopify order by hand, or break the order into one draft order per shipment and send each invoice from Shopify. Both are process changes rather than code. Neither gives the buyer a single order with staged bills, which is what Plus's feature does.
- Effort band
- $8,000–$20,000 for the fulfillment-to-invoice sync, payment matching, daily reconciliation and an overdue report — Deploi estimate (illustrative); lands in the $10–25K contact-form band
- Typical timeline
- 3–5 weeks, with the overdue report shippable in the first week (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $1,200–$4,000/yr (Deploi estimate, illustrative) covering ERP invoice-field changes, new company structures, and moving the integration forward before an API version sunsets on Shopify's 12-month support window.
- What you own — and what you take on
- You own: every shipment's payment request and payment on the Shopify order, the matching ERP invoices, and the overdue view by company. You take on: the sync's reconciliation, and the Plus subscription the native feature requires.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$500 (invoice templates and a process doc) | $8,000–$20,000 (native requests are configuration; the sync is the cost) |
| Years 1–3 (recurring) | $21,000–$63,000 (manual invoicing labor) | $3,600–$12,000 (upkeep) |
| 3-year total | ≈$21,000–$63,500 | ≈$11,600–$32,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column: no app sells this mechanic, so the column prices what a non-Plus merchant actually runs instead: manual per-shipment invoicing from accounting at about 10 minutes per shipment, 100–300 shipments a month, illustrative labor at $35/hour. Balance's fees are quote-based and excluded.
- † Build column is the CUSTOMIZE lane on Plus: native payment requests per fulfillment (configuration only) plus the ERP invoice sync and overdue report; three-year horizon. The pure WAIT lane costs nothing beyond the plan.
What the Sticker Price Hides
On the buy path
- — No App Store app splits a B2B order's bill across fulfillments; the nearest listing, Balance, shows 0 reviews and documents no per-shipment feature (verified Sep 2026)
- — Free to install on a net-terms platform is not free to run: processing and terms fees are billed by the vendor and never appear on your Shopify bill
- — The pay-later category looks relevant and is entirely consumer cash-on-delivery apps (verified Sep 2026)
- — Handing receivables to a net-terms provider also hands over the buyer conversation on every late shipment
On the build path
- — Payments aren't automatically captured when terms expire, so a per-shipment request without an overdue report is three receivables where there used to be one (verified Sep 2026)
- — Webhook delivery isn't guaranteed; a sync without daily reconciliation leaves an ERP invoice missing and nobody knows
- — Per-fulfillment requests are Plus-only, so a non-Plus merchant's first cost is the plan, which starts at $2,300 USD/month (verified Sep 2026)
- — ~$1,200–$4,000/yr upkeep as ERP fields and API versions change (Deploi estimate, illustrative)
What Merchants Say
Wholesale ops teams describe the choice they'd rather not make: bill the whole order before the first pallet leaves and take the buyer's pushback, or wait for the last shipment and carry three weeks of receivable for nothing.
Low-star reviews on B2B payments platforms cluster on onboarding rather than features: approvals that take days while the order sits, and fees that show up on the vendor's statement instead of the Shopify bill.
If You Change Your Mind Later
If you bought and outgrow it
Leaving a net-terms platform is the expensive exit here, because receivables and credit risk return to your balance sheet mid-relationship and the payment history that justified buyer limits usually stays with the provider. Ask at signup what data you get back and in what format. The per-shipment billing itself was never the platform's job, so nothing about that mechanic is lost.
If you built and want out
Nothing strands. Payment requests and payments sit on the Shopify order, ERP invoices sit in the ERP, and the sync between them can be switched off without touching either. If Shopify or a vendor later ships a native ERP invoice sync, you retire a few hundred lines of code and keep every record. The exit cost rounds to a few days of work.
When This Answer Changes
We're watching for:
- ▸ Shopify extending payment requests per fulfillment or partial payments to Advanced, which would end the plan-gate decision for most wholesalers
- ▸ Balance or another B2B payments listing documenting per-shipment invoicing and passing about 30 reviews
- ▸ Shopify adding automatic capture when payment terms expire, which would remove the overdue-report half of the build
Verdict change log:
No changes since first publication (September 2026).
Common Questions
What does 'payment requests per fulfillment' mean in Shopify B2B?
Payment requests per fulfillment let a B2B order shipped in several waves carry a separate payment request for each fulfillment instead of one bill for the whole order. Shopify's B2B plan-features table lists the feature as Plus only, alongside partial payments and deposit requirements (verified Sep 2026). Net payment terms still set each request's due date, and payments aren't automatically captured when those terms expire, so collection needs an owner.
Can I invoice each shipment of a B2B order separately without Shopify Plus?
Not inside Shopify. Basic, Grow and Advanced have net payment terms but no payment requests per fulfillment and no partial payments (verified Sep 2026), and no App Store app supplies the mechanic. Two workarounds exist: issue one invoice per shipment from your accounting system and record payments against the order by hand, or split the order into one draft order per shipment. Plus, which starts at $2,300 USD/month, makes it a native setting.
Is there a Shopify app that splits a B2B order's bill across shipments?
No. A check of five App Store categories on 2026-09-05 found the pay-later category full of consumer cash-on-delivery apps. The B2B pricing category, led by BSS B2B Wholesale Pricing at 1,146 reviews, does quoting and discounting rather than invoicing. Balance, the nearest B2B payments listing, is free to install with 0 reviews and documents no per-shipment feature (verified Sep 2026). The native Plus feature is the only in-Shopify answer.
Your Next Steps
If you're going with WAIT(matches your selected profile)
- Confirm every company that ships in waves has payment terms set, because the request's due date comes from them
- Fulfill the portion leaving and send the payment request for that fulfillment on the same day
- Add a deposit requirement to companies that need cash before the first shipment
- Name one owner for a weekly review of requests past due, since payments aren't captured automatically
- Revisit the build the month an ERP starts owning your receivables
If you're going with BUILD
- Decide where the split lives below Plus: one invoice per shipment from accounting, or one draft order per shipment from Shopify
- Write the process down, including who records each payment against the Shopify order and when
- Put the Shopify order number on every accounting invoice so reconciliation is a lookup, not a hunt
- Track hours spent on manual split invoicing for one quarter to price the Plus upgrade honestly
- Re-run this decision when a second Plus-only B2B feature, such as deposits or direct company catalogs, lands on the roadmap
Official Docs & Sources
- B2B features by plan — Shopify Help Center
- Setting up payment terms in B2B — Shopify Help Center
- B2B draft orders — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Plan Around Shopify's B2B Company-Size Ceilings?
A B2B company holds up to 10,000 locations and 10,000 customers, but only 50 customers per location. The 50 is the number that actually constrains you.
Should You Build or Buy B2B Deposit Payments on Shopify Plus?
Plus's native B2B deposits collect the percent up front, but the balance is never auto-captured. Both purpose-built B2B deposit apps had 0 reviews when checked.
ERP vs. Shopify: Who Should Own B2B Pricing?
Shopify's B2B integration page names three sanctioned ERP paths and never says which system should own pricing. Channel count decides the answer, not the platform.
Can Shopify's Catalog Model Hold 30+ Price Tiers?
A company location holds a maximum of 25 B2B catalogs (verified Sep 2026). Model 30+ tiers as volume breaks, or split the account across company locations.
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 bill each pallet as it leaves?
Plus already sends the request per shipment. We wire each one to your ERP as its own invoice, reconcile daily so nothing goes missing, and give finance the overdue view by company and shipment that Shopify doesn't draw.
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.