Babylist EDI Requirements: A Complete Guide for Suppliers

Babylist requires its suppliers to exchange a defined set of EDI documents — typically the 850 (Purchase Order), 855 (PO Acknowledgment), 856 (Advance Ship Notice), 810 (Invoice), and 997 (Functional Acknowledgment) — transmitted over a supported communication protocol such as AS2, SFTP, or API. Suppliers must also meet Babylist’s labeling, packaging, and routing standards to avoid chargebacks.

If you sell to Babylist — whether through their wholesale program, drop ship network, or registry fulfillment model — getting EDI right is the difference between a clean partnership and a stack of compliance penalties. This guide walks through exactly what Babylist expects, document by document, with the operational details brands actually need.

What Is Babylist and Why Does EDI Matter?

Babylist is the largest baby registry platform in the United States, serving more than two-thirds of expecting parents. Beyond being a registry, Babylist operates a curated retail business and a drop ship marketplace, working with hundreds of brands across baby gear, apparel, feeding, sleep, toys, and lifestyle products.

Like every modern retailer at scale, Babylist runs on EDI. Manual order processing — emailed POs, spreadsheets, phone confirmations — does not scale past a handful of partners and creates the kind of errors (mis-shipments, late ASNs, invoice mismatches) that generate chargebacks and erode margin. EDI standardizes the exchange of orders, shipment notices, and invoices so both sides operate from the same data in near real time.

For suppliers, the practical reality is simple: if you want to grow with Babylist, you need to be EDI-capable. New vendor onboarding, drop ship program enrollment, and most catalog expansions require it.

The Babylist EDI Document Set

Babylist follows the ANSI X12 EDI standard, which is the dominant standard for North American retail. The core transaction set most suppliers will exchange includes the documents below. Confirm exact requirements with Babylist’s vendor team during onboarding — the specifics can vary by program (wholesale vs. drop ship) and by category.

Drop ship suppliers in particular should expect the 846 to be required — Babylist needs accurate inventory feeds so it does not sell items you cannot fulfill.

EDI 850 — Purchase Order

The 850 is the order itself, sent from Babylist to the supplier. It contains the PO number, ship-to address (Babylist warehouse for wholesale, end consumer for drop ship), line-level SKU and quantity detail, requested ship dates, and any special handling instructions. Suppliers are expected to acknowledge receipt with a 997 within minutes and respond with an 855 within the timeframe specified in the vendor agreement — typically 24 hours, faster for drop ship.

EDI 855 — PO Acknowledgment

The 855 confirms the supplier can fulfill the PO as ordered, or flags exceptions (substitutions, partial fills, backorders, ship date changes). Babylist relies on the 855 to maintain accurate availability on the consumer-facing site, so silent acceptance — fulfilling without acknowledging — is a common chargeback trigger. Send a real 855 for every 850.

EDI 856 — Advance Ship Notice (ASN)

The 856 is the most operationally important document and the most common source of compliance issues. It tells Babylist’s receiving team exactly what is in the shipment, broken down by pack hierarchy: shipment → order → pack (carton) → item. The ASN must be transmitted before the shipment physically arrives — generally on the day of pickup — and the data on the ASN must match the GS1-128 carton labels and the physical contents exactly.

Common ASN failures include missing tracking numbers, mismatched carton counts, missing or incorrect SSCC-18 numbers, and ASNs sent after the shipment arrives at the warehouse. Each of these typically carries a per-occurrence chargeback.

EDI 810 — Invoice

The 810 is the supplier’s invoice. It must reference the PO number from the 850 and the ASN from the 856. Quantities, prices, and terms must reconcile against the PO. Discrepancies — even small ones — block payment and trigger reconciliation work that delays cash.

EDI 997 — Functional Acknowledgment

The 997 is the receipt for every other EDI document. It confirms the document arrived and parsed successfully at the structural level. It is not a business acknowledgment (that is the 855); it is purely a transport-layer confirmation. Both Babylist and the supplier should generate 997s automatically for every inbound document.

EDI 846 — Inventory Advice

For drop ship suppliers, the 846 keeps Babylist’s catalog accurate. It is sent on a recurring schedule — daily is typical, hourly for fast-moving categories — and lists available inventory by SKU. If the 846 says you have 12 units and you only have 4, Babylist will sell items you cannot ship and you will be on the wrong side of every chargeback that follows.

Communication Protocols

Babylist supports the standard set of EDI transports. The right choice depends on your existing infrastructure and your EDI provider’s capabilities.

• AS2: The most common protocol for retail EDI. Encrypted, signed, with built-in receipts (MDNs). Reliable but requires certificate management and a static endpoint.
• SFTP: Simple file-based exchange. Suppliers drop files into a directory and pick up incoming files on a schedule. Lower setup overhead than AS2; less real-time.
• REST API / Webhooks: Increasingly available for modern partners, particularly for drop ship. Real-time push of orders and ship notices. Best fit for brands running on modern commerce platforms.
• VAN (Value Added Network): Traditional third-party EDI mailbox service. Still used but largely superseded by AS2 and direct connections.

If you do not already have EDI infrastructure, an EDI platform like Crstl handles all of these protocols natively — you connect once to your ERP or commerce platform and Crstl manages the AS2 certificates, SFTP credentials, and document mapping with Babylist on your behalf.

Labeling, Packaging & Routing

EDI compliance is only half the story. The physical shipment has to match the EDI data, and Babylist enforces specific labeling and packaging standards.

GS1-128 carton labels. Every carton in a wholesale shipment must carry a GS1-128 (formerly UCC-128) shipping label with an SSCC-18 serial number. The SSCC must match the carton-level data in the 856 ASN. Mismatches between the label and the ASN are a top-three chargeback category at most retailers.

UCC compliance. Item-level UPC/GTIN barcodes must be present and scannable on every consumer unit. Items without correct, readable barcodes get rejected at receiving.

Packing slips. Even with a complete ASN, Babylist typically requires a printed packing slip inside or attached to the shipment, referencing the PO number.

Routing guide. Wholesale shipments must follow Babylist’s routing guide — the document that specifies approved carriers, carrier selection rules by weight and destination, and any preferred routing programs. Using an unapproved carrier or shipping outside the routing window is a chargeback trigger.

Drop ship packaging. Drop ship shipments to consumers carry different rules: branded packaging may be required or prohibited depending on category, return labels are often included, and packing slips must use the customer-facing format Babylist provides — not your standard wholesale slip.

Onboarding Process

Babylist EDI onboarding follows a fairly standard retailer pattern, though timelines vary by program and supplier readiness.

1. Vendor agreement and program selection. You sign the vendor agreement, decide between wholesale and drop ship (or both), and Babylist’s vendor team confirms the document set and protocols you will use.
2. Technical specifications. Babylist sends EDI specs (sometimes called a “companion guide” or “implementation guide”) that detail the exact segment-level expectations, qualifier values, and any retailer-specific data elements. Read these carefully — the 856 spec in particular has retailer-specific quirks at almost every retailer.
3. Connectivity setup. You configure AS2, SFTP, or API connectivity with Babylist’s EDI environment. Certificates are exchanged for AS2; credentials are issued for SFTP.
4. Testing. You exchange test transactions in a sandbox environment. Babylist will send sample 850s and review your 855, 856, and 810 responses. Expect multiple iterations to clear the test plan.
5. Certification. Once test transactions pass, Babylist certifies you for production. You move to live PO flow.
6. Production ramp. Initial production POs are monitored closely. Expect heightened scrutiny on the first few shipments and faster feedback on any compliance issues.

End-to-end, suppliers using a modern EDI platform typically certify with Babylist in two to four weeks. Suppliers building EDI in-house from scratch should plan on two to four months.

Common Babylist EDI Chargebacks (and How to Avoid Them)

The exact chargeback schedule is documented in Babylist’s vendor agreement, but the categories that hit suppliers most often are universal across retail EDI:

• Late or missing ASN. ASN must transmit before the shipment arrives. A late ASN is one of the most common and expensive penalties.
• ASN data mismatch. Cartons, SKUs, or quantities on the ASN do not match the physical shipment or the GS1-128 labels.
• Missing 855 acknowledgment. Silent acceptance of a PO without sending an 855.
• Invoice discrepancies. Quantity, price, or term differences between the 810 and the 850 that block matching.
• Routing violations. Using an unapproved carrier or shipping outside the routing window for wholesale orders.
• Label and barcode failures. Missing, unreadable, or incorrect GS1-128 carton labels or item UPC barcodes.

The strongest single defense against chargebacks is ensuring the data flow between your ERP, your warehouse (or 3PL), and your EDI platform is automated end-to-end. Manual re-keying — pulling a PO from EDI into a spreadsheet, then into the WMS, then back into EDI for the ASN — is where errors enter the system.

How Crstl Helps Brands Become Babylist EDI-Compliant

Crstl is an AI-native EDI and supply chain commerce platform that automates order-to-cash workflows between brands, retailers, and logistics partners. For brands selling to Babylist, Crstl handles:

• Native connectivity to Babylist via AS2, SFTP, or API — no certificate management or VAN fees
• Pre-built mappings for the full Babylist document set (850, 855, 856, 810, 846, 997)
• Direct integrations with Shopify, NetSuite, QuickBooks, and other ERP and commerce platforms, so PO data flows into your system of record automatically and ASN/invoice data flows back out
• GS1-128 label generation tied to the 856, so the label and the ASN are guaranteed to match
• Automated 855 acknowledgments, exception flagging, and chargeback prevention checks before documents go out the door
• Onboarding to Babylist in days, not months

If you are evaluating EDI providers for Babylist, or if you are already live with Babylist and dealing with chargebacks you do not understand, book a demo and we will walk you through exactly how Crstl would map to your situation.

Frequently Asked Questions

What EDI documents does Babylist require?

At minimum, Babylist requires the 850 (Purchase Order), 855 (PO Acknowledgment), 856 (Advance Ship Notice), 810 (Invoice), and 997 (Functional Acknowledgment). Drop ship suppliers also typically exchange the 846 (Inventory Advice). The exact document set is confirmed during onboarding based on whether you are wholesale, drop ship, or both.

Does Babylist require AS2 or can I use SFTP?

Babylist supports both AS2 and SFTP, and offers API-based integration for some partners — particularly drop ship. AS2 is the most common choice for established suppliers because of its built-in encryption and signed receipts. SFTP has a lower setup overhead and works well for smaller volumes. Confirm preferred protocols with Babylist’s EDI team during onboarding.

How long does Babylist EDI onboarding take?

Suppliers using a modern EDI platform typically complete Babylist onboarding in two to four weeks, including testing and certification. Suppliers building EDI in-house, or using an older VAN-based provider, should plan on two to four months. The biggest variables are the supplier’s existing data infrastructure and how quickly the team can iterate through test transactions.

What is the difference between Babylist wholesale and drop ship EDI?

Babylist wholesale EDI ships goods to a Babylist warehouse, which then handles consumer fulfillment. The ship-to on the 850 is the warehouse, GS1-128 carton labels are required, and the routing guide governs carrier selection. Drop ship EDI ships goods directly to the end consumer. The ship-to on the 850 is the consumer’s address, the 846 inventory feed is critical, and packaging and packing slip requirements differ. Many suppliers run both programs.

What happens if I send an ASN late?

A late ASN — one that arrives after the physical shipment hits Babylist’s receiving dock — typically triggers a per-shipment chargeback. The exact penalty is documented in your vendor agreement. The fix is operational: ensure your warehouse or 3PL transmits the 856 at the moment of pickup, not at the end of the day or after the fact.

How do I avoid Babylist chargebacks?

The most effective approach is end-to-end data automation: your PO flows from EDI into your ERP, your warehouse confirms shipment data back to your EDI system in real time, and your ASN, GS1-128 labels, and invoice are generated from a single source of truth. Most chargebacks come from manual re-keying or stale data. A modern EDI platform with native ERP and WMS integration eliminates the most common error paths.

Do I need an EDI provider, or can I build EDI in-house?

You can build EDI in-house, but it is rarely the right call for brands whose core business is not EDI. In-house builds require ongoing maintenance — every retailer companion guide changes, certificates rotate, new document types are introduced — and the engineering cost compounds with every new trading partner. Most brands selling to Babylist alongside Amazon, Walmart, Target, and others find that an EDI platform pays for itself within the first one or two trading partner integrations.

Is Babylist EDI the same as Amazon, Walmart, or Target EDI?

The underlying standard (ANSI X12) is the same, and the document types overlap significantly, but every retailer publishes its own companion guide with retailer-specific segment usage, qualifier values, and operational rules. A supplier who is fully compliant with Walmart EDI is not automatically compliant with Babylist; the mappings have to be configured for each retailer. This is one of the strongest arguments for using an EDI platform — the platform absorbs the per-retailer variation so you do not have to.

Crstl is an AI-native EDI and supply chain commerce platform that automates order-to-cash workflows between brands, retailers, and logistics partners. We help brands go live with retailers like Babylist, Amazon, Walmart, Target, and Shopify in days — not months.