Dated Lot Demand Allocation Plan Match dated lot quantities to demand with a clear earliest-expiry allocation plan.
Match dated lot quantities to demand with a clear earliest-expiry allocation plan. Supply sourceRevision, commonUnit, up to 64 lots with unique id, itemId, availableMinute, expiryMinute and availableUnits, and up to 64 demands with unique id, itemId, requiredMinute and requiredUnits. All identities are opaque, case-sensitive ASCII labels of 1 to 48 letters, digits, underscores, periods, colons, pipes or hyphens. Lot and demand identity namespaces are separate; delimiter characters have no composite-key meaning. Quantities are positive safe whole integers in the one supplied common unit. Minutes are nonnegative safe whole integers on one common timeline, with each expiry strictly after availability. Demands run by earliest requiredMinute then original demand order. A lot is eligible only for the exact same itemId when availableMinute is at or before requiredMinute and requiredMinute is strictly before expiryMinute. Eligible lots run by earliest expiry, then earliest availability, then original lot order. Allocation may split across lots, never reuses a unit and never substitutes an item. A demand exactly at expiry cannot use that lot; a demand exactly at availability may use it. Future or expired remaining stock stays visible in balances. demandPlans and lotBalances retain their respective input order. allocations records chronological policy order and each used lot in its policy order. Quantity fields and aggregate totals are exact canonical decimal strings computed with integer arithmetic, including sums beyond the safe-number range. Per-demand status is fulfilled, partial or unfilled; aggregate totals reconcile supplied availability, required units, allocated units, shortage and remaining units. Empty lists are valid. Invalid identities, quantities, times, duplicate identities and non-increasing expiry reject during preflight before quoting. Shared limits are 36,000 input bytes, 6,000 nodes, depth 24 and 500,000 output bytes. This supplied-record policy does not read or change external inventory, reserve stock, purchase goods, guarantee physical availability or provide a global allocation optimum. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.
Agent API guide → · Website orders show the report on your private order page.
Your input · JSON Load a small example The complete checkout request must fit within 40,000 UTF-8 bytes. Your input is validated again before an order is created.