> 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-v1.md).

# Menu V1

In Menu V1, you can set differential pricing in three ways:

1. Push the menu from your POS, or pull it from Atlas.
2. Edit directly on Atlas.
3. Bulk upload.

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

Use this method if your menu reaches UrbanPiper from your POS. The menu can be pushed from the POS, or pulled from Atlas (UrbanPiper). The prices for each platform are sent as part of the menu, so differential pricing is updated for the different platforms when the menu is received.

### How it works

* The push is done from the POS. The pull is done from Atlas (UrbanPiper).
* In either method, make sure the payload follows the API documentation, so that the prices are updated correctly: [Add or update menu](https://api-docs.urbanpiper.com/downstream/api/endpoints/menu/add-update-menu).
* Once the menu is received, the differential pricing is updated for the different platforms.

In the menu payload, the platform prices for an item are sent in the `platform_pricing` section. Each entry names a platform and the price of the item on that platform, as highlighted below.

![](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-802c6e7eaecd900e23a924a8593140b8265d3a9b%2Fdifferential-pricing-v1-pos-push-platform-pricing.png?alt=media)

### Steps

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

Push the menu from your POS, or pull it from Atlas. In either case, the payload must follow the format described in the API documentation linked above.

**Step 2: Verify the prices in Atlas**

1. Log in to **Atlas**.
2. Go to **Catalogue → Items**.
3. Open an item.
4. Go to **Locations**.
5. Check the pricing for each platform.

The **Locations** tab lists the item's price for each platform at the location.

![](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-5293d565095b914399cbf383b79aadf381381e51%2Fdifferential-pricing-v1-item-locations-pencil.png?alt=media)

**Step 3: Publish the menu**

Once the prices are verified, publish the menu to see the changes reflect on the aggregator UI.

***

## Method 2: Edit Directly on Atlas

Use this method to change an item's price for a platform yourself, without pushing a menu from the POS.

### Steps

**Step 1: Open the item**

1. Log in to **Atlas**.
2. Go to **Catalogue → Items**.
3. Open one item.

**Step 2: Open the item's locations**

Go to **Locations**.

**Step 3: Edit the price**

1. Click the **pencil icon** at the end of the location's row, as highlighted below.
2. Edit the pricing to the desired value.
3. Click **Save**.

![](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-5293d565095b914399cbf383b79aadf381381e51%2Fdifferential-pricing-v1-item-locations-pencil.png?alt=media)

**Step 4: Publish the menu**

Once you are satisfied with the prices, push or publish the menu to the aggregator to see the changes on the aggregator UI.

***

## Method 3: Bulk Upload

Use this method to change prices for many items at once. You export a file from Atlas, make your price changes in the file, and upload it back.

### Steps

**Step 1: Open the bulk action**

1. Log in to **Atlas**.
2. Go to **Catalogue → Items**.
3. Click **Bulk Actions** on the top bar, as highlighted below.

![](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-0c3f7998f387d2cb57b909203274c1b765efe068%2Fdifferential-pricing-v1-items-bulk-actions.png?alt=media)

4. On the **Bulk actions on items** page, open the third option in the list, **Item-Location-Platform associations**.

**Step 2: Export the file**

1. Under **Export Template**, enter your email ID in **Recipient Emails**.
2. Click **Export Item-Location-Platform Associations**.

A file is emailed to you.

![](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-3701ba9f60ed8bc5b5f698352cdf6e169f43315b%2Fdifferential-pricing-v1-bulk-export.png?alt=media)

**Step 3: Make your changes in the file**

1. Download the file from your email. The file has a fixed format.
2. Make the desired price changes in the file.

{% hint style="info" %}
You can filter the rows by item handle or by aggregator name to find the items you want to change.
{% endhint %}

The page also lists the columns of the template. **Item Handle**, **Store Handle**, **Platform** and **Price** are all required.

**Step 4: Upload the file**

1. Save the file in **CSV** format. Only CSV files can be uploaded.
2. Go back to the same page. The upload area is at the bottom, under **Upload filled data**.
3. Click the area to select the file, or drag the file onto it.

![](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-8c1adb5923e4c5803b9904f757352b147cdd32e0%2Fdifferential-pricing-v1-bulk-upload.png?alt=media)

{% hint style="warning" %}
Upload the file in CSV format only.
{% endhint %}

**Step 5: Publish the menu**

Once the changes show as updated, publish the menu to see them 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-v1.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.
