Shopify B2B Net Terms vs Credit Limits: Build a Safer Wholesale Credit Workflow

Separate four controls before you configure a single company

Write four fields into the credit policy before touching settings. First is payment timing: immediate payment, net 15, net 30, due on fulfillment, or another supported term. Second is the deposit requirement: the portion of a particular order that must be paid up front. Third is account exposure: the maximum unpaid commitment the merchant is willing to carry for that company. Fourth is overdue status: whether a past-due balance stops new credit ordering even when the nominal credit cap has room left.

Consider a buyer on net 30 with a merchant-defined $25,000 credit cap. If the account already has $22,000 of unpaid exposure and requests another $8,000 order, the existing invoices might still be within their due dates. The problem is not lateness; it is exposure. A different account might have only $4,000 outstanding against the same cap but be past due. That account has a timing problem even though the balance is small. Treating both cases as 'net terms' hides the decision you actually need to make.

A deposit introduces a third path. Instead of raising the permanent credit limit for a large project order, the merchant might require part of that order up front when the Shopify plan and workflow support deposits. That reduces the unpaid portion of the transaction without pretending the buyer's long-term credit profile changed. Your policy should explain when that option is appropriate and who can authorize exceptions.

Use Shopify payment terms for the due-date mechanics they actually provide

Shopify currently documents net 7, 15, 30, 45, 60, and 90 terms for B2B company locations and individual draft orders, with the term starting from the order date. Due on fulfillment is also supported. A fixed calendar date is available for individual draft orders. Those controls are useful when the main requirement is simply to tell an approved buyer when the remaining balance must be paid.

The due date is not a collection engine. Shopify states that payments are not automatically captured merely because the payment term expires. The order becomes overdue, and the merchant still follows the applicable payment-collection process. That distinction matters when designing an overdue rule: a red overdue status tells you that the agreed date passed; it does not mean the money was attempted, declined, or collected automatically.

If your wholesale operation has a few trusted accounts, modest balances, and finance already reviews exposure manually, native terms may be enough. Do not add procurement software merely to recreate a due date that Shopify already supports. Add another layer when the missing control is about exposure, overdue blocking, approval, or another documented procurement job.

Use deposits to change the unpaid amount, not to disguise a credit-limit problem

Shopify documents percentage deposit requirements for B2B as a Shopify Plus feature. A merchant can configure a deposit as part of company or company-location payment terms for checkout-created orders, and can also set a deposit requirement on an individual draft order. The deposit is due up front and the remaining balance follows the payment terms. This gives merchants a native way to reduce the unpaid portion of a specific order without converting the whole account to immediate payment.

That is useful for a newly approved buyer placing an unusually large first order, a project purchase that is far larger than the account's normal replenishment, or an account whose credit policy allows a transaction only when part of the value is prepaid. The commercial rule should be explicit. For example, the business might keep the company's normal net terms but require a deposit on exceptional project orders rather than permanently increasing the account's limit.

Shopify also documents the payment-state behavior. After a deposit is captured, the order becomes Partially paid. If the customer uses a manual payment method for the deposit, the order can remain Payment pending until staff record the payment. These states should be included in the operating checklist so warehouse or sales staff do not read 'deposit requested' as 'deposit received.'

Do not confuse a deposit requirement with later partial payments

A deposit requirement is an agreed up-front condition of the order. Shopify's separate partial-payment feature lets Shopify Plus merchants collect or record multiple partial payments for orders that have payment terms, using a fixed amount or percentage-based amount. After a partial payment is recorded, the order is shown as Partially paid and the payment is reflected in the buyer's customer account.

Those tools can support flexible payment arrangements, but the policy still needs one source of truth. If a $20,000 order requires 25% up front, finance should be able to distinguish the required $5,000 deposit from a later voluntary $2,000 partial payment toward the remaining balance. Otherwise the same 'partially paid' status can represent different commercial situations.

B2B Procurement OS should not be described as the deposit collector or partial-payment processor on the basis of its current public listing. Its verified role here is different: company credit limits, net terms, automatic blocking of over-limit or overdue orders, and approval workflows. Use Shopify's documented payment capabilities for payment collection, and use the procurement layer for the account controls it actually advertises.

Add a company credit limit when unpaid exposure must stop before it grows

A credit limit becomes valuable when staff should not have to reconstruct an account's position from memory every time another buyer places an order. B2B Procurement OS advertises per-company credit limits and automatic blocking for orders that exceed the configured limit. That turns a merchant-defined exposure rule into an ordering control instead of a spreadsheet check performed after the commitment has already moved forward.

Imagine a chain with three purchasing users ordering for the same company. Each cart can look reasonable in isolation while the combined unpaid commitment exceeds what finance intended to carry. A company-level limit addresses the relationship rather than the latest cart. The merchant still owns the policy, including the cap and exception process; the application enforces the configured boundary it advertises.

Do not assume every product calculates 'credit used' from the same set of objects. Open orders, draft orders, invoiced balances, deposits, partial payments, cancellations, and external accounting records can create edge cases. The B2B Procurement OS listing verifies per-company limits and over-limit blocking, but it does not publish every accounting formula behind exposure. Verify your real account scenarios before treating any balance calculation as equivalent to your finance team's internal ledger.

Treat overdue blocking as a second gate, not as a smaller credit cap

An account can be under its credit limit and still violate policy because an earlier invoice is overdue. Shopify surfaces overdue status after payment terms expire. B2B Procurement OS goes further in its current listing by advertising automatic blocking of overdue orders as well as orders above the company limit. These controls solve different failure modes, so keep them separate in policy and reporting.

For example, a company with a $50,000 limit and only $8,000 outstanding may look safe by exposure alone. If that $8,000 is already past due and your policy says no additional credit while overdue, available headroom should not become a loophole. Conversely, a company with no overdue invoices can still exceed its cap through several large orders placed close together.

Define an exception path that does not rely on silently changing permanent settings. A bank transfer might be in transit, an invoice could be disputed, or finance may authorize one urgent release. Record who approved the exception, why, and whether it expires after one order. Raising a permanent limit because sales needs one order to pass is a fragile substitute for an exception workflow.

Route large or unusual orders through approval instead of weakening the credit rule

B2B Procurement OS also advertises multi-level approval workflows with conditional rules based on order amount, with Purchasing, Manager, and CFO as the published example. That matters because a large order can create two independent approval questions. The buyer's organization may need internal authority to spend the amount, while the merchant may need to decide whether to extend the requested credit exposure.

A $4,000 routine restock may stay inside both the buyer's authority and the merchant's account policy. A $40,000 project order can cross an approval threshold, exceed normal exposure, and justify a deposit or another commercial treatment. Do not collapse those decisions into one vague 'approved' status. Keep buyer-side spend approval, merchant credit approval, and payment state understandable to the teams that act on them.

If the order includes a purchase-order reference or requires seller-side draft review, keep those states separate too. ShopRadar's `/blog/shopify-b2b-purchase-order-number-workflow` explains why a PO number is a reference, not universal proof of buyer authorization, while `/blog/shopify-b2b-order-approval-workflow` separates buyer procurement approval from merchant review.

Pilot the policy with scenarios that expose false assumptions

Before enabling hard blocks broadly, choose accounts that represent the uncomfortable edges: a new customer placing a large first order, a reliable high-volume buyer near its limit, a company with several purchasing users, an account with a payment in transit, and a project buyer that needs a deposit. For each case, write the due term, deposit rule if any, merchant-defined credit cap, overdue treatment, and named exception owner. Then walk through what should happen before anyone changes production settings.

Include payment-state scenarios. Confirm how staff will interpret Payment pending, Partially paid, Due, and Overdue in the workflows you use. Shopify's native states describe payment progress; your credit policy still decides whether another order may proceed. If a partial payment changes how finance wants exposure understood, verify that interpretation against the tools involved rather than assuming the application and the ledger use the same formula.

As verified on September 15, 2026, the official Shopify App Store listing shows B2B Procurement OS Starter at $79 per month, Growth at $199, and Enterprise at $499, each with a 14-day free trial. B2B Procurement OS is available in English. Choose it when you need the documented combination of company credit limits, overdue blocking, and procurement approvals. Stay with Shopify's native terms and deposit tools when payment scheduling and collection mechanics are the whole problem.

• Due date: use the appropriate Shopify B2B payment term for when money is owed.
• Deposit: on eligible Shopify Plus setups, use it to reduce the unpaid portion of a specific order.
• Credit limit: define the maximum unpaid exposure your business is prepared to carry for the company.
• Overdue hold: decide whether any past-due balance blocks additional credit orders even below the cap.
• Approval: route exceptional spend or credit decisions to an identified approver instead of weakening permanent policy.
• Reconciliation: verify how deposits, partial payments, drafts, cancellations, and external accounting records affect the exposure view you rely on.

Apps mentioned in this guide

Frequently asked

What is the difference between Shopify B2B net terms and a credit limit?

Net terms define when payment becomes due, such as net 30. A credit limit is the merchant's cap on unpaid exposure for an account. A buyer can be within its due date and still exceed the merchant's credit cap, or remain below the cap while having an overdue invoice.

Which net terms does Shopify B2B support?

Shopify currently documents net 7, 15, 30, 45, 60, and 90, plus due on fulfillment. Fixed-date terms are available for individual draft orders.

Can Shopify B2B require a deposit?

Yes, on Shopify Plus. Shopify documents percentage deposit requirements as part of B2B payment terms for company or company-location checkout orders and for individual draft orders. The deposit is due up front and the remaining balance follows the payment terms.

Does Shopify automatically charge a B2B customer when net terms expire?

No. Shopify's current documentation says payment is not automatically captured merely because the term expires. The order becomes overdue and collection follows the applicable payment workflow.

Does B2B Procurement OS collect deposits or process partial payments?

That capability is not verified in its current public Shopify App Store listing. The listing explicitly advertises per-company credit limits, net terms that block over-limit or overdue orders, multi-level approvals, quote and reorder workflows, and controlled editing of unfulfilled orders. Use Shopify's documented payment features for deposits and partial payments unless you separately verify another payment capability.

Is B2B Procurement OS available in English?

Yes. B2B Procurement OS is available in English. ShopRadar's promotional CTA uses the authentic b2b-procurement-os App Store slug with locale=en; that selects the English listing view and does not change installed-app language settings.