New
- New
scheduled_receiptsfield on/v2/inventory-planningtells the plan about purchase or production orders you have already placed but not yet received — say, 200 pieces ordered three weeks ago that arrive next Tuesday. Anything arriving before a supplier could deliver a new order counts as available supply and shrinks that supplier's suggested order, instead of the endpoint recommending you buy stock that is already on a truck. Items are dated by expected arrival, as{"date": "...", "quantity": ...}. - New
committed_outflowsfield does the same for the outgoing side: sales orders, reservations, or anything else already booked to leave on a known date. These are firm allocations on top of the demand forecast, so 100 pieces committed to ship on the 15th reduce what's actually available — and commitments exceeding your stock increase the suggested order by exactly that backlog. Items share the shape of forecast data points (valueworks as an alias forquantity), so you can pass them the same way you pass history. - When either field is present,
stock_analysisreturns a per-periodprojected_stocktimeline — running stock plus arrivals minus forecast demand and committed outgoing, period by period. A negative value is your shortage warning, with the date attached. Days of coverage, the next order date, and stockout risk are all read off this projection instead of a flat daily average, so a large delivery or shipment lands on the date it actually happens rather than being smeared across the horizon. - Each supplier recommendation reports what it netted:
incoming_within_lead_timeandcommitted_within_lead_timeshow exactly how much scheduled supply and committed demand landed inside that supplier's delivery window.
Requests that don't use the new fields are completely unchanged.