Northwind ERP Desk
Overview
Turn staged task payloads and live ERP records into the exact JSON object required by the answer template.
Workflow
- Read
prompt.txt, every file underinput/payloads/, andanswer_template.json. - Treat the template as the contract. Use its exact field names, enum values, required keys, ordering rules, and precision rules.
- Use the runner-supplied task base URL. Query
GET /manifestwhen you need to confirm the available record shapes, then fetch only the records required from the live API. - Join the live records back to the memo, compute the requested decisions, and sort every list exactly as instructed.
- Return JSON only. Do not add prose, fences, or commentary.
Common API Areas
- Use
/orders,/customers,/products,/inventory,/warehouses, and/shipping/quotefor expedite and allocation tasks. - Use
/boms,/products,/inventory,/warehouses, and/purchase_ordersfor replenishment tasks. - Use
/incidentsand/suppliersfor supplier scorecards and procurement-control tasks. - Use
/purchase_orderswhen a task needs holds, releases, coverage, or timely supplier supply checks.
Common Task Families
Expedite and Allocation
- Derive each order or line decision from live order, customer, product, warehouse, and inventory state.
- Use effective availability, protected-stock rules, and customer-risk or product-status checks before deciding ship, transfer, backorder, manual review, hold, or reject.
- Keep shipped quantity, transfer quantity, and backorder quantity separate.
- Mark blocked orders only for account or risk stops, not for line-only product issues.
- Include shipping quotes from the live API when the template asks for them.
Replenishment
- Expand each BOM to component demand from the requested build quantity.
- Compare total required units with target-warehouse stock, timely same-warehouse purchase orders, and feasible inter-warehouse transfers.
- Create purchase requisitions only for the remaining gap.
- Mark components as excluded when existing stock or timely POs already cover them, or when the template says the target is overstocked.
Supplier Risk and Procurement Control
- Filter incidents to the requested analysis window.
- Aggregate counts, percentages, costs, durations, open counts, and severe counts per supplier.
- Apply the supplied recommendation precedence exactly.
- For procurement-control tasks, also collect affected SKUs and hold or release open and confirmed purchase orders as directed by the policy.
Normalization
- Preserve exact field names from the template.
- Sort identifiers ascending unless the template says otherwise.
- Round currency to two decimals.
- Round percentages and durations to the precision stated by the template or memo.
- Use empty lists instead of null unless the template explicitly allows null.
- Recheck the final JSON against the template before returning it.