Overview
Understanding A.N. Deringer integration
Who this is for: Shippers, brokers and logistics teams that import or export goods and use a customs broker and forwarder with A.N. Deringer, and the transportation, IT and finance staff who connect those shipments to a TMS or ERP.
Scope: Formats, protocols, implementation guides and 997 come from Deringer's EDI page. Set numbers for shipment and invoice documents are not listed there and are typical practice.
Importers and exporters using A.N. Deringer need shipment, entry and invoice data to flow between their systems and the broker. The exchange that matters is the shipping and commercial data out and clearance status, documents and invoices back.
Deringer's EDI page says it accepts X12 EDI, XML, positional, CSV and proprietary flat file formats; supports AS2 (its preferred method), AS1, HTTPS, VAN, FTP, FTPS, SFTP and SMTP; provides implementation guides showing mandatory, optional and conditional segments and code values; and sends 997 functional acknowledgments on request. It describes its main focus as forwarding processed data to U.S. Customs and Border Protection and its warehouse management system, with lights-out processing as the aim. Its eShipPartner portal provides shipment data. The page does not list X12 set numbers, so the documents below are typical.
ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications. It then monitors every file after go-live and handles partner changes, as software, as a managed service or both.