> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/2ba.md).

# 2BA

Understand what 2BA adds, when to activate it, and where to continue with setup.

**2BA** helps you search technical products, supplier information, stock, and prices directly in OutSmart.

Use this section to understand what the feature adds and when to enable it.

Use the connected [**2BA setup and use**](/marketplace-packages-and-power-ups/power-ups/2ba/2ba-setup-and-use.md) for configuration and daily use.

{% hint style="info" %}
**2BA** is available on **Maximize** and included there.

You need an active **2BA account** to use it.
{% endhint %}

### In this guide

* [**Introduction to 2BA**](/marketplace-packages-and-power-ups/power-ups/2ba/introduction-to-2ba.md)
* [**Activate 2BA through the License Manager**](/marketplace-packages-and-power-ups/power-ups/2ba/activate-2ba-through-the-license-manager.md)
* [**2BA setup and use**](/marketplace-packages-and-power-ups/power-ups/2ba/2ba-setup-and-use.md)

### What you do with 2BA

* search products outside your own item database
* compare suppliers, stock, and prices
* import product data into calculations, quotations, and invoices

### Important to know before you start

* You activate 2BA through the **License Manager**.
* 2BA is available on **Maximize**.
* Then you configure your **2BA username** and **password**.
* Searching in 2BA works from **3 characters** onward.
* The search flow is the same in **calculations**, **quotations**, and **invoices**.
* The 2BA integration currently **requires OCS**. It cannot be used without OCS, even if you only want to work with gross prices.

{% hint style="warning" %}
At the moment, the 2BA pricing endpoint requires **OCS**. As a result, the 2BA integration cannot currently be used without OCS, even if you only intend to work with gross prices.
{% endhint %}

### Webinar

Prefer to follow the process visually? Watch the webinar about 2BA.

{% embed url="<https://youtu.be/zDWKvRRoQ3w>" %}

### Related topics

* [**2BA setup and use**](/marketplace-packages-and-power-ups/power-ups/2ba/2ba-setup-and-use.md)
* [**OutSmart packages**](/marketplace-packages-and-power-ups/marketplace/outsmart-packages.md)
* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.md)
* [**OutSmart Marketplace**](/marketplace-packages-and-power-ups/marketplace.md)


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/2ba.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.