Get replenishment status
get_replenishment_statusRetrieve the current status and timestamp of a replenishment order by providing its store ID and order ID.
Instructions
Read back a single replenishment order that was created through this server, scoped to its store. Read-only.
WHAT IT RETURNS The order record: order_id, store_id, sku, quantity, reason, current status, and its creation timestamp. status reflects where the order stands in StoreLink's internal flow; it begins at "submitted" on creation and advances from there. Report the status and the timestamp together — a status you read five minutes ago may have moved.
WHEN TO USE IT Step 4 and the final step of the standard workflow: lookup_sku -> get_stock_position -> create_replenishment_order -> get_replenishment_status. Use it when the buyer asks "did that order go through?" or "where is RPL-47-001?", and to confirm a write landed after create_replenishment_order returned. You need the order_id from the creation call — there is no browse, search or list-orders capability here, so an order_id you were never given cannot be recovered from this server.
SCOPE CHECK Both store_id and order_id are required and must match the same order. A valid order_id paired with the wrong store_id returns a not-found style error — it will never leak another store's order. If you get not-found, re-check the order_id and the store it was created for before telling the buyer the order is missing.
ACCESS ERRORS ARE NOT "NOT FOUND" "No credentials for store " and "Authentication failed for store after key reload" mean this server could not ask the question — NOT that the order is missing. The order may well exist and be on its way. Never report an access error to the buyer as a missing or failed order; give them the message so they can raise it with Korral IT.
WHEN NOT TO USE IT Reading an order does not change it, and nothing here can: there is no cancel, delete, amend or expedite on this server, and status is not writable through any tool. If the buyer wants the order stopped or altered, tell them this server cannot do it and they must contact Korral ops. It also shows no supplier or vendor detail, no lead time or delivery ETA, no cost, price or margin, and no POS data. For current shelf stock rather than order state, call get_stock_position instead.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes | Order identifier returned by create_replenishment_order, format RPL-<store>-<seq>, e.g. "RPL-47-001". Orders cannot be searched or listed — without this exact ID the order is unreachable. | |
| store_id | Yes | Korral store ID the order was created for, e.g. "47". Acts as a scope check: it must match the order, or the lookup returns not-found rather than another store's order. |