Skip to content

Williams Sonoma EDI
integration guide.

Plan your Williams Sonoma EDI integration using 10 listed document types across 2 channels. Compare channels, map business records and test the operational handoff.

Book an EDI demo Explore EDI documents
Listed documents
10
Partner document references
Listed channels
2
Williams Sonoma (via Manhattan Associates) → Williams Sonoma via SPS
Implementation
Plan
Map, validate and reconcile

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Implementation guide

Williams Sonoma: EDI implementation plan

Build a reliable EDI workflow for Williams Sonoma. Use 10 document types across 2 channels to plan record mapping, prevent duplicate processing and reconcile results in your business systems.

The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 204 Motor Carrier Load TenderListed on 1 channel: Williams Sonoma (via Manhattan Associates) load tender

load reference, pickup and delivery stop identifiers
  • Send an amended pickup appointment and retain the previous tender decision.
  • Test a multi-stop load whose stop sequence differs from address sorting.
X12 990 Response To A Load TenderListed on 1 channel: Williams Sonoma (via Manhattan Associates) load-tender response

original load reference, carrier and response
  • Associate acceptance with the correct version of the load tender.
  • Test a declined tender and ensure it returns to dispatch for reassignment.
X12 214 Transportation Carrier Shipment Status MessageListed on 1 channel: Williams Sonoma (via Manhattan Associates) shipment status event

shipment reference, event code, event time and location
  • Deliver an older status after a newer one and retain event history without moving the current status backward.
  • Send one milestone twice and avoid duplicate customer notifications.
X12 865 Purchase Order Change Acknowledgment Request Seller InitiatedListed on 1 channel: Williams Sonoma via SPS seller order-change response or request

original purchase order, change reference and affected line
  • Distinguish a seller-proposed change from acceptance of a buyer-requested change.
  • Reject an outdated revision that would overwrite a later agreed quantity.
X12 855 Purchase Order AcknowledgmentListed on 1 channel: Williams Sonoma via SPS purchase-order response

original purchase order, response revision and order line
  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
X12 810 InvoiceListed on 1 channel: Williams Sonoma via SPS accounts-receivable or accounts-payable invoice

invoice number, purchase order and invoice line
  • Reconcile line amounts, allowances, charges and tax to the invoice total.
  • Submit the same invoice twice and verify that it cannot create a second payable.
X12 860 Purchase Order Change Request Buyer InitiatedListed on 1 channel: Williams Sonoma via SPS buyer order-change request

original purchase order, change revision and affected line
  • Apply a quantity reduction to the existing order instead of creating another order.
  • Test a cancellation arriving after allocation or shipment and route it to an exception owner.
X12 846 Inventory Inquiry AdviceListed on 1 channel: Williams Sonoma via SPS inventory availability record

item, location, quantity type and snapshot time
  • Distinguish on-hand, available and reserved quantities before publishing availability.
  • Deliver an old snapshot after a new one and prevent stale stock from replacing current values.
X12 856 Ship Notice ManifestListed on 1 channel: Williams Sonoma via SPS shipment notice (ASN)

shipment, order, package and item references
  • Reconcile item quantities through shipment, order and packaging levels against the physical shipment.
  • Test split shipments for one purchase order and prevent the second ASN from replacing the first.
X12 850 Purchase OrderListed on 1 channel: Williams Sonoma via SPS purchase order or sales order

buyer purchase order, order line and trading-party identifiers
  • Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit.
  • Resend one purchase order and confirm that only one sales order is created.

Implementation steps

  1. Choose the trading account and channel

    Choose among Williams Sonoma (via Manhattan Associates), Williams Sonoma via SPS. Confirm the business unit and account before copying a mapping from another channel.

  2. Map records and assign owners

    Start with load tender, load-tender response, shipment status event. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.

  3. Test a complete exchange

    Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Williams Sonoma production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using load reference, pickup and delivery stop identifiers. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document catalog

EDI documents listed for Williams Sonoma

10 transactions across 2 channels.

Document flow

Example document relationships for Williams Sonoma

Where each document sits in its trading cycle, based on the 10 document types listed for Williams Sonoma across 2 channels. These are example relationships; the trading agreement determines the required sequence.

Catalog & inventory

Some example steps listed
  1. 832 Price / Sales Catalog not listed for Williams Sonoma
  2. 846 Inventory Inquiry Advice
  3. 852 Product Activity Data not listed for Williams Sonoma
  • 204 Motor Carrier Load Tender — is listed on 1 of Williams Sonoma's 2 channels
  • 214 Transportation Carrier Shipment Status Message — is listed on 1 of Williams Sonoma's 2 channels
  • 810 Invoice — is listed on 1 of Williams Sonoma's 2 channels
  • 846 Inventory Inquiry Advice — is listed on 1 of Williams Sonoma's 2 channels
  • 850 Purchase Order — is listed on 1 of Williams Sonoma's 2 channels
  • 855 Purchase Order Acknowledgment — is listed on 1 of Williams Sonoma's 2 channels
  • 856 Ship Notice Manifest — is listed on 1 of Williams Sonoma's 2 channels
  • 860 Purchase Order Change Request Buyer Initiated — is listed on 1 of Williams Sonoma's 2 channels
  • 865 Purchase Order Change Acknowledgment Request Seller Initiated — is listed on 1 of Williams Sonoma's 2 channels
  • 990 Response To A Load Tender — is listed on 1 of Williams Sonoma's 2 channels

Network context

Williams Sonoma channel references for Manhattan Associates and SPS Commerce

These network names are derived from the listed Williams Sonoma channels. Confirm routing, enrollment and contractual requirements for your account before selecting a connection method.

LEGACY EDI MIGRATION FUND

Still with a legacy EDI vendor? We cover the buyout.

Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.

Check your eligibility for the EDI migration fund
Migrate from SPS Commerce
Migrate from Cleo
Migrate from TrueCommerce
Migrate from OpenText
SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more

Related references

Partners with related document listings

Compare document requirements for similar business processes.

Target 23 docs · 4 channels The Home Depot 48 docs · 11 channels Walmart 32 docs · 8 channels Costco 55 docs · 12 channels KeHE Distributors 18 docs · 5 channels Rivian Automotive, Inc 11 docs · 1 channel Sysco 11 docs · 2 channels Staples Inc. 9 docs · 2 channels United Natural Foods, Inc. (UNFI) 17 docs · 4 channels Aldi 16 docs · 2 channels Starbucks Coffee Company 14 docs · 3 channels Bealls Inc. 11 docs · 2 channels Shoe Carnival 10 docs · 2 channels Dick's Sporting Goods 10 docs · 3 channels Wayfair LLC 9 docs · 1 channel MSC Industrial Supply Co. 8 docs · 1 channel White Cap 8 docs · 1 channel MidwayUSA 7 docs · 1 channel Sportsman's Guide 7 docs · 1 channel QVC Group (dba Cornerstone Brands Inc) 7 docs · 1 channel Big Lots 7 docs · 2 channels

Showing 21 of 48 references

Browse the full directory

FAQ

Williams Sonoma EDI questions

Which EDI documents are listed for Williams Sonoma?

X12 204 Motor Carrier Load Tender; X12 990 Response To A Load Tender; X12 214 Transportation Carrier Shipment Status Message; X12 865 Purchase Order Change Acknowledgment Request Seller Initiated; X12 855 Purchase Order Acknowledgment; X12 810 Invoice; X12 860 Purchase Order Change Request Buyer Initiated; additional documents are shown in the mapping plan. Confirm which documents, directions and versions apply to your account.

How should I choose the Williams Sonoma EDI channel?

The directory lists 2 channels for Williams Sonoma, including Williams Sonoma (via Manhattan Associates), Williams Sonoma via SPS. Match the channel to your actual trading relationship and compare its document list before reusing a mapping.

Which identifiers should the Williams Sonoma mapping preserve?

For X12 204 Motor Carrier Load Tender, plan around load reference, pickup and delivery stop identifiers. For X12 990 Response To A Load Tender, use original load reference, carrier and response. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean Williams Sonoma accepted the business document?

Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.

What should be tested before launching Williams Sonoma EDI?

Send an amended pickup appointment and retain the previous tender decision. Test a multi-stop load whose stop sequence differs from address sorting. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Get started