Zales is one of North America's largest fine jewelry retailers — over 700 stores across the US and Canada, operating under the Signet Jewelers umbrella alongside Kay and Jared. SBSA Technology handles full EDI compliance for all Zales fulfillment paths: Distribution Center, store replenishment, and drop ship to customer.
Select your ship-to destination to see requirements
Zales issues POs for DC replenishment. Includes item UPCs, quantities, required delivery dates, and routing instructions.
Acknowledge acceptance, partial fulfillment, or issues at line-item level. Missing the 855 window triggers compliance chargebacks.
Zales expects complete order fulfillment. Each carton requires a compliant GS1-128 label with PO number, UPC, quantity, and carton ID.
Shipments arriving at the DC without a valid ASN are subject to refusal. The ASN must precede the physical goods.
One electronic invoice per purchase order only. Invoice amounts must match the 855 acknowledged quantities and pricing.
The 850 will route directly to a specific Zales or Peoples Jewellers store location rather than the DC.
All acknowledgment, ASN timing, labeling, and invoice rules are identical to DC shipments.
Zales store deliveries may have carrier restrictions, appointment scheduling requirements, and delivery window rules. SBSA flags these per location.
Store deliveries require the same carton-level labeling as DC shipments — no exceptions for smaller quantities.
Drop ship POs identify the end customer and may include gift messaging or special handling instructions. Zales branding must be preserved throughout.
For drop ship, real-time inventory availability matters most. The 855 must reflect your actual ability to ship the specific item.
Your branding must not appear anywhere on the shipment. The packing slip is generated from the ASN and must carry Zales branding exclusively.
The customer tracking number must be included in the ASN so Zales can trigger customer notification emails automatically.
Zales works with three primary supplier categories. Your fulfillment path, EDI setup, and compliance obligations differ based on your relationship with Zales — SBSA configures everything specific to your category.
You sell jewelry, watches, or accessories in bulk to Zales' Distribution Center for store replenishment. This is the most common supplier relationship — Zales manages in-store merchandising, you manage inventory and replenishment.
You ship smaller quantities directly to individual Zales, Zales Outlet, or Peoples Jewellers stores. Common for high-value or fast-turn items that bypass the DC. Carrier and delivery rules vary by store location.
You fulfill Zales.com or ZalesOutlet.com customer orders directly to the end consumer. Zales owns the customer relationship — your shipment must be invisible, carrying Zales branding with no trace of your own company identity.
Zales supports AS2, SFTP, and VAN for EDI transmission. SBSA Technology handles complete setup, certificate management, testing, and ongoing compliance monitoring for all three protocols.
Direct Protocol
Encrypted, point-to-point EDI via AS2. The preferred option for higher-volume Zales suppliers — fast, reliable, with full delivery receipts and the lowest per-transaction cost at scale.
Secure File Transfer
Secure FTP-based document exchange — practical for suppliers with existing SFTP infrastructure or transitioning from manual processes to fully automated EDI workflows.
Managed Network
Value-Added Network transmission for suppliers who prefer a fully managed, intermediary-based connection. SBSA acts as your complete EDI department — routing, translating, and monitoring all Zales documents through the VAN.
SBSA Technology supports core and supplemental Zales EDI Integration EDI documents. Critical transactions are highlighted because they carry the highest compliance risk when transmitted incorrectly or late.
Zales' PO initiates the fulfillment cycle. Specifies ship-to location (DC, store, or end customer), items by UPC, quantities, required ship dates, and pricing. Drop ship POs include customer name and address.
InboundMust be sent within 1 business day of PO creation. Confirms fulfillment at line-item level — quantity changes, revised ship dates, or pricing discrepancies must be reflected here, not assumed.
Outbound 1 business day deadline — chargeback risk if missedSent as shipment leaves your facility. Incomplete or missing ASNs trigger chargebacks or shipment refusals. Drop ship ASNs must include carrier tracking so Zales can trigger customer notifications.
Outbound Must transmit before physical goods arrive — refusal riskOne EDI invoice per PO. Invoice quantities and pricing must match the 855 Acknowledgment exactly. Discrepancies between invoiced and acknowledged amounts are the most common source of payment deductions.
Outbound Must match 855 acknowledgment — deduction risk if mismatchedConfirms syntactic validity of every EDI document transmitted. SBSA monitors all 997 responses and surfaces rejections before they can escalate into compliance issues.
OutboundZales' payment order and remittance advice — auto-reconciles against your open invoices when received, surfacing any deductions or adjustments made at payment time.
InboundBuyer-initiated PO modifications — quantity, pricing, or delivery date changes. SBSA flags all 860s and applies updates at the line-item level to your ERP automatically.
InboundSales and inventory activity data shared with Zales for demand planning and replenishment forecasting — helps Zales optimize stocking decisions for your product lines across their store network.
OutboundSBSA Technology integrates Zales EDI with all major ERP platforms. As an Intuit Silver Partner, we provide certified, production-grade integration with QuickBooks Online and QuickBooks Enterprise — eliminating manual data entry and keeping your books in sync with every Zales order.
SBSA's certified QuickBooks Online integration maps every Zales EDI transaction directly into your QBO account. Incoming 850 POs create sales orders automatically. Outbound invoices sync from QBO to the EDI 810 with no manual export required.
For jewelry suppliers with higher complexity — multi-location inventory, advanced pricing tiers, or manufacturing workflows — SBSA's QuickBooks Enterprise integration provides the same seamless Zales EDI connectivity with support for QBE's advanced inventory and reporting capabilities.
Bidirectional integration: 850 POs create sales orders in NetSuite automatically; ship confirmations and invoices flow back to Zales as EDI 856 and 810.
Full SAP integration via IDocs or direct API. Maps Zales 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 Zales 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 Zales 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.
Zales enforces compliance strictly — missed 855 windows, late ASNs, mislabeled cartons, and invoice discrepancies all generate chargebacks that erode your margin. SBSA Technology automates every compliance step so your Zales relationship stays profitable and penalty-free.
855 PO Acknowledgment auto-fired within minutes of PO receipt — never miss the 1-business-day window
856 ASN generated and transmitted the moment shipment departs your facility — ahead of the physical goods
Drop ship ASNs include carrier tracking number — triggers Zales customer notification emails automatically
Zales-branded packing slip auto-generated from ASN data for all drop ship orders — your branding never appears
GS1-128 / UCC-128 carton labels auto-generated and validated against ASN contents before dispatch
810 invoice auto-matched to 855 acknowledged quantities — prevents deductions from quantity mismatches
820 Remittance Advice auto-reconciled against open invoices — deductions flagged immediately
860 PO Change Requests applied at line-item level to your ERP automatically
Backordered items flagged in 855 with revised ship dates — never silently cancelled
Real-time inventory sync prevents drop ship orders from being acknowledged when stock is unavailable
Common questions from jewelry and accessories suppliers beginning their Zales EDI compliance journey.
Zales requires four core EDI transactions: the EDI 850 Purchase Order (inbound from Zales), the EDI 855 Purchase Order Acknowledgment (outbound from you — must be sent within 1 business day), the EDI 856 Advance Ship Notice (outbound — must be transmitted as the shipment leaves your facility), and the EDI 810 Invoice (outbound — one per PO, quantities must match the 855). SBSA supports all required transactions plus optional ones including 860 (PO Change), 820 (Remittance Advice), 852 (Product Activity), and 997 (Functional Acknowledgment).
Zales enforces strict ASN compliance. Any shipment received at a Zales DC or store location without a corresponding EDI 856 ASN — or where the ASN arrives after the physical goods — is subject to refusal or a compliance chargeback. The 856 must be transmitted the moment your shipment leaves your facility. SBSA automates this transmission so it fires at the same time your shipping system generates the label, eliminating this risk entirely.
Yes — and as an Intuit Silver Partner, SBSA provides certified integration with both QuickBooks Online and QuickBooks Enterprise. Incoming Zales 850 POs create sales orders automatically in QuickBooks. Acknowledgments are generated from your QBO or QBE order confirmation, ASN data is pulled from your shipment records, and EDI 810 invoices are auto-generated from QuickBooks invoices — matched to 855 acknowledged quantities. Payments from the 820 Remittance Advice are auto-applied to open invoices. There is no manual data entry at any step in the process.
Zales requires a GS1-128 (formerly UCC-128) carton label on every inbound carton, whether shipping to a DC, a retail store, or as part of a drop ship order. The label must contain a scannable barcode encoding the PO number, item UPC, quantity, and carton sequence number. SBSA generates GS1-128 labels automatically from ASN data as part of the shipping workflow — labels are validated against the ASN contents before you dispatch, preventing labeling errors from reaching Zales.
For drop ship orders, the Zales EDI 850 PO includes the end customer's name, shipping address, and any gift or handling instructions. You fulfill the order and ship directly to the customer — but the shipment must appear to come from Zales. This means a Zales-branded packing slip only (no mention of your company), Zales-specified packaging where required, and a carrier tracking number included in the 856 ASN so Zales can trigger automated customer notifications. SBSA generates the Zales-branded packing slip from ASN data automatically and enforces branding compliance at every step.
Yes. Zales, Kay Jewelers, and Jared all operate under the Signet Jewelers umbrella and function as separate EDI trading partners with separate ISA/GS IDs and implementation guides. SBSA can set up and manage all three simultaneously. While each requires its own connectivity configuration and compliance monitoring, they share the same ERP mapping layer in your system — minimizing setup effort, reducing the number of integrations to maintain, and giving you a single consolidated compliance dashboard across all Signet banners.
Zales issues chargebacks for a range of compliance failures: missing or late 855 PO acknowledgment, late or missing ASN, ASN transmitted after physical goods arrive, non-compliant or missing GS1-128 carton labels, invoice quantities that don't match the 855, and drop ship packing slips with supplier branding. SBSA automates every step in this cycle — 855s fire within minutes of PO receipt, ASNs transmit at shipment time, labels are generated and validated before dispatch, and invoices are auto-matched to acknowledged quantities. Chargebacks from these causes are effectively eliminated.
Most suppliers are fully live with Zales EDI within 2–4 weeks of completing SBSA's onboarding questionnaire. The timeline covers connectivity setup (AS2, SFTP, or VAN), document mapping for all required and requested transactions, ERP or QuickBooks integration, GS1-128 label and packing slip configuration, Zales test environment validation, and production go-live with 24/7 monitoring active. Complex setups — for example, suppliers also onboarding Kay or Jared simultaneously, or those with custom ERP environments — may take slightly longer.
Tell us your fulfillment path — DC, store, or drop ship — and we'll build a complete Zales integration plan tailored to your business.
