Skip to main content

Send Planner

📄️Get Send Plan Product Detail

Everything the plan knows about one product: its source pool (`row`), every network line with its source lanes, step-by-step `explanation` and `events` (the audit trail of overrides, resets, resolutions and carry-forwards: event, from/to quantity, reason, note, user and time), the plan's source warehouses, incoming supply at those warehouses (open purchase and manufacturing orders, with the nearest ETA in days), and whether the product is a kit or manufactured — useful for deciding how to close a shortfall.

📄️Draft supplier POs (supplier-direct sends)

Create draft purchase orders from the plan's supplier-direct suggestions: what your warehouses can't cover of a network's need, ordered from a supplier that ships straight to that network (supplier profile → Ships to Fulfillment Networks). One draft PO per supplier × network, delivered to the network's warehouse, quantities rounded to whole cases and at least the supplier's minimum; the PO's expected delivery date is today + that supplier's lead time for the network. Each line is priced at the supplier's price for the product, or its average cost when the supplier has no price (or a $0 price). Nothing is sent to the supplier: the POs are drafts. Use **Preview supplier POs** first to see what would be created. A suggestion that already has a PO is skipped. The next plan counts the PO as on its way to the network (line `inbound`, `meta.on_order`), so the units aren't suggested again.

📄️Get the AI approval summary

Everything a one-click approval of a send plan approves, calculated from the plan (the AI only words the narrative): totals (units, cases, estimated weight in lb, volume in ft³, pallets, value at average cost, SKUs, kept for self-fulfilled orders, stock-outs before arrival, shortfall, supplier units/value); per destination the same numbers plus sources, draft groups, reasons and checks before shipping; supplier orders shipped direct (supplier × destination, units, value, lead time, ETA, prep notes); lines already drafted; the SKU closest to running out; what changed since the previous full working plan; a plain `narrative`; `approvable` (why this plan can't be approved here, or null — scenarios and send runs aren't); and the latest `approval` with its run state.