Outbound Specialist

Multiple shifts are available, including day, evening/night, and weekend shifts.

GENERAL DESCRIPTION

The Outbound Specialist, Ground owns the origin half of the ground shipment file — from acceptance of the booking through confirmed departure from the origin. Working across e2open TMF and Descartes Aljex, the Outbound Specialist builds the shipment file in both systems, applies cost and revenue, generates the bill of lading, secures the pickup appointment, issues the warehouse pre-alert, establishes in-transit visibility through Tive and MacroPoint, and audits loading documentation against what was physically loaded.

The role concludes with a clean, complete handoff to the Inbound Specialist at origin departure. The Outbound Specialist is accountable for data parity between TMF and Aljex, for the accuracy of the signed BOL and piece count, and for the prompt escalation of scheduling, transportation, and security exceptions.

ESSENTIAL JOB FUNCTIONS

Booking Intake & File Build

• Accept the TMF booking created by the Operational Account Manager and verify shipment data, asset detail, and references are complete before building the file.
• Create the job in TMF, adding Crane Solutions as the carrier, and trigger the EDI booking to Descartes Aljex.
• Add cost and revenue in TMF and generate the bill of lading (BOL).
• Accept the EDI booking in Aljex, upload the TMF BOL into Aljex, and add revenue to Aljex so both systems carry matching financials.
• Assign the shipment to the Capacity Planning team and monitor the capacity planner queue until a carrier is confirmed, escalating unassigned loads that risk the pickup window.

Appointment, Pre-Alert & Shipment Visibility

• Update the TMF reference with the Open Dock appointment and set the estimated pickup milestone.
• Send the pre-alert email to the pickup warehouse using the TMF outbound template, including all BOLs and, where no system pre-alert exists, the originating email chain.
• Create the Tive shipment in the Tive portal using the BOL / shipment number, then enter the Tive tracker number into the Aljex reference field and the corresponding TMF field.
• Confirm with the origin site that the Tive session is active and MacroPoint has been downloaded before the truck is released.
• Apply the correct Tive process for CWW-loaded versus customer-loaded shipments and support GSOC Security Team auditing of Tive activations.

Loading, Documentation & Origin Departure

• Obtain the signed BOL from the carrier confirming which assets were physically loaded and upload it to both Aljex and TMF.
• Audit TMF against the signed BOL; add or remove assets, correct piece counts, and update carrier detail in both systems so the file reflects what shipped.
• Release the truck with a documented “good to go” within one hour of loading.
• Change the Aljex status to Loaded, add the delivery ETA, and post origin departure milestones in both Aljex and TMF.
• Clear the Service Rep field in Aljex to place the shipment into the Inbound Specialist queue, completing the origin-to-destination handoff.
• Work the TMF EDI booking queue so no booking sits unaddressed; the Operations Supervisor monitors this queue for coverage.
• Identify consolidation opportunities before duplicate bookings are built and raise them to the Operational Account Manager, Operations Supervisor, and Capacity Manager via Teams.
• Escalate scheduling exceptions (missed or unavailable appointments, capacity shortfalls, tight pickup windows) to the Capacity Planning Specialist and Operations Supervisor.
• Escalate transportation exceptions (carrier no‑shows, delays, equipment failures, routing problems) and drive them to resolution with the carrier and internal partners.
• Escalate security concerns — cargo integrity, tampering, chain-of-custody, or failed Tive activation — to the GSOC Security Team and management immediately.
• Escalate systemic and tooling gaps (assets missing from PULSE, manual TMF data entry, cross-border document requirements, integration defects) to the Program Manager rather than absorbing them as recurring manual rework.
• Maintain consistent milestones and reason codes across TMF and Aljex, and complete the shift handover checklist so in-flight files…