ASN Ingest & Pre-Receipt Worksheet Builder

The problem this kills

A truck shows up at the dock and nobody knows exactly what's on it. The vendor "sent the ASN" - meaning an advance ship notice, the heads-up file that says what's coming - but it landed in someone's inbox as a spreadsheet with columns nobody recognizes, half the SKUs spelled differently than your system, and quantities in cases when your master is in eaches.

So the receiving team improvises. They count blind, they re-key numbers into the WMS, they find an item that isn't even on the PO halfway through unloading, and the same ASN gets processed twice because two people opened the same email. Every one of those is a discrepancy, a chargeback fight, or an afternoon of cleanup.

The fix isn't a six-figure integration. It's a small tool that reads whatever the vendor sent, remembers each vendor's quirky layout, lines it up against your open POs, and hands the dock a clean worksheet that says exactly what to count and where it goes.

What you'll build

A private, login-protected web app for your inbound team that:

• Lets a coordinator drop an ASN file (Excel or CSV) exported or forwarded from any vendor.
• Auto-maps the columns - figures out which column is the SKU, the quantity, the unit of measure, the carton or pallet - and remembers a saved mapping per vendor so the next file from that vendor maps itself.
• Matches the ASN to the right open PO and flags any SKU that isn't on that PO before it becomes a dock surprise.
• Puts the parsed result in front of a coordinator to review, correct the mapping, and approve - nothing reaches the dock until a person signs off.
• Generates a sequenced pre-receipt worksheet broken out by carton and pallet, ready to print or export as CSV.
• Refuses to process the same ASN twice by guarding on the ASN ID plus the PO.

What's inside the Implementation Plan

• A copy-paste runbook you hand to an AI coding agent (Claude Code) - it does the building.
• It opens by interviewing you about your business. Before a single line of code, the plan makes the agent ask how your receiving works today, which systems and spreadsheets you live in, exactly how your SKUs and POs are named, your real and peak inbound volumes, your approval rules, and your messiest vendor edge cases. Then it reflects a short tailored spec back to you for a thumbs-up - so you get a tool shaped to your dock, not a generic template.
• Step-by-step build instructions, each ending in a ready-to-paste prompt.
• The per-vendor saved-mapping engine, the PO-matching and off-PO flagging logic, the human approval gate, and the carton/pallet worksheet generator.
• A "No API yet?" fallback so you can build and use the whole thing today using uploaded sheets and CSV exports - no integration to your WMS or ERP required.

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 put in front of a real receiving team:

• Login so only your team can open it.
• Row-level security so each organization only ever sees its own ASNs and POs.
• A full audit trail - who uploaded, who corrected the mapping, who approved, and when.
• A hard human-in-the-loop approval gate - the tool drafts the worksheet, a coordinator reviews and approves, and only then is it released to the dock.
• Duplicate guards so the same ASN-plus-PO can't be processed twice.

Who it's for

Inbound coordinators and receiving leads who own what comes through the dock door - the people who today are forwarding vendor spreadsheets to themselves, hand-keying counts, and absorbing the discrepancies when the ASN and the PO don't line up. No coding background needed.

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