Reference · built on requestOperator by FibricFleet, routes & field

Dock Schedule

Watches inbound carrier ETAs against dock-door appointments and proposes re-slotting late or early trucks before doors sit idle or queue.

Request accessPricing ↗

About

Dock Schedule is an operator job for the receiving door. It reads today's appointments at each site: slot, door, carrier, trailer, and the shipment expected. It reads where each inbound load actually is and when the tracking platform now expects it, and it reads the purchase orders and advance ship notices the warehouse is waiting on.

When a truck's ETA drifts outside its slot, it looks for a slot that fits: later for a late truck, earlier for one that will arrive with time to spare, and the door that leaves the fewest gaps. It proposes the change to the receiving lead with the ETA that caused it. Once approved, the appointment is rescheduled once through the appointment system, and the ETA, slot, and decision are kept together.

This is a reference listing. It documents what Fibric would read from Dock Schedule and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Appointments at a site through project44 GET /services/appointments/v1/appointments by siteCode and date, with slot times and the yardShipment's carrier and trailer
  • Site capacity for a date through GET /services/appointments/v1/capacity: totalSlots, totalBookedSlots, availableSlots, and unplannedShipmentsCount
  • Shipment ETAs and exceptions from project44 tracking, and FourKites load status, position, and ETA for truckload and LTL
  • Arrival milestones on an appointment: ARRIVED, CHECKED_IN, and START with scheduledDateTime and actualDateTime
  • Own-fleet trucks reaching the yard through Samsara RouteStopArrival events at the site's stop
  • Inbound purchase orders and advance ship notices in ShipHero, with the Shipment ASN and PO Update webhooks

Proposed actions

  • Target capability: propose a reschedule through PUT /services/appointments/v1/appointments/{appointmentId} with the new slot times and a reasonCode
  • Target capability: propose an earlier slot for a truck ahead of schedule, chosen from POST /services/appointments/v1/slots for its shipment
  • Target capability: propose the change to the receiving lead in Slack or Microsoft Teams, with the ETA, the old slot, and the new one
  • Target capability: propose a note to the carrier or driver with the confirmed slot, through the messaging connector you bind
  • Target capability: propose a morning list of appointments whose ETA already misses the slot, ordered by door

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Re-slot a late truck in project44

    A tracked shipment's ETA moves past its appointment. The operator finds a later slot through the slots call and proposes PUT on the appointment with reasonCode RESCHEDULE, for the receiving lead to approve in Slack.

    With project44, Slack

  • Pull an early FourKites load forward

    A load with an ETA well ahead of its slot is matched to an open earlier slot at the same site. The operator proposes the move so the door does not sit idle before it.

    With FourKites, Microsoft Teams

  • Match the door to what the ASN says is on the truck

    The ShipHero ASN shows the lines expected. Where the load needs more receiving time than its slot allows, the operator proposes a longer slot before the truck arrives.

    With ShipHero, project44

  • Slot the company's own trucks by arrival

    Samsara RouteStopArrival at the yard shows a truck arriving without an appointment. The operator proposes the next open slot at the site.

    With Samsara, project44

Requirements

  • An appointment system with slots and reschedules through an API: project44 YMS Appointments, or FourKites Appointment Manager
  • Shipment tracking with an ETA per inbound load: project44 or FourKites
  • A warehouse connector for what each load carries, ShipHero or another WMS, where receiving labor depends on the contents
  • Slack or Microsoft Teams for the receiving lead's approval
Authentication
Appointments, tracking, and warehouse records are read and proposed through the connectors you bind; the operator keeps no credential of its own.

Limits

  • It reschedules within the slots the appointment system offers. It does not add doors, extend hours, or change site capacity
  • An ETA is the tracking platform's estimate; a truck that stops reporting keeps its last ETA until a new position arrives
  • FourKites' API reference sits behind a sign-in, so the FourKites side of this listing is drawn from its developer portal and public pages
  • A carrier that has not accepted a new slot is shown as proposed, not confirmed, until the appointment system says otherwise

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Dock Schedule ↗

Questions and answers

What does the receiving lead approve?
A slot change for one appointment: the carrier and trailer, the slot it holds, the ETA that no longer fits, the slot proposed, and the door. The lead accepts, picks another slot, or leaves it. The appointment stays as booked until then.
What record is left?
The appointment as booked, the ETA and position read with their time, the capacity for the day, the slot proposed, the approval with name and time, and the reschedule as the appointment system confirmed it, so the original slot can be restored.
Does it move appointments without asking?
No. Every reschedule waits for approval. The operator can list what already misses its slot, but it changes nothing on its own, and it never cancels an appointment.
Ask about Dock Schedule

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy