Hudson's Bay EDI
integration guide.
Plan your Hudson's Bay EDI integration using 4 listed document types across 2 channels. Compare channels, map business records and test the operational handoff.
Listed documents
4
Partner document references
Listed channels
2
Hudson's Bay → Hudson's Bay 856
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
Hudson's Bay: EDI implementation plan
Build a reliable EDI workflow for Hudson's Bay. Use 4 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.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 810 InvoiceListed on 1 channel: Hudson's Bay | accounts-receivable or accounts-payable invoice invoice number, purchase order and invoice line |
|
| X12 850 Purchase OrderListed on 1 channel: Hudson's Bay | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
| X12 856 Ship Notice ManifestListed on 2 channels: Hudson's Bay, Hudson's Bay 856 | shipment notice (ASN) shipment, order, package and item references |
|
| X12 824 Application AdviceListed on 1 channel: Hudson's Bay | application validation result original document reference, error location and response status |
|
Implementation steps
-
Choose the trading account and channel
Choose among Hudson's Bay, Hudson's Bay 856. Confirm the business unit and account before copying a mapping from another channel.
-
Map records and assign owners
Start with accounts-receivable or accounts-payable invoice, purchase order or sales order, shipment notice (ASN). 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.
-
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 Hudson's Bay production handoff and save the results of each approved test.
-
Check results after launch
Match records between systems using invoice number, purchase order and invoice line. 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 Hudson's Bay
5 transactions across 2 channels.
Hudson's Bay 856
1 docDocument flow
Example document relationships for Hudson's Bay
Where each document sits in its trading cycle, based on the 4 document types listed for Hudson's Bay across 2 channels. These are example relationships; the trading agreement determines the required sequence.
Order-to-cash
Some example steps listed- 850 Purchase Order
- 855 Purchase Order Acknowledgment not listed for Hudson's Bay
- 856 Ship Notice Manifest
- 810 Invoice
- 810 Invoice — is listed on 1 of Hudson's Bay's 2 channels
- 824 Application Advice — is listed on 1 of Hudson's Bay's 2 channels
- 850 Purchase Order — is listed on 1 of Hudson's Bay's 2 channels
- 856 Ship Notice Manifest — is listed on 2 of Hudson's Bay's 2 channels
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 fundMigrate 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.
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:
Related references
Partners with related document listings
Compare document requirements for similar business processes.
John Deere 80 docs · 10 channels 
Costco 55 docs · 12 channels 
Walmart 32 docs · 8 channels 
JCPenney 25 docs · 20 channels 
CVS 25 docs · 5 channels 
Amazon 24 docs · 4 channels 
Saks Fifth Avenue & Saks OFF 5th 21 docs · 10 channels United Natural Foods, Inc. (UNFI) 17 docs · 4 channels AAFES (Army and Air Force Exchange Service) 15 docs · 3 channels 
AT&T Inc. 14 docs · 2 channels 
Starbucks Coffee Company 14 docs · 3 channels 
Kroger 11 docs · 2 channels Kroger Modernized Systems 10 docs · 1 channel 
Albertsons (Safeway) 9 docs · 2 channels John Deere Mexico 8 docs · 1 channel 
Joann Stores 6 docs · 1 channel 
Burlington Coat Factory 6 docs · 1 channel Kroger Manufacturing 5 docs · 1 channel 
Fred Meyer Group 5 docs · 1 channel Quebec Health Ministry 85 docs · 17 channels 
The Home Depot 48 docs · 11 channels 
Dillard's Department Stores, Inc. 30 docs · 3 channels 
Nordstrom 28 docs · 8 channels 
Target 23 docs · 4 channels 
NEXCOM (Navy Exchange Service Command) 20 docs · 2 channels 
Sprouts Farmers Market 19 docs · 2 channels 
Ulta Beauty 18 docs · 3 channels KeHE Distributors 18 docs · 5 channels 
Macy's 17 docs · 5 channels 
Aldi 16 docs · 2 channels 
GovX Inc. 15 docs · 3 channels 
Dot Foods, Inc. 14 docs · 2 channels 
Neiman Marcus 14 docs · 3 channels Boscov's Department Stores 13 docs · 2 channels 
Lowe's 13 docs · 2 channels 
AGCO Your Agriculture Company 12 docs · 2 channels 
Mountain High Outfitters 12 docs · 2 channels 
Loblaw Companies Limited 12 docs · 2 channels 
TJX Companies 12 docs · 3 channels 
Bloomingdale's 12 docs · 3 channels 
Grainger 12 docs · 4 channels 
Best Buy 12 docs · 3 channels 
Rivian Automotive, Inc 11 docs · 1 channel 
PetSmart 11 docs · 2 channels 
Bealls Inc. 11 docs · 2 channels 
Cardinal Health, Inc. 11 docs · 3 channels 
Sysco 11 docs · 2 channels Granite City Electric 10 docs · 1 channel
No references match your search.
Showing 21 of 48 references
Browse the full directoryFAQ
Hudson's Bay EDI questions
Which EDI documents are listed for Hudson's Bay?
X12 810 Invoice; X12 850 Purchase Order; X12 856 Ship Notice Manifest; X12 824 Application Advice. Confirm which documents, directions and versions apply to your account.
How should I choose the Hudson's Bay EDI channel?
The directory lists 2 channels for Hudson's Bay, including Hudson's Bay, Hudson's Bay 856. Match the channel to your actual trading relationship and compare its document list before reusing a mapping.
Which identifiers should the Hudson's Bay mapping preserve?
For X12 810 Invoice, plan around invoice number, purchase order and invoice line. For X12 850 Purchase Order, use buyer purchase order, order line and trading-party identifiers. Use the partner guide to locate these values and check their allowed formats.
Does a successful EDI receipt mean Hudson's Bay 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 Hudson's Bay EDI?
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. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
