Skip to content

Order Traceability ​

The Order traceability screen shows the path of an order through the integration middleware. For each order it shows when it was created in Glovo, when it was received, when it was sent to the POS, the exact content sent to the POS endpoint and the exact reply returned by it.

Open Profile → Order traceability. The screen is available to POS accounts.

VISIBILITY

The screen shows only orders from stores that belong to the POS of the signed-in account. An order belonging to another POS is treated the same as an order that does not exist.

Searching for an Order ​

Enter the order code and click Search.

The order code is the number printed on the Glovo receipt (e.g. 101703806119), identical to the order_code field of the order notification.

If the order is not found, check the code first. If it is correct, the order was not received from Glovo for any of the POS's stores.

What the Screen Shows ​

Verdict ​

The first line of the result states whether delivery to the POS succeeded:

VerdictMeaning
The order was delivered to your system (green)The POS endpoint replied with an HTTP 2xx code
The order did NOT reach your system (red)The order was received from Glovo, but no call to the POS endpoint completed successfully. The cause appears under Delivery attempts and Errors

POS RESPONSE

A 2xx code confirms that the call reached the endpoint. If the reply has no body, it cannot tell whether the POS saved the order. The endpoint should return an identifier of the order in the POS. The reply is shown in full on this screen.

Order ​

FieldDescription
Order codeThe Glovo order code
StoreThe full store_id (partner_name__store_id), followed by the name of the location defined in the portal
Internal statusThe middleware processing status. It is not proof of delivery: delivery is read from the verdict

CHECK THE STORE

The order is sent to the store_id that Glovo indicates in the notification. If Store shows a different location than the one expecting the order, check the mapping between the Glovo store and the POS location.

Timeline ​

MomentDescription
Created in GlovoWhen the order was created, in the local time sent by Glovo (order_time)
Received by usWhen the middleware received the order from Glovo
Sent to youWhen the order was sent to the POS endpoint
Time inside our systemTime between receipt and sending to the POS

Received and Sent are shown in Romanian time (Europe/Bucharest).

The timeline shows where a delay occurs:

  • between Created in Glovo and Received: the time until Glovo transmits the order;
  • between Received and Sent: processing in the middleware, usually under a second;
  • after Sent: processing in the POS.

Calls to the POS System ​

For each call to a POS endpoint the screen shows:

  • the result: Accepted or Refused;
  • the HTTP code and the URL of the endpoint called;
  • What we sent you: the exact payload sent to the POS;
  • What you replied: the exact reply of the endpoint.

Both have a copy button. For a refused call only the reply is kept, not the request content.

Delivery Attempts ​

This section appears only when the first attempt failed and delivery was retried, according to the configuration under Profile → Delivery retry. Each attempt shows the time, the wait before it, the HTTP code received and the error message.

Errors ​

This section appears only when errors were recorded for the order. Each error shows the time, the message and the operation during which it occurred.

Common Situations ​

What is shownWhat it means
Green verdict, HTTP 200, empty replyThe order reached the POS endpoint. Whether it was saved is checked in the POS
Red verdict, timeout or 5xx errorsThe POS endpoint did not reply or replied with an error. The exact message is under Errors
Red verdict, 4xxThe POS endpoint refused the order. The reason is in the reply shown under Calls
Store shows a different locationThe order was sent to the store indicated by Glovo
Order not foundThe code is wrong, or the order was not received from Glovo for the POS's stores

TEST ORDERS

Orders placed on a test store do not appear on this screen. They are checked through the test order traceability API, with the traceability token shown on the Allocate Test Store screen.