Sealed Carton Kit Pick Plan Choose whole sealed cartons to cover a kit demand with the fewest cartons opened.
Choose whole sealed cartons to cover a kit demand with the fewest cartons opened. Supply sourceRevision, up to 16 declared skus with unique id and nonnegative requiredPieces, and up to 16 cartons with unique id and 1 to 16 contents entries. Each entry has a declared skuId and positive pieces, and a SKU may appear only once within a carton. Quantities are safe whole integers. The revision, SKU and carton identities are opaque, case-sensitive ASCII labels of 1 to 48 letters, digits, underscores, periods, colons, pipes or hyphens; namespaces are separate and delimiter characters have no composite-key meaning. A carton is selected whole and every declared SKU demand must be covered. The exact objective first minimizes openedCartonCount, then the sum of extra individual pieces across all declared SKUs, then the lexicographically smallest vector of selected carton input indexes. Indexes are zero based and returned in ascending input order. Carton counts take priority over excess: one oversized covering carton beats two exact cartons. Surplus for zero-demand SKUs still counts as extra. There is no package splitting or substitution. skuPlans retains declared SKU order and reports requiredPieces plus exact decimal strings for pickedPieces, extraPieces, shortagePieces and availablePieces. Available pieces sum all supplied carton contents. Shortage is required minus all available pieces, floored at zero. If any demand is infeasible, the result is atomic: no cartons are selected, picked and extra totals are zero and the original requirements and actual stock shortages remain visible. Empty or all-zero demands select no cartons. totalExtraPieces is an exact decimal-string sum. Bounded exact search examines at most 65,536 subsets and uses exact integer arithmetic for all quantity totals. Duplicate identities, duplicate SKU content, unknown references and invalid quantities reject the whole request during preflight. The shared 36,000-byte, 6,000-node, depth-24 input profile and 500,000-byte output guard apply. These are technical workload bounds. This supplied-record optimum does not open cartons, mutate or reserve stock, prove physical availability or condition, authorize picking, or model handling and compatibility constraints. 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.