# Configure store/merchant order receiving mode
+ Pay before meal
After the user scans the code to order and pays, the kitchen printer prints the order and cooks it. Front-end development can be based on this field information of store details (tablePayMod: 0 means to pay before the meal; 1 means to pay after the meal) to determine the order-taking mode and guide users to interact accordingly.
+ Pay after meal
After users scan the QR code to order, they can place the order without paying. After finishing the meal, they can pay the bill in a unified manner.
In this case, after the user places an order, the merchant needs to confirm it before the kitchen printer prints the order and cooks it.
# The merchant pulls the dishes to be confirmed
Please note that this is a backend interface and requires the administrator (store/merchant administrator) to log in and obtain the X-TOKEN before it can be called.You can pull the dishes to be confirmed by passing in the following combination of parameters:
+shopId current store/merchant ID
+ type order type is 2 (scan the QR code to order)
+ status status is 0 (unpaid)
+ cyTableStatus status is 0 (pending confirmation)
After the data is returned, it is recommended that the returned data betableCode (table code)Display in groups/blocks, and dishes ordered from the same table are displayed together; it is also recommended to add a multi-select (selected by default) one-click confirmation menu function on the front-end interface.
# Merchant confirmation menu
Please note that this is a backend interface and requires the administrator (store/merchant administrator) to log in and obtain the X-TOKEN before it can be called.
Input the order ID that needs to be confirmed and call this interface to confirm the order. For stores/merchant that pay after the meal, after the merchant confirms, the kitchen printer will be triggered to print out the order.
# Configure printer
When a user orders and pays/the merchant confirms that the order has been made, the kitchen printer should be able to automatically print out the information on the items that the current user has ordered/newly ordered. The specific configuration is as follows:
Select "ordering mode" as the printing mode. In this mode, the printer will only print the dishes confirmed by the merchant. It is generally used to configure kitchen printers.
# The merchant marks the dish as being served
Please note that this is a backend interface and requires the administrator (store/merchant administrator) to log in and obtain the X-TOKEN before it can be called.
+ orderGoodsId order detail record table record ID
# Merchants place orders & add or remove dishes
## Place an order & add dishes
Please call the front-end API interface, obtain the table token, and use the table token to order food.
## Withdrawal
Please note that this is a backend interface and requires the administrator (store/merchant administrator) to log in and obtain the X-TOKEN before it can be called.
+ orderGoodsId order detail record table record ID