> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chap-6-system-configuration/backup/copy-item-config.-by-revenue-center.md).

# Copy Item Config. by Revenue Center

### Copy Item Config. by Revenue Center

The Copy Item Config by Revenue Center option allows to rapidly recreate the same configurations in all modes of another revenue center once you have manually setup the configurations for all modes of all sales items of a first revenue center. This option is useful to program a new revenue center, such as creating a To GO revenue center from a Dining Room revenue center, and then modify the target revenue center to change a few items, such as replacing fountain soda by soda cans, for example. The Back-Office copies the sales items configuration only.

**From Revenue Center**

Select the source revenue center from which you want to copy the configuration.

**To Revenue Center**

Select the destination revenue center where you want the previously selected configuration to be copied.

{% hint style="info" %}
NOTE: If you choose a source revenue center that has more modes than the target revenue center, the existing mode(s) will be copied to, but no new mode will be added to the destination revenue center.
{% endhint %}

**Replace Existing:**

Enable this option to overwrite an existing revenue center and its mode(s) with the previously selected configuration in addition to creating new configurations for empty sales items and modes.

**OK**


---

# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chap-6-system-configuration/backup/copy-item-config.-by-revenue-center.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.