PlainEDI
← Back to Guides

Best Buy Edi 855

By Alexander Georges|Updated August 4, 2026
TL;DR: This guide explains Best Buy EDI 855 (Purchase Order Acknowledgment) end-to-end: required segments, real-world examples for full/partial/cancel acknowledgments, step-by-step conversion to CSV, common rejection causes and fixes, and how to validate with PlainEDI to prevent errors. Use the provided annotated EDI samples and CSV mapping to implement automated acknowledgments and to troubleshoot 997 rejections efficiently.

What This Is

The Best Buy EDI 855 is the X12 Purchase Order Acknowledgment transaction set vendors use to confirm acceptance, change, or rejection of one or more purchase orders sent by Best Buy. The 855 communicates per-PO and per-line-item status (accepted, acknowledged with change, shipped, backordered, cancelled), dates such as promised ship or delivery, and reference numbers required by Best Buy vendor compliance programs.

This guide gives an operational playbook: why common 855 errors occur, exact segments Best Buy expects, line-by-line annotated EDI examples for common scenarios (full acceptance, partial ship, cancel), CSV output examples for downstream systems, validation steps to avoid 997 rejections, and troubleshooting with concrete fixes. Best Buy vendor program details were last updated effective 2026-05-17; Verify current requirements with the Best Buy vendor portal before production submissions.

Who This Is For

This guide targets EDI specialists, integration engineers, supply chain operations, and vendor onboarding teams working with Best Buy who need to generate correct 855 acknowledgments or parse inbound 855s from Best Buy for internal systems such as ERP, WMS, or order management.

Key Segments Explained

The 855 has header, party, summary, and detail loops. Below are the segments you will handle most often for Best Buy PO acknowledgments.

  • ST — Transaction Set Header

    ST marks the start of the 855 transaction and carries the transaction set control number (ST02). Best Buy validates ST02 against SESE trailer values. Failure to match ST/SE control numbers triggers 997 AK5 level rejects.

  • BAK — Beginning Segment for Purchase Order Acknowledgment

    BAK contains the acknowledgment type code (BAK01), the PO number (BAK03/BAK04 areas), and the acknowledgment date (BAK05). Common BAK01 values: '00' (Original), '01' (Canceled), '05' (Accepted). Use the proper code to indicate full acceptance, cancellation, or change. Incorrect BAK01 or missing PO number is a frequent compliance error.

  • REF — Reference Identification

    REF conveys additional IDs like Best Buy's internal Reference ID, Vendor Order Number, or ASN references. Best Buy often expects specific REF qualifiers per vendor setup. If REF qualifiers do not match Best Buy's mapping, the 855 may be treated as invalid by downstream systems.

  • DTM — Date/Time Reference

    DTM carries promised ship dates, delivery dates, or acknowledgement dates. Best Buy frequently requires specific DTM qualifier codes (e.g., '002' = Delivery Requested). Sending the wrong date qualifier causes misinterpretation of expected ship/delivery windows and operational issues.

  • PO1 — Baseline Item Data

    PO1 is the line-level segment that references PO line number, quantity ordered, UOM, and item identifiers. In an 855, PO1 is paired with ACK (Line Item Acknowledgment) to convey accepted quantity, backorder quantity, or cancellation status.

  • ACK — Line Item Acknowledgment (X12)

    ACK provides the line-level status code (accepted, rejected, changed), acknowledged quantity, and measurement unit. Use standard ACK codes (for example, 'IA' = Item accepted, 'IP' = Item partially accepted, 'RE' = Item rejected) per trading partner agreement. Incorrectly formatted ACK segments are a common cause of EDI processing failures.

Example EDI Snippet

The following 855 example shows a PO with three lines: line 1 accepted in full, line 2 partially accepted (backorder), line 3 cancelled. This is an illustrative example for Best Buy integration. Replace ISA/GS identifiers with your production/translator IDs.

ISA*00*          *00*          *ZZ*VENDORID      *ZZ*BESTBUY        *230101*1200*^*00501*000000905*0*T*:~
GS*PR*VENDORID*BESTBUY*20230101*1200*905*X*005010~
ST*855*0001~
BAK*00*AC*PO123456**20230101~
REF*IA*BESTBUYREF123~
DTM*002*20230110~
N1*ST*BEST BUY*92*12345~
PO1*1*10*EA*15.00*VN*1234567890123~
ACK*IA*10*EA~
PO1*2*20*EA*12.00*VN*2345678901234~
ACK*IP*5*EA*BO*15~
PO1*3*5*EA*20.00*VN*3456789012345~
ACK*RE*0*EA~
CTT*3~
SE*12*0001~
GE*1*905~
IEA*1*000000905~

Line-by-line explanation:

  • ISA*...~ — Interchange header: control identifiers and default delimiters. Ensure correct sender/receiver IDs and control number.
  • GS*PR*VENDORID*BESTBUY*20230101*1200*905*X*005010~ — Functional group for Purchase Order Acknowledgment.
  • ST*855*0001~ — Transaction start; ST02 = '0001' must equal SE02.
  • BAK*00*AC*PO123456**20230101~ — BAK01='00' (original), BAK02='AC' (acknowledgement code), BAK03 is the PO number, BAK05 is ack date.
  • REF*IA*BESTBUYREF123~ — Best Buy reference ID. Qualifier 'IA' is example; use qualifier assigned by Best Buy.
  • DTM*002*20230110~ — DTM qualifier 002 = delivery requested (example).
  • PO1/ACK pairs — each PO1 defines the line and ACK reports the accepted/cancelled/backorder qty with status code.
  • CTT*3~ — Total line count (3 lines).
  • SE*12*0001~ — Transaction set trailer; SE02 matches ST02.

CSV Output Example

When converting 855 to CSV for an ERP or order-management import, normalize header and line items into two tables. Below is a combined representation mapping key fields.

PO Number PO Line Vendor Item Ordered QTY Ack Status Ack QTY Ack Reason Promised Date
PO123456 1 1234567890123 10 Accepted 10 2023-01-10
PO123456 2 2345678901234 20 Partial 5 Backorder 2023-01-10
PO123456 3 3456789012345 5 Rejected 0 Cancelled 2023-01-10

Step-by-Step Conversion Process

  1. Detect delimiters and parse interchange
    1. Read ISA segment to determine element separator (position 4), component separator and segment terminator (last char of ISA). Configure parser accordingly.
    2. Validate ISA/GS sender/receiver IDs against Best Buy trading partner setup. Incorrect IDs cause routing failures and may be rejected downstream.
  2. Validate transaction envelope and control numbers
    1. Verify ST02 equals SE02 and GS06 equals GE02 to ensure control integrity. If mismatch, halt processing and generate exception report.
    2. Record ISA/GS/ST control numbers for audit and 997 tracing.
  3. Extract header fields into CSV header rows
    1. Map BAK03 to CSV PO Number column. Map BAK05/DTM qualifiers to a Promised Date column. Map REF qualifiers per Best Buy mapping to reference columns.
    2. If BAK01 indicates cancellation, set a header-level status flag in CSV for downstream workflow.
  4. Process PO1/ACK line pairs to create line-level rows
    1. For each PO1 element, capture PO line (PO1-01), quantity ordered (PO1-02), UOM (PO1-03), and items (PO1-07+). For Best Buy, ensure item identifiers match the vendor's assigned UPC/GTIN or Best Buy item ID as specified in your trading partner setup.
    2. Map ACK values to CSV columns: ACK status code -> human-readable status, ACK quantity to AcceptedQty, and any qualifiers (e.g., backorder amount) into ReasonCode or Remarks.
  5. Apply Best Buy-specific business rules
    1. If Best Buy requires certain REF qualifiers or prohibits specific ACK codes, transform or reject the file accordingly. Use a configurable ruleset rather than hard-coded values.
    2. Enforce date formats (YYYY-MM-DD) and UOM normalization (EA -> Each) during export to CSV to reduce import errors in ERP systems.
  6. Run schema & business validation, generate 997 if required
    1. Perform X12 schema validation (segment existence, element data type, mandatory segments). If validation fails, create an internal rejection or prepare a 997 functional acknowledgment to send back to Best Buy where applicable.
    2. Log all validation errors with control numbers and line references for troubleshooting.
  7. Output CSV and audit trail
    1. Export a normalized CSV file per the table above. Keep a complete EDI-to-CSV mapping log that includes original segments for each CSV row to support audits and dispute resolution.
    2. Upload or push CSV to ERP/WMS and retain EDI files in a secure archive for at least the vendor agreement retention period.

Common Errors and Fixes

  • Error: ST/SE control number mismatch (AK5/AK3 errors in 997)

    Cause: ST02 not equal to SE02 or transaction truncated. Fix: Rebuild transaction ensuring SE02 equals ST02 and that segment count in SE01 matches actual segment count. Re-run validation before sending.

  • Error: Invalid/refused PO number in BAK (997 AK2)

    Cause: PO number format differs from Best Buy's expected PO format or REF mapping mismatch. Fix: Normalize PO number formatting (remove leading zeros if Best Buy expects none) and verify REF qualifier configuration. Confirm with Best Buy vendor portal mapping.

  • Error: Missing ACK segment for a PO1 line

    Cause: Parser expects PO1/ACK pair; missing ACK causes ambiguous line status. Fix: Ensure your EDI generator emits an ACK for each PO1, even if the ACK indicates full acceptance (ACK*IA*qty*UOM). Add unit tests for line pairing.

  • Error: Wrong DTM qualifier or date format

    Cause: Using incorrect DTM qualifier (e.g., sending promised ship date with incorrect code) or invalid date format. Fix: Use qualifiers per Best Buy mapping and output dates as YYYYMMDD in the DTM segment; convert to canonical ISO in CSV export.

  • Error: Invalid REF qualifier / missing Best Buy reference

    Cause: Best Buy requires a specific REF qualifier (e.g., 'IA' or 'ZZ') which doesn't match vendor setup. Fix: Confirm required REF qualifiers in Best Buy vendor documents and update generator mappings. Use PlainEDI validation to check REF presence pre-send.

  • Error: 997 AK5 R (Transaction Set Not Accepted) with AK3 pointing to specific segment

    Cause: Segment-level syntax error, wrong element count, or invalid enumeration. Fix: Parse AK3 to locate the offending segment number then validate that segment against the 855 segment definitions; correct element separators or missing composite elements; re-validate.

Related Resources

FAQ

Q: What is the primary purpose of a Best Buy EDI 855?

The Best Buy EDI 855 formally communicates whether the vendor accepts, partially accepts, changes, or rejects the purchase order. It provides per-line item status, acknowledged quantities, and dates that Best Buy uses for planning and fulfillment. Use the 855 to confirm commitments and to supply updated ship or delivery dates.

Q: Which segments are mandatory in a Best Buy 855?

Mandatory segments commonly include ST/SE, BAK (with PO number), at least one PO1/ACK line pair for each PO line, and CTT for line totals. Best Buy-specific mandates are defined in the vendor EDI requirements; check the Best Buy vendor portal for your trading partner profile. Effective information was last updated 2026-05-17; Verify current requirements with the Best Buy vendor portal.

Q: How do I indicate a backorder or partial shipment in an 855?

Use the ACK segment paired with PO1 to indicate partial acceptance: include ACK status code for partial ('IP' or partner-assigned code), the accepted quantity, unit of measure, and optionally a qualifier or REMARK segment indicating backorder quantity. Also provide an updated DTM for expected ship/delivery date.

Q: What common 997 rejection codes should I watch for when sending 855s to Best Buy?

Watch for AK5 codes indicating transaction acceptance or rejection (A=Accepted, R=Rejected). AK3 provides the segment where syntax error occurs and AK4 provides element-level issues. Use the AK3/AK4 details to pinpoint errors, then correct ST/SE counts, missing segments, or data-type mismatches.

Q: How should I map an 855 to CSV for ERP ingestion?

Map header-level fields (PO number, ack date, overall ack code) into a header CSV, and map each PO1/ACK pair into line-level rows including PO line, vendor item identifier, ordered qty, ack qty, ack status, and promised date. Normalize UOM and date formats in CSV to match ERP import requirements.

Q: What steps prevent common 855 processing failures?

Implement these practices: 1) Validate delimiters from ISA before parsing, 2) enforce ST/SE number consistency, 3) require a 1:1 PO1-to-ACK pairing by automated checks, 4) run X12 schema plus Best Buy business-rule validations before sending, and 5) run automated unit tests that simulate 997 AK5 rejections. Use a validation tool such as PlainEDI to catch issues pre-transmission.

Q: Can I use the same EDI mapping for all Best Buy purchase orders?

Use a common mapping skeleton, but review Best Buy trading partner setup because qualifiers and required REF/DTM codes can vary by business unit, product type, or program. Maintain configuration-driven qualifier mappings to handle variations without code changes.

Q: If Best Buy changes requirements, how will I know?

Best Buy posts vendor program updates to its vendor portal. The vendor requirements referenced here were last updated effective 2026-05-17; Verify current requirements with the Best Buy vendor portal. Subscribe to vendor portal announcements and maintain an internal change-control process to apply updates quickly.

Practical Case Studies

Case study 1 — Partial Acceptance with earlier ship date change: A vendor receives PO for 100 units across two SKUs and can only supply 60 units total due to inventory. The vendor sends an 855 with two PO1/ACK lines: first ACK shows accepted 40, second ACK shows accepted 20 and a DTM with new promised date 5 days later. Outcome: Best Buy's planning system consumes the 855 and updates replenishment orders. Prevent rejection by validating REF qualifiers and ST/SE controls before sending.

Case study 2 — Cancellation and resubmission: Vendor must cancel an entire PO that was already confirmed. Send BAK with cancellation code at header and ACK segments with RE (rejected) status per line. Create an audit entry and notify purchasing. Re-submit a corrected PO on receipt of a revised purchase order from Best Buy.

How PlainEDI Helps

PlainEDI provides multi-layer validation to prevent the most common Best Buy 855 errors: delimiter detection from ISA, ST/SE control consistency checks, required segment presence checks (BAK, PO1/ACK), and Best Buy-specific qualifier validation. PlainEDI's pre-send validator highlights AK3/AK4-style segment and element errors and offers suggested corrections so you correct issues before the 855 reaches Best Buy.

Use PlainEDI to preview CSV mappings from EDI and to automate mapping templates for Best Buy. PlainEDI maintains an audit trail of original EDI files, conversion outputs, and validation reports which supports dispute resolution and compliance audits.

Closing Checklist Before Production

  • Confirm ISA/GS IDs match trading partner setup in Best Buy vendor portal.
  • Ensure ST02 equals SE02 and segment counts are correct.
  • Validate every PO1 has a corresponding ACK and that status codes match Best Buy mapping.
  • Standardize REF qualifiers and DTM codes per Best Buy requirements last reviewed effective 2026-05-17; Verify current requirements with the Best Buy vendor portal.
  • Run a final pass through PlainEDI for schema + business validations and CSV preview.

Ready to validate or convert your Best Buy 855 files? Upload a sample to PlainEDI for automated validation, CSV conversion previews, and instant error reports.