100%
Integrations › Entreo

Entreo activity: what was sent and received

The Activity tab: every order event sent to Entreo, every update Entreo sent back, retrying an order Entreo never got, and seeing the exact order as Entreo receives it.

Back Office › Integrations › Entreo Delivery Drivers › Activity shows the conversation between the store and Entreo. It is where to look when an order did not reach Entreo, or a status did not reach the board.

Sent To Entreo

Image needed · entreo-14
Capture: Same page, Activity tab: the Sent To Entreo table with a Sent row, a Not Sent row and its Retry button.

Every message the store sent Entreo: a new order, an update, ready, or a cancellation. Each row shows when it was queued, the event, its status, how many attempts it took and Entreo’s answer.

StatusMeaning
PendingWaiting to go, or waiting for its next try. Retries come after 10 seconds, 30 seconds, 1, 2 and 5 minutes, then every 5 minutes for half an hour.
SentEntreo accepted it.
Not SentEntreo refused it, or could not be reached for half an hour. Retry sends it again.
DroppedNo longer needed: a newer update replaced it, or the request had already ended.

JSON on a row shows exactly what was sent, with Copy JSON.

Received From Entreo

Image needed · entreo-15
Capture: Same page, Activity tab: the Received From Entreo table with event, sequence, status and the verified tick.

Every delivery update Entreo sent: when it arrived, the event, its sequence number, what was done with it, and whether its signature was verified (✓). An update Entreo sends twice, or one that arrives after a newer one, is recorded and ignored, so the board always shows the latest.

Driver ETA updates are the exception: Entreo sends one about every minute per delivery while a driver is on the job, so they are not listed one by one. The line above the table counts them for the last 24 hours and shows when the last one arrived; a count that keeps rising while a driver is out means the connection is healthy. An ETA update that failed or could not be matched to an order is still listed.

A row with ✗ in Verified was not signed with the right secret and was not applied. One by itself can be anything on the internet; a steady stream means the signing secret on the server does not match Entreo’s — contact support.

Seeing an order as Entreo receives it

Image needed · entreo-13
Capture: Same page, Deliveries tab: the JSON panel opened for one order (order.created preview) with Copy JSON.

JSON on a row of the Deliveries tab builds the order exactly as Entreo would receive it now, without sending anything. Entreo asks for a few of these when a store is connected; copy them from here. It is also the quickest way to see what is missing from an order Entreo refused.