Oracle

Oracle Transportation Management (OTM) is the enterprise TMS inside Oracle Fusion Cloud SCM for planning, executing and billing freight. Order releases and shipments created in OTM appear in Load Hub with stops, ship units and reference numbers. Digital workers quote, dispatch and track them, and each milestone posts back to the OTM shipment. Transport operations usually requests it; the OTM admin provisions the integration user.

What teams use it for

Quote a shipment when OTM releases it

An order release lands in OTM, and a planner would normally email carriers for a rate and type the winner back in. Cargofy reads the order release and its shipment into Load Hub and matches locations and parties to Carrier Network, so the lane has contacts. A digital worker quotes the shipment in Sales against your carrier list and puts the offers side by side. The planner picks one, and the order release status is written back to OTM.

Dispatch without re-keying stops and ship units

OTM builds a shipment from an order release, with stops, ship units, lines, reference numbers and remarks. Cargofy reads it into Load Hub as one object. A dispatcher tenders a tanker load from Houston to Atlanta with the pickup window, ship units and customer PO attached. When the carrier confirms, Cargofy writes the shipment update back to OTM, and the reference numbers on the rate confirmation match the ones on the OTM shipment.

See exceptions before the customer calls

In OTM, a late truck is late only once someone posts the event. With Tracking connected, a digital worker follows the carrier's milestones and posts each one to the OTM shipment as a tracking event. When a pickup slips past its window or a delivery appointment is at risk, the worker flags it in Tracking. The customer service rep sees the exception with the shipment, carrier contact and affected stop, and OTM shows the same event.

Match the carrier invoice to the agreed rate

Carrier invoices arrive in OTM weeks after the rate was agreed. Cargofy reads invoices and freight charges from OTM into Finance and puts them beside the rate from the tender. A digital worker matches the base rate, isolates the accessorials, and flags a detention charge that has no supporting event. The AP clerk approves the clean invoices and reviews only the flagged lines.

Move peak volume in batches

When a plant releases hundreds of orders at once, a shipment-by-shipment sync is slow and hits limits. Cargofy uses the asynchronous batch REST endpoint, so a Monday release of several hundred order releases lands in Load Hub in one pass. Planners start the shift with the full board, and statuses go back to OTM through the same batch path.

How it fits your stack

OTM stays the system of record. Cargofy reads order releases, shipments with their stops, ship units, lines, reference numbers and remarks, locations, parties, invoices and freight charges. It writes order release status updates, shipment updates and tracking events. Setup is per instance: your admin provisions an integration user with HTTP Basic or OAuth credentials, and Cargofy maps the active entities to your configuration. Rate contracts and rating logic stay in OTM. Cargofy does not rewrite rate records or change OTM agents or flows.

Who it is for

Large shippers and manufacturers on a licensed Oracle Cloud OTM instance that run their own carrier base. Transport planners work order releases and shipments in Load Hub, AP clerks reconcile carrier invoices in Finance, and the OTM admin owns the integration user.