Skip to content

Channel

SPS Stord

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

Documents
4 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

SPS Stord: EDI implementation plan

Build a reliable EDI workflow for SPS Stord. 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 945 Warehouse Shipping AdviceListed for SPS Stord warehouse shipment confirmation

warehouse order, shipment and shipped line

  • Test partial fulfillment and leave the unshipped order quantity open.
  • Reconcile shipped units and tracking references before preparing a customer-facing shipment notice.
X12 850 Purchase OrderListed for SPS Stord 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 846 Inventory Inquiry AdviceListed for SPS Stord 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 940 Warehouse Shipping OrderListed for SPS Stord warehouse fulfillment order

warehouse order, owner, ship-to and item

  • Test a cancellation after picking and define who approves any warehouse reversal.
  • Validate owner-specific SKU and unit mappings before allocating stock.

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 SPS Stord. Compare other Stord channels before reusing a mapping.

  2. Map records and assign owners

    Start with warehouse shipment confirmation, purchase order or sales order, inventory availability record. 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 Stord production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using warehouse order, shipment and shipped 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 flow on this channel

Document relationships on SPS Stord

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

Order-to-cash

Some example steps listed
  1. 850 Purchase Order
  2. 855 Purchase Order Acknowledgment not listed on SPS Stord
  3. 856 Ship Notice / Manifest (ASN) not listed on SPS Stord
  4. 810 Invoice not listed on SPS Stord

Catalog & inventory

Some example steps listed
  1. 832 Price / Sales Catalog not listed on SPS Stord
  2. 846 Inventory Inquiry Advice
  3. 852 Product Activity Data not listed on SPS Stord

SPS Stord questions

Which EDI documents are listed for SPS Stord?

X12 945 Warehouse Shipping Advice; X12 850 Purchase Order; X12 846 Inventory Inquiry Advice; X12 940 Warehouse Shipping Order. Confirm which documents, directions and versions apply to your account.

How should I choose the Stord EDI channel?

SPS Stord 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 Stord mapping preserve?

For X12 945 Warehouse Shipping Advice, plan around warehouse order, shipment and shipped 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 Stord 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 SPS Stord EDI?

Test partial fulfillment and leave the unshipped order quantity open. Reconcile shipped units and tracking references before preparing a customer-facing shipment notice. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Connect Stord 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.