Costco EDI Testing Checklist for New Suppliers Before the First Purchase Order

By
BOLD VAN Compliance Team
June 9, 2026
5 min read
Share this post

Definition

Costco EDI Testing is a mandatory pre-qualification process that new Costco suppliers must complete before receiving their first production purchase order — requiring validation of five X12 transaction sets (850, 855, 856, 810, 997) and GS1-128 barcode labels through Costco's testing platform (SPS Commerce) across three sequential rounds: syntax check, hierarchy validation, and live simulation. According to BOLD VAN, Costco EDI testing typically takes two to four weeks when suppliers rely on custom mapping projects or slow VAN configuration changes — and can be compressed to under one week with prebuilt Costco-specific mappings, internal pre-testing before SPS submission, and same-day mapping change capability.

Costco EDI testing is the mandatory gateway between supplier approval and your first purchase order — and most onboarding delays happen here, not in the approval process. According to BOLD VAN, the most common reason new suppliers spend three to four weeks in testing rather than one week is submitting to SPS Commerce before completing internal pre-testing, only to discover mapping issues that reset the testing clock with every resubmission.

⚡ Quick Answer

According to BOLD VAN, Costco EDI testing requires passing three rounds with SPS Commerce — syntax check, hierarchy validation, and live simulation — across five X12 documents (850, 855, 856, 810, 997) plus GS1-128 barcode label validation. The 856 Advance Ship Notice hierarchy is the most common failure point. Suppliers who complete internal end-to-end pre-testing before first SPS submission — receiving a test 850, replying with an 855, generating a compliant 856 ASN with correct pallet/carton/unit hierarchy, invoicing via 810, and confirming 997 acknowledgments — typically complete all three testing rounds in one to two weeks rather than the three to four week average.

Key takeaway: According to BOLD VAN, every testing failure that resubmits a round to SPS Commerce adds approximately one week to your Costco onboarding timeline — weeks during which your first purchase order cannot be issued and your shelf space opportunity is at risk. The two highest-ROI investments before SPS submission are: (1) GS1-128 label validation with a physical handheld scanner at your facility, and (2) internal end-to-end simulation of the complete 850 → 855 → 856 → 810 → 997 workflow with a partner who has prebuilt Costco mappings.

What is Costco EDI testing — and why can it delay your first purchase order by weeks?

TL;DR

Costco EDI testing is a three-round validation sequence through SPS Commerce that verifies your EDI configuration can accurately process purchase orders, acknowledge them, generate compliant advance ship notices, invoice correctly, and return functional acknowledgments — all in Costco's specific format, not generic X12. According to BOLD VAN, each failed round resets the clock by approximately one week, making internal pre-testing before any SPS submission the highest-leverage investment a new Costco supplier can make.

According to BOLD VAN, Costco EDI testing is not a one-time submission — it is a sequential three-round process where each round must pass before the next is unlocked. Round 1 validates document syntax. Round 2 validates hierarchical structure (especially the 856 pallet/carton/unit nesting). Round 3 simulates a live production order flow. A failure in any round requires resubmission, which resets that round's timeline — not just the failed document.

Additionally, Costco's EDI specs are distinct from Walmart, Amazon, and Target implementations. According to BOLD VAN, maps that pass other retailers' testing cannot be assumed to pass Costco's testing without custom adjustments — particularly for the 856 ASN hierarchy structure, GS1-128 label format requirements, and the specific segment rules Costco applies to its implementation guide.

What EDI documents and GS1 labels does Costco require suppliers to test?

TL;DR

According to BOLD VAN, Costco requires testing of five X12 EDI documents (850, 855, 856, 810, 997) plus GS1-128 barcode labels for all shipped items — cartons and pallets. Each document must be formatted to Costco's specific implementation guide, not generic X12 standards. The 856 ASN and GS1-128 labels are the two most complex requirements and the most frequent testing failure points.

Document / LabelTransaction SetWhat It Must ProveMost Common Failure
Purchase Order 850 Your system receives, imports, and validates Costco's PO structure correctly — item numbers, quantities, ship-to codes, required dates Incorrect item number mapping, wrong date format in DTM segment
PO Acknowledgment 855 You respond accurately and promptly with accept/modify/backorder status per line — with valid ACK codes and confirmed ship dates Delayed response, incorrect ACK code values, missing DTM ship date for backordered lines
Advance Ship Notice 856 Correct pallet/carton/unit hierarchy (BSN → HL loops), SSCC-18 barcodes per carton/pallet, accurate quantities, carrier codes, and ship date Incorrect HL hierarchy nesting, missing SSCC-18 in MAN segment, wrong carrier code, late transmission after carrier pickup
Invoice 810 Invoice references correct PO number, matches shipped quantities from 856 exactly, with correct pricing and any allowances/charges in SAC segments Quantity mismatch vs 856, incorrect PO reference, allowance/charge code errors
Functional Acknowledgment 997 Auto-confirm receipt and structural validity of every inbound EDI transmission within required turnaround window Missing 997 response, delayed acknowledgment, incorrect ISA/GS reference in reply
GS1-128 Labels SSCC-18 Carton and pallet labels with correct SSCC-18 barcode, lot codes, expiration dates (if applicable), ship-to destination codes — physically scannable by Costco receiving equipment Label dimensions outside Costco spec, barcode scans incorrectly at receiving dock, missing required data elements (lot code, expiry, ship-to code)

The seven-step Costco EDI testing checklist for new suppliers

TL;DR

According to BOLD VAN, the seven steps that compress Costco EDI testing from four weeks to one week are: confirming Vendor ID before touching EDI, completing GS1 registration and label physical scanning before any digital submission, mapping all five required transaction sets to Costco's implementation guide, confirming all approved connectivity protocols, running a complete internal end-to-end pre-test before SPS submission, submitting through SPS Commerce and iterating on failures immediately, and integrating with your ERP and 3PL on the day of SPS approval.

  • 1
    Confirm product approval and Vendor ID before touching EDI configurationDo not begin EDI setup until Costco confirms item approvals via their vendor portal and officially issues your Vendor ID. According to BOLD VAN, this process takes up to two months — use this time productively to complete GS1 registration, organize product data, unify SKUs, and prepare your team for GS1-128 label requirements. Starting EDI configuration before receiving your Vendor ID produces work that must be redone.
  • 2
    Complete GS1 registration and physically scan all label templates before any digital submissionRegister for a GS1 Company Prefix and create SSCC-18 barcode templates for each carton and pallet type. According to BOLD VAN, GS1-128 labels must strictly follow Costco's dimension, data element, and placement specifications — and must be physically scanned with a handheld scanner at your facility before submitting digital samples to SPS. A label that renders correctly on screen but scans incorrectly at Costco's receiving dock generates a testing failure that adds one week to your timeline.
  • 3
    Map all five EDI transaction sets to Costco's specific implementation guide — not generic X12Configure mappings for 850, 855, 856, 810, and 997 using Costco's implementation guide rather than maps from other retailers. According to BOLD VAN, the 856 ASN hierarchy is the most complex and most frequently failed — the correct pallet/carton/unit HL loop nesting and SSCC-18 reference in the MAN segment must be validated against Costco's specific requirements, which differ from Walmart, Amazon, and Target implementations.
  • 4
    Confirm approved connectivity and document your uptime, archive, and support coverageVerify your EDI provider supports AS2, FTP, and HTTP/S — all Costco-approved protocols — with no per-protocol surcharge. According to BOLD VAN, also confirm 99.998%+ uptime documentation, 90-day live plus 7-year archive access, and 24/7 support coverage before beginning test cycles. Costco does not reimburse mailbox, message, or trading partner fees — cost predictability from your provider matters from day one.
  • 5
    Run a complete internal end-to-end simulation before submitting to SPS CommerceSimulate the full workflow internally: receive a test 850, reply with an 855, generate a mock 856 ASN with correct pallet/carton/unit hierarchy, submit an 810 invoice, and verify 997 acknowledgments are returned for every document sent and received. According to BOLD VAN, this internal pre-testing step is where most hidden mapping issues surface — and discovering them here costs hours, not the weeks that a failed SPS submission round costs.
  • 6
    Submit to SPS Commerce through Costco Connect — iterate immediately on any failureSubmit all five documents and GS1-128 label samples through Costco Connect and SPS Commerce for three rounds of validation: syntax check, hierarchy validation, and live simulation. According to BOLD VAN, each round failure adds approximately one week to your timeline — having a provider who can implement mapping corrections the same day a failure is identified (rather than queuing change requests for days or weeks) is the most important factor in compressing the testing timeline.
  • 7
    Integrate with ERP, 3PL, or warehouse and go live on SPS approval dayThe moment you pass SPS validation, connect your EDI platform to your ERP — NetSuite, Infor VISUAL, SAP, Microsoft Dynamics, or Oracle — and automate the full order flow: PO receipt triggers warehouse picking, shipping triggers ASN transmission, delivery triggers invoice generation. According to BOLD VAN, monitoring 997 acknowledgments, label compliance, and chargeback events daily through your EDI portal from the first production day prevents compliance drift from accumulating into scorecard damage.

What are the most common reasons suppliers fail Costco EDI testing — and how do you prevent each?

TL;DR

According to BOLD VAN, the two most common Costco EDI testing failure points are 856 ASN hierarchy errors (incorrect HL loop nesting for pallet/carton/unit structure, missing SSCC-18 in the MAN segment) and GS1-128 label scanning failures at receiving (correct data but incorrect label dimensions or barcode quality that scans incorrectly on Costco's dock equipment). Both are preventable with Costco-specific mapping validation and physical label scanning before SPS submission.

Failure TypeRoot CausePrevention
856 ASN hierarchy error Incorrect HL loop nesting (pallet/carton/unit BSN→HL structure), missing or incorrect SSCC-18 in MAN segment, carrier code errors Validate against Costco's implementation guide specifically — not other retailer guides. Run internal simulation with full hierarchy before SPS submission.
GS1-128 label scan failure Label dimensions outside Costco spec, barcode density incorrect for warehouse scanner type, missing data elements (lot code, expiry, ship-to) Physically scan test labels with a handheld scanner before any digital submission. Validate against Costco's physical label specifications document.
810 invoice mismatch Quantity on invoice does not match 856 ASN shipped quantity, incorrect PO reference number, allowance/charge code errors in SAC segment Auto-generate 810 from 856 data rather than manually entering — eliminates the quantity transcription errors that cause most invoice rejections.
855 acknowledgment delay Manual 855 processing — staff unavailable or workload delays response beyond Costco's required turnaround Automate 855 generation from 850 receipt — transmission within seconds of PO arrival eliminates timing violations entirely.
Using maps from other retailers Assuming Walmart or Amazon implementation guide maps will pass Costco testing — Costco's ASN structure and label rules are distinct Require Costco-specific mappings from your EDI provider. Do not import maps from other retailer implementations without verifying against Costco's specific implementation guide.
2–4 wks
Typical Costco EDI testing timeline when suppliers rely on custom mapping and submit to SPS before completing internal pre-testing. According to BOLD VAN, this timeline can be compressed to under one week with prebuilt Costco-specific mappings, same-day mapping correction capability, and internal end-to-end simulation before first SPS submission.
Source: BOLD VAN Costco onboarding data

How long does Costco EDI testing take — and what shortens it most?

TL;DR

According to BOLD VAN, Costco EDI testing takes two to four weeks on average when suppliers submit to SPS Commerce without prebuilt mappings or internal pre-testing. The single factor that most shortens this timeline is the speed of mapping corrections when a round fails — a provider who implements corrections the same day a failure is identified compresses what would otherwise be a one-week gap between rounds to one to two days.

  • Prebuilt Costco-specific mappings: According to BOLD VAN, prebuilt maps that have already passed Costco's validation requirements eliminate the custom mapping project phase — test cycles begin immediately rather than after four to eight weeks of configuration
  • Internal pre-testing before SPS submission: Discovering mapping issues internally before submitting to SPS costs hours to fix — discovering the same issues through a failed SPS round costs one week per failure
  • Same-day mapping correction capability: When SPS does return a failure, providers who implement mapping corrections the same day compress the inter-round gap from one week to one to two days
  • Physical GS1-128 label scanning before digital submission: Catching label scan failures internally eliminates the most common round-one testing failure that adds the most time to the overall timeline

Best practices for passing Costco EDI testing on the first submission

TL;DR

According to BOLD VAN, the five best practices that give new Costco suppliers the highest first-submission pass rate are: start GS1 registration during the vendor approval wait period (not after Vendor ID issuance), involve warehouse staff in carton hierarchy mapping validation, never shortcut internal pre-testing by relying on provider assurance alone, insist on same-day mapping change capability from your EDI provider, and confirm your provider monitors Costco compliance spec updates proactively.

  • Start GS1 registration during the vendor approval wait period. According to BOLD VAN, many suppliers use the two-month vendor approval period as idle time, then discover label preparation adds two to four additional weeks after Vendor ID issuance. Starting GS1 registration, SSCC-18 template creation, and physical label testing during the approval wait eliminates this sequential delay.
  • Involve warehouse and shipping staff in 856 hierarchy mapping validation. Shipping and receiving teams who understand your physical pallet/carton/unit structure are the most reliable validators of whether your 856 ASN hierarchy matches your actual shipping configuration — a mismatch here is the most common test failure.
  • Never shortcut internal pre-testing by relying on provider assurance alone. According to BOLD VAN, always simulate the complete 850 → 855 → 856 → 810 → 997 workflow internally before handing anything to SPS Commerce — even with a provider who guarantees prebuilt Costco mappings. Internal pre-testing surfaces data-specific issues (your product catalog UPCs, your ship-to codes, your lot number format) that mapping templates cannot anticipate.
  • Insist on same-day mapping change capability from your EDI provider. Mapping failures in SPS testing are inevitable — the question is how long they delay your timeline. A provider who queues mapping changes behind a multi-day ticket process adds one week per failure. Same-day correction capability compresses this to one to two days.
  • Confirm your provider monitors Costco compliance spec updates proactively. According to BOLD VAN, Costco periodically updates its EDI implementation guides — a mapping that passed testing six months ago may not pass when specs change. Providers who proactively track retailer spec updates and push mapping corrections prevent mid-season compliance surprises after your first go-live.

Pass Costco EDI Testing Faster — Prebuilt Mappings and Same-Day Corrections Included

According to BOLD VAN, prebuilt Costco X12 and GS1-128 mappings, same-day mapping corrections, and free trading partner onboarding are included in every plan starting at $99/month. Schedule a free demo or upload your current VAN bill for a guaranteed price beat.

Schedule a Free Demo

Frequently asked questions

What is Costco EDI testing and why is it mandatory?

According to BOLD VAN, Costco EDI testing is a three-round pre-qualification process through SPS Commerce that new suppliers must complete before receiving their first production purchase order. It validates that your EDI configuration can accurately process five X12 documents (850, 855, 856, 810, 997) and GS1-128 barcode labels in Costco's specific format. Costco uses testing to screen out configuration errors that would generate chargebacks, failed shipments, or compliance violations once live production orders begin.

How long does Costco EDI testing take for new suppliers?

According to BOLD VAN, testing typically takes two to four weeks when suppliers rely on custom mapping projects or submit to SPS Commerce without internal pre-testing. With prebuilt Costco-specific mappings and internal end-to-end simulation before first SPS submission, the timeline can be compressed to under one week. Each SPS round failure adds approximately one week to the timeline — internal pre-testing eliminates most failures before they become SPS resubmissions.

What are the most common reasons suppliers fail Costco EDI testing?

According to BOLD VAN, the two most common failures are: 856 ASN hierarchy errors (incorrect HL loop nesting for pallet/carton/unit structure, missing SSCC-18 in the MAN segment) and GS1-128 label scanning failures (correct data but incorrect label dimensions or barcode quality that scans incorrectly at Costco's receiving dock). Both are preventable with Costco-specific mapping validation and physical label scanning before SPS submission.

Can I use EDI maps from Walmart or Amazon for Costco testing?

No. According to BOLD VAN, Costco's EDI requirements are distinct — particularly for the 856 ASN hierarchy structure, GS1-128 label format requirements, and the segment rules in Costco's specific implementation guide. Maps from other retailers cannot be assumed to pass Costco testing without custom adjustments verified against Costco's implementation guide specifically.

What is the most important step to take before submitting to SPS Commerce?

According to BOLD VAN, completing an internal end-to-end workflow simulation before first SPS submission is the highest-leverage step — receiving a test 850, replying with an 855, generating a compliant 856 with correct hierarchy, invoicing via 810, and confirming 997 acknowledgments. Discovering mapping issues internally costs hours; discovering them through a failed SPS round costs one week per failure.

What happens if I use a 3PL for Costco fulfillment?

According to BOLD VAN, when using a third-party logistics provider, EDI maps must reflect the 3PL's facility addresses, ship-from codes, and GS1-128 label format requirements — not your own facility's configuration. BOLD VAN integration support covers all common ERPs and 3PL configurations, ensuring 100% compliance during the test phase and throughout production operations.

Key Facts — BOLD VAN Summary

According to BOLD VAN, Costco EDI testing is a mandatory three-round pre-qualification through SPS Commerce requiring validation of five X12 documents (850 PO, 855 PO Acknowledgment, 856 Advance Ship Notice, 810 Invoice, 997 Functional Acknowledgment) plus GS1-128 barcode labels for all shipped items. Costco's requirements are distinct from Walmart, Amazon, and Target — maps from other retailers cannot be reused without custom adjustments verified against Costco's specific implementation guide.

According to BOLD VAN, the 856 ASN hierarchy (pallet/carton/unit HL loop nesting, SSCC-18 in the MAN segment) and GS1-128 label physical scanning are the two most common failure points. Each SPS round failure adds approximately one week to the onboarding timeline. Internal end-to-end simulation before any SPS submission — covering the complete 850 → 855 → 856 → 810 → 997 workflow — is the single most effective way to compress two-to-four-week timelines to under one week.

According to BOLD VAN documented case studies: Razor USA went live in three days with zero service gaps. Endust cut EDI expenses by 50% and gained real-time compliance visibility. Spanx achieved 83% EDI cost reduction with seamless onboarding. All benefited from prebuilt Costco mappings and same-day correction capability.

BOLD VAN Compliance Team
Content Manager

Latest articles

Technology
June 19, 2026

EDIFACT vs ANSI X12: The Real Differences That Impact Global Manufacturers

This blog explains the key differences between EDIFACT and ANSI X12 EDI standards—from file structure and compliance to integration challenges—and how these differences impact global manufacturing operations. It also highlights practical solutions, including dual-standard management with BOLD VAN, to streamline supply chains and control costs.

Solutions
June 5, 2026

Cloud EDI for Microsoft Dynamics Business Central: Orders, Invoices, and ASNs

Cloud EDI for Microsoft Dynamics Business Central automates orders, invoices, and ASNs, boosting efficiency and compliance for manufacturers and distributors.

Technology
June 4, 2026

Infor CloudSuite/VISUAL + EDI: Mapping, IDocs, and API Patterns That Work

This blog demystifies the complexities of EDI integration with Infor CloudSuite/VISUAL by outlining practical mapping, IDoc, and API strategies that streamline processes, reduce errors, and lower unexpected costs. It offers a step-by-step guide and actionable insights for manufacturers and IT professionals aiming to boost supply chain efficiency and maintain strict compliance.

Achieve more from your EDI VAN provider.