--- title: "Canadian Pacific Railway EDI Integration | Stacksync" description: "Canadian Pacific Railway EDI: 6 listed document types, channel comparison, record mapping and validation guidance for your integration." canonical: https://www.stacksync.com/edi/canadian-pacific-railway last_modified: 2026-09-15 --- # *Canadian Pacific Railway* 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 Canadian Pacific Railway EDI integration using 6 listed document types across 1 channel. 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 | 6 | Partner document references | | Listed channels | 1 | Canadian Pacific Railway | | 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 ## Canadian Pacific Railway: EDI implementation plan Build a reliable EDI workflow for Canadian Pacific Railway. Use 6 document types across 1 channel 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 404 Rail Carrier Shipment Information](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-404-rail-carrier-shipment-information) Listed on 1 channel: Canadian Pacific Railway | **rail shipment** rail shipment reference, equipment and route | Test a route involving more than one carrier and retain interchange details. Separate repeated equipment numbers across different shipment dates. | | [X12 322 Terminal Operations And Intermodal Ramp Activity](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-322-terminal-operations-and-intermodal-ramp-activity) Listed on 1 channel: Canadian Pacific Railway | **terminal equipment event** container or rail equipment, event time and terminal | Process an out-gate event arriving before the in-gate event without discarding either. Test reuse of an equipment number on a later visit and keep the visits distinct. | | [X12 214 Transportation Carrier Shipment Status Message](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-214-transportation-carrier-shipment-status-message) Listed on 1 channel: Canadian Pacific Railway | **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 417 Rail Carrier Waybill Interchange](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-417-rail-carrier-waybill-interchange) Listed on 1 channel: Canadian Pacific Railway | **rail waybill interchange** waybill, originating carrier and equipment | Preserve originating references when a connecting carrier assigns its own number. Test a waybill correction after interchange and identify which record it supersedes. | | [X12 990 Response To A Load Tender](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-990-response-to-a-load-tender) Listed on 1 channel: Canadian Pacific Railway | **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 824 Application Advice](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-824-application-advice) Listed on 1 channel: Canadian Pacific Railway | **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 Choose among Canadian Pacific Railway. Confirm the business unit and account before copying a mapping from another channel. 2. #### Map records and assign owners Start with rail shipment, terminal equipment event, 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 Canadian Pacific Railway production handoff and save the results of each approved test. 4. #### Check results after launch Match records between systems using rail shipment reference, equipment and route. 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/) - [Canadian Pacific Railway document reference](https://www.orderful.com/network/canadian-pacific-railway) Document catalog ## EDI documents listed for Canadian Pacific Railway 6 transactions across 1 channel. ### [Canadian Pacific Railway](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway) 6 docs - [X12 404 Rail Carrier Shipment Information](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-404-rail-carrier-shipment-information) - [X12 322 Terminal Operations And Intermodal Ramp Activity](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-322-terminal-operations-and-intermodal-ramp-activity) - [X12 214 Transportation Carrier Shipment Status Message](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-214-transportation-carrier-shipment-status-message) - [X12 417 Rail Carrier Waybill Interchange](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-417-rail-carrier-waybill-interchange) - [X12 990 Response To A Load Tender](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-990-response-to-a-load-tender) - [X12 824 Application Advice](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-824-application-advice) Document flow ## Example document relationships for Canadian Pacific Railway Where each document sits in its trading cycle, based on the 6 document types listed for Canadian Pacific Railway across 1 channel. These are example relationships; the trading agreement determines the required sequence. ### Logistics Some example steps listed 1. 204 Motor Carrier Load Tender not listed for Canadian Pacific Railway 2. [990 Response To A Load Tender](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-990-response-to-a-load-tender) 3. [214 Transportation Carrier Shipment Status Message](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-214-transportation-carrier-shipment-status-message) 4. 210 Motor Carrier Freight Details and Invoice not listed for Canadian Pacific Railway 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. [Canadian National Railway 6 docs · 1 channel](https://www.stacksync.com/edi/canadian-national-railway) [Costco 55 docs · 12 channels](https://www.stacksync.com/edi/costco) [Walmart 32 docs · 8 channels](https://www.stacksync.com/edi/walmart) [United Natural Foods, Inc. (UNFI) 17 docs · 4 channels](https://www.stacksync.com/edi/united-natural-foods-inc-unfi) [Starbucks Coffee Company 14 docs · 3 channels](https://www.stacksync.com/edi/starbucks) [CPKC (formerly Kansas City Southern) 4 docs · 1 channel](https://www.stacksync.com/edi/kansas-city-southern) [COFC 3 docs · 1 channel](https://www.stacksync.com/edi/cofc) [E2open, LLC 143 docs · 37 channels](https://www.stacksync.com/edi/e2open) [Ryder 49 docs · 21 channels](https://www.stacksync.com/edi/ryder) [The Home Depot 48 docs · 11 channels](https://www.stacksync.com/edi/the-home-depot) [Mercury Gate 45 docs · 12 channels](https://www.stacksync.com/edi/mercury-gate) [Target 23 docs · 4 channels](https://www.stacksync.com/edi/target) [KeHE Distributors 18 docs · 5 channels](https://www.stacksync.com/edi/kehe-distributors) [Aldi 16 docs · 2 channels](https://www.stacksync.com/edi/aldi) [Ventura Foods 12 docs · 2 channels](https://www.stacksync.com/edi/ventura-foods) [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) [Dow Inc. 10 docs · 1 channel](https://www.stacksync.com/edi/dow-inc) [Williams Sonoma 10 docs · 2 channels](https://www.stacksync.com/edi/williams-sonoma) [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) [Browse the full directory](https://www.stacksync.com/edi) FAQ ## Canadian Pacific Railway EDI questions ### Which EDI documents are listed for Canadian Pacific Railway? X12 404 Rail Carrier Shipment Information; X12 322 Terminal Operations And Intermodal Ramp Activity; X12 214 Transportation Carrier Shipment Status Message; X12 417 Rail Carrier Waybill Interchange; X12 990 Response To A Load Tender; X12 824 Application Advice. Confirm which documents, directions and versions apply to your account. ### How should I choose the Canadian Pacific Railway EDI channel? The directory lists 1 channels for Canadian Pacific Railway, including Canadian Pacific Railway. Match the channel to your actual trading relationship and compare its document list before reusing a mapping. ### Which identifiers should the Canadian Pacific Railway mapping preserve? For X12 404 Rail Carrier Shipment Information, plan around rail shipment reference, equipment and route. For X12 322 Terminal Operations And Intermodal Ramp Activity, use container or rail equipment, event time and terminal. Use the partner guide to locate these values and check their allowed formats. ### Does a successful EDI receipt mean Canadian Pacific Railway 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 Canadian Pacific Railway EDI? Test a route involving more than one carrier and retain interchange details. Separate repeated equipment numbers across different shipment dates. 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/)