Introducing Multi-Price Overrides for POS Application Integration
[Released on: 5th February, 2026]
Integrators can now send aggregator-specific item and modifier prices that differ from the default menu price.
This enhancement allows POS integrations to support platform-based pricing variations across multiple food aggregators without requiring duplicate menus or separate catalogue configurations.
Multi-price overrides are especially useful when:
- Aggregator platforms enforce different pricing rules
- Restaurants apply delivery markups per platform
- Items or modifiers require custom prices depending on the ordering channel
With this update, integrators can continue to send a single default price while optionally defining override prices for each aggregator context.
Key Updates
1. New Root Field: contexts
contextsA new top-level field, contexts, has been introduced to define pricing contexts that map to one or more aggregator platforms.
Each context contains:
- A unique
idused for reference - A list of platform identifiers under
ranges - A structured way to group override rules for pricing
Example:
"contexts": [
{
"id": "S001",
"ranges": [
{
"type": "PLATFORM",
"ids": [
"<food_aggregator_id>"
]
}
]
},
{
"id": "SA001",
"ranges": [
{
"type": "PLATFORM",
"ids": [
"<food_aggregator_id_1>",
"<food_aggregator_id_2>"
]
}
]
}
]2. New Overrides Field for Items and Modifiers
A new overrides field has been added inside each item and modifier object to support context-specific pricing adjustments.
Overrides allow integrators to specify: • Which context the override applies to (contextId) • The custom price that should be used on that platform
Example:
{
"id": "11ed91e6a5af3bf4ffa2178cca0dc8c0",
"name": {
"translations": {
"en-us": "Sprite Zero"
}
},
"description": {
"translations": {
"en-us": "Sprite Zero"
}
},
"classifications": [
"NON_VEG"
],
"imageUrl": " ",
"priceInfo": {
"price": 600
},
"externalData": null,
"modifierGroups": [
"6e71000d2f6811eeb9a98af909157777"
],
"quantityInfo": {
"maxPermitted": 100,
"minPermitted": 1
},
"type": "ITEM",
"availability": "AVAILABLE",
"overrides": [
{
"contextId": "S001",
"properties": {
"price": 50
}
},
{
"contextId": "SA001",
"properties": {
"price": 190
}
}
]
}When an aggregator platform matches a defined context, the override price will be applied instead of the default base price.
If no override is provided for a platform, the system will fall back to the standard item/modifier price.
Supported Endpoints
Multi-price overrides are supported across the following POS Applications APIs:
The payload structure remains consistent across both endpoints.
Supported Aggregator IDs
| Aggregator Name | Aggregator ID |
|---|---|
| Bolt | bolt-food-aggregator |
| BOX | box-food-aggregator |
| Careem | careemnow-food-aggregator |
| The Chefz | chefz-food-aggregator |
| Deliveroo | deliveroo-food-aggregator |
| eFood | efood-food-aggregator |
| Foodhub | foodhub-food-aggregator |
| Foodpanda | foodpanda-food-aggregator |
| Glovo | glovo-food-aggregator |
| HungerStation | hungerstation-food-aggregator |
| Instashop | instashop-food-aggregator |
| Jahez | jahez-food-aggregator |
| Just Eat | justeat-food-aggregator |
| Keeta | keeta-food-aggregator |
| Noon Food | noon-food-aggregator |
| Snoonu | snoonu-food-aggregator |
| Talabat | talabat-food-aggregator |
| ToYou | toyou-food-aggregator-v2 |
| UberEats | uber-food-aggregator |
| Wolt | wolt-food-aggregator |