Northwind ERP Solver
Overview
Use the prompt, payloads, and live ERP records to fill the exact JSON template. Keep output machine-readable, honor every sort order and enum, and round currency and percentages exactly as requested.
Workflow
- Read
prompt.txt, every file underinput/payloads/, and the matchinganswer_template.json. - Treat the template as the source of truth for keys, enum values, ordering, and rounding.
- Pull only the public ERP records needed for the task from the base URL supplied by the task environment.
- Compute derived fields before writing output.
- Return JSON only. Do not add commentary, markdown, or extra keys.
Shared Calculations
- Compute inventory
effective_availableason_hand - reserved - quarantined - safety_stock. - Treat positive
effective_availableof 1-10 units aslow_stockunless the template says otherwise. - Treat
effective_available < requested quantityasshortage. - Treat
product.active == falseas inactive stock. - Compute shipping quote weight as
sum(line.quantity * product.weight_lb)and call/shipping/quotewithwarehouse_id,destination_zip, andweight_lb. - Map customer exceptions from account state first, then risk flag: blocked ->
account_blocked, review_required ->review_required, fraud_watch ->fraud_watch, credit_watch ->credit_watch, otherwisenone. - Keep list fields sorted exactly as the template requires.
Task Patterns
- Expedite queues and order decision files: see northwind_patterns.md.
- Kit replenishment runs: see northwind_patterns.md.
- Supplier incident scorecards: see northwind_patterns.md.
- Mixed warehouse allocation waves: see northwind_patterns.md.
- Procurement-control reviews: see northwind_patterns.md.
Output Discipline
- Follow the template's field names exactly.
- Preserve required casing for enums and identifiers.
- Round currency to 2 decimals and percentages to the requested precision.
- Prefer simple derivations over inferred shortcuts when the API exposes the needed records directly.