Direct-to-Consumer Fulfillment
Zulily sends you individual consumer orders during and after sale events. You ship directly to the shopper — but the experience must be completely Zulily-branded.
Zulily runs flash sales at high velocity — new events go live daily, each one generating a surge of dropship orders that need same-day acknowledgment. SBSA Technology handles full EDI compliance for both Zulily fulfillment models: direct-to-consumer dropship and bulk purchase orders to Zulily's fulfillment centers.
Select your order type to see EDI requirements
Each Zulily dropship PO contains the end customer's address — not a Zulily location. Multiple POs can arrive in bursts during active sale events.
Must acknowledge within 24 hours of PO creation. SBSA automates this the moment the 850 arrives in your queue.
Your brand must not appear on any packaging. Zulily's branded packing slip, generated from your ASN, must accompany every shipment.
Tracking number is mandatory in the ASN. Send the 856 before the package leaves your facility — not after carrier scan.
One invoice per PO only. Submit after shipment confirmation. SBSA automates invoice generation from your shipping data.
Ship-to address specifies a Zulily fulfillment center. Quantities are larger than dropship but less time-critical per unit.
Zulily requires confirmed ship dates per SKU in the 855 acknowledgment — not just at order level.
All cartons must carry compliant GS1-128 (UCC-128) labels with data matching the ASN exactly. Labels auto-generated by SBSA.
One ASN per shipment. Do not send the ASN before goods are ready to ship — and never after the freight leaves.
Invoice quantities must match what was actually shipped in the ASN. Discrepancies trigger chargeback review.
The two Zulily fulfillment models share the same transaction set but differ significantly in ASN content, labeling requirements, and timing constraints. SBSA applies the correct rules automatically based on the ship-to address in each 850.
Zulily sends you individual consumer orders during and after sale events. You ship directly to the shopper — but the experience must be completely Zulily-branded.
Zulily places larger wholesale POs for inventory to be received at their fulfillment centers. Compliance requirements are warehouse-grade: labels, ASN accuracy, and complete shipments.
Zulily enforces chargebacks automatically for late ASNs, missing tracking numbers, incorrect labels, and shipments that don't match the acknowledged PO. A single event sale can generate hundreds of POs — without automation, one delayed response compounds into dozens of penalties.
Zulily supports three EDI transmission protocols. SBSA handles full configuration, certification testing, and ongoing monitoring for all three — you choose based on your technical environment.
Applicability Statement 2
Direct, encrypted, real-time connection between SBSA and Zulily's EDI server. AS2 is Zulily's preferred protocol for high-volume suppliers — lowest latency, immediate delivery receipts, and the strongest security posture.
Secure File Transfer Protocol
Scheduled file-based EDI transmission via a secure FTP server. SFTP is reliable and widely supported — a good option for suppliers with existing FTP infrastructure who need a lower-friction setup path.
Value-Added Network
Indirect transmission through a third-party EDI network (VAN) such as SPS Commerce, TrueCommerce, or Sterling. VAN is the most common starting point for new Zulily suppliers — no direct connectivity required, just mailbox routing through the VAN provider.
SBSA Technology supports core and supplemental Zulily EDI Integration EDI documents. Critical transactions are highlighted because they carry the highest compliance risk when transmitted incorrectly or late.
Sent by Zulily when a consumer places an order or a bulk PO is issued
InboundMust be returned within 24 hours of PO creation date
OutboundSent as shipment leaves facility — before carrier pickup scan
OutboundOne invoice per PO; submitted after shipment confirmation
OutboundReturned by Zulily to confirm receipt of your EDI transmissions
OutboundSent by Zulily with payment details; reconciled against 810 invoices
InboundSBSA integrates Zulily's EDI data directly into your ERP, order management, or accounting system — eliminating manual order entry, invoice creation, and inventory updates across every Zulily transaction.
Certified integration between Zulily EDI and QuickBooks Online. Zulily purchase orders flow in as sales orders, shipment confirmations trigger invoice generation, and payments from the EDI 820 reconcile automatically.
Full EDI-to-ERP integration for QuickBooks Enterprise users. Supports advanced inventory, multi-location warehousing, and high-volume order processing — ideal for suppliers running both Zulily dropship and bulk PO models simultaneously.
Bidirectional integration: 850 POs create sales orders in NetSuite automatically; ship confirmations and invoices flow back to Zulily as EDI 856 and 810.
Full SAP integration via IDocs or direct API. Maps Zulily's EDI segments to SAP order management, warehouse management, and FI invoice processing.
Native D365 integration for purchase order receipt, warehouse pick and ship confirmation, and automated invoice creation from confirmed shipments.
Integration with Oracle Fusion Order Management and Inventory. SBSA maps Zulily 850s to Oracle sales orders and returns 856/810 from Oracle confirmations.
For brands using Shopify as their OMS or third-party WMS platforms (ShipBob, 3PL Central, Logiwa, etc.), SBSA provides API-based integrations that route Zulily orders into your fulfillment workflow.
If your ERP or WMS isn't listed, SBSA builds a custom integration. We've connected EDI to hundreds of systems — flat-file imports, AS/400 mainframes, proprietary ERPs, and everything in between.
Zulily's flash-sale model means order volume can spike dramatically during an active event. Manual processing is not a viable compliance strategy. SBSA automates every time-sensitive step in the EDI cycle so your team focuses on fulfillment — not data entry.
Auto-Acknowledgment (EDI 855)
Label & Packing Slip Generation
ASN Transmission on Ship Confirm
Automated Invoice Generation (EDI 810)
Compliance Monitoring & Scoring
ERP Data Sync
Common questions from suppliers beginning their Zulily EDI compliance journey.
Zulily suppliers operate under two models: Dropship — where Zulily sends individual consumer orders via EDI 850 and you ship directly to the end customer under Zulily's branded packing slip — and Bulk Purchase Order, where Zulily places a larger wholesale PO for inventory to be shipped to one of their fulfillment centers. Many suppliers run both models simultaneously. SBSA handles both from a single integration, routing each 850 to the correct compliance rules based on the ship-to address.
Zulily requires the Purchase Order Acknowledgment (EDI 855) to be returned within 24 hours of the PO being issued. During active flash sale events, dozens or hundreds of POs can arrive in a single day — making manual acknowledgment impractical. SBSA automates the 855 the moment each 850 arrives, ensuring the deadline is met regardless of when POs hit your queue.
For bulk POs, Zulily is strict: any shipment received at a fulfillment center without a prior ASN can be refused and returned at your cost. For dropship orders, a missing or late ASN — where the tracking number isn't transmitted before carrier pickup — triggers an automatic chargeback. SBSA transmits the 856 ASN at the moment your warehouse confirms shipment, eliminating both risks.
Yes. Every Zulily dropship order must include a Zulily-branded packing slip — your supplier branding must not appear anywhere on the package or inside the box. For bulk POs shipped to a Zulily fulfillment center, GS1-128 (UCC-128) carton labels are required on every carton, with data that matches the ASN exactly. SBSA generates all required labels and packing slips automatically from the EDI 850 data.
Yes. As an Intuit Silver Partner, SBSA offers certified integrations with both QuickBooks Online and QuickBooks Enterprise. Zulily purchase orders flow into QuickBooks as sales orders on receipt, invoices are posted automatically when you ship, and payment remittances from the EDI 820 reconcile against your open invoices — all without manual data entry.
Zulily supports AS2, SFTP, and VAN (Value-Added Network) for EDI transmission. AS2 is the preferred protocol for high-volume suppliers — it provides real-time delivery, encrypted transmission, and immediate delivery receipts. SFTP is a reliable alternative for suppliers with existing file-transfer infrastructure. VAN connections through providers like SPS Commerce or TrueCommerce are available for suppliers who prefer indirect connectivity. SBSA handles full setup, certification testing, and ongoing monitoring for all three protocols.
Tell us whether you're dropshipping, shipping bulk POs, or both — and we'll build a complete integration plan tailored to your volume and tech stack.