Describe the bug
When order is recalled from the table view (by selecting a table that's already linked to an order), the linked order is not properly recalled.
To Reproduce
Steps to reproduce the behavior:
- Go to POS
- Create and select a table
- Send an order to the table
- Reselect the table from the table view
Expected behavior
When the table is selected with an order linked to it, the order should reappeared on the right of the POS.
Additional context
When the table view is dynamically updated, the API returns the correct informations :
GET https://api.hellokitchen.fr/api/3/pos_config/
...
{
"x": 381,
"y": 288,
"name": "3",
"id": 3,
"type": "square",
"plates": 2,
"time": "2025-10-02T09:19:03.073Z",
"orderId": 126 //< this information here is important
}
...
So the issue doesn't come from when the order is firstly sended or in what returns the API. It seems to just be not stored at all by the POS :
What stored in the cache for the table 3
{
"fused": [],
"h": 100,
"id": "3",
"left": 258.6302083333333,
"plates": 2,
"time": "2025-10-02T09:19:03.073Z",
"top": 288,
"type": "square",
"w": 100
// no orderId stored
}
Describe the bug
When order is recalled from the table view (by selecting a table that's already linked to an order), the linked order is not properly recalled.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When the table is selected with an order linked to it, the order should reappeared on the right of the POS.
Additional context
When the table view is dynamically updated, the API returns the correct informations :
GET https://api.hellokitchen.fr/api/3/pos_config/
So the issue doesn't come from when the order is firstly sended or in what returns the API. It seems to just be not stored at all by the POS :
What stored in the cache for the table 3
{ "fused": [], "h": 100, "id": "3", "left": 258.6302083333333, "plates": 2, "time": "2025-10-02T09:19:03.073Z", "top": 288, "type": "square", "w": 100 // no orderId stored }