Skip to content

Dock doors and arrivals

Floormode can plan when a delivery arrives, at which dock door, and land the goods in that door’s own bin. Nothing here is required: a warehouse that receives straight to the shelf keeps working exactly as before.

  • Dock doors
  • Receiving at a door
  • Plan arrivals
  • The put-away tour from a door
  • Correcting a dock booking
  • For integrations
  • See also

Add a door under Settings → Warehouses → your warehouse → Zones, stations & staff → Add station, kind Dock door.

  • Direction: Inbound (the default) or Inbound and outbound. A door that only ships is an outbound lane’s dispatch station (see outbound-lanes.md).
  • Door bin code (optional): the code of the door’s own bin. When empty, the bin takes the door’s code. The bin is named once: renaming the door later keeps the bin’s code.
  • The door’s bin belongs to the door. It is never picked from, never sold, never counted by a count task, never suggested for put-away and never a product’s home. You cannot edit, move, archive or retype it from Locations: edit the door instead.
  • Turning a door off keeps its bin; turning it on again uses the same bin. Deleting a door archives its bin with its history; adding a door with the same code later takes that bin back.
  • A door that still holds goods to put away, or that has a delivery checked in or being received at it, cannot be turned off or deleted. Deliveries only planned at the door lose the door and can be planned at another one.

A receipt’s receive place is a receiving station or an inbound dock door, chosen in Receiving station & route on the receipt page. There is one place per receipt.

  • In the Dock receiving flow, goods booked on a receipt at a door land in that door’s bin and owe a put-away from there. Without a door they land in DOCK-01, as before.
  • In Dock + inspect, goods always go to QC-IN-01 first.
  • In Direct, the door is only where the delivery is received; goods go to the shelf.
  • On the floor, ⋯ Change door moves the receipt to another door; a booking that names a door’s bin (the REST API, MCP) does the same.
  • If another phone moved the receipt to a different door while you were receiving, the floor asks “This receipt is now at DOOR-5. Book these there?” before booking. Nothing is booked twice.

Turn on Plan arrivals in Settings → Receiving & stock. Then:

  • A receipt shows an Arrival card: the day and time the delivery is due at the dock (in the warehouse’s own time zone), the door and a Reference (a trailer, container or booking number). Edit arrival changes the time and reference; Change door opens the receive place.
  • New receipt has an optional Arrival group.
  • Check in when the truck is at the door: on the receipt page, or on the floor under ⋯ in the receive screen. Receiving never waits for a check-in: the first booking marks the delivery as arrived. Undo check-in is offered while nothing is booked.
  • A delivery whose time has passed by 30 minutes with nothing checked in or booked shows Not arrived. A supplier’s promised day that has passed stays Overdue.
  • The Schedule and Home’s next deliveries list a receipt on its arrival day when one is planned, otherwise on its promised day.

Turning Plan arrivals off hides the arrival fields and the check-in; what was planned is kept.

On Floor Today, a person whose place is a dock door (in a warehouse using the Dock flow) walks the put-aways out of that door’s bin: “Put away 14 items · From DOOR-3”. Choosing another place walks every door’s put-aways. The tour from a door never adds another door’s work by itself.

A booking keyed wrong, or a carton found damaged, never has to go onto a shelf first. On the receipt’s Dock card, “Waiting at the dock” lists each putaway with Correct:

  • Reverse the booking takes the units back out of stock, and the receipt line is owed them again, as if they were never booked. It works on an open receipt of your own; a receipt a connected app sent (it was told what was received) or a delivery linked to a document keeps its bookings.
  • Set aside moves the units to a bin that sells nothing: damaged or packaging to HOSP-01, a wrong item, expired or other to QUAR-01. They count as rejected on the receipt line.

Either way the putaway carries fewer units, and is cancelled when none are left. A putaway a worker has already started is theirs to finish. Both need the receiving manage permission, and neither can be undone.

The REST API and the MCP server offer the same doors: receiving_set_station, receiving_set_arrival, receiving_check_in, receiving_check_in_undo, and receiving_record_line’s optional expectedAcceptanceBinId (the bin your screen showed), and receiving_dock_units / receiving_dock_correct for the corrections above.