How POS Integration Works
Just Eat and Flyt have partnered to integrate with any Point of Sale (POS) system. Running an ancient POS system? No problem - Just Eat and Flyt run many deep custom software integrations with the key players in the market, helping you to sidestep technology problems and focus on serving happy customers and growing your business.
Just Eat will automatically push orders to your POS system through Flyt, removing all the heavy lifting for you.
When does the order get sent to my POS system?
For orders where Just Eat fulfils the delivery, Just Eat continuously monitors the driver's location and sends the order when the driver's estimated arrival time is equal to the 'preparation time' for orders at your restaurant. This means that the driver will arrive when the food is piping hot and ready to go.
For orders where the restaurant fulfils the delivery, Just Eat will inject the order immediately after it has been accepted on the Orderpad, allowing your restaurant staff to manage their workload and driver dispatching as they would normally.
What if something goes wrong?
Problems can sometimes happen, e.g. devices losing connectivity. If we detect an issue sending an order to your POS system, we will trigger backup processes utilising our own device. This means you don’t have to sacrifice precious time solving technology problems and can focus on keeping your hungry customers happy.
Coming Soon
The following relates to capabilities that are under development.
Menu & Inventory Management
Submit a Menu
https://uk.api.just-eat.io/docs#operation/putMenuForIngestion.
Please see the validation rules below, along with the error codes that our API would return
Validation Rules
Menu
| Code | Description |
| 201 | The restaurant id must match the restaurant id of the request |
Availability
| Code | Description |
| 202 | At least one availability must be specified |
| 204 | Availability ids must be unique across the menu |
| 205 | Availability id must be a menu card id for the restaurant |
| 206 | Availability ids must be numeric (Note: 206 and 284 are mutex rules) |
| 208 | Availabilities must have exactly one service type |
| 209 | Service type must match the service type of the menu card |
| 210 | There can be only two availabilities of each service type |
| 212 | FromDateTime must be before ToDateTime |
| 213 | Each availability can have one one time per service type |
| 214 | Times cannot overlap other times |
| 284 | Availability ids must be in the format '<tenant>.<restaurant_id>.<guid>' (Note: 206 and 284 are mutex rules) |
Categories
| Code | Description |
| 204 | Category ids must be unique across the menu |
| 215 | At least one category must be provided |
| 216 | Categories must have at least one menu item |
| 217 | Categories must reference a valid menu item id |
| 265 | Category ids cannot contain # character |
| 271 | Category items must be unique |
Items
| Code | Description |
| 204 | Item ids must be unique across the menu |
| 215 | At least one category must be provided |
| 216 | Categories must have at least one menu item |
| 217 | Categories must reference a valid menu item id |
| 218 | The menu must contain at least one item |
| 221 | Menu items must have at least one variation |
| 224 | Variation id cannot be the same as any item id other than its parent |
| 225 | The Kitchen Number must match the format 123 or 123-a
|
| 264 | Menu items must have a name |
| 267 | Items cannot contain # character |
Variations
| Code | Description |
| 282 | Variation ids must be unique per availability |
| 226 | A variation of type NoVariation must be the only variation in the collection |
| 227 | A variation of type Variation cannot be the only variation in the collection |
| 228 | Variations must be associated with at least one availability |
| 229 | Variations cannot reference a non-existent availability id |
| 230 | Variations cannot have modifiers if the parent item is a deal type |
| 231 | Variation must reference a modifier group id on the parent item |
| 232 | If parent item is of type MenuItem, variations cannot contain deal groups |
| 233 | Variation must reference a deal group id on the parent item |
| 234 | Each item in each referenced deal group must, at some point, be available at the same time as the variation |
| 260 | The variation name must be an empty string when type is NoVariation |
| 270 | Variation ids cannot contain # character |
| 272 | Variations with Deal Group IDs must not contain duplicate Deal Group IDs |
| 274 | Maximum energy content for a variation must be greater than or equal to minimum energy content |
| 275 | Energy unit for a variation must be kJ or kcal |
| 276 | Minimum number of servings for a variation must be greater than or equal to 0 |
| 277 | Maximum number of servings for a variation must be greater than or equal to the minimum number of servings |
Modifiers
| Code | Description |
| 236 | Minimum choices for group must be at least 0 |
| 237 | Maximum choices for group must be at least 1 |
| 238 | Maximum choices for group must be greater than minimum choices |
| 239 | Modifier groups must contain at least one modifier |
| 241 | The total number of possible modifier choices must be greater than or equal to the minimum number of choices for the group |
| 242 | The maximum number of choices must be greater than the minimum |
| 243 | Minimum choices for modifiers must be at least 0 |
| 244 | Maximum choices for modifiers must be at least 1 |
| 245 | Maximum choices for modifiers must be greater than minimum choices |
| 246 | Modifier groups must have different ids if they are not identical |
| 247 | Modifier group ids must be unique to the menu item |
| 248 | Modifiers must have different ids if they are not identical |
| 249 | Modifier ids must be unique to the modifier group |
| 263 | Modifier name must not be empty |
| 268 | Modifier group ids cannot contain # character |
| 278 | Maximum energy content for a modifier must be greater than or equal to minimum energy content |
| 279 | Energy unit for a modifier must be kJ or kcal |
| 280 | Minimum number of servings for a modifier must be greater than or equal to 0 |
| 281 | Maximum number of servings for a modifier must be greater than or equal to the minimum number of servings |
Deal groups
| Code | Description |
| 251 | Deal groups must have at least 1 required choice |
| 252 | Deal groups must include at least 1 deal item |
| 254 | The total number of possible choices must be greater than or equal to the number of required choices |
| 255 | The number of mandatory choices must be less than or equal to the required number of choices |
| 256 | The variation being referenced must exist on the menu |
| 257 | Minimum choices for deal items must be at least 0 |
| 258 | Maximum choices for deal items must be at least 1 |
| 259 | Maximum choices for deal items must be greater than minimum choices |
| 261 | Number of choices must be 1 if deal group contains variations with modifier groups |
| 262 | Deal groups cannot contain any deal item variations that have deal groups themselves |
| 266 | Deal group ids cannot contain # character |
| 273 | Deal item variations must have unique Ids per deal group |
| 283 | Deal groups with different deal item variations cannot have the same deal group ID |
| 285 | A menu item cannot contain multiple deal groups with the same ID |
Updated 3 months ago