> 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/business-manager/configuring-differential-pricing-for-aggregators/menu-v2.md).

# Menu V2

In Menu V2, differential pricing is managed through **rules**. You can set it in two ways:

1. Push the menu from your POS, or pull it from Atlas. Rules are created automatically.
2. Edit rules directly on Atlas.

## Method 1: Push from the POS or Pull from Atlas

Use this method if your menu reaches UrbanPiper from your POS. The push is done from the POS and the pull is done from Atlas (UrbanPiper). Atlas creates rules automatically from the data in the payload.

### How it works

* In either method, make sure the payload follows the API documentation, so that the rules are created correctly: [Add or update menu](https://api-docs.urbanpiper.com/downstream/api/endpoints/menu/add-update-menu).
* Rules are created automatically based on the conditions in the pushed data. For example:
  * If a particular location is not associated to the item, a rule is created saying do not sell that item at that location.
  * If an item's price for one aggregator differs from the others, a rule is created for that difference, so that the item is sold on that aggregator at a different price than the default.

### Steps

**Step 1: Push or pull the menu**

Push the menu from your POS, or pull it from Atlas, following the API documentation.

**Step 2: Review the rules**

1. Log in to **Atlas**.
2. Go to **Menu** and open the menu.
3. Open the **Rules** tab.

The **Rules** tab lists every rule on the menu. Each rule reads as a condition followed by an action. For example, *When Platform is Talabat, change Default price of an item*. You can filter the list by entity, location and platform.

![](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-33b18025259c9ead03dd1c8737d51e0476dab825%2Fdifferential-pricing-v2-rules-list.png?alt=media)

Once the rules are created, check that the menu looks good.

**Step 3: Publish the menu**

Publish the menu to the aggregator to see the changes.

***

## Method 2: Edit Rules Directly on Atlas

Use this method to create or change differential pricing rules yourself in Atlas.

{% hint style="warning" %}
Ingested menus cannot be edited. Atlas shows the message "Imported menu cannot be directly edited in Atlas. To make changes, please make a copy of the menu." Click **Make a copy** to create a copy, then make your changes in the copy.
{% endhint %}

### Steps

**Step 1: Open a copy of the menu**

1. Log in to **Atlas**.
2. Go to **Menu**.
3. Open a copy of the menu.

**Step 2: Open the item**

In the item section, click an item. Open the **Rules** tab to see its **Associated Rules**.

**Step 3: Add a rule**

1. Click **Add Rule**, as highlighted below.
2. Choose a condition. For example:
   * Do not sell this item at this location.
   * Change the default price from one value to another.
3. Save the rule.

![](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-16d39e3b99400766c3041c95374718a29097e2b3%2Fdifferential-pricing-v2-item-add-rule.png?alt=media)

The rules on the item show how the item behaves on different locations and platforms. For example, one rule can change the default price on selected platforms, while another can stop the item from being sold on a platform at a location.

**Step 4: Publish the menu**

Publish the menu to the aggregator to see the changes on the aggregator UI.


---

# 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/business-manager/configuring-differential-pricing-for-aggregators/menu-v2.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.
