PlainEDI
← Back to Guides

Best Buy Edi 856

By Alexander Georges|Updated August 7, 2026
TL;DR: This guide explains Best Buy EDI 856 (ASN) processing, common hierarchy and quantity pitfalls, and step-by-step conversion to CSV for downstream systems. It includes real-world 856 X12 examples, annotated code, a CSV mapping table, five+ common errors with fixes, and integration tips using PlainEDI validation to prevent rejections.

What This Is

This guide is a comprehensive, practical reference for generating, validating, and troubleshooting Best Buy EDI 856 Advance Ship Notices (ASNs). It focuses on Best Buy-specific expectations for 856 structure, hierarchical sequencing (HL loops), item identification and quantity reporting, carrier and pallet-level information, and how those elements map to accounting, warehouse, and retail systems when converting 856 to CSV and other formats.

The examples in this guide are realistic X12 856 transactions with explicit segment-level annotations and conversion steps that you can apply to automated EDI pipelines. The guide explains why common Best Buy rejections occur and provides step-by-step corrective actions, plus validation strategies using PlainEDI to reduce rework and chargebacks. Best Buy vendor program data referenced in this guide was Last Updated: 2026-05-17; Verify current requirements with the Best Buy vendor portal before final submission.

Who This Is For

This guide targets EDI specialists, warehouse operations engineers, ERP integrators, and vendor compliance teams responsible for producing or consuming Best Buy 856 ASNs and converting them into CSV/ERP-friendly formats.

Key Segments Explained

Below are the core 856 segments you will handle frequently when working with Best Buy ASNs. Each explanation includes the role of the segment, Best Buy expectations, and how errors typically arise.

  • BSN – Beginning Segment for Ship Notice

    The BSN segment provides the ASN control number and shipment purpose (e.g., Original, Replacement). Best Buy requires a unique BSN03 (Shipment Identification) per ST/856 transaction and consistent use of BSN01 (Purpose Code) values: 00 for Original shipments and 05 for Replacement when applicable. Errors occur when BSN03 duplicates prior ASNs or when characters exceed field length.

  • HL – Hierarchical Level

    The HL segments create the shipment/order/item tree. Best Buy enforces strict HL sequencing: parent HL segments must appear before child HL segments and HL IDs must be unique within the transaction. Common Best Buy rejections relate to incorrect HL level codes (Shipment=1, Order=2, Item=3) and non-sequential HL parent references.

  • LIN – Item Identification

    The LIN segment carries the item identifier (UPC, GTIN, SKU). Best Buy expects GTIN/UPC in the correct composite position and the qualifier code that identifies the identifier type (e.g., UP for UPC, IN for Buyer's Item Number). Errors arise when a vendor sends the wrong qualifier or an unsupported identifier type.

  • SN1 – Item Detail (Ship Notice)

    The SN1 segment reports shipped quantity and unit of measurement (UOM). Best Buy requires UOM consistency with purchase order units and carton/pallet-level quantities that match TD1 and MAN count pairs when pallet-level manifests are used. Quantity mismatches between SN1 and child HL sums frequently produce chargebacks.

  • TD1/TD5 – Carrier and Packaging

    TD1 reports packing detail (weight, number of pieces), and TD5 identifies the carrier. Best Buy requires trailer/pro number in REF or TD5 depending on EDI agreement; missing PRO numbers or incorrect carrier SCAC codes generate transportation compliance exceptions.

Example EDI Snippet

ISA*00*          *00*          *ZZ*SENDERID      *ZZ*BESTBUYID     *210517*1230*U*00401*000000905*0*T*:~
GS*SH*SENDERID*BESTBUYID*20210517*1230*905*X*004010~
ST*856*0001~
BSN*00*ASN90520210517*20210517*1230~
HL*1**S~
TD1*CTN25*10~
TD5*B*2*UPS*G~
REF*BM*PRO1234567~
N1*ST*BEST BUY STORE 0123*92*1000123~
HL*2*1*O~
PRF*4500123456~
HL*3*2*I~
LIN**UP*00812345678905*VN*SKU12345~
SN1**20*EA~
MAN*CP*756321A~
SE*13*0001~
GE*1*905~
IEA*1*000000905~

Line-by-line explanation:

  • ISA...~ and GS...~: Transport envelope headers. Validate ISA13 control number uniqueness and ISA15 usage indicator per Best Buy agreement.
  • ST*856*0001~: Transaction set header with control number 0001. ST02 must match SE02.
  • BSN*00*ASN90520210517*20210517*1230~: ASN purpose code 00, ASN ID ASN90520210517, date/time. ASN ID must be unique per vendor account.
  • HL*1**S~: HL 1 is the shipment level; parent ID blank and level code 'S'.
  • TD1*CTN25*10~: 10 cartons of 25 units per carton? In X12, TD1 conveys packaging — verify element usage; provide counts in the expected element positions.
  • TD5*B*2*UPS*G~: Carrier qualifier and ID for UPS. Verify SCAC mapping.
  • REF*BM*PRO1234567~: Reference number, here the bill of lading/PRO number.
  • N1*ST*BEST BUY STORE 0123*92*1000123~: Ship-to name qualifier ST with Best Buy store ID qualifier 92.
  • HL*2*1*O~: HL 2 is the order level referencing parent HL 1.
  • PRF*4500123456~: Purchase Order reference number. PRF01 must match the PO Best Buy sent.
  • HL*3*2*I~: HL 3 is the item level referencing order HL 2.
  • LIN**UP*00812345678905*VN*SKU12345~: UPC qualifier UP and vendor SKU qualifier VN.
  • SN1**20*EA~: Shipped 20 Each units. SN102 may be blank when SN103 contains quantity.
  • MAN*CP*756321A~: Manufacturer's assigned container/package ID (pallet carton ID). Best Buy uses MAN segments to match physical labels.
  • SE*13*0001~, GE*1*905~, IEA*1*000000905~: Transaction, functional group, and interchange trailers; control counts must reconcile with headers.

CSV Output Example

The table below shows a practical CSV mapping for downstream warehouse ingestion when converting the EDI 856 to CSV. This example flattens hierarchical data (shipment, order, item, pallet) into a single row per item-per-pallet where applicable.

ShipmentID PO StoreID CarrierSCAC PRO HL_Level ProductID_Type ProductID QtyShipped UOM CartonID PalletCount
ASN90520210517 4500123456 1000123 UPS PRO1234567 Item UPC 00812345678905 20 EA 756321A 1

Step-by-Step Conversion Process

  1. Extract and validate envelope headers
    1. Parse ISA and GS segments; confirm ISA/GS identifiers match Best Buy trading partner values.
    2. Verify ISA control number and date/time in ISA and GS fields to ensure uniqueness.
    3. Use understanding X12 delimiters and structure to configure parser delimiters when input files use non-standard characters.
  2. Validate ASN header and uniqueness
    1. Read BSN for ASN ID and purpose. Compare BSN03 to your submission history to prevent duplicates.
    2. Check that ST02 equals SE02 and that transaction set counts in SE are accurate.
  3. Build HL hierarchy and detect sequence errors
    1. Traverse HL segments in order and validate that child HLs reference a previously-defined parent HL ID. For example, if HL ID 3 has parent 2, HL 2 must exist earlier in the file.
    2. Run a deterministic parser, not a naive line-scan: ensure your HL parser tracks level codes ('S', 'O', 'I') and enforces one HL root (shipment) per ST for Best Buy if required by the trading partner agreement.
  4. Map item-level data to CSV fields
    1. For each item-level HL, read LIN, SN1, MAN, and REF segments to gather identifiers, quantities, and packaging IDs.
    2. Flatten the hierarchical structure into rows using a deterministic rule set: one CSV row per MAN + LIN combination when container IDs exist; otherwise one row per LIN.
  5. Perform Best Buy-specific validation rules
    1. Confirm the PO number from PRF matches Active PO list for the store/ship-to. If not, flag and halt ingestion.
    2. Confirm sum of item-level SN1 quantities equals the order-level totals if Best Buy requires aggregated confirmation.
    3. Validate carrier SCAC and PRO number presence per the TD/REF requirements in your Best Buy trading partner agreement.
  6. Generate CSV and reconcile control totals
    1. Populate CSV columns as per the mapping table above.
    2. Reconcile counts: total rows, total cartons, and total shipped quantities should match values in TD1, MAN, and BSN controls where applicable.
  7. Validate with PlainEDI and submit
    1. Upload the prepared 856 or the converted CSV to PlainEDI to run automated Best Buy validation rules. PlainEDI checks HL hierarchy, SN1 vs. TD1 sums, and ISA/GS control consistency.
    2. Fix any validation errors reported by PlainEDI, regenerate the CSV, and then submit the ASN to Best Buy via your agreed transport (AS2 or VAN).

Common Errors and Fixes

Below are frequent Best Buy 856 errors with clear solutions. Each bullet includes an error description, probable cause, and a corrective action.

  • Error: HL parent reference invalid (functional acknowledgment rejects). Cause: Child HL references an HL ID that does not exist or appears later. Fix: Reorder HL segments so parent occurs before child, ensure HL IDs are unique and sequential. Refer to how to fix EDI 856 hierarchy errors.
  • Error: Duplicate BSN03/ASN ID (Best Buy rejects as duplicate). Cause: Re-sent ASN with same shipment identifier. Fix: Generate a new ASN ID per shipment or append vendor unique suffixes if resubmitting; track ASN IDs in your system to avoid duplication.
  • Error: SN1 quantity does not match summed item quantities (chargeback risk). Cause: Incorrect aggregation across cartons/pallets or misuse of SN102/SN103 fields. Fix: Recalculate quantities at item HL level and ensure SN1 reports shipped quantity in SN102 (or SN103 per syntax). Use total reconciliation before submission.
  • Error: Missing PRO or invalid carrier SCAC (transport compliance exception). Cause: REF/TD5 segments not populated per Best Buy rules. Fix: Populate PRO in REF*BM or where Best Buy requires it; verify SCAC codes against Best Buy carrier list. See carrier mappings in your trading partner agreement.
  • Error: Wrong product identifier qualifier (Best Buy reports item not recognized). Cause: Sending SKU under UPC qualifier or using unsupported qualifiers. Fix: Use the correct qualifiers: UP for UPC/GTIN, VN for vendor SKU when permitted. Validate identifier types against Best Buy item master.
  • Error: ISA/GS control number mismatch (997 rejects). Cause: Incorrect control numbers in SE/GE/IEA segments. Fix: Ensure ST02 equals SE02; GS06 equals GE02; IEA02 equals ISA13. Use deterministic control-numbering routines. Consult reading 997 functional acknowledgments and resolving EDI 997 rejection codes for triage steps.

Related Resources

FAQ

Q: What is the required HL loop order for Best Buy 856?

Best Buy requires HL segments ordered from shipment (level code 'S') to order ('O') to item ('I'). Each child HL must reference a previously defined parent HL ID in the third element. Validate HL parent references and ensure unique HL IDs within a transaction. Use how to fix EDI 856 hierarchy errors for automated repair steps.

Q: How do I choose whether to send pallet-level MAN segments?

Send MAN segments when you provide per-container serials or SSCC pallet IDs. Best Buy uses MAN values to match carton/pallet barcodes during receiving. Include MAN per package/pallet and ensure MAN IDs are encoded on the physical label. Validate MAN presence with PlainEDI to avoid store-level scanning mismatches.

Q: Which identifier should I use in LIN for Best Buy?

Use the UPC/GTIN qualifier (UP) when sending barcoded product UPCs. Use vendor SKU qualifiers (VN) only if permitted by Best Buy and when the SKU is in Best Buy’s item master. Confirm identifier expectations on the PO and in Best Buy’s vendor portal.

Q: What causes Best Buy to reject an ASN as duplicate?

Rejections as duplicates occur when BSN03 (Shipment Identification) repeats a previously submitted ASN ID for the same Vendor ID. Implement unique ASN ID generation per shipment and maintain a submission log. If resubmitting a corrected ASN, use a new ASN ID and reference the original in an explanatory segment if required by Best Buy policy updated Last Updated: 2026-05-17. Verify current rules in the vendor portal.

Q: How do I map nested HL structures into a flat CSV for WMS import?

Flatten HL structures by establishing a deterministic rule: include parent shipment and order fields on each item row. When pallet/container IDs exist, generate one CSV row per item-per-container with columns for shipment ID, PO, store, product ID, quantity, UOM, and container ID. Reconcile aggregated counts with TD1 and SN1 totals prior to import. Use EDI-to-CSV patterns as transformation templates.

Q: What transport data does Best Buy require in 856 for truckload shipments?

Include TD1 for packing counts, TD5 for carrier identification, and REF*BM or a trading-partner-specific REF qualifier for PRO/trailer numbers. Confirm where to place PRO numbers in your Best Buy SLA; use PlainEDI to validate that the carrier SCAC and PRO/BL are present to prevent transportation compliance exceptions.

Q: How important is SN1 UOM consistency and how should it be validated?

SN1 UOM must match the UOM used on the PO and within your packing configurations. Validate that SN1 UOMs are consistent across item-level HLs and sum correctly into order-level totals if Best Buy requires aggregated matching. Use automated validation rules in PlainEDI to detect UOM mismatches before submission.

Q: What penalties exist for ASN non-compliance with Best Buy?

Best Buy enforces compliance penalties for OTIF/ASN accuracy and other vendor program breaches. Penalties include deductions and chargebacks for incorrect ASNs, missing or incorrect cartoning/pallet data, and ASN timing violations. Best Buy vendor program information referenced Last Updated: 2026-05-17. Verify current penalty amounts and thresholds with the Best Buy vendor portal for up-to-date details.

Final Checklist and Best Practices

  • Always validate HL hierarchy and control counts before submission.
  • Ensure unique BSN03 per ASN and consistent ST/SE control numbers.
  • Use correct identifier qualifiers in LIN and confirm identifiers against Best Buy item master.
  • Include pallet/container MAN segments when physical labels are used at receiving.
  • Validate carrier SCAC and PRO fields per Best Buy transport rules.
  • Run automated validations via PlainEDI to catch HL, quantity, and control-count issues before sending to Best Buy.

Best Buy-specific guidance in this guide is based on the Best Buy vendor program notes Last Updated: 2026-05-17. Verify current requirements with the Best Buy vendor portal to confirm any changes since that effective date.

Call to Action

If you want automated validation and fast conversion of Best Buy 856 files to CSV or your ERP format, upload a sample to PlainEDI to run Best Buy-focused validation rules and get a CSV ready for your warehouse management or accounting systems.