--- title: "Williams Sonoma EDI Integration | Stacksync" description: "Williams Sonoma EDI: 10 listed document types, channel comparison, record mapping and validation guidance for your integration." canonical: https://www.stacksync.com/edi/williams-sonoma last_modified: 2026-09-15 --- # *Williams Sonoma* EDI integration guide. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md 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](https://www.stacksync.com/book-a-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 - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding 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 decision | Record and matching IDs | What to test | | --- | --- | --- | | [X12 204 Motor Carrier Load Tender](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates/x12-204-motor-carrier-load-tender) Listed 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 Tender](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates/x12-990-response-to-a-load-tender) Listed 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 Message](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates/x12-214-transportation-carrier-shipment-status-message) Listed 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 Initiated](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) Listed 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 Acknowledgment](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-855-purchase-order-acknowledgment) Listed 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 Invoice](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-810-invoice) Listed 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 Initiated](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-860-purchase-order-change-request-buyer-initiated) Listed 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 Advice](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-846-inventory-inquiry-advice) Listed 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 Manifest](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-856-ship-notice-manifest) Listed 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 Order](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-850-purchase-order) Listed 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. ### Related documents and resources - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [Evaluate your integration requirements](https://www.stacksync.com/blog/integration-evaluation-worksheet) **Sources.** Directory data as of 2026-05-07. Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) - [Williams Sonoma document reference](https://www.orderful.com/network/williams-sonoma) Document catalog ## EDI documents listed for Williams Sonoma 10 transactions across 2 channels. ### [Williams Sonoma (via Manhattan Associates)](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates) 3 docs - [X12 204 Motor Carrier Load Tender](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates/x12-204-motor-carrier-load-tender) - [X12 990 Response To A Load Tender](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates/x12-990-response-to-a-load-tender) - [X12 214 Transportation Carrier Shipment Status Message](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates/x12-214-transportation-carrier-shipment-status-message) ### [Williams Sonoma via SPS](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps) 7 docs - [X12 865 Purchase Order Change Acknowledgment Request Seller Initiated](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-865-purchase-order-change-acknowledgment-request-seller-initiated) - [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-855-purchase-order-acknowledgment) - [X12 810 Invoice](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-810-invoice) - [X12 860 Purchase Order Change Request Buyer Initiated](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-860-purchase-order-change-request-buyer-initiated) - [X12 846 Inventory Inquiry Advice](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-846-inventory-inquiry-advice) - [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-856-ship-notice-manifest) - [X12 850 Purchase Order](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-850-purchase-order) 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. ### Order-to-cash All example steps listed 1. [850 Purchase Order](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-850-purchase-order) 2. [855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-855-purchase-order-acknowledgment) 3. [856 Ship Notice Manifest](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-856-ship-notice-manifest) 4. [810 Invoice](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-810-invoice) ### Logistics Some example steps listed 1. [204 Motor Carrier Load Tender](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates/x12-204-motor-carrier-load-tender) 2. [990 Response To A Load Tender](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates/x12-990-response-to-a-load-tender) 3. [214 Transportation Carrier Shipment Status Message](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-manhattan-associates/x12-214-transportation-carrier-shipment-status-message) 4. 210 Motor Carrier Freight Details and Invoice not listed for Williams Sonoma ### Catalog & inventory Some example steps listed 1. 832 Price / Sales Catalog not listed for Williams Sonoma 2. [846 Inventory Inquiry Advice](https://www.stacksync.com/edi/williams-sonoma/williams-sonoma-via-sps/x12-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. ### Manhattan Associates 17 channels · 16 trading partners in the catalog Williams Sonoma channel on this network: Williams Sonoma (via Manhattan Associates) Most frequently listed documents - 204 17 ch - 214 17 ch - 990 17 ch - 210 9 ch Also listed with Manhattan Associates - [Dicks Sporting Goods, Inc. (via Manhattan Associates)](https://www.stacksync.com/edi/dicks-sporting-goods-via-manhattan) - [Carhartt, Inc.](https://www.stacksync.com/edi/carhartt) - [The Marzetti Company (formerly Lancaster Colony Company)](https://www.stacksync.com/edi/lancaster-colony-company) - [GNC Holdings, LLC (via Manhattan Associates)](https://www.stacksync.com/edi/gnc-manhattan) - [BJ's Wholesale Club (via Manhattan Associates)](https://www.stacksync.com/edi/bjs-wholesalemanhattan) - [Ventura Foods](https://www.stacksync.com/edi/ventura-foods) ### SPS Commerce 94 channels · 74 trading partners in the catalog Leaving SPS Commerce? See how Stacksync compares as an [SPS Commerce alternative](https://www.stacksync.com/sps-commerce-alternative). Williams Sonoma channel on this network: Williams Sonoma via SPS Most frequently listed documents - 850 92 ch - 810 91 ch - 856 90 ch - 855 87 ch - 860 56 ch Also listed with SPS Commerce - [Sports Basement](https://www.stacksync.com/edi/the-sports-basement) - [Core-Mark (via SPS Commerce)](https://www.stacksync.com/edi/coremark-pfgcoremark) - [West Coast Kids](https://www.stacksync.com/edi/west-coast-kids) - [Ferguson Enterprises Inc.](https://www.stacksync.com/edi/ferguson-enterprises) - [Grove Collaborative, Inc.](https://www.stacksync.com/edi/grove) - [Superior Communications](https://www.stacksync.com/edi/superior-communication) LEGACY EDI MIGRATION FUND ## Still with a legacy EDI vendor? Ask about a contract buyout. Stacksync can buy out your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. Eligibility and terms are confirmed on a call. [Check your eligibility for the EDI migration fund](https://www.stacksync.com/book-a-demo) | | | | --- | --- | | | [Migrate from SPS Commerce](https://www.stacksync.com/sps-commerce-alternative) | | | 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](https://www.stacksync.com/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 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more Related references ## Partners with related document listings Compare document requirements for similar business processes. [Target 23 docs · 4 channels](https://www.stacksync.com/edi/target) [The Home Depot 48 docs · 11 channels](https://www.stacksync.com/edi/the-home-depot) [Walmart 32 docs · 8 channels](https://www.stacksync.com/edi/walmart) [Costco 55 docs · 12 channels](https://www.stacksync.com/edi/costco) [KeHE Distributors 18 docs · 5 channels](https://www.stacksync.com/edi/kehe-distributors) [Rivian Automotive, Inc 11 docs · 1 channel](https://www.stacksync.com/edi/rivian-automotive-inc) [Sysco 11 docs · 2 channels](https://www.stacksync.com/edi/sysco) [Staples Inc. 9 docs · 2 channels](https://www.stacksync.com/edi/staples) [United Natural Foods, Inc. (UNFI) 17 docs · 4 channels](https://www.stacksync.com/edi/united-natural-foods-inc-unfi) [Aldi 16 docs · 2 channels](https://www.stacksync.com/edi/aldi) [Starbucks Coffee Company 14 docs · 3 channels](https://www.stacksync.com/edi/starbucks) [Bealls Inc. 11 docs · 2 channels](https://www.stacksync.com/edi/bealls-inc) [Shoe Carnival 10 docs · 2 channels](https://www.stacksync.com/edi/shoe-carnival) [Dick's Sporting Goods 10 docs · 3 channels](https://www.stacksync.com/edi/dicks-sporting-goods) [Wayfair LLC 9 docs · 1 channel](https://www.stacksync.com/edi/wayfair-llc) [MSC Industrial Supply Co. 8 docs · 1 channel](https://www.stacksync.com/edi/msc-industrial-supply) [White Cap 8 docs · 1 channel](https://www.stacksync.com/edi/white-cap) [MidwayUSA 7 docs · 1 channel](https://www.stacksync.com/edi/midwayusa) [Sportsman's Guide 7 docs · 1 channel](https://www.stacksync.com/edi/sportsmans-guide) [QVC Group (dba Cornerstone Brands Inc) 7 docs · 1 channel](https://www.stacksync.com/edi/garnet-hill) [Big Lots 7 docs · 2 channels](https://www.stacksync.com/edi/big-lots) [Browse the full directory](https://www.stacksync.com/edi) 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. ## Your last integration took months. Your next one takes a prompt. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)