Order Tools
Six tools answer questions about orders: finding one, reading it, and following it through to the package.
| Tool | What it answers |
|---|---|
search_orders | Orders you don’t have a number for. |
get_order | One order in full. |
list_order_items | What was ordered on it. |
list_order_fulfillments | How it is being prepared. |
list_order_shipments | Where its packages are. |
get_order_timeline | What happened to it. |
Finding an Order
search_orders covers the ways an operator actually looks for one: by date placed, state, sales channel, origin, tag, SKU, or tracking number. Its keyword matches the order number, the number the order carries in the system it came from, the customer and billing name, email, phone, and company, and the sales channel name. A SKU or a tracking number is matched in full.
- “Which orders came in from Shopify yesterday with SKU ABC-100 on them?”
- “Find the order with tracking number 1Z999AA10123456784.”
- “Show me every order tagged rush that hasn’t shipped.”
- “How many orders did we take last week?”
The application filters orders by around thirty things and this tool offers nine. The nine are the ones people say out loud.
Reading One
get_order answers who the order is for, its state, whether it is on hold and why, what it is worth, how it is meant to ship, what was written on it, and the state of each fulfillment. It reports how many items and shipments there are without listing them, so ask about those directly when that is the question.
- “Look up order 1042 and tell me where it stands.”
- “Which orders are on hold right now, and why?”
Why It Has Not Shipped
list_order_fulfillments is the tool for that question. It gives the state of each fulfillment, the warehouse preparing it, when it is expected, which integration should receive it, and the ids it carries there.
A fulfillment with no external id was created inside Endless and never reached the system meant to receive it. That is how an order reads as shipped in Endless and as unfulfilled in the channel, and your AI tools can see it.
- “Why hasn’t order 1042 gone out?”
- “Which fulfillments never made it to ShipStation?”
Where the Package Is
list_order_shipments gives carrier, tracking number and link, package count, and the dates it shipped and arrived. Each shipment also carries the id it has in the system that reported it, so two records for the same package can be told apart from two real packages.
What Happened to It
get_order_timeline reads the history of the order and of every fulfillment on it, most recent first: what happened, when, who did it, and the detail behind it. Ask it what went wrong and it narrows to warnings and errors.
Something that happened repeatedly is answered once, with how many times and between when and when, so a long history stays readable.
- “Walk me through what happened to order 1042.”
- “What went wrong on this order?”
- “Who changed the shipping address, and when?”
For the history of anything other than an order, see History.