> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/samita-wholesale-b2b/add-on-features/create-payment-term-for-your-b2b-customers/set-priority-between-payment-term-and-invoice-payment-at-cart.md).

# Set Priority between Payment Term and Invoice Payment at Cart

Since Payment Term and Invoice Payment share the same **Pay Later** button in the cart, you need to tell the app what to do when both could apply to the same order.

*Example: you've set up both Payment Term and Invoice Payment to apply to customers tagged "wholesale," and every product in your store qualifies for both.*

## Steps to manage

{% stepper %}
{% step %}

### Open Payment term settings

Go to **Add-on Features > Payment term**, then click **Settings**.
{% endstep %}

{% step %}

### Choose what happens after "Pay Later"

Under **After clicking "Pay Later"**, choose one of the 3 options:

* **Prioritize Payment Terms** — automatically select Payment Terms when both options are available.
* **Prioritize Invoice Payments** — automatically select Invoice Payments when both options are available.
* **Let customer choose** — show a popup for customers to select their preferred payment method.

Check the **Preview** panel on the right to see how the **Pay later** button behaves.

<figure><img src="/files/fDCDNu1oYvNfi0W0RqAe" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
A draft order is created whenever a customer clicks **Pay Later** — its details depend on which feature (Payment Term or Invoice Payment) was active at that moment.
{% endhint %}

You can also set the **Button style** (matching your checkout button by default) and add **Custom CSS** on this same settings page.


---

# 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.samita.io/samita-wholesale-b2b/add-on-features/create-payment-term-for-your-b2b-customers/set-priority-between-payment-term-and-invoice-payment-at-cart.md?ask=<question>&goal=<endgoal>
```

`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.