Skip to content

Channel

Hudson's Bay

Plan a reliable EDI exchange for Hudson's Bay. Explore 4 document references, map them to your business records and test the complete workflow before launch.

Book an EDI demo ← All Hudson's Bay channels
Documents
4 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

Hudson's Bay: EDI implementation plan

Build a reliable EDI workflow for Hudson's Bay. Use 4 document types 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 810 InvoiceListed for Hudson's Bay 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 850 Purchase OrderListed for Hudson's Bay 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.
X12 856 Ship Notice ManifestListed for Hudson's Bay 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 824 Application AdviceListed for Hudson's Bay application validation result

original document reference, error location and response status
  • Return an error for one line and associate it with that line rather than rejecting unrelated records.
  • Keep application acceptance distinct from transport receipt and syntax acknowledgment.

Implementation steps

  1. Choose the trading account and channel

    Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Hudson's Bay. Compare other Hudson's Bay channels before reusing a mapping.

  2. 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.

  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 Hudson's Bay production handoff and save the results of each approved test.

  4. 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

4 EDI transactions listed in this catalog.

Document flow on this channel

Document relationships on Hudson's Bay

This channel lists all 4 document types in the Hudson's Bay directory. Example relationships are shown below; confirm the required sequence in the channel guide.

Hudson's Bay 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?

Hudson's Bay lists 4 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.

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.

Related references

Other Hudson's Bay channels

Compare the document lists for other Hudson's Bay channels.

Hudson's Bay 856 1 doc

Showing 1 of 1 references

Browse the full directory

Connect Hudson's Bay EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.

Book an EDI demo Explore the EDI platform