Order Merge & Split Tool

The problem this kills

Two orders from the same customer are headed to the same dock on the same day, so someone merges them by hand. Or one big order has half its lines backordered, so someone splits it across two ship dates. Either way, it happens in a spreadsheet or by retyping into the order screen - and that is exactly where things break. A line gets dropped. The customer's PO number doesn't make it onto the new order. The link back to the original order disappears, so when the customer calls asking "where is PO 88421?" nobody can trace it.

Manual merges and splits are quietly one of the most error-prone things a fulfillment team does, because the whole point is to restructure data that other systems and the customer depend on. When references break, you get mis-ships, invoicing disputes, and hours of detective work reconstructing what happened.

This tool makes the restructure deliberate and safe: the computer proposes the new order shape, keeps every line and PO reference attached, a human approves it, and only then is anything committed.

What you'll build

A small private web app for your fulfillment team and CSRs:

• Load your open orders from a CSV export or a shared Google Sheet - no integration required to get started.
• Select the orders to combine, or pick one order to split, and the tool proposes a clean new order structure: a merge that rolls multiple orders into one ship, or a split that breaks one order across ship dates - keeping each line tied back to its source order and carrying every customer PO reference forward.
• Send the proposal to a fulfillment lead for approval. Nothing is committed while it sits in review.
• On approval, commit the restructured orders, write a complete audit record, and produce a clean CSV in the exact columns your order system expects so you can import it back.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding assistant (Claude Code), which then builds the tool with you step by step - you do not write code.

It opens by interviewing you about your business - your order and line numbering, how you reference customer POs, what your merge and split rules actually are, and your messy edge cases - so the tool is tailored to how you work, not a generic template. The AI reads a short spec back to you and waits for your thumbs-up before it builds anything.

From there it walks through setting up the database, the login, the order-selection screen, the merge/split proposal logic, the approval gate, the commit step, the audit trail, and the CSV export - each step ending in a ready-to-paste prompt.

The governance it includes (this is the point)

This isn't a throwaway script. The plan bakes in the controls that make a tool safe to use on real orders:

• Login so only your team can open it.
• Row-level security so each person only ever sees their own organization's orders.
• A hard approval gate - the AI drafts the merge or split, a fulfillment lead reviews and approves, and only then is the new structure committed. Nothing reaches your system of record without a human yes.
• A complete audit trail - who selected what, who approved, when, and exactly which source orders mapped to which new order set.
• Duplicate guards - the same set of source orders can't be merged or split twice, so you never double-process.
• Reference integrity - every resulting order carries forward its original customer PO references and keeps each line linked to its source order.

Who it's for

Fulfillment teams and customer service reps who restructure orders by hand today - combining shipments, splitting backorders across dates - and who are tired of broken references, dropped lines, and lost PO numbers. If you can fill out a spreadsheet, you can build and run this.

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