Skip to content
P4 Software P4 Software / logisticaHQ-en

Add these docs to Claude

Ask Claude questions about these docs. Claude reads the published pages and links you back to them. Copy this address:

https://p4-software.opendocs.page/mcp

In claude.ai or Claude Desktop: open Settings, then Connectors, choose Add custom connector and paste the address.

In Claude Code, run:

claude mcp add --transport http docs https://p4-software.opendocs.page/mcp

Document locks and client users

How an appointment locks its documents

When you book a purchase order, pick ticket, Truck Load or Master Truck Load, the appointment copies its number, date and dock door onto the document (a Master Truck Load also copies them onto the children that have not shipped; a shipped load is never rewritten). From then on, while the appointment is active (not finished, cancelled or a no-show) and the module is on, those three fields belong to the appointment:

  • On the document, they cannot be changed. The Purchase order details, Pick ticket details, Truck Load and Master Truck Load pages show them read-only, with the line Managed by dock appointment and the number. (The pick ticket page shows the appointment number and date for truck-load freight and the door for private-fleet freight, where it shows them at all.) A save that still carries the old values goes through, but the three fields stay as the appointment set them. Assigning a dock door directly or bulk-editing them is refused: "The appointment number, date and dock door of this purchase order are managed by appointment . Move the appointment on the dock schedule to change them" (each document kind says its own name). The customer return page has no such note: customer Returns cannot be booked in this release. The note is not read from the number written on the document: each page asks the server which active appointment covers it, so the note shows exactly when the server will hold those fields (a child of a booked master load is covered through the master and shows the note too). A delete or a save is still decided by the server, whatever the page shows.
  • To change them, move the appointment on the board. The document's copies move with it in the same save.
  • A covered document cannot be moved to another Warehouse: "Purchase order is booked on dock appointment [Y] in its current Warehouse; cancel that appointment first, then change the Warehouse" (for the other documents it begins "This pick ticket is booked on dock appointment [Y] ...").
  • A booked Truck Load cannot be added to a master load until its appointment is cancelled: "Truck Load is booked on appointment [Y]: cancel that appointment before adding it to a master load".

Cancelling (Cancel the appointment on the truck panel, or Undo booking on the confirmation) frees the door and the slots at once, unlinks the documents so the three fields can be edited again, and leaves what was copied on them as a record. A finished truck also lets go of its documents. Cancelling sends the carrier Email when that is on and the appointment holds an address.

Truck loads built from a booked pick ticket follow the appointment. When you build a Truck Load (Generate Truck loads, Create Truck Load from a pick ticket, or adding cartons to a load) from Pick tickets that are booked on a dock appointment, the load takes that appointment's number, date and dock door, is shown as covered by it (its page says Managed by dock appointment), and is listed among the appointment's documents. Moving the appointment moves the load with the tickets; cancelling it (or the truck being finished or a no-show) lets the load go, with what it copied left as a record. A load built before its ticket was booked, or before this rule existed, is brought along when the appointment is booked or next moved.

  • A Truck Load cannot hold Pick tickets booked on two different appointments: "Pick ticket [A] is booked on dock appointment and pick ticket [B] on dock appointment [Y], so they cannot go on one Truck Load. Book them on the same appointment first". Nothing is changed when this is refused. Tickets of one appointment plus tickets not booked at all make one load that follows the appointment.
  • A load and its Pick tickets cannot be booked apart: booking the load on its own while one of its tickets is on another appointment, or booking a ticket whose load is on another appointment, is refused and names the appointment. Cancel that appointment first.
  • Taking every ticket of the appointment off the load, or turning the load back to Draft, lets the load go from it.
  • A load booked on its own cannot be deleted while its appointment is active: "The Truck Load is already booked on appointment [Y]: cancel that appointment first".
  • A carton moved on the floor onto a pallet of another load takes the tie with it: the load it left lets go once its last ticket of the appointment has gone, and the load it joined follows the appointment. A move on the floor is never refused for this. If the load it joined already follows another appointment, that load stays as it is.
  • A load that has shipped is never rewritten, and a load inside a master load or an LTL load is left to the master (book the master load instead). Because a load built from a booked ticket is booked, it cannot be added to a master load until the appointment is cancelled.

What a client user sees

A user tied to one client (a 3PL customer's own login) sees and books only that client's trucks:

  • The board draws only that client's appointments. Other Clients' trucks still hold their doors, so a time can be refused ("Door is already booked at [Y]") or missing from the options without saying whose truck it is.
  • Find shows only that client's documents; every appointment is made for that client.
  • There is no crew strip, no crew reasons, no "Hour" ideas and no Open Dock doors button.
  • On the Setup screens there are no New, Seed defaults or Delete buttons for equipment types, groups and capacity rules; the server refuses those changes: "Dock scheduling Setup is changed by Warehouse staff. Ask your Warehouse contact to make this change." The same sentence answers a delete of a zone, Warehouse, carrier or dock door that runs into dock rows, and moving a dock door that holds trucks that are still coming to another Warehouse.
  • On Dock load types they see their own types and the shared ones, and can change only their own; the client is set for them.
  • The Dock scheduling part of the door dialog is not shown to them.

Was this page helpful?