> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/pos-integrations/foodics/enabling-price-tags-on-foodics-aggregator-specific-pricing.md).

# Enabling Price Tags on Foodics- Aggregator-Specific Pricing

The **Price Tags** feature in Foodics allows restaurants to assign **different prices for the same product** based on the delivery channel, without duplicating the item. This is especially helpful when pricing needs to vary between channels such as **Talabat**, **Careem, etc.**

***

**How to Create and Apply Price Tags in Foodics**

Follow the steps below to configure price tags:

1. **Login to the Foodics Web Console**.
2. Navigate to **Manage > More > Price Tags**.
3. Click on **Create Price Tag**.

A pop-up window will appear with the following fields:

* **Name**: Enter the price tag name (e.g., *Talabat*, *Zomato*, etc.).
* **Order Tags (Optional)**: Link an order tag if needed.
* **Branches**: Choose whether this pricing applies to **all branches** or only specific ones.

4. Click on **Save**.

***

**Adding Products to a Price Tag**

Once the price tag is created, you can apply it to products as follows:

5. Click on the created **Price Tag**.
6. Click on **Add Products**.
7. Select the relevant product(s) from the list.
8. Click **Save**.

Now, the selected products will reflect the pricing defined under this tag when orders are placed through the corresponding delivery channel integrated via **UrbanPiper**.

{% hint style="info" %}
This setup is ideal for managing pricing strategies across various platforms while maintaining a unified product database in Foodics.
{% endhint %}


---

# 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://help.urbanpiper.com/pos-integrations/foodics/enabling-price-tags-on-foodics-aggregator-specific-pricing.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.