> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/excellar-commission.md).

# Excellar & Commission

Step-by-step guides for Bevica Excellar (direct ship) and Commission workflows in Business Central. Use the process that matches your order type. Requires Bevica Essentials.

Use this section to find the process guides for Excellar and Commission workflows.

<a class="button primary" data-icon="microsoft">Requires: Bevica Essentials extension to be installed</a>

{% hint style="info" %}
Bevica Excellar & Commission is a separate extension. Please contact your system administrator or your TVT contact if you would like further information or would like to install Bevica Excellar & Commission.
{% endhint %}

### Summary

* This area contains the step-by-step order processing guides for Excellar and Commission.
* Use the guide that matches your order type and fulfilment method.

### Next steps

1. Open the guide you need:
   * [Bevica Excellar Order Processing](https://kb.bevica.com/documentation/guides/excellar-commission/bevica_excellar_order_processing.md)
   * [Bevica Commission Order Processing](https://kb.bevica.com/documentation/guides/excellar-commission/bevica_commission_order_processing.md)
   * [Drop Shipment (Excellar) Order Processing](https://kb.bevica.com/documentation/guides/excellar-commission/drop_shipment_-excellar-_order_processing.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://kb.bevica.com/documentation/guides/excellar-commission.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.
