Shopify B2B Payment Terms: What to Define Before Offering Net 30

Offering Net 30 in Shopify is easy to configure. Deciding who should receive it, when an order can ship, and how finance will collect the balance is the real work.

A merchant can assign payment terms to a B2B company location, let the buyer place an order without paying the full balance at checkout, and show a due date in the customer account. That looks complete inside the admin. It is not complete if the credit decision lives in a spreadsheet, the warehouse releases every unpaid order, the accounting platform calculates a different due date, or nobody owns overdue follow-up.

Shopify B2B payment terms should be treated as an operating policy expressed through the store. Before offering Net 30, define the buyer, order, payment, fulfillment, finance, and exception rules that make the term safe to use.

Configuration is not a credit policy

Shopify documents Net 7, Net 15, Net 30, Net 45, Net 60, Net 90, due on fulfillment, and fixed-date terms for supported B2B order paths. Selecting one of those options answers when Shopify should display payment as due. It does not decide whether a buyer is creditworthy, how much open exposure the business will accept, or what happens when an account becomes overdue.

Write the commercial policy before the Shopify rule. At minimum, define:

• Which buyer types can request terms and who approves a new account.
• Whether approval applies to a whole company or a specific company location.
• The maximum open balance or order value the team will accept.
• Which payment methods can be used for deposits and final balances.
• Whether orders can enter fulfillment before payment.
• What happens when invoices are overdue, disputed, partially paid, or changed.
• Who can suspend, shorten, extend, or restore terms.

The policy does not need to be complicated. It needs to be explicit enough that sales, ecommerce, finance, customer service, and fulfillment make the same decision when the normal path breaks.

Assign terms at the right company location

Shopify B2B separates a company, its locations, and the individual customers associated with those locations. Shopify's payment-term guidance allows terms to be set for a company location, across a company, or on an individual draft order.

That scope matters. A parent company can have one location that pays centrally, another that must pay at checkout, and a third that needs order review before approval. Applying one bulk rule without checking those differences can create unintended credit or block a buyer who should have access.

Build a location-level term record with the commercial account owner, approved term, effective date, review date, payment method, deposit rule, tax and billing contact, invoice destination, fulfillment rule, and any exception. Keep the source decision outside a free-form note that nobody can report on later.

Then test identity. Shopify's B2B considerations require the customer to be associated with a company location when the order is placed so the correct B2B context applies. A buyer using the wrong login, location, or draft-order path can therefore receive the wrong prices, checkout options, or terms even when the company record itself looks correct.

Define when the due-date clock starts

Net 30 sounds universal, but teams often mean different things by it. One person means 30 days after the order. Another means 30 days after shipment. Finance may mean 30 days after the invoice is issued or received.

Shopify states that its Net periods start on the day the order is placed. Due on fulfillment is a separate term, and fixed dates can be applied to individual draft orders. That distinction should appear in the commercial agreement, invoice, customer account, accounting system, and collections queue.

• Name the event that starts the clock and the time zone used for the due date.
• Decide how weekends, holidays, partial fulfillment, edits, returns, and credits affect follow-up.
• Name the system that owns the final due date when Shopify and accounting disagree.
• Show the term before order submission and repeat it on the order and invoice.

Do not let the buyer learn the definition from an overdue notice.

Separate payment terms from payment methods

Payment terms describe when money is due. Payment methods describe how the buyer will pay. Combining those decisions creates avoidable exceptions.

Shopify's B2B checkout guidance covers card, manual, and other supported payment paths alongside terms, deposits, vaulted payment methods, draft orders, and invoices. Map the allowed combinations before launch. A buyer might have Net 30 with bank payment, Net 15 with a vaulted card, immediate card payment for a special order, or a deposit followed by a manual balance payment.

For every combination, decide who initiates collection, where remittance instructions appear, how a manual payment is recorded, what reference finance needs, and what state allows fulfillment. Shopify's payment-term documentation notes that balances are not automatically captured merely because the term expires.

That leaves an owner decision. If finance must capture or record payment, the work needs a queue, a schedule, evidence, and an escalation path. If the buyer pays through the customer account, the team still needs to reconcile the payment against the correct order and accounting record.

Use deposits and order review deliberately

A deposit can reduce exposure, but it also adds another payment state. Shopify supports percentage deposits for eligible B2B configurations and draft-order paths, with the remaining balance due according to the selected terms. Shopify also distinguishes orders that are submitted as drafts for merchant review.

Decide which problem the deposit solves. It may protect a custom production run, reserve scarce inventory, cover freight, or create a commitment before a large order enters fulfillment. If the team cannot explain the reason, a deposit can become a random checkout difference between accounts.

• Which company locations or order types require a deposit.
• Whether the deposit is calculated before or after discounts, shipping, and tax.
• What happens when the order changes after the deposit is paid.
• Whether fulfillment can begin after the deposit or only after internal review.
• How cancellations, returns, and credits affect the deposit.
• Which invoice and notification templates show the amount due now and later.

Shopify warns that merchants with customized draft-order invoice templates may need to update them so deposit information appears correctly. Treat that as a launch test. The buyer should see the same amount and due date at checkout, on the invoice, in the customer account, and in any finance communication.

Tie fulfillment release to the commercial decision

An unpaid B2B order can be valid. It can also be an order that should not ship yet.

Create a release matrix before connecting Shopify to a warehouse, ERP, or 3PL. A prepaid order may release immediately. An approved Net 30 account may release when the order passes fraud, inventory, and order-review checks. A high-value order may need a deposit. An overdue account may require finance approval. A draft order may need a salesperson to confirm products, pricing, freight, or a purchase-order reference.

The integration should transmit the payment state, term, due date, deposit state, review state, company location, and stable order identifiers needed for that decision. Do not make the warehouse infer release from a generic unpaid status.

This is especially important for due-on-fulfillment terms. Shopify's B2B considerations documents manual-capture conditions for certain B2B and due-on-fulfillment orders. Test the complete sequence: order acceptance, fulfillment creation, partial fulfillment, final fulfillment, capture or invoice action, buyer visibility, and accounting readback.

Reconcile Shopify with accounting and ERP systems

Shopify can own the storefront term while another system owns accounts receivable. That split is workable only when both systems agree on the account, order, invoice, payment, credit, and due date.

• Map Shopify company, company-location, order, draft-order, and buyer identifiers.
• Carry purchase-order and invoice references into the finance record.
• Reconcile original amount, deposit, payments, credits, refunds, and balance.
• Assign one source of truth for term type, due date, fulfillment state, and payment state.
• Decide how changes flow between Shopify and accounting without creating duplicate receipts.

Reconciliation should compare individual orders and balances, not only daily totals. A total can match while one invoice is duplicated and another is missing.

Build the collections workflow before the first invoice is late

Shopify lets buyers view and pay eligible orders through customer accounts, and overdue orders remain payable. The platform state is useful, but it is not a collections operating model.

Define what happens before, on, and after the due date. Decide when reminders are sent, which channel they use, who receives them, when the account owner is notified, when new orders are held, and who can grant an exception. Keep service disputes separate from simple late payment so a legitimate fulfillment issue does not receive the same message as an ignored invoice.

Use a small set of clear states such as due soon, due today, overdue, disputed, promised, partially paid, on hold, and escalated. Every state should have one owner and one next action. If Shopify, accounting, and the CRM use different labels, map them rather than asking the team to interpret them manually.

Test the buyer and internal experience together

Payment-term QA is not complete when a test order shows Net 30 at checkout. The buyer, ecommerce team, sales owner, finance team, support team, and fulfillment partner each see a different part of the order.

• Two locations under one company with different terms.
• An approved Net 30 buyer paying early through the customer account.
• A buyer using a vaulted card where collection still needs an internal action.
• An order with a required deposit or submitted as a draft for review.
• A partial fulfillment under due-on-fulfillment terms.
• An order edited, returned, credited, or cancelled after its due date is created.
• An overdue account attempting another order.
• A manual payment recorded in Shopify and accounting.
• A buyer linked to the wrong company location.

For each case, compare checkout, thank-you page, order, invoice, customer account, admin payment state, fulfillment release, integration payload, accounting record, reminder workflow, and support view. The test passes only when the amounts, dates, identifiers, owners, and next actions agree.

Launch with a payment-term control report

The first launch report should make exceptions visible. Review open balance by company location, orders without the expected term, deposits not reconciled, orders released while on hold, due dates that differ between systems, overdue balances without an owner, manual payments waiting to sync, and buyers whose account context did not apply.

Review the report daily during launch, then move to a cadence that matches order volume and risk. Sample buyer-facing invoices and customer-account pages as well as backend rows. A clean integration log does not prove that the buyer saw the right balance or that finance can collect it.

The goal is not zero exceptions. The goal is to see each exception early, route it to the right owner, and prevent the same rule from failing repeatedly.

Where Lake House Group fits

Lake House Group treats Shopify B2B payment terms as part of the commerce operating layer. We connect company data, checkout, order review, payment state, fulfillment, accounting, customer accounts, and team ownership so Net terms work beyond the setting screen.

If your wholesale operation is moving to Shopify or replacing a manual B2B order process, talk to Lake House Group about Shopify migration and unified Shopify operations.

Related reading:

• Shopify B2B Customer Portal: What to Test Before Buyers Self-Serve
• Shopify B2B 3PL Integration: What to Define Before Wholesale Orders Ship
• Shopify B2B Unified Commerce: What to Decide Before Wholesale and Retail Share One Store
• Shopify Order Automation: What to Define Before Connecting a 3PL and Klaviyo