How to enforce B2B credit limits and automate Net 30 dunning on Shopify without Shopify Plus
In 2026, Shopify Basic, Grow, and Advanced plans include native B2B payment terms up to Net 90. What Shopify still leaves uncovered is credit risk control: hard credit-limit blocks, overdue buyer holds, automated multi-step dunning reminders, sequential credit notes, and clean accounting close exports.
Short answer for non-Plus Shopify B2B merchants
You no longer need Shopify Plus to assign Net 30 due dates to a wholesale buyer. You do still need a credit-control layer as soon as more than a handful of B2B accounts buy on invoice, because native Shopify will let a customer with three overdue invoices keep placing Net 30 orders past their approved exposure cap.
Interactive 3-minute product walkthrough
Jump straight to any B2B workflow step or switch video narration language.
1. What Shopify native B2B Net 30 covers on Basic, Grow, and Advanced (and where it stops)
Shopify opened its core Company and Payment Terms objects to standard non-Plus plans, so wholesale merchants can assign Net 15, Net 30, Net 60, or Net 90 to a company location and let approved buyers check out with payment pending. For low-volume wholesale with trusted long-term partners, native terms are a sensible baseline.
Once B2B order volume grows past 10 to 20 monthly invoices, four operational bottlenecks appear immediately on Basic, Grow, and Advanced stores:
No hard credit-limit block
Native Shopify does not track a live credit line per company or reject a cart when open invoices plus the new order exceed the buyer's approved cap.
No automatic overdue hold
A buyer with past-due Net 30 balances can keep submitting new invoice orders unless your finance team checks aging reports daily and disables the account by hand.
Manual invoice chasing
Shopify does not auto-charge cards on the due date or run a staged reminder sequence with automatic stop-on-payment reconciliation across wire, ACH, and card payments.
Fragmented accounting close
Managing partial wire settlements, sequential credit notes (CN-YYYY-NNNN), and 18-column FEC or ERP journals still falls back to error-prone spreadsheets.
2. Comparison: Native Shopify Net Terms vs Manual Workarounds vs Credit-Control App
The table below compares the three real-world setups used by non-Plus Shopify wholesale stores in 2026 across credit risk, dunning automation, checkout friction, and month-end accounting close.
| Operational capability | Shopify Native B2B Net Terms (Non-Plus) | Manual Draft Orders + Shopify Flow | Eclipse Net Terms & PO (Basic to Plus) |
|---|---|---|---|
| Net 15 / Net 30 / Net 60 due dates | Included natively on company locations (capped at 3 B2B catalogs on non-Plus) | Manual per draft order, slow for repeat buyers | Automated per company account with self-serve cart checkout |
| Atomic credit-limit enforcement | Not available natively | Manual spreadsheet check before confirming order | Enforced atomically at submission (prevents race-condition overspend) |
| Automatic block on overdue accounts | Not available natively | Manual account suspension after aging review | Instant checkout hold when open balance exceeds limit or account is on hold |
| Purchase Order (PO) capture | Limited field handling; no credit validation | Collected by email and pasted into order notes | Required or optional PO # validated directly in the OS 2.0 Cart App Block |
| Multi-step dunning reminders | No built-in staged dunning cadence | Custom Flow triggers; brittle across partial offline payments | Scheduled J-3, J+1, J+7, J+15 cadence with instant halt on payment |
| Offline wire / ACH & webhook sync | Manual Mark as Paid per order | Manual Mark as Paid per order | One-click settlement + automatic orders/paid webhook releasing credit immediately |
| Sequential credit notes | Standard Shopify refunds only (no sequential B2B credit note numbering) | Issued manually in external invoicing software | Immutable sequential CN-YYYY-NNNN linked to original INV-YYYY-NNNN |
| Accounting close export (CSV & FEC) | Raw order CSV; manual journal mapping required | Manual reconciliation in Excel or QuickBooks | Ready-to-import CSV + 18-column French FEC export with AR aging buckets |
3. Architecture for enforcing credit limits on non-Plus Shopify stores
A common misconception is that enforcing B2B credit limits requires Shopify Checkout UI Extensions reserved for Shopify Plus. In practice, an Online Store 2.0 Theme App Block embedded in the Cart template combined with a signed Shopify App Proxy delivers strict credit enforcement on Basic, Grow, and Advanced plans with zero Liquid theme edits:
- Customer verification via App Proxy: When a logged-in B2B buyer opens the cart, the Cart App Block requests live available credit, payment terms (Net 15, Net 30, or Net 60), and hold status over an HMAC-verified App Proxy endpoint (/apps/net-terms).
- Atomic credit reservation: When the buyer submits their Purchase Order number, the backend locks the company credit ledger in a single database transaction. If open_balance + cart_total > credit_limit or if the account is on hold, submission is rejected cleanly before any order is created.
- Draft Order and invoice creation: Approved requests immediately create a Shopify Draft Order carrying the buyer's PO reference and agreed due date, plus a sequential invoice entry (INV-YYYY-NNNN) in the AR aging ledger.
- Automated dunning with stop-on-payment: A daily scheduler sends configurable reminders at J-3, J+1, J+7, and J+15. As soon as Shopify fires the orders/paid webhook or your team settles an offline wire/ACH transfer, credit is released instantly and pending reminders stop.
- Clean month-end accounting close: Finance teams issue sequential credit notes (CN-YYYY-NNNN) for returns or disputes and export the entire period as CSV or a compliant 18-column FEC journal without hand-reconciling spreadsheets.
4. Rollout checklist (under 15 minutes on Basic, Grow, or Advanced)
- Audit your top 10 to 50 wholesale accounts and assign a realistic starting credit cap plus payment term (Net 15, Net 30, or Net 60).
- Enable the OS 2.0 Theme App Block on your Cart template (zero deprecated ScriptTags, zero theme code modifications) and choose whether Purchase Order numbers are required or optional.
- Test two edge cases before inviting buyers: an order strictly under the credit cap (must succeed and decrement available credit) and a second order pushing the balance over the cap (must block cleanly).
- Verify your dunning sender templates and download a sample CSV and 18-column FEC export to confirm column mapping with your accountant before month-end close.
5. Frequently asked questions
Do I need Shopify Plus to offer Net 30 payment terms in 2026?
No. Shopify now enables native B2B payment terms (including Net 15, Net 30, Net 60, and Net 90) on Basic, Grow/Shopify, and Advanced plans without upgrading to Shopify Plus. However, native Shopify still lacks automated credit-limit blocking, overdue account holds, multi-step dunning reminders, sequential credit notes, and accounting FEC exports.
Does Shopify natively block a B2B buyer who exceeds their credit limit or has overdue Net 30 invoices?
No. Native Shopify payment terms allow approved company locations to place pending Net 30 orders without checking live credit utilization or overdue balances. Merchants must monitor aging spreadsheets manually or use a dedicated credit-ledger app that runs an atomic credit-limit check before creating the order.
How can I automate Net 30 payment reminders without manually chasing every invoice?
Because Shopify does not automatically charge cards or run multi-step dunning on Net 30 invoices, merchants either maintain custom Shopify Flow rules or install a dedicated Net Terms app with scheduled dunning stages (such as J-3, J+1, J+7, and J+15) that automatically halt the moment Shopify fires the orders/paid webhook.
Can a non-Plus Shopify store enforce Purchase Order (PO) numbers and credit checks without editing Liquid theme code?
Yes. An Online Store 2.0 Theme App Block placed on the Cart template checks the logged-in buyer's B2B credit balance via an authenticated Shopify App Proxy, validates an optional or required PO reference, reserves the credit limit atomically, and generates a Shopify Draft Order with the agreed Net 15, Net 30, or Net 60 due date.
How do European and French merchants reconcile Shopify B2B Net 30 invoices and credit notes with accounting?
Native Shopify order exports do not produce immutable sequential credit notes or compliant 18-column FEC journals. A dedicated B2B ledger generates sequential invoice numbers (INV-YYYY-NNNN) and credit notes (CN-YYYY-NNNN), records partial wire or ACH settlements, and exports monthly CSV and 18-column FEC files ready for bookkeepers.
Ready to add atomic credit limits and Net 30 dunning to your Shopify store?
Eclipse Net Terms & PO is engineered specifically for Shopify Basic, Grow, Advanced, and Plus merchants who need strict credit-limit protection, Purchase Order capture, automated dunning, sequential credit notes, and 18-column FEC exports priced strictly on active B2B accounts.
Related resources: Back to Eclipse Technology (EN) · Fixed-price SME AI automations (FR) · Live interactive business demos