What this account should be sent next, ranked by impact
What this account should be sent next, highest composite score first: one row per variant with the recommended quantity, the impact level, the replenishment date, the destination location and the default supplier, and production_type saying which act follows, a basket for a bought item or a manufacturing order for a made one.
their_rule is the account's own reorder rule for that variant, as its file stated it: min_stock and max_stock in units, the sell_from / sell_until window and the as_of date of the file. It is theirs, not a recommendation, and is null where the account has stated none; a field they left unstated is null.
partner_id is the account and limit bounds the rows.
A recommendation is advice, not an order. Placing it is create_purchase_order or convert_basket_to_purchase_orders; nothing here reserves stock or contacts anyone.
Sold with Essentials+: without Tightly Connect the answer is 403 plan_excludes.
Scope: accounts:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/wholesale/retailers/{partner_id}/replenishment-recommendations
- Auth: HTTP bearer
Path parameters
The account. An id, never a name. Duplicate account names are ordinary in apparel.
Query parameters
How many rows to return. Clamped to 1 to 100.
Headers
The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.
Response
rows, ranked by composite score, each with the quantity, the date and where it ships from.
Changes
No recorded changes to this operation across all 1 revision of this API.