> 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/online-ordering/online-ordering/inventory/clone-inventory.md).

# Clone inventory

***Clone inventory*** allows you to copy the entire inventory from one branch to another within the same company.

### Clone an inventory

1. To access the ***Clone inventory*** page, go to the branch management page for the desired company and click ***Clone Inventory*** in the ***Admin*** tab of the navigation bar.
2. In the ***To copy to*** field, select the branch office that will receive the copied inventory.
3. In the ***From*** field, select the branch that has the inventory to copy.
4. Click ***Copy*** to clone the inventory of the desired branch.

#### Related Articles

Combos

Combos are made up of one or more choice products. A choice product must be selec...

Choice products

Choice products are additional products or ingredients with which a product must ...

Menu display

The menu display is a tool for changing the order and visibility of categories an...

Modifiers groups

Modifiers groups are associations of different modifiers under the same group. Th...


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maitredpos.com/online-ordering/online-ordering/inventory/clone-inventory.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 `build a script that syncs our docs to a CMS` 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.
