runbookify
← All plans
Order Management & Fulfillment / Order Changes & Cancellations

Ship-To Address Change Validator: Stop Address Edits From Becoming Failed Deliveries

Take a post-order ship-to change request, standardize and validate the new address, confirm the order hasn't shipped, and apply it only after shipping approves — so address edits stop turning into returned, re-shipped, and undeliverable orders.

BeginnerAn afternoonBuilds onNext.jsSupabaseResend
What you'll build

A web tool where a CSR pastes or imports a ship-to change request, AI standardizes and validates the new address and flags risky cases (PO box or residential on a freight order), the tool confirms the order hasn't shipped, shipping reviews and approves, and only then is the ship-to updated and the change logged.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.

Before you start

  • A Supabase account (free)
  • A Vercel account (free)
  • A Resend account (free)
  • An open-orders CSV (or Google Sheet export)
  • Your incoming address-change requests (email, form, or CSV)
  • Claude Code or any AI coding agent

The problem this kills

A customer emails the day after they order: "Actually, ship it to my new place." A CSR copies the new address into a reply, maybe pastes it into the order, and moves on. Then it goes wrong in all the usual ways. The address had a typo, so it bounces. The order had already left the dock, so now there are two shipments chasing each other. Someone changed a freight order to a residential address with no loading dock, and the carrier refuses it. Or the same change request got worked twice by two different people and the customer got charged for two re-ships.

Post-order address changes look trivial and quietly cause some of your most expensive fulfillment failures: undeliverable packages, return-to-sender fees, re-ship costs, angry customers, and freight surcharges nobody budgeted for. The fix isn't "be more careful." It's a small tool that standardizes the new address, checks the order hasn't shipped, and makes shipping sign off before anything changes — and you don't need to be a developer to build it.

What you'll build

A simple internal web tool. A CSR brings in a ship-to change request (typed in, or imported from a CSV/form export) against an order from your open-orders CSV. The tool standardizes the new address into a clean, consistent format, validates it (real street, city/state/ZIP that agree, complete fields), and flags the risky cases — a PO box or a residential address on a freight order. It checks the order's fulfillment stage and blocks the change if the order has already shipped. Then it puts the request in front of shipping, who confirms it isn't shipped yet and approves the validated address. Only on approval does the tool write the updated ship-to back to the order, log the change, and (optionally) email a confirmation. No approval, no change.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how change requests reach you today, what system holds your orders, the exact columns and naming in your open-orders export, how you tell a shipped order from an open one, what counts as a freight order, your typical and peak request volumes, and your messy edge cases (split shipments, partial fulfillment, international, already-printed labels) — and then it tailors the data model, the validations, and every later step to your answers. This is not a generic template; the agent reads a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through importing orders and requests, the address standardize-and-validate logic, the shipment-stage check, the shipping review-and-approve screen, the write-back of the new ship-to, and the confirmation email — each step with a ready-to-copy prompt. There's also a fallback so you can build the whole thing today even with no API into your order system.

The governance it includes (this is the point)

This is real fulfillment tooling, so it ships with the controls a serious ops team needs: login so only your team can use it, row-level security so you only ever see your own organization's orders, a complete audit trail of who requested, validated, and approved each change and when, a hard human-approval gate so no ship-to is ever overwritten until shipping confirms the order hasn't shipped and approves the validated address, and duplicate guards keyed on order ID + change ID so the same request can't be applied twice. Risky changes — PO boxes and residential addresses on freight orders — are flagged for a human to resolve, not silently pushed through.

Who it's for

CSRs and shipping/fulfillment teams who field "can you change my address?" requests all day and eat the cost when one slips through after the order has already moved. If you can describe how a change request reaches you and how you tell a shipped order from an open one, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll see your first validated, ready-to-approve address change the same afternoon.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.