Channel-Based Order Router
Build an internal tool that applies your channel-specific routing rules to every incoming order, assigns the right warehouse and SLA, and commits the assignment only after a planner approves - then exports clean per-warehouse fulfillment CSVs.
Orders come in, your channel routing rules are applied automatically, a planner reviews and approves the assignments, and you export per-warehouse fulfillment CSVs - no more routing orders by hand.
Before you start
- A consolidated-orders export (CSV or Google Sheet) with an order ID per row
- Your routing rules by channel (which warehouse and SLA each channel should use)
- Free Vercel, Supabase, and Resend accounts (the plan walks you through them)
The problem this kills
Every channel wants something different. Your marketplace orders ship from one warehouse on a two-day clock, your wholesale orders go from another with a longer SLA, and your DTC site has its own preferences. Right now a planner reads each order, remembers the rule for that channel, picks the warehouse, eyeballs the SLA, and types the assignment into a spreadsheet or warehouse portal by hand.
That works until volume spikes. Then routing gets slow, the rules live only in one person's head, the same order occasionally gets routed twice, and a tired Friday afternoon turns into a mis-shipped order from the wrong site. The knowledge isn't written down anywhere a machine can apply it consistently.
This plan turns your routing rules into software you actually own - so the rules get applied the same way every time, a human still signs off before anything is committed, and the busy season stops being terrifying.
What you'll build
A small, private web app for your fulfillment team:
- Orders in. Import a consolidated-orders CSV (or connect a Google Sheet) - the exact columns you already export.
- Rules applied automatically. The tool reads your per-channel routing rules and proposes a warehouse, a fulfillment path, and an SLA / promised ship date for each order.
- A planner reviews. Every proposed assignment lands in an approval queue. The planner can adjust any routing, then approve the batch.
- Committed on approval - not before. Nothing is written as final or exported until a human approves it.
- Per-warehouse CSVs out. Approved orders export as clean, separate fulfillment files - one per warehouse, in the column shape each site expects.
What's inside the Implementation Plan
- It starts by interviewing you about your business. Before writing a line of code, the plan has the AI agent ask you about your channels, your warehouses, the real field names in your order export, your SLAs, your volumes, and your weird edge cases. It reads back a short tailored spec and waits for your thumbs-up. You get a tool shaped around your routing - not a generic template you have to bend to fit.
- A clear definition of done so you know exactly when you're finished.
- Step-by-step build instructions, each ending with a ready-to-paste prompt for your AI coding agent.
- A routing-rules engine you can edit without touching code.
- The full governance layer (login, per-org data isolation, audit trail, approval gate, duplicate guards).
- A "No API yet?" fallback so you can build the entire thing today from a CSV or Google Sheet, with no integration to your warehouse systems required.
- A verification checklist to confirm it actually works before you trust it.
The governance it includes (this is the point)
- Login so only your team can open the tool.
- Row-level security so each organization only ever sees its own orders and rules.
- A complete audit trail - who routed what, who approved it, and exactly when.
- A hard human-in-the-loop approval gate - the AI proposes routings, a planner reviews and approves, and only then is anything committed or exported. The machine never ships an order on its own.
- Duplicate guards keyed on order ID so the same order can't be routed or exported twice.
Who it's for
Fulfillment planners and operations teams who handle orders across more than one channel and warehouse, and who are tired of routing each one by hand. If you can run a spreadsheet, you can build and run this. No coding background needed.
You've got this - paste the first prompt and let the interview tailor the rest.