Announcement:

SharkeyTransportation

EDI integrations

Sharkey Transportation is a respectable and well-established transportation firm based in the United States. Sharkey Transportation is well-known for its focus on customer satisfaction, on-time delivery, and safety. Sharkey Transportation, with a significant presence in the market, specializes in offering dependable and effective transportation solutions across various industries. Truckload, less-than-truckload (LTL), dedicated, and expedited delivery are among the services provided by the company.

Integrate EDI with SharkeyTransportation and fully automate your EDI workflow in under 2 weeks, starting at $200/doc. Zenbridge is the fastest and cheapest way to get EDI integrated with SharkeyTransportation.

End-to-end EDI Automation with SharkeyTransportation

Zenbridge has a pre-built connector for all EDI documents required & supported by SharkeyTransportation. You can integrate the EDI transaction sets listed below with SharkeyTransportation at 100% compliance.

Set No

Name

EDI 204 (Motor Carrier Load Tender) is an X12 transaction set that shippers or other parties use to tender a shipment to full-load motor carriers. It includes shipping instructions, schedule details, equipment requirements, and commodities apposite a load tender. It is not used for less-than-truckload bills, pickup notifications, or manifest data.
EDI 210 (Motor Carrier Freight Details and Invoice) is an X12 transaction used for providing details for charges for services offered by a motor carrier. It can be used to send motor carrier invoices or details for motor freight shipment charges.
EDI 214 (Transportation Carrier Shipment Status Message) is an X12 transaction set that transportation carriers use to send shipment statuses, including time, date, location, route, identification numbers, and conveyance, to the shippers, consignees, and other parties.
EDI 990 (Response to a Load Tender) is an X12 transaction set used for general information requested for a specific shipment. EDI 990 is used as a response to EDI 204, which is used as a load tender.