Inventory reorder proposal
Turns item demand, on-hand stock, open purchase orders, supplier lead times, and service-level rules into a cited reorder proposal with quantity, timing, stockout risk, and assumptions. Use for replenishment planning, inventory control, purchasing recommendations, and warehouse exception reviews.
Publicado 21 de ago de 2026 · Actualizado 26 de ago de 2026
Requisitos
Add replenishment policy with service target and demand window. Map SKU, location, stock, demand, PO, supplier, and unit fields. Define usable inbound statuses and overdue-PO treatment. Set planning horizon and proposal-cost currency.
Documento de la habilidad
El SKILL.md completo que tu agente lee y sigue.
Inventory reorder proposal
Purpose
Calculate replenishment proposals from demand history and current supply while exposing the lead-time, safety-stock, and service-level assumptions behind each recommendation.
Scope
Cover inventory master, stock ledger, demand history, open purchase orders, supplier lead-time table, minimum order quantities, safety-stock policy, and warehouse calendar. Excluded: placing purchase orders, changing stock counts, supplier negotiation, and guaranteeing availability.
Data basis
- Inventory fields sku, location, on_hand, allocated, available, reorder_point, safety_stock, and unit_cost.
- Demand fields date, sku, location, quantity, and status.
- Purchase orders with po_id, ordered_qty, due_date, and status.
- Supplier lead time, MOQ, pack-size, and replenishment policy.
Result
Produce a reorder sheet with net available, demand rate, projected stockout date, suggested quantity, order-by date, MOQ adjustment, cost, confidence, and source citations.
The proposal is a decision workpaper rather than a purchase order: each quantity is accompanied by its calculation inputs, inbound assumption, and confidence level. Items blocked by missing parameters remain visible with a reason and no invented quantity.
Quality criteria
- Exclude cancelled demand and distinguish allocated from available units.
- Include open POs only when status and due date make them usable.
- Apply stated demand window, lead time, safety stock, MOQ, and order-cycle rules.
- Flag negative stock, missing lead time, stale demand, and conflicting units.
- Cite inventory, demand, PO, supplier, or policy rows for every proposal.
Instructions
Calculate net available as on-hand minus allocated plus usable inbound. An overdue PO is not received without a receipt row. Use the policy demand window and service target; never invent a safety factor. Round proposed quantity up to MOQ or pack multiple and show unrounded need. Separate data-gap risk from demand-driven stockout risk.
Adapt before use
- Add replenishment policy with service target and demand window.
- Map SKU, location, stock, demand, PO, supplier, and unit fields.
- Define usable inbound statuses and overdue-PO treatment.
- Set planning horizon and proposal-cost currency.
Habilidades relacionadas
- 8D problem-solving report
Builds a traceable 8D problem-solving report from a manufacturing complaint, defect record, and process evidence. Use for customer complaints, recurring production defects, containment records, corrective action reports, and structured root-cause investigations.
- Capacity resource plan
Converts demand forecasts, staffing calendars, work hours, absences, and throughput assumptions into a capacity plan with bottleneck dates and quantified staffing options. Use for workforce capacity planning, resource allocation, utilization review, and delivery-load analysis.
- Construction punch list
Converts inspection notes, photos, room data, and project requirements into a prioritized construction punch list with trade grouping and verification fields. Use for substantial completion, handover inspections, snagging, closeout walks, and defect follow-up.
- Construction RFI draft
Converts a construction field question or document conflict into a precise request for information with evidence, options, and schedule or cost implications. Use for RFIs, design clarifications, plan conflicts, specification gaps, and field coordination questions.