Orders¶

Read a website's tracked orders: what was bought, when, for how much, and which Hello Retail solution led to each product being bought.

Tips & tricks¶

Pick the card that matches what you're doing. Each prompt is ready to paste into your assistant.

Which of yesterday's orders came through Search, and which search configs drove them?

Did anyone place more than one order this week? Pull the whole week in one go.

Go through every order from Black Friday and tell me which Recommendations boxes sold the most.

orders_list¶

List a website's tracked orders in a date range, newest first. Each order carries its order number, time, total and the products bought, with quantity, price and line total. Each product line carries attributedTo: the solutions whose click led to it being bought, each listing the configs clicked. An empty attributedTo means no Hello Retail solution drove that line.

The shopper's email is never returned. customerEmailHash is an HMAC-SHA256 of the lowercased email, keyed with a Hello Retail secret and salted with the current UTC date and the website. It matches across orders pulled on the same day and changes the next day, so it can't be reversed or joined with hashes pulled on another day.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "orders_list",
    "arguments": {
      "websiteUuid": "<string>",
      "from": "2026-10-19",
      "to": "2026-10-19"
    }
  }
}

{
  "orders": [
    {
      "orderNumber": "<string>",
      "placedAt": "2026-10-19T14:32:10Z",
      "total": 499.0,
      "customerEmailHash": "<string>",
      "products": [
        {
          "productId": "<string>",
          "quantity": 1,
          "price": 499.0,
          "lineTotal": 499.0,
          "attributedTo": {
            "SEARCH": [
              { "key": "<search config key>", "name": "Main search" }
            ]
          }
        }
      ]
    }
  ],
  "totalCount": 1
}