Dock Scheduling

The dock stops
being a phone call.

Carriers book their own appointments against the doors, hours and rules you set. The yard, the doors and the appointments are one picture — and it stays accurate because the people booking are the people arriving.

dock.freightronics.net
Trailers backed into numbered dock doors Doors · appointments · yard
What it does

Appointments, doors and yard

Carrier self-service booking against rules you set, with the yard and the doors in the same picture.

Carrier self-service

Carriers get their own login, or a single-use booking link, and take a slot that is actually available — rather than calling a number and waiting for someone to check a spreadsheet.

Rules that hold

An availability engine evaluates your rules against every request — lead times, windows, appointment types, door capabilities — and explains which rule blocked a slot instead of just refusing it.

Doors and capacity

Doors with their own capabilities and downtime, capacity rules by shift, operating hours and schedule exceptions — so the calendar reflects the building rather than an ideal version of it.

Yard

Trailers, spots and moves tracked as their own records, so what is on the property and where is a question with an answer.

Availability engine

A refusal that explains itself

Most scheduling tools answer a booking request with a slot list and nothing else. When a carrier cannot get the time they need, the conversation moves to the phone — which is what the tool was supposed to prevent.

Rules here are evaluated individually and each violation is named, so a carrier is told which constraint they hit and what would satisfy it. Your team is not the exception-handling layer.

  • Rule registry and scopeRules defined, scoped and evaluated per request rather than hardcoded.
  • Named violationsA blocked slot comes back with the specific rule that blocked it.
  • Candidate slotsAvailability computed against real door capacity, hours and existing appointments.
  • Appointment typesDifferent rules for different work — live load, drop, pickup, return.
  • Webhook endpoints and deliveryRegistered endpoints with delivery records and retry.
  • Appointment eventsEvery state change kept as an event on the appointment.
  • Notification outboxDriver and carrier notifications queued and delivered, not fired and forgotten.
  • API accessAPI keys for systems that need to book or read programmatically.
Integration

Built to be talked to

A dock calendar that only exists in its own screen creates a second job: telling everyone else what it says.

Appointments raise events, webhooks deliver them with retry, and the appointment record carries its own history — so the warehouse, the TMS and the carrier all learn about a change the same way.

Coverage

What is in the box

Booking, capacity, yard and the integrations that keep everyone in step.

Booking 5

  • Carrier self-service portal
  • Single-use booking links
  • Appointment types
  • Reschedule and cancel
  • Check-in and check-out

Rules engine 5

  • Rule registry and scoping
  • Per-request evaluation
  • Named violations on refusal
  • Lead times and windows
  • Candidate slot generation

Capacity 5

  • Doors and door capabilities
  • Door downtime
  • Capacity rules by shift
  • Operating hours
  • Schedule exceptions

Yard 4

  • Yard spots
  • Trailer records
  • Yard moves
  • Live door status

Carriers 4

  • Carrier organisations
  • Carrier users
  • Tenant links and access
  • Carrier directory

Integration 6

  • Webhook endpoints
  • Delivery records and retry
  • Appointment event history
  • Notification outbox
  • API keys
  • Optional Opendock link
Connected

One layer under the whole lifecycle

A dock appointment is one moment in a longer chain. It comes from an order or a load and it ends as warehouse work — so it belongs on the same record.

Bring us your busiest door

The site where carriers queue, appointments slip and somebody spends the morning on the phone. That is where this earns its place.

Request a demo See all products