EvolutionAPI
orderMessage from iOS does not include product details or correct order title
Welcome!
- [x] Yes, I have searched for similar issues on GitHub and found none.
What did you do?
I have a WhatsApp Business account connected to Evolution API with a product catalog. When a customer sends an order from the catalog:
If the order is placed from Android, the webhook messages.upsert contains an orderMessage with some context, including a correct orderTitle (related to the actual order) and more details that can be used to identify the products.
If the order is placed from iOS, the webhook messages.upsert contains an orderMessage with no product list, no productId/retailerId, and the orderTitle is actually the name of the Evolution API instance, not the order name.
This makes it impossible to identify which products were ordered by an iOS customer via the webhook.
What did you expect?
When an order is placed from iOS, I expected the orderMessage payload to include:
A list of products in the order.
The productId or retailerId for each product.
A correct orderTitle that represents the actual order, not the instance name.
What did you observe instead of what you expected?
From iOS, the payload contains only:
orderId
Incorrect orderTitle (instance name)
No product details (IDs, names, prices)
From Android, the payload contains more meaningful information to identify the order contents.
Screenshots/Videos
Android payload:
{
"messageType": "orderMessage",
"orderMessage": {
"orderId": "...",
"orderTitle": "Combo Burger + Soda",
...
}
}
iOS payload:
{ "messageType": "orderMessage", "orderMessage": { "orderId": "...", "orderTitle": "InstanceName", ... } }
Which version of the API are you using?
2.3.0
What is your environment?
Windows
Other environment specifications
No response
If applicable, paste the log output
No response
Additional Notes
It is possible that the iOS client sends the cart data encapsulated in a different message type (viewOnceMessage or similar) which Baileys/Evolution API is not parsing yet. If that’s the case, parsing that hidden block would allow extracting product details from iOS orders just like Android.
Same issue here, is there a solution?
I have integrated WABA too, and the Cloud API from Meta returns a list of orders perfectly readable.
BUT I still need to see the chats on the mobile App, and with WABA is not possible (Once you register your number in Meta, then it is not possible to open a session in regular Whatsapp mobile App)
