Shopify Payment Terms, Net Terms and B2B Credit.

How Shopify B2B issues credit: term types, where they attach, vaulted payment methods, deposits, and what happens after the due date passes.

Shopify's native B2B suite handles the credit side of wholesale through payment terms templates: the buyer checks out without paying, the order sits at Payment pending, and the merchant collects later. The templates cover the common cases well, and they run on all plans. What they do not cover is collection itself. Shopify charges no one automatically when terms expire, tracks no credit exposure, and settles invoices one order at a time. This chapter walks through both halves: what the native terms engine does, and where the accounts receivable work moves back onto your team.

What payment terms does Shopify B2B support?

Shopify defines five term types. Each changes when payment is due and how checkout behaves.

The net menu is fixed. Net 7, 15, 30, 45, 60, and 90 are the only periods offered; there is no custom net period, so net 10 or net 120 is not an option in the template list. The Admin API exposes the same model through the PaymentTermsType enum: NET, RECEIPT, FULFILLMENT, and FIXED.

Plan availability is broader than most merchants expect. Per Shopify's plan feature matrix, most B2B features run on all plans, including companies, catalogs, net payment terms, and self-serve ordering. Deposits, partial payments, and per-fulfillment payment requests require Shopify Plus.

How do you enable net terms for B2B customers?

Terms are assigned, not requested. Per the payment terms documentation, a merchant attaches a terms template at any of four levels:

• An individual company location, so each ship-to can carry its own terms
• An entire company, which applies the template to all of its locations
• An individual draft order, which overrides the standing setting for that order
• Many companies at once, via bulk edit

Via the API, you pass buyerExperienceConfiguration.paymentTermsTemplateId to the companyLocationUpdate mutation. Draft orders inherit automatically: when a draft order has a B2B customer and a company location assigned, prices, payment terms, and checkout options reflect that company's settings.

Terms can also be set dynamically at checkout. The Payment Customization API's paymentTermsSet operation lets a Shopify Function apply net, fixed, or event-based terms per checkout, with an optional deposit; Shopify's own example collects a 50 percent deposit when the cart passes a 500 dollar threshold.

What does checkout look like with payment terms?

Checkout behavior follows the terms on the buyer's company location. With no terms, the buyer enters a card and clicks Pay now. With net terms, the buyer clicks Submit instead, and the order is created with payment status Payment pending: no money moves. With net terms plus a deposit, the buyer pays the deposit immediately and the balance sits at Payment pending. B2B customers can also enter a purchase order number at checkout, and buyers with terms can pay early at any time by logging in to customer accounts and clicking Pay now. The full flow is covered in the B2B checkout chapter.

How do vaulted credit cards and bank accounts work?

Vaulted payment methods are the bridge between issuing terms and actually getting paid. Per the vaulted cards documentation, card vaulting requires Shopify Payments, and only B2B customers can vault a card: either a checkbox at checkout or by adding a card to a company location from customer accounts. The card belongs to the company location, so every customer with permissions for that location can use it at checkout. Merchants can view vaulted cards, manually charge one against a pending-payment order, and delete cards, but cannot vault a card on the customer's behalf.

US merchants on Shopify Payments can additionally let B2B customers vault US bank accounts for ACH debit. An authorization mandate from the customer is required, charging requires a specific staff permission, and, critically, vaulted bank accounts are not automatically debited when payment terms expire.

Automation exists, but you assemble it: a Shopify Flow workflow with the trigger Payment schedule is due and the action Charge vaulted payment for B2B order can charge a vaulted card when terms come due. That is the closest native path to automatic collection, and it only works for buyers who vaulted a card.

Can Shopify collect deposits and partial payments?

Yes, on Shopify Plus. A deposit is a percentage collected upfront at checkout or on a draft order invoice; the percentage applies to the order subtotal only, excluding taxes and shipping, and the remaining balance follows the payment terms. Partial payments are merchant-initiated: on an order with terms, staff can collect or record a fixed amount or percentage, moving the order to Partially paid. Recorded manual payments are bookkeeping entries; Shopify does not capture them. For due-on-fulfillment orders that ship in multiple fulfillments, Plus merchants can send a payment request per fulfillment.

What happens when a B2B invoice comes due?

Very little, natively. Per the deferred payments documentation, if payment is not received by the due date, the order status becomes Overdue. The order remains payable, and nothing is charged. Merchants can schedule up to five payment reminder emails, sent on the due date or up to 30 days after it, never before it. For anything beyond that, you build it yourself: the API exposes PaymentTerms.overdue, nextDueAt, and paymentSchedules, plus the payment_schedules/due webhook topic, so an app or workflow can react to due dates programmatically.

The collection gap: what Shopify payment terms do not do

Everything above issues credit. Almost none of it collects. This is the single most important thing to understand before turning net terms on for real wholesale volume.

No credit limits

Shopify B2B has no credit limit field on companies or company locations, no running exposure total, and no mechanism to block a new order when an account's open balance crosses a ceiling. Shopify's own admin extension docs list displaying real-time credit limits and outstanding balances as a third-party app use case. Company-location store credit exists as of late 2025, but it is a prepaid balance, not a credit line: it cannot represent money a buyer owes you.

No batch invoice payment

Every native collection surface operates per order. The buyer's Pay now button pays one order. The admin's Collect payment action collects one order. The Flow action charges one B2B order. Shopify documentation describes no way for a buyer to settle multiple open invoices in a single transaction, so a customer with fifteen open invoices makes fifteen separate payments, and your finance team reconciles fifteen separate deposits. For wholesale accounts that order weekly, this is the constraint merchants hit first. The gap and its fix are covered in batch invoice payments for Shopify B2B.

No automatic collection

Shopify states it directly: payments are not automatically captured when the payment terms expire. On B2B checkouts, automatic capture on fulfillment events is not supported either, even though D2C checkouts support it. The due date changes a status; a human, or automation you build, moves the money.

These constraints sit alongside the rest of the platform's edges in the constraints ledger.

Where B2B Supercharge fits

The Payments module of B2B Supercharge takes over where the native terms engine stops. Buyers see every open invoice in one place and pay any number of them in a single transaction, including partial amounts against a specific invoice. Balances roll into aging buckets automatically as they pass due, and each batch payment splits back to its invoices and posts to your AR ledger with remittance attached. Paired with the ERP and CRM Integrations module, remittance lands in Dynamics 365, NetSuite, or Sage without a manual row.

Native terms decide when payment is due. The Payments module handles what happens next: see how batch invoice payment works.

Frequently asked questions