> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/trade-and-b2b/checkout-and-payment/setting-up-payment-terms-for-your-b2b-retailers.md).
# Setting up payment terms for your B2B retailers
Configure Shopify B2B payment terms at the company location level, and match each retailer relationship to the right term type.
Last verified against Shopify: April 21, 2026
This article explains how Shopify B2B payment terms work, how to assign them to a company location, and how Roadmap recommends matching each retailer to the right term.
Shopify documents company level payment terms in its [B2B payment terms guide](https://help.shopify.com/en/manual/b2b/checkout-and-orders/payment-terms).
Shopify documents order level deferred payment terms in its [deferred payments guide](https://help.shopify.com/en/manual/fulfillment/managing-orders/payments/deferred-payments).
### What payment terms do at checkout
Payment terms decide when the retailer needs to pay for an order.
When a company location uses `Automatically submit orders`, payment terms become the main trust control.
This is why Roadmap recommends choosing your order submission mode first. Use [Choosing your B2B company checkout settings](/trade-and-b2b/checkout-and-payment/choosing-your-b2b-company-checkout-settings.md) if you have not set that yet.
### Company location payment term options
At the company location level, Shopify supports these payment terms:
* `No payment terms`
* `Due on fulfillment`
* `Net 7`
* `Net 15`
* `Net 30`
* `Net 45`
* `Net 60`
* `Net 90`
These terms apply to every order from that company location unless you override them on a specific order.
### Match the term to the retailer relationship
Roadmap recommends keeping this simple.
#### New account
Use `Due on fulfillment`.
This lets the retailer place the order, while still requiring payment before stock ships.
#### Established account
Use `Net 7` or `Net 15`.
This suits retailers who order regularly, but do not yet need long dated credit.
#### High trust account
Use `Net 30`.
This is a common default for mature wholesale relationships.
#### Strategic account
Use `Net 45`, `Net 60`, or `Net 90` only when the commercial agreement clearly supports it.
Longer terms should be deliberate. They should not be your default.
{% hint style="info" %}
Roadmap treats payment terms as the cleanest way to express trust.
They scale better than manual draft review.
{% endhint %}
### How to set payment terms on a company location
{% stepper %}
{% step %}
#### Open the company
In Shopify, go to `Customers → Companies`.
{% endstep %}
{% step %}
#### Open the company location
Open the company, then open the company location you want to update.
{% endstep %}
{% step %}
#### Find the payment terms setting
Open the part of the company location record that controls payment terms.
{% endstep %}
{% step %}
#### Choose the default term
Select the payment term you want that location to use for new orders.
{% endstep %}
{% step %}
#### Save and test
Save the change, place a test order, and confirm the order shows the expected due date.
{% endstep %}
{% endstepper %}
### How payment terms affect invoices and collection
The company location term becomes the default payment expectation for new orders.
That due date then carries through the order record and payment collection flow.
In practice, this means you can let the order submit normally while still controlling when payment is due.
This is the key difference from draft review. Draft review blocks order creation. Payment terms control the commercial timing instead.
### When to use order level overrides
Use an order level override when one order needs a different due date from the company default.
This is useful when:
* a single order needs faster payment
* a one off order needs longer credit
* you need a specific fixed date for that order
At the order level, Shopify supports:
* `Due on receipt`
* `Due on fulfillment`
* `Within 7`, `Within 15`, `Within 30`, `Within 45`, `Within 60`, `Within 90 days`
* `Fixed date`
`Fixed date` is only available at the order level. It is not available as a company location default.
That matters for custom terms such as `20th of the month following`. Use [Handling custom payment terms like "20th of the month following"](/trade-and-b2b/checkout-and-payment/handling-custom-payment-terms-like-20th-of-the-month-following.md) for that workflow.
### Related articles
* [Choosing your B2B company checkout settings](/trade-and-b2b/checkout-and-payment/choosing-your-b2b-company-checkout-settings.md), for the order flow Roadmap recommends before you assign terms.
* [Handling custom payment terms like "20th of the month following"](/trade-and-b2b/checkout-and-payment/handling-custom-payment-terms-like-20th-of-the-month-following.md), for terms that do not fit Shopify's native `Net` options.
* [Troubleshooting "Your order cannot be shipped to the selected address" at B2B checkout](/trade-and-b2b/shipping/troubleshooting-your-order-cannot-be-shipped-to-the-selected-address-at-b2b-checkout.md), for the checkout issue that often pushes merchants away from draft review and towards payment terms.
Need a hand? Contact us in the Roadmap app via Intercom.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.roadmap.so/trade-and-b2b/checkout-and-payment/setting-up-payment-terms-for-your-b2b-retailers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
