Research library

Sources checked: October 22, 2026

B2B Freight Delivery Appointments and Proof of Delivery

Freight planning does not end when a carrier is booked. A delivery also has to reach the intended site and dock, fit an agreed receiving window, and leave enough linked evidence for the receiving team to decide what physically arrived. When appointment, carrier, and warehouse records use different identifiers or status labels, an expected arrival can become hard to find just when an exception needs attention.

For Educational and Informational Purposes Only — Not Legal or Financial Advice.

This guide is general technical research for B2B commerce teams. It does not provide legal, tax, accounting, financial, security, performance, pricing, compliance, or individualized implementation advice. Carrier, appointment, document, and warehouse behavior depends on the selected systems, accounts, locations, and operating agreements.

Define the handoff this guide covers

This guide focuses on the freight handoff from an arranged delivery stop through appointment coordination, carrier arrival and delivery evidence, and the receiving team's linked record. For the earlier stage of connecting fulfillment providers and defining each provider's activation and exception boundaries, see the 3PL onboarding guide. The OMS architecture guide covers broader order routing and fulfillment responsibilities.

Keep four outcomes separate in the operating model:

  1. A delivery window was requested or confirmed for a particular site and shipment stop.
  2. A carrier reported arrival, an attempt, or delivery using its own event and reference.
  3. A delivery document or other source evidence became available, if the connected service and carrier provide it.
  4. The receiving operation recorded the goods it handled, including any partial quantity or discrepancy that needs review.

One outcome may inform the next, but the record of one should not silently complete the others. For example, a booked dock window does not prove the truck arrived, a carrier-delivered status does not establish an inventory quantity, and a delivery receipt should be matched to the receiving record before it is treated as evidence for a specific order or load.

Link the appointment to shipment, stop, and receiving references

Before evaluating an appointment API, yard or dock system, transportation platform, carrier portal, or manual process, agree on how one planned delivery can be found across systems. Preserve the original identifier with its issuing system and scope; do not assume an order number, bill of lading (BOL), or carrier PRO number is unique across every source.

RecordUseful linkage questions
Freight shipment or loadWhich order, purchase order, transfer, inbound shipment notice, fulfillment, and shipment or load IDs describe the intended movement? Can one order line arrive on multiple loads?
Delivery stopWhich receiving site, address, location code, stop sequence, dock or receiving area, and local time zone apply? Who can correct them?
AppointmentWhich request or appointment ID, requested window, confirmed window, source status, and last-change reference connect the slot to the shipment and stop?
Carrier movementWhich BOL, PRO or other carrier shipment reference, event ID, source timestamp, and carrier status can be correlated with the appointment?
Delivery evidenceWhich document or image ID, document type, source, retrieval time, shipment reference, and access location connect evidence to the delivery?
Receiving recordWhich warehouse receipt, order line, item, quantity, site, and discrepancy record represents the physical result?

Use the keys that the connected systems support and validate them with real partner examples. Keep a cross-reference when one system assigns its own appointment or load ID. If a freight shipment has several stops, treat the appointment as a stop-level record rather than attaching every appointment only to the overall shipment.

project44's Appointments API documents create, reschedule, cancel, and fetch operations for yard-management appointments. Its appointment request example uses a start and end time and identifies a shipment reference, stop sequence, and site code. Those fields illustrate one product's documented integration model; confirm which identifiers, time conventions, and operations are supported in the product and site being evaluated.

Make the requested window and its changes visible

An appointment is a coordination record, not just a date field. Capture the requested window, the time zone and location it applies to, who requested it, the shipment and stop it concerns, and the response that made it confirmed, rejected, or in need of another slot. Retain changes so transportation and receiving teams can see both the current plan and the prior request.

Define the states your own operators need to distinguish. A practical local model may separate draft, requested, confirmed, reschedule requested, cancelled, arrival reported, check-in recorded, unloading underway, and completed or missed. These are example distinctions, not a standard status vocabulary. Map each local state to the source action or message that justifies it, and preserve the source status beside any normalized label.

Microsoft's Dynamics 365 Supply Chain Management appointment procedure describes an appointment for an inbound or outbound load based on a sales, purchase, or transfer order, with a date and time agreed with the carrier. The procedure schedules after a load has been created; after scheduling, the appointment status shown in that workflow is Waiting, which Microsoft explains means the driver has not yet checked in. This is a Dynamics 365 example only. It is a useful reminder to confirm whether the selected system distinguishes an agreed appointment from a driver's actual arrival.

For each state transition, decide who can make the change and who must be notified. A carrier reschedule request, a receiving-site capacity change, a transportation-team correction, and a check-in scan may arrive through different paths. Route conflicts to an owner with the original shipment and appointment references instead of replacing a confirmed slot without a trace.

Correlate carrier events with the planned stop

Carrier movement signals and dock scheduling often describe related milestones from different viewpoints. The carrier may report an estimated arrival, attempted delivery, or delivered event; the yard or warehouse may record gate arrival, check-in, dock assignment, unloading, or a physical receipt. Define which system supplies each event, retain its timestamp and source, and state whether a value is an estimate, an observation, or a completed business action.

Use an explicit matching rule for incoming updates. Depending on the integration, the match may require a carrier reference plus a destination, stop, or appointment reference; an order ID alone can be too broad when deliveries split or a load visits multiple locations. Handle repeated or delayed events idempotently at the business-record level: a duplicate arrival event should not create a second receiving record, and an event for a cancelled or replaced appointment should reach review.

When the date or time zone changes, preserve the value as received and the local interpretation used by the receiving site. Verify how daylight-saving transitions, overnight windows, and changes to the planned delivery day are represented in the systems under consideration. These are evaluation and test cases, not a claim that any one data format or time policy is universal.

Treat proof of delivery as linked evidence

Use “proof of delivery” (POD) as a document or evidence category only after confirming what the source actually supplies. A document might be available from a carrier portal, a transportation platform, an API, or a separate approved workflow; it may arrive later than a status update or may not be available through the integration being evaluated. Keep the reference and availability state even when the image itself cannot be attached to the receiving transaction.

project44's LTL image retrieval documentation lists DELIVERY_RECEIPT as a document type that can be requested. The documented query includes a PRO number, destination postal code, document type, and capacity-provider account context; it also says some carriers require the pickup date to help retrieve documents. This is a project44 LTL API example, not a promise that every carrier supplies a delivery receipt or that one document has the same evidentiary content in every workflow. Confirm availability, formats, identifiers, permissions, and retention behavior for each provider path.

For every returned status or document, retain enough context for an operator to locate the source record: carrier or provider, shipment and stop references, document type, source event or retrieval time, response or availability state, and the receiving record to which it was matched. Keep an unavailable, delayed, or ambiguous document as an explicit exception. Do not translate “no document returned” into “delivery failed,” or “document returned” into “all goods were received in full.”

Keep physical receipt and quantity review with the receiving process

The transportation handoff should give the warehouse a usable expectation: which site and order or load are due, the current appointment, and the shipment references operators can match at the dock. The receiving system should retain its own actual result and route short, excess, damaged, substituted, unidentified, or split quantities according to the organization's configured workflow.

Microsoft's inbound load handling guide documents one Dynamics 365 workflow in which an inbound load is linked to purchase-order lines, a receiving clerk registers quantities against the load, and product receipt is posted separately. Its example explicitly shows a quantity that differs from the expected order amount and a remaining unregistered quantity. This is specific to the described Dynamics 365 process; use it as an example of why an appointment, load, registered quantity, and posted receipt can be distinct records, not as a template for another WMS or ERP.

Before release, agree how the appointment and carrier reference will be visible at receiving without granting a carrier event authority to adjust inventory. Define which staff or process may confirm the physical count, which system records the discrepancy, and how the receiving result is correlated back to the purchase order, inbound load, or transfer. If the appointment is for customer delivery rather than inbound supply, use the matching outbound fulfillment and customer-location context; do not force both directions into the same receipt rules.

Give exceptions a queue and an owner

Build a short exception path for cases the happy path cannot resolve:

  • The shipment has no confirmed window, or two sources show different windows.
  • A carrier requests a reschedule after the receiving site planned labor or dock capacity.
  • The arrival or delivery event cannot be matched to the expected site, appointment, load, or order.
  • The carrier reports arrival or delivery, but the site has no corresponding check-in or receiving activity.
  • A delivery receipt is delayed, unavailable, or returned for a different shipment reference.
  • The receiving record is partial or discrepant, or the delivery is split across multiple appointments or loads.
  • A retry, cancellation, or late event refers to an appointment that has already been replaced.

Each exception should show the affected shipment and stop, the identifiers and source values received, the last confirmed appointment state, the next action, and the person or team responsible. Let an operator determine whether to query, correct, reschedule, receive, reconcile, or escalate. Avoid automatic retries or inventory updates until the responsible systems' duplicate and correction behavior is understood.

Evaluate the integration with concrete delivery cases

When comparing a transportation, YMS, dock scheduling, WMS, or custom integration path, use the same sample loads and sites across vendor discussions. Ask teams to demonstrate these behaviors using documented product capabilities and your own receiving rules:

  1. Can a request, confirmation, reschedule, cancellation, arrival, and completed stop be represented as separate states with source timestamps?
  2. Can an operator find an appointment by the identifiers actually present in carrier, order, load, and site records?
  3. How are time zone, site, stop sequence, appointment changes, duplicate messages, and events arriving out of order represented?
  4. What proves that a slot was confirmed, that a driver checked in, that a delivery event was received, and that a warehouse quantity was registered?
  5. Which delivery documents can be requested, which carrier paths provide them, how are missing documents represented, and how are records linked to a shipment stop?
  6. Can the receiving team act on an expected delivery without letting a carrier status overwrite physical counts or purchase-order state?
  7. What reports or queues show unmatched, rescheduled, late, partial, or discrepant deliveries, and who owns each resolution?
  8. What reference history and audit context remain available when an appointment or load is cancelled, replaced, or corrected?

Test one ordinary delivery, one changed or missed appointment, one split or partial arrival, one unmatched carrier reference, a duplicate or delayed event, and a delivery document that is unavailable. Record expected and observed outcomes, source references, responsible owners, and any setup or carrier-account limits. Expand only after transportation and receiving teams can trace the same delivery across their systems.

For adjacent responsibilities, see the 3PL onboarding guide, B2B inventory availability guide, OMS architecture guide, reverse-logistics guide, and EDI purchase-order amendment guide.

First-party source register

The first-party pages below were opened and checked on October 22, 2026. Named-product statements in this guide are limited to the specific API and Microsoft Dynamics 365 workflows described at each source; the evaluation framework is vendor-neutral.

Editorial and education-only note

This guide is educational technical research for B2B e-commerce teams. It does not provide legal, tax, accounting, financial, security, performance, pricing, compliance, or individualized implementation advice. Carrier documents, appointment capabilities, status semantics, and receiving procedures vary by product, account, site, partner, and configuration. Confirm current first-party documentation and local operating requirements with the responsible teams before acting.

Continue reading