EDI 816 Ship-To Location Master Data From Retail Partners

The truck reached store 1184 at 10:45 and found an empty unit with a leasing sign in the window. The retailer had moved the store two miles east and sent the new address weeks earlier in an EDI 816. The supplier's translator accepted the file and returned a 997, so everyone assumed the change had landed. It had not: the load job only processed new locations, and the change record sat untouched in a staging table.

The 816 is the retailer's location master arriving by EDI, and treating it as master data, with validation, dated changes and an audit trail, prevents most deliveries to wrong or closed addresses. This guide shows how the transaction is built, which fields matter to the warehouse, the carrier bill and, for Indian buyers, the GST documents, and how to load changes so they take effect on the right day.

• Inside this explainer: the 816's structure, identifier qualifiers, action codes and effective dates, downstream use in orders, labels and rating, and India's GSTIN, PIN and state code checks on ship-to records.
• Artefacts to copy: an annotated sample 816, a worked cost of a stale record in $ and ₹, a validation rule table and a go-live checklist.

Why a retailer sends an 816 instead of a spreadsheet of stores

A retailer with hundreds of stores changes its location list every week, and the 816 lets every supplier receive those changes in one machine-readable format. The transaction exists to describe a parent organisation, its members and how they relate; for a retail chain, the members are stores, distribution centers and billing entities.

X12 describes the 816 as able to transmit information about a parent organisation, its members and the relationship of members to the parent or to each other. The standard names retail chains alongside associations, hospital systems and holding companies as examples of a parent. The functional group identifier is OR, so the 816 travels in its own GS envelope separate from orders and invoices.

EDI 816 Organizational Relationships files, under X12 release 004010 and functional group OR, carry a retailer's store and distribution center records to suppliers; loading each HL location with its ASI action and DTM effective date keeps the supplier's ship-to master within one business day of the retailer's.

For suppliers, the practical payoff is a ship-to master that stays aligned with the retailer's. Purchase orders usually reference a store or DC by number, not by full address. If the supplier's master holds the wrong address against that number, every downstream document inherits the error: the pick label, the bill of lading, the advance ship notice and the carrier's rating zone.

Heading N1 loop, HL levels and nested N1 detail in an 816

The 816 has a short heading that identifies who is sending the list and a detail area made of repeating HL loops, one per location or level in the hierarchy. Each HL loop holds one or more N1 loops with the location's identity, address, contacts, dates and action.

The HL segment carries an ID in HL01 and the parent's ID in HL02, which lets a retailer show that a group of stores is served by a particular DC or rolls up to a regional buying office. N105, when used, states how the entity relates to its parent organisation, with codes such as parent, child, subsidiary or division. Not every retailer sends a hierarchy; many send a flat list of stores under one HL.

ISA*00*          *00*          *ZZ*RETAILERID     *ZZ*SUPPLIERID     *261002*0600*U*00401*000004512*0*P*>~
GS*OR*RETAILERID*SUPPLIERID*20261002*0600*4512*X*004010~
ST*816*0001~
BHT*0059*04*LOC-20261002-01*20261002~
N1*BY*EXAMPLE RETAIL HQ*92*0001~
HL*1**34*1~
N1*WH*EXAMPLE DC 07*92*DC07*01~
N4*COLUMBUS*OH*43217*US~
HL*2*1*34*0~
N1*ST*STORE 1184*92*1184*02~
N3*4410 EAST MAIN STREET~
N4*WHITEHALL*OH*43213*US~
REF*ZZ*0614141001184~
DTM*152*20261020~
ASI*2*001~
SE*14*0001~
GE*1*4512~
IEA*1*000004512~
-- Illustrative only. BHT01, HL03, N105 and REF usage are set by each retailer's
-- implementation guide. Here: BHT02 04 = Change; N103 92 = assigned by buyer;
-- HL03 34 = location record; DTM 152 = effective date of change;
-- ASI 2 / 001 = change (update) / change.

Read the retailer's own implementation guide before mapping. Guides narrow the standard by marking segments as used or not used, restricting code lists and fixing which hierarchy levels appear. A map built from the generic standard will accept files the retailer never sends and may misread the ones it does, especially where the guide repurposes REF or N2 for store formats or receiving hours.

Store numbers, D-U-N-S and GLN qualifiers in the N103 element

The N103 qualifier tells you what kind of identifier sits in N104, and the ship-to master must be keyed on the identifier the retailer uses on its orders. Pick the key from the 850 and 856 specifications, then store every other identifier the 816 supplies as a cross-reference.

• Qualifier 92: assigned by buyer or buyer's agent; usually the retailer's store or DC number, such as 1184 or DC07.
• Qualifier UL: a globally unique 13-digit code identifying a legal, functional or physical location, which is the GS1 Global Location Number.
• Qualifiers 1 and 9: D-U-N-S number and D-U-N-S with a four-character suffix; more common for legal entities and bill-to parties than for docks.
• Qualifier 91: assigned by seller; your own customer location code, rarely sent by the retailer but useful as the internal key.

Entity codes in N101 matter as much. ST is ship-to, BY is the buying party, BT is bill-to, SN is store, WH is warehouse and Z7 is mark-for. A retailer that sends stores as SN but orders with N1*ST must be mapped so both resolve to one record. How GLNs are allocated, validated and carried on GS1-128 labels is covered in our guide to GS1 Global Location Numbers; here the point is only which code becomes the master key.

Effective dates and ASI action codes for openings and closures

Every 816 record should be applied on its effective date, not on the day the file arrives. Store openings, relocations and closures are announced in advance, and applying a change early sends open orders to an address that is not yet receiving.

The ASI segment states what to do with the record. In X12 element 306, action code 1 is Add, 2 is Change (Update) and 3 is Delete; element 875 adds a maintenance type such as 001 Change, 002 Delete, 003 Add Full Item Detail or 024 Cancellation or Termination. DTM qualifiers such as 007 Effective, 036 Expiration and 152 Effective Date of Change give the date the action takes hold.

• Opening: ASI add with a DTM effective date; create the record inactive and activate it on the date, so early orders cannot route to an unopened store.
• Relocation: ASI change with a change-effective date; keep the old address active for orders shipping before the date and the new one after.
• Closure: ASI delete or an expiration date; block new orders after the date and flag open orders and in-transit shipments for review.
• Full refresh: some retailers resend the whole list; compare it with the master and treat records missing from the refresh as candidates for closure, not as automatic deletes.

Ship-to master updates from an X12 816 apply each ASI action at its DTM date: qualifier 152 sets when a change takes effect and 036 when a record expires, so a relocation sent on 2 October with a 20 October date keeps 18 days of open orders on the old address.

Feeding 816 records into order entry, WMS labels and carrier rating

A ship-to record is used by at least four systems, and each must read the dated version that applies on the ship date. If order entry has the new address but the transport system still rates to the old ZIP or PIN, the freight bill and the delivery both go wrong.

• Order entry: resolves the store number on each 850 to an active record for the requested ship date, and rejects orders for expired locations.
• WMS and labels: prints the ship-to and mark-for from the same record that the ASN will carry, so labels and EDI agree.
• Advance ship notice: the 856 repeats the ship-to with the same qualifier and ID the retailer sent, which the retailer uses to match receipts.
• Carrier rating and audit: the destination postal code decides the rating zone, so a stale code produces a rate that will not match the carrier's invoice.

How an unprocessed change became a failed store delivery

Most failed deliveries traced to master data come from a change that was received but not applied. A 997 acknowledgment confirms the file's syntax, not that your business system loaded every record, so the control has to sit after the translator.

1. 2 October, 06:00: the retailer sends interchange 000004512, an 816 with store 1184's new address, ASI change and DTM 152 effective 20 October.
2. 2 October, 06:04: the translator validates the file and sends a 997 with code A; the map writes the record to staging, but the ERP load job only processes ASI add records, so the change is skipped without an error.
3. 21 October, 13:10: purchase order 4500921 for store 1184 ships; the bill of lading and the 856 carry the old address and ZIP 43213 from the unchanged master.
4. 22 October, 10:45: the carrier finds the old site closed, records a delivery exception and holds the six pallets at its terminal; reconsignment to the new address completes on 23 October, a day after the delivery window.
5. Control added: the load job now handles all ASI actions, a daily report compares staged 816 records with the master, and any unapplied record older than one business day raises an alert.

Our guide to logistics master data governance covers ownership, effective boundaries and conflict priorities across all logistics masters. This article narrows that to one inbound feed, the retailer's 816, and to the specific segments, codes and load checks that keep its ship-to records current.

India: GSTIN, PIN and state code on every ship-to record

The 816 is an ANSI X12 transaction most common in US retail; this article does not assume Indian buyers send it. Whatever the source of an Indian ship-to list, each record needs a GSTIN or URP, a PIN and a state code that agree, because the e-invoice and e-way bill both validate them.

NIC's e-invoice API, version 1.03, defines a ShipDtls object with Gstin, legal name, trade name, two address lines, location, PIN and state code. In that published version Gstin is optional while the legal name, first address line, location, six-digit PIN and state code are mandatory. Later schema versions may tighten these flags, so confirm the version your IRP provider runs before mapping.

Ship-to master records for Indian retail stores hold GSTIN or URP, PIN and state code together; GSTN's 20 May 2026 e-way bill advisory requires Ship To GSTIN on bill-to/ship-to movements, and NIC e-invoice schema 1.03 requires a six-digit PIN and state code in ShipDtls.

On e-way bills the requirement is firmer. GSTN's advisory of 20 May 2026 made the Ship To GSTIN a mandatory data element in bill-to/ship-to e-way bills, with the value URP where the consignee is unregistered. The advisory set production deployment of the API changes for 15 June 2026; check the e-way bill portal for current enforcement before relying on the validation. The details of generating e-way bills from the invoice are in our guide to e-way bills from e-invoice IRN.

• Place of supply: under Section 10(1)(a) of the IGST Act, goods that move are supplied where the movement ends for delivery; under 10(1)(b), goods delivered on a third person's direction are deemed received by that person, at its principal place of business.
• Consequence for the master: a bill-to/ship-to sale needs two linked records, the directing buyer's registration and the store's delivery details, rather than one address.
• State and PIN agreement: the first two digits of a GSTIN are the state code, so the store's state code must equal them, and its PIN should belong to the same state, a pairing worth validating before any e-invoice or e-way bill call.

Cost of a stale ship-to record in Ohio and in Karnataka

A single misdirected store delivery typically costs several hundred dollars or tens of thousands of rupees once reconsignment, extra freight, handling and customer charges are added. The figures below are illustrative; replace them with your carrier's accessorial schedule and the retailer's vendor terms.

Neither figure includes the sale lost when the shelf stays empty for a promotion, which retailers often measure and suppliers rarely see. The cost of the control, a load job that handles all action codes and a daily comparison report, is a few days of integration work, which is why stale ship-to records are among the cheapest delivery failures to remove.

Checks a translator enforces and calls a master data analyst makes

Most 816 checks are mechanical and belong in the translator or the load job. Matching an unfamiliar address to an existing location, or deciding whether a missing store in a full refresh has really closed, needs a person with access to the account team.

Go-live checklist for a new 816 trading partner

Treat the first 816 from a new retailer as a data migration, not just a new map. Reconcile the initial file against your existing customer locations before activating anything, and prove that changes and deletes load as well as adds.

For broader onboarding steps, such as connectivity, test cycles and partner sign-off, see our EDI trading partner onboarding checklist, with more EDI explainers collected on the Logistics and Supply Chain section.

Need 816 loads, dated ship-to switching and GSTIN checks wired into order and transport systems? List your retail accounts, translator and ERP on our project enquiry page and our integration team will size the effort.