Partial-Ship vs Hold Decision Tool

The problem this kills

A picker fills 8 of 12 lines on an order. Now what? Ship the 8 now and the rest later - eating a second freight charge? Or hold the whole thing until it's complete and risk a late, unhappy customer? Right now that call gets made differently by whoever happens to be standing there, and nobody can explain later why a $40 order shipped twice on $90 of freight, or why a key account waited four days for nothing.

These decisions are not actually hard - they just need the customer's rules and the freight math applied the same way every single time. That's exactly what software is good at, and exactly what humans are bad at doing consistently under pressure.

What you'll build

An internal web tool your fulfillment team logs into. You feed it your open orders with their fill status and your per-customer ship rules. For every partially-fillable order it:

• Checks whether that customer is ship-complete, ship-partial-OK, or "ask first."
• Weighs the extra freight of a second shipment against the service impact of holding.
• Recommends a clear action - ship partial now, hold for complete, or escalate - with a one-line reason.
• Queues the recommendation for a lead to approve or override.
• On approval, drops the order onto a clean action list and a CSV you can hand to the warehouse or push into your system of record.

Nothing gets actioned until a human says yes.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent (Claude Code). It walks the agent through building the whole tool step by step, and it opens by interviewing you about your business - your current process, the systems and spreadsheets you use, how your order and customer data is actually named, your real volumes, and your messy exceptions. It then tailors the data model, the decision rules, and every later build step to your answers instead of dropping a generic template on you.

Inside you'll find:

• The exact discovery questions the agent asks before it builds anything.
• A data model shaped around open orders, fill status, and per-customer ship rules.
• The decision engine that scores partial-ship vs hold and explains itself.
• The approval queue and one-click approve/override screen for leads.
• The action list and CSV export in the columns your system expects.
• A "No API yet?" path so you can build and run the whole thing from a Google Sheet or CSV today - no integration required.

The governance it includes (this is the point)

This isn't a script that quietly reshuffles your orders. Governance is built in from the first step:

• Login so only your team can use it.
• Row-level security so each organization only ever sees its own orders and rules.
• A complete audit trail - who recommended, who approved or overrode, and exactly when.
• A hard human-in-the-loop gate - the tool drafts a recommendation, a lead reviews and approves, and only then is anything actioned.
• Duplicate guards keyed on order ID so the same order can't be processed twice.

Who it's for

Fulfillment leads and CSRs who are tired of partial-ship calls being ad hoc - and who want a defensible, consistent answer every time without waiting on IT to build it.

You've got this. Paste the first prompt and let the agent interview you.