In this article, you can find solutions to some of the more common issues when using the DiDi Food integration.
Issues shown on the Orders page
Error message or issue | How to resolve |
The order number shown in Deliverect doesn’t match the number shown in the DiDi Food app or the courier app | This is expected. DiDi Food’s own order number resets to 1 at the start of every day, which makes it hard to tell orders apart. Deliverect adds the order’s date and time in front of DiDi’s number (format: YYYYMMDDHHMMSS, followed by DiDi’s number), so no action is needed – use the full Deliverect order number when referencing an order with our support team or with DiDi. |
Orders are being cancelled automatically / DiDi Food closes the store after a failed order | DiDi Food requires an order to be accepted within 5 minutes, or it will be cancelled and the store may be taken offline. Make sure your POS or tablet is online and orders are accepted promptly. If you’d rather Deliverect not report failed orders as accepted, this can be adjusted in your channel settings – contact our support team for help. |
Issues shown on the Operation reports page
All non-order-related issues are found on the Operation reports page. This includes menu publishing, busy mode, and snoozing.
Menu publishing
Error message or issue | How to resolve |
InvalidChannelConfiguration: This shop does not have auth_token. Please contact partner’s support. | Your DiDi Food store isn’t linked to Deliverect. Link your DiDi Food store to Deliverect. If your store was already live and this error appears suddenly, contact our support team. |
“errno”:0,“errmsg”:“ok” – but the menu still doesn’t update | Wait 60 seconds and try to publish your menu again. If it still doesn’t come through, contact our support team. |
InvalidMenuPush: [DiDiFood] Menu push failed: 200] The calling frequency exceeds the setting: window: 60s, limit: 1 | DiDi Food only allows one menu update every 60 seconds. Wait a minute and try again. |
InvalidMenuPush: [DiDiFood] Menu push failed: 200] Internal error: create task failed | Wait 60 seconds and try to publish your menu again. |
each item can only belong to one category, duplicate app_item_id list in category list / Duplicate app_content_id in the same item | DiDi Food doesn’t allow the same item to appear in more than one category, or the same modifier to be used more than once on the same item. Remove the duplicate and republish your menu. |
errno:1004, errmsg: Adjust item price limited / Error errno:80111 | DiDi Food doesn’t allow item prices to increase by more than 10% within a 15-day period. Ask your DiDi Food account manager to lift this restriction, then republish your menu. |
errno:13028, errmsg: Item price error – Price is 0 or not numeric | A top-level menu item can’t be priced at 0, even if the cost is carried by a required modifier. Update the product to add a price and republish your menu. |
Busy mode
Error message or issue | How to resolve |
Failed to set busy mode: the allowed calling frequency has been exceeded (window: 60s, limit: 1) | DiDi Food only allows one busy mode update every 60 seconds. Wait a minute and try again. |
Failed to set busy mode: This shop does not have auth_token. Please contact partner’s support. | Your DiDi Food store isn’t linked to Deliverect. Link your DiDi Food store to Deliverect, or contact our support team if it was previously connected. |
The store does not allow this value because it is greater than 30 min. Allowed values 5 min and 30 min. | DiDi Food only supports busy mode delays between 5 and 30 minutes. Choose a value within that range. |
Snoozing
The same rate limit that applies to menu publishing and busy mode also applies to snoozing products: DiDi Food allows one update every 60 seconds. If you see a rate limit error, wait 60 seconds and try again.
Other things to know
Error message or issue | How to resolve |
Order notes aren’t coming through to Deliverect | Order notes must be activated on DiDi’s side first, in the DiDi Food app or dashboard under Menu Tienda > Configuración de comentarios (Store menu > Comment settings). |
One store closes automatically whenever another store opens | This happens when two stores share the same phone number on DiDi Food. Each store needs its own unique phone number registered with DiDi. |
Sales dropped after connecting to Deliverect | DiDi Food wipes historical item and store data when a new integration is made, which can temporarily affect a store’s ranking on the platform. DiDi can restore historic data on request – contact our support team and we’ll help you request this. |
Can’t link or unlink a DiDi Food store; “Credentials are not set” / “Invalid authToken” | This can happen if the channel link was previously connected to a store in a different environment. Contact our support team for help resolving it. |