Overview
Understanding Canadian Pacific Kansas City integration
Who this is for: Shippers, intermodal marketing companies and logistics providers that move freight by rail with Canadian Pacific Kansas City, and their transportation and finance teams.
Scope: CPKC's base 404 implementation guide and its invoice documents are not on its public pages. Documents beyond the 404, 417 and status messages are listed as commonly used.
Canadian Pacific Kansas City is a freight railroad. ECOM's directory lists it under rail. Shippers and logistics providers working with railroads typically send shipment information, receive status events and ramp or terminal activity, and settle charges through the railroad's billing process.
With a railroad, the difficulty is keeping tenders, status events and invoices consistent with each other, and noticing a missing message early. Canadian Pacific Kansas City's own EDI or API specification is not part of this guide and no Canadian Pacific Kansas City document was read: treat what follows as typical practice for a railroad, and confirm the documents, X12 version, delivery method and testing steps with Canadian Pacific Kansas City.
ECOM maps the documents to your TMS, ERP and finance systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.