SPD vs LTL/FTL inbound: when small-parcel inbound becomes a hidden cost trap
SPD vs LTL/FTL Inbound: When Small-Parcel Inbound Becomes a Hidden Cost Trap
SPD (Small Parcel Delivery) ships individual cartons through a parcel carrier. LTL (Less-than-Truckload) and FTL (Full Truckload) ship palletized freight on a freight carrier. The right mode depends on shipment volume, carton count, and how much variability in receiving time and damage risk you can absorb — not on which mode is generally cheaper.
The Inbound Mode That Grows Into a Problem
SPD is the default inbound mode for most new Amazon sellers. The process is familiar — generate carton labels, hand the boxes to a parcel carrier, watch the tracking numbers update. At low volume, it works. The friction is manageable, the cost is visible, and there’s no scheduling complexity.
The problem is that SPD doesn’t scale linearly. At low volume, the per-carton cost is the dominant variable. As shipment size grows, the labor cost of producing individual parcel labels for dozens or hundreds of cartons, the variability in receiving times when cartons arrive across multiple tracking events rather than a single delivery, and the higher per-unit exposure to in-transit damage all grow proportionally — and the aggregate cost starts to diverge from what a rate comparison would suggest.
SPD (Small Parcel Delivery): An Amazon inbound mode where individual cartons are shipped via a parcel carrier (typically UPS or FedEx) without palletization. Each carton receives a unique carrier label and is tracked individually through delivery.
LTL (Less-than-Truckload): A freight shipping mode where a seller’s palletized shipment shares a truck with other shippers’ freight. Amazon assigns a dock appointment, and the delivery is made on a scheduled basis rather than carrier-driven routing.
FTL (Full Truckload): A freight shipping mode where the seller’s palletized shipment occupies an entire truck. Used for very large shipments where the volume justifies the dedicated vehicle.
The choice between these modes is not primarily a rate question — it’s an operational control question. Each mode has different requirements, different failure modes, and different points where things break.
How SPD Creates Hidden Costs at Scale
The cost trap in SPD is not the carrier rate per carton — it’s the aggregate operational load that accumulates as shipment size grows.
At 10 cartons, generating individual parcel labels and handing them to a carrier is straightforward. At 100 cartons, the label generation process takes meaningful time, and each carton that gets lost, damaged, or delayed in transit requires a separate carrier investigation. If 3 of those 100 cartons arrive at the fulfillment center with damage, each one is a separate receiving exception — three separate investigation threads, each requiring its own documentation and follow-up.
Receiving variability is the factor most often underestimated. With SPD, a 100-carton shipment may arrive at the fulfillment center across 4 or 5 different delivery events, depending on carrier routing. Inventory doesn’t become available for sale until Amazon has received and checked in all the cartons in the inbound plan. If 95 cartons arrive on Monday and 5 arrive the following Thursday, the inventory from that shipment is partially unavailable for a week — not because of a stock problem, but because of a parcel routing pattern.
The expert observation: sellers who calculate SPD cost using only the carrier rate are consistently underestimating total inbound cost. The true cost includes label generation labor, per-carton damage investigation at receiving, receiving variability (days of unavailable inventory), and the prep labor of individual carton labeling versus palletizing for LTL. When these components are included, the threshold where LTL becomes cheaper moves earlier than most sellers expect.
What LTL/FTL Changes — and What It Doesn’t
LTL and FTL inbound shifts the operational model from carrier-driven delivery to appointment-driven delivery. A scheduled dock appointment means the shipment arrives at a defined time, is received as a unit (a pallet or a set of pallets), and the receiving event is single rather than spread across multiple carrier deliveries.
This changes the receiving variability problem. A palletized shipment on a scheduled appointment arrives together. When it arrives correctly, inventory posts faster and with fewer receiving exceptions than a carton-by-carcel SPD shipment of equivalent size. The entire shipment is received in one event rather than five.
Palletization requirements: For LTL inbound to Amazon, shipments must be prepared on pallets that meet Amazon’s specifications — standard pallet dimensions, maximum height, secure stretch wrapping, and correct placement of pallet labels. The pallet label must be applied to all four sides of the pallet and must correspond to the inbound plan.
What LTL doesn’t resolve is the preparation complexity that comes with palletization. Pallets must be built to spec: correct stacking pattern, appropriate stretch wrap, pallet labels on all four sides matching the inbound plan. If a pallet arrives at the dock with a label on only two sides, or with damage that compromises the wrap, the dock appointment may be refused or the pallet flagged for inspection. A refused dock appointment creates a scheduling and logistics problem that takes time to resolve and delays inventory availability by more than a simple late SPD delivery would.
LTL also introduces appointment scheduling as a dependency. The seller (or their prep partner) must coordinate a scheduled delivery appointment with Amazon’s fulfillment center, which adds lead time to the inbound process. For sellers who need to replenish quickly, this appointment window — which can be several days out — is a planning constraint that SPD doesn’t have.
Comparison: SPD vs LTL/FTL Inbound
| Criterion | SPD | LTL / FTL |
|---|---|---|
| Shipment format | Individual cartons, no palletization | Palletized freight |
| Carrier type | Parcel carrier (UPS, FedEx) | Freight carrier |
| Label type | Unique parcel label per carton | Carrier label + pallet labels (4 sides) |
| Dock appointment required | No | Yes |
| Receiving events | Multiple (cartons arrive separately) | Single (full pallet delivery) |
| Receiving variability | High — cartons may arrive across days | Low — appointment-based single delivery |
| In-transit damage exposure | Per-carton (each carton individually at risk) | Per-pallet (better protection with correct wrap) |
| Cost per carton | Generally higher at volume | Generally lower at sufficient volume |
| Preparation complexity | Lower — individual carton labels | Higher — pallet build, wrap, pallet labels |
| Best fit | Low carton counts, frequent small replenishments | High volume, stable replenishment cadence |
| Plan-split handling | Standard (cartons route to different centers) | Requires separate pallets per destination |
Decision Rules and the Volume Threshold
The question of when to switch from SPD to LTL is not a fixed number — it depends on the seller’s product, carton dimensions, and how the inbound plan is structured. But there are practical signals that indicate the transition point is near.
When the time spent generating individual carton labels for a single shipment becomes significant, and when the prep operation is packaging cartons that could be more efficiently moved on a pallet, SPD is starting to cost more than the rate comparison shows. When receiving variability is affecting inventory availability — inventory that should be available for sale is sitting in receiving status because a portion of the shipment hasn’t arrived yet — the cost of that variability in lost sales needs to be added to the SPD calculation.
A useful working heuristic: when a single shipment regularly exceeds a threshold of cartons that require meaningful prep labor, and when the replenishment cadence is stable enough to support scheduling an LTL appointment in advance, the transition to LTL is worth evaluating. The exact threshold depends on the product and the prep facility’s workflow, but the evaluation should happen before the cost of SPD at scale becomes a known problem rather than a hypothesis.
FTL becomes relevant when a single shipment fills a truck. That threshold is typically reached by brands sending large volumes in a single replenishment, or in peak-season operations where multiple months of inventory move in a concentrated period. For most mid-volume Amazon sellers, FTL is not a regular inbound mode — it becomes relevant for peak preparation or market expansion shipments.
Controlling for the Failure Modes in Each Mode
Both modes have predictable failure points. Managing inbound means controlling for those specific points, not just choosing the mode and assuming it will work.
For SPD, the primary failure modes are carton-level damage in transit and receiving variability. The controls are: cartons that are properly packed to withstand parcel handling (items not rattling, appropriate void fill, sealed securely), and inbound plans that account for the possibility that not all cartons will arrive simultaneously. Building a buffer in inventory planning for the tail of a parcel delivery — those last few cartons that may arrive days after the majority — prevents the situation where a stockout occurs while inventory is technically in the inbound chain but not yet available.
For LTL, the primary failure modes are pallet build quality and appointment scheduling gaps. A pallet that isn’t built to spec — unstable stack, insufficient wrap, labels missing from required sides — creates a risk of dock refusal or damage flagging. The control is a pallet inspection step before the freight pickup: verify the wrap, confirm pallet label placement, check that the pallet dimensions are within spec. Appointment scheduling gaps — booking a dock appointment that doesn’t account for the carrier’s transit time from the prep facility — are a planning error that creates a late arrival, which may require rescheduling and delay inventory posting.
A simple cadence to review inbound performance by mode: after each shipment, note how many receiving exceptions occurred, how long it took for inventory to post, and whether any cartons or pallets required investigation. Over a few shipments, the pattern of failure modes by mode becomes clear, and the controls can be tightened to the specific points where errors are occurring rather than applied uniformly.
Frequently Asked Questions
Q: What is the difference between SPD and LTL inbound on Amazon? A: SPD (Small Parcel Delivery) ships individual cartons through a parcel carrier, with each carton tracked and delivered separately. LTL (Less-than-Truckload) ships palletized freight on a scheduled dock appointment, with the entire shipment arriving as a single delivery event. SPD is simpler to set up but creates more receiving variability at scale. LTL requires palletization and appointment scheduling but delivers inventory more predictably and with lower per-unit receiving friction at higher volumes.
Q: When should I switch from SPD to LTL for Amazon inbound? A: The practical signals are: when generating individual carton labels for a single shipment is taking significant prep time, when receiving variability is causing inventory to sit in receiving status for extended periods while waiting for the full shipment to arrive, and when the aggregate cost of SPD (including labor, damage investigation, and unavailable inventory days) is clearly exceeding what LTL would cost. The transition point varies by product and carton count, but the evaluation should happen before SPD costs become a known fixed drag, not after.
Q: Does LTL inbound require a dock appointment with Amazon? A: Yes. LTL inbound requires a scheduled delivery appointment at the Amazon fulfillment center. The appointment must be booked through Amazon’s system, and the freight carrier must arrive within the appointment window. A missed appointment typically requires rescheduling, which adds days to the time before inventory is received. Building the appointment lead time into your replenishment planning is essential — LTL doesn’t offer the walk-up flexibility of a parcel carrier drop-off.
Q: What are the pallet requirements for Amazon LTL inbound? A: Pallets for Amazon LTL inbound must meet Amazon’s dimensional specifications, be stretch-wrapped securely, and have pallet labels applied to all four sides. The pallet labels correspond to the inbound shipment plan and must match the ASINs and quantities on the pallet. A pallet that arrives without labels on all four sides, with damaged wrap, or with unstable stacking may be refused at the dock or flagged for inspection, which delays receiving and inventory availability.
Q: Can SPD and LTL be used together in the same inbound plan? A: Amazon’s inbound workflow allows sellers to choose inbound modes at the shipment level, so it’s possible to run SPD for some replenishments and LTL for others. Mixing modes within a single inbound plan is generally not practical — the prep and carrier requirements are incompatible in a single shipment. The more useful approach is to evaluate the appropriate mode for each replenishment cycle based on the carton count and timing, rather than committing permanently to one mode regardless of shipment characteristics.
If you want to evaluate whether your current inbound mode is creating hidden costs — or to understand what the prep requirements would be for an LTL transition — share the basics of your current setup: carton counts per shipment, replenishment frequency, and product profile. We’ll clarify what the implications are before anything changes.