What you’ll get from this article
- Separate appointment from notification. Booked window vs call-ahead are different products—and different invoice lines.
- See who pays when the receiver requires the window. Prepaid shippers often absorb a consignee policy unless customer terms recover it.
- Expect stacking. Appointment can sit beside detention, liftgate, and limited access on the same PRO.
- Flag site profiles that trigger fees. Retail DCs, construction, hospitals, schools, and tight receiving hours.
- Audit with evidence, not irritation. When to pay, when to dispute, and what to fix in master data and quotes.
Most guides say “declare appointment at quote.” Useful—and incomplete. The invoice problem shippers actually hit is different: the receiver’s site forced a window, the prepaid shipper got the bill, and the same stop may also show detention or liftgate. This article reads appointment and notification the way carriers bill them.
Introduction
An appointment delivery fee is an accessorial charged when the carrier must secure a specific delivery (or sometimes pickup) window with the receiver instead of delivering on the carrier’s discretionary schedule. A notification or call-ahead fee covers contacting the site before arrival so someone is ready—without necessarily locking a hard window.
Those charges exist because LTL networks run multi-stop routes. A dock that only accepts freight between 10:00 and 11:30, or that requires a phone call before the truck rolls into the yard, breaks the default plan. The fee pays for coordination and route risk—not for the minutes a driver waits after free time. Waiting after free time is detention.
If your process stops at “remember to check the appointment box,” you will keep losing money on surprises: auto-applied fees when the carrier discovers the requirement at delivery, prepaid invoices for consignee site rules, and stacked lines that look like double-billing when they are not.
Appointment vs notification (do not merge the lines)
| Product | What the carrier does | Typical invoice language | Common audit mistake |
|---|---|---|---|
| Notification / call-ahead | Phone, email, or portal notice before arrival so the site can prepare | Notification, call ahead, pre-notify | Calling every notification an “appointment” and disputing the wrong tariff item |
| Appointment | Books and meets a time window with receiving | Appointment delivery, scheduled delivery, APPT | Assuming the fee includes unlimited wait once the window is set |
Dollar amounts are carrier- and contract-specific. Treat public “typical ranges” as orientation only. What matters operationally is whether the tender asked for the right product—and whether the invoice product matches what the site actually required.
Who pays when the receiver requires the window
Carriers bill the contractual payor. On a prepaid LTL shipment, that is usually the shipper. If the consignee’s DC will not accept freight without an appointment, the shipper still often sees the line first—even though the policy lived at the customer’s door.
That is the three-party argument tip lists skip:
- The carrier is not wrong to bill the payor on the BOL when the service was performed.
- Whether you recover from the customer depends on sales terms, collect / third-party billing, or a chargeback process with appointment confirmation evidence.
- If customer contracts say nothing about delivery accessorials, appointment fees at slow receiving sites become a quiet margin leak.
Same commercial shape as detention at the customer dock: site cause does not automatically rewrite the freight payor. Fix the customer agreement, not only the CSR checklist.
Example 1 — Surprise appointment: discovered at delivery
A Greater Toronto Area distributor tenders prepaid LTL to a retail back room. The CSR quotes without appointment because the shipper’s master data marks the address as a standard commercial dock. On delivery day, receiving refuses the truck until a window is booked. The carrier schedules, delivers, and invoices appointment plus a liftgate the site also required.
Operations says, “We didn’t ask for appointment.” The tariff says the carrier may apply the charge when the consignee requires scheduled delivery. The dispute fails. The fix is master-data and quote hygiene: flag appointment-required consignees, and put the fee in the customer cost model before the next order—not after the PRO.
Example 2 — Appointment plus detention on the same stop
A manufacturer books an appointment for 13:00–14:00 at a construction site. The driver arrives at 13:10. The site is not ready until 14:45. The invoice shows an appointment fee and waiting time after free time.
That is not automatically double billing. Appointment paid for securing the window. Detention paid for dwell after the free-time clock expired. Audit each line on its own rule: confirmation that an appointment was required and performed; timestamps that support (or refute) detention. Use the detention & free time calculator to model the wait side; keep appointment as a separate product.
Example 3 — When paying the fee is cheaper than fighting it
A hospital receiving desk only accepts freight by appointment. A shipper disputes every appointment line for six months and wins almost none—while also eating occasional redelivery after refused attempts. The cheaper path was: flag the ship-to as appointment-required, quote it, and recover via the customer’s freight terms or a small order surcharge where commercial agreements allow.
Dispute energy belongs on misapplied products and wrong payors—not on fighting a site policy the carrier cannot waive.
Site profiles that commonly trigger fees
- Retail stock rooms and mall docks — limited receiving windows; often appointment or call-ahead.
- Construction and job sites — gate control, safety briefings, and “arrive when we say.”
- Healthcare, schools, government — security and restricted dock hours.
- High-volume DCs with appointment portals — window booking is a condition of entry, not a courtesy.
- Limited-access or residential-adjacent commercial — often stacks with limited access or residential classification; confirm each trigger separately.
If a consignee repeatedly triggers appointment on invoices, treat it as a profile attribute in your TMS or rate shop—not as a one-off CSR miss.
What appointment is commonly confused with
- Detention / waiting time — elapsed wait after free time; not the fee for booking the window.
- Layover — multi-day or overnight delay rules; different tariff logic.
- Liftgate / inside delivery — equipment or placement beyond the dock threshold.
- Guaranteed / expedited service — transit product, not receiving coordination.
How it shows on the invoice
Look for “appointment,” “APPT,” “scheduled delivery,” “notification,” or “call ahead.” Map the code to the tariff item. If the line is a flat amount with no service note, ask whether an appointment was booked, with whom, and for which window—especially when your tender did not request it.
In payables, keep appointment and notification in their own buckets (or a shared “scheduling accessorials” bucket split by code). Dumping them into “other” hides chronic consignees and quote gaps.
How to audit an appointment or notification line
- Identify the product on the invoice (appointment vs notification vs something else).
- Check tender / BOL / quote: was the requirement known and declared?
- Confirm site policy: does this consignee actually require the service?
- Separate stacked accessorials—detention, liftgate, limited access—each needs its own evidence.
- Confirm payor terms: prepaid vs collect; any customer recovery path.
- Dispute when the product is wrong, the site does not require it, or the known requirement was omitted from a quoted rate you were promised would be inclusive—document that promise.
- Pay when the site required it and the service was performed—then fix master data and customer terms.
Same evidence habit as the rest of the accessorial cluster: accessorial audit checklist and the freight invoice audit checklist.
What actually reduces appointment spend
- Consignee profiles: Flag appointment-required ship-tos before rating.
- Quote honesty: Put known appointment/notification in the rate—not as a post-delivery surprise to finance.
- Customer terms: Decide who owns delivery accessorials at appointment-heavy receivers.
- Mode / site design: Chronic appointment + liftgate + detention stacks may justify a different service design or customer pickup for that lane—not a deeper linehaul discount that ignores accessorials.
- Contract language: Clarify how auto-applied appointment is priced when the consignee requires it; that is part of contract optimization.
FAQ
What is an appointment delivery fee in LTL?
An accessorial for scheduling a specific delivery window with the receiver instead of discretionary delivery. It pays for coordination and route impact—not for wait after free time.
How is notification different from appointment?
Notification is call-ahead or pre-advise. Appointment is a booked time window. Different tariff items; do not audit them as synonyms.
Who pays if the receiver requires the appointment?
Usually the contractual payor—often the prepaid shipper. Recover via customer terms, collect billing, or chargeback with confirmation evidence.
Can appointment stack with detention or liftgate?
Yes. Each line has its own trigger. Audit them separately.
Should you always dispute a surprise appointment fee?
No. Dispute wrong products and non-required sites. Pay required, performed service—then fix profiles and quotes so the next invoice is not a surprise.
Final takeaway
Appointment and notification fees are not “forgot to check a box” problems alone. They are site-policy products billed to a contractual payor, often stacked with other accessorials. Separate the products, know who pays when the receiver sets the rules, and audit with confirmation and timestamps—not with the assumption that every surprise line is a carrier error.