> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-installation-and-setup/maitred-installation-guide/license-activation/auxiliary-back-office-before-activating-the-license.md).

# Auxiliary Back-Office - Before activating the license

## Maitre'D Auxiliary Back-Office License Activation

### Before activating the license

Before the license can be activated, you need:

#### License Serial Number

When activating an Auxiliary Back-Office, the serial number to use is the same as the Main Back-Office. The Auxiliary back-Office is an option that can be purchased through the same channels as new licenses and license add-ons.

{% hint style="info" %}
NOTE: Please note that there is a turnaround time of 4 hours for all orders and that new licenses are only created during normal business hours. The License serial number can be found on the invoice received after the creation of the license.
{% endhint %}

#### Commerce Name

When activating an Auxiliary Back-Office, the Main Back-Office should already be up-and-running, therefore the commerce name is already established and can no longer be changed.

Obtain the commerce name from printed guest checks or receipts, or by looking up the license details on the Main Back-Office PC.


---

# 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.maitredpos.com/maitred/maitred-installation-and-setup/maitred-installation-guide/license-activation/auxiliary-back-office-before-activating-the-license.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.