> For the complete documentation index, see [llms.txt](https://docs.b2b-sellers.com/b2b-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2b-sellers.com/b2b-platform/user-guide/available-add-ons/order-lists.md).

# Order Lists

Order templates and product lists for professional procurement

While similar to "wish lists" in B2C, the B2Bsellers Suite provides order lists (also known as order templates or product lists) specifically designed for professional procurement.

Order list functionality is included with your Core license but must be installed via the standalone **B2bProductLists** plugin.

## User experience & interface

Logged-in B2B customers see an **Add to order list** button on both the product listing boxes and the item detail pages.

* **Contextual status:** a dropdown displays all existing lists. If a product is already assigned to a list, it is marked with a green checkmark.
* **Quick actions:** users can create new lists directly from the product page.
* **Navigation:** order lists are accessible via a dedicated icon in the header or through the B2B Platform navigation menu.

See [Order Lists as an Employee](/b2b-platform/user-guide/using-the-b2b-platform/customer-portal/order-lists-as-an-employee.md) for the full walkthrough from the buyer's perspective.

## Standard list types

The system provides several default list types out of the box:

* **My assortment:** for frequently required products.
* **Default:** a general-purpose notepad.
* **Cart history:** automatically captures items placed in the cart.
* **Sales representative lists:** templates curated by sales staff for their customers.

## Key features

* **Company-wide sharing:** lists can be kept private or shared across the entire company.
* **Intelligent automation:** lists can be populated automatically based on triggers, such as items left in a cart or products ordered repeatedly.
* **Item-level detail:** customers can add custom comments to specific items within a list.
* **Efficient procurement:** users can search within lists and move individual items or entire lists into the shopping cart with one click.
* **Role-based management:** deletion and editing rights are controlled by the customer's permissions and the plugin configuration.

![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/3Nr3m6nIeMZSS5R3i9Eq/Produktlists.png)

## Admin configuration

The settings are found under **Extensions > My Extensions > B2bProductLists > Configuration**.

### Basic configuration

| Setting                                                                                        | Meaning                                                                              |
| ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Show all connected customer order lists for employees                                          | Whether an employee sees the order lists of all customers they are connected to.     |
| Which types of product lists should the unauthenticated and logged-in customer be able to see? | The list types visible to visitors who are not logged in and to logged-in employees. |
| Hide automatically generated order lists by default                                            | Hides the lists created by the automation rules until the filter is changed.         |
| Which types is from Customer deleteable?                                                       | The list types a customer or their employees are allowed to delete.                  |
| Default List-Type, if not filled?                                                              | The type used for a new order list when none is specified.                           |
| Default order list name                                                                        | The name a new list uses by default, for example "My order list".                    |
| On which types can the customer delete products from the list?                                 | The list types from which customers may remove individual products.                  |

{% hint style="info" %}
If lists may be created without being logged in, those lists are only stored in the browser session rather than on the customer, so they can be gone on the next visit.
{% endhint %}

### Automatic product lists

| Setting                                                                        | Meaning                                                            |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------ |
| Create "my ordered products" list after order submit                           | Maintains a list of everything the customer has ordered.           |
| Default list type for "my ordered products"                                    | The type used for that list.                                       |
| Create add-to-cart products in an own product list                             | Captures products that were placed in the cart.                    |
| Default list type for cart products                                            | The type used for that list.                                       |
| Create frequently ordered product list                                         | Maintains a list of products ordered repeatedly.                   |
| Default list type for frequently ordered products                              | The type used for that list.                                       |
| Define how often a product should be ordered for the "frequently ordered" list | The threshold at which a product is considered frequently ordered. |

{% hint style="info" %}
Automatically created order lists are named in the language of the user who triggered them. The name is not updated when a different language is used later.
{% endhint %}

## Technical details

The frontend implementation adapts to the user type:

* **Standard users:** powered by vanilla JavaScript for lightweight performance.
* **B2B Platform users:** built on Vue.js, offering a reactive application experience within the platform.

### Price calculation & performance

To ensure fast load times, order lists display an estimated price. This prevents the system from calculating complex B2B pricing rules for every single item in a large list simultaneously.

* **Automatic updates:** prices are recalculated once per day via a scheduled task.
* **Manual update:** you can force a recalculation for a specific customer and sales channel:

```bash
bin/console b2b:product-lists:calculate <customerId> <salesChannelId>
```

![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/litBHGO4aFZz6CAaGJyN/image.png)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.b2b-sellers.com/b2b-platform/user-guide/available-add-ons/order-lists.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.