Playbook · Shopify EDI ASN not matching

ASN lines do not match the Shopify order the warehouse ships.

Written for a Shopify owner whose EDI ASN (Advance Ship Notice) quantities, SKUs, or line items do not match the Shopify order or fulfillment the 3PL / EDI partner expects — SKU vs barcode vs GTIN mapping drift, UOM mismatch, cancelled or edited lines after the ASN was cut, partial ASN vs full order, EDI app ingest reject, or you chased 3PL tracking write-back, inventory transfer receiving, or partial fulfillment stuck instead. DIY-first: prove order vs ASN → fix mapping → re-send → retest. Distinct from 3PL tracking not writing back (carrier tracking never lands on the Shopify fulfillment — not ASN line mismatch), transfer order not receiving, and partial fulfillment stuck. Soft-link webhooks not delivering when the EDI app never receives order / fulfillment events, and fulfillment hold stuck when Shopify will not release the order to the warehouse. No earnings claims, no invented case studies.

Nico at Latch AI Ops · Sep 10, 2026 · ~12 minute read

Buy the 72-hour install — $9973PL trackingTransfer receiveMerchant FAQ

01

EDI ASN mismatch — not 3PL tracking, transfer receive, or partial fulfill.

Several “warehouse / 3PL / Shopify do not agree” bugs look alike. They do not share a fix. This page is only when the ASN (Advance Ship Notice) lines should match the Shopify order / fulfillment and do not. Carrier tracking never writing back to Shopify after ship is 3pl-tracking-not-writing-back — tracking numbers, not ASN SKU/qty match. Inventory transfer not receiving at a destination location is shopify-transfer-order-not-receiving. Remaining line items stuck after a partial fulfill is shopify-partial-fulfillment-stuck.

Soft links when the bug is adjacent: EDI / 3PL app never gets Shopify events is shopify-webhooks-not-delivering. Order held so the warehouse never gets a clean release is shopify-fulfillment-hold-stuck. This playbook stays on ASN expected to match Shopify lines → mismatch / reject → merchant cannot close the shipment cleanly.

02

Prove Shopify order lines vs ASN payload vs 3PL mapping.

Export the Shopify order: SKU, barcode / GTIN if used, quantity, fulfillment line status, and any order edits after the ASN was generated. Capture the ASN from the EDI portal or 3PL (raw EDI / XML / JSON if the app exposes it). Diff identifiers first — merchants often map Shopify SKU while the ASN carries barcode or a 3PL item ID.

Reproduce one known-bad order. Note: wrong qty, missing line, extra line, UOM (each vs case), or ASN rejected with a mapping error. Check whether the EDI / 3PL app shows ingest failures. Soft-check: if tracking is the missing piece after a clean ASN, leave for 3pl-tracking-not-writing-back. If warehouse stock transfer receive is the bug, use shopify-transfer-order-not-receiving. If remaining fulfill lines will not close, use shopify-partial-fulfillment-stuck.

Soft-check webhooks: if the EDI app never saw the order or fulfillment event, continue on shopify-webhooks-not-delivering. If Shopify still holds the order, use shopify-fulfillment-hold-stuck.

03

Repair mapping, re-send ASN, retest ingest — then retest.

Align SKU / barcode / GTIN / 3PL item ID in the EDI or 3PL app catalog map. Wait for order edits to settle before cutting a new ASN. Re-send or re-ingest the ASN for one test order. Confirm Shopify fulfillment lines now match qty and SKU. Fix UOM (each vs case) if the ASN multiplies quantities.

If the ASN matches but tracking never appears on the Shopify fulfillment, continue on 3pl-tracking-not-writing-back. If multi-location transfer receive is wrong, use shopify-transfer-order-not-receiving. If remaining lines will not fulfill after a partial ship, use shopify-partial-fulfillment-stuck.

Retest: Shopify order → ASN accepted → lines match → no mismatch exception in the EDI app. Soft notes: tracking belongs on 3pl-tracking-not-writing-back. Transfer receive belongs on shopify-transfer-order-not-receiving. Partial fulfill belongs on shopify-partial-fulfillment-stuck.

04

You tested tracking write-back, transfer receive, or partial fulfill instead.

3PL tracking not writing back is 3pl-tracking-not-writing-back. Transfer order not receiving is shopify-transfer-order-not-receiving. Partial fulfillment stuck is shopify-partial-fulfillment-stuck. Webhooks not delivering is shopify-webhooks-not-delivering. Fulfillment hold stuck is shopify-fulfillment-hold-stuck.

The only honest test for this page: ASN payload lines match the Shopify order / fulfillment SKUs and quantities (or you prove why the EDI partner rejects the match). Anything else is a different product.

05

When to stay DIY vs pay $997.

Stay DIY if you can spend one afternoon on the list above: prove order vs ASN, fix SKU/barcode mapping, re-send one ASN, separate tracking vs transfer vs partial fulfill, retest one shipment through to a clean match. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: 3PL tracking, transfer receive, partial fulfillment.

Pay for help when the work is not the ASN map itself — it is connecting the stack you already have so ASN / 3PL / fulfillment exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a theme rebuild retainer, not a conversion guarantee, not a brand or theme job.

Other shops’ public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or conversion-lift claim.

What it does not buy: more orders, recovered revenue, a forever ASN-match guarantee, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.