EDI Data Mapping

EDI mapping organizes information by matching data fields from your internal system to the correct fields in the EDI standard. Good mapping is the difference between an integration that ships in a week and one that drags for a quarter.

What gets mapped

Names and addresses (party identifiers, ship-to, bill-to).
Order metadata (PO number, date, currency, terms).
Line items (SKU, quantity, unit price, UOM).
Totals, taxes and discounts.
References that link an invoice back to a purchase order, an ASN to a shipment, etc.

One map per partner, per document

Mappings are partner-specific because trading partners interpret the standard differently. One retailer might put the store number in N1*ST*92; another puts it in REF*ST. EDIFlux mappings are scoped to a partner and document type so these variations stay contained.

Reusable transformations

Most mappings consist of small, reusable transformations: trim whitespace, convert dates from CCYYMMDD to ISO, pad short codes, look up an internal SKU from a partner SKU. EDIFlux stores these as JSON rules attached to the mapping.

Validation as part of mapping

A good map doesn't just move data — it validates it. Missing required fields, lengths that exceed the standard's limits, codes not in the allowed list. Catching these at map time prevents a 997 rejection from your partner later.