The Pickup and Delivery Problem (PDP) is a combinatorial optimization challenge that generalizes the Vehicle Routing Problem by requiring every transportation request to have a specific origin and destination. The core constraint is a precedence relationship: a vehicle must visit a pickup location and load the cargo before it can subsequently visit the corresponding delivery location to unload it. This pairing couples the two stops, making the problem significantly more complex than standard node-routing variants.
Glossary
Pickup and Delivery Problem (PDP)

What is Pickup and Delivery Problem (PDP)?
A fundamental class of vehicle routing problems where goods or passengers must be transported between specific pickup and delivery locations, governed by precedence constraints.
PDPs are foundational to modern logistics, modeling scenarios from less-than-truckload (LTL) freight consolidation to dial-a-ride passenger services. Solving a PDP involves simultaneously assigning requests to vehicles and sequencing the stops to minimize total travel cost while respecting vehicle capacity, time windows, and maximum ride-time constraints. Exact solutions via Mixed-Integer Linear Programming (MILP) are computationally intractable for large instances, driving the widespread use of metaheuristics like Adaptive Large Neighborhood Search (ALNS) to find near-optimal routes in operational timeframes.
Key Features of the Pickup and Delivery Problem
The Pickup and Delivery Problem (PDP) is a fundamental class of vehicle routing that introduces precedence constraints—a pickup must occur before its corresponding delivery—and pairing constraints—the same vehicle must handle both operations for a given request.
Precedence Constraints
The defining characteristic of the PDP is the temporal ordering requirement. For every request, the pickup node must be visited before the delivery node on the same route. This transforms the problem from a simple sequencing task into a complex combinatorial challenge where inserting a new request requires validating that no existing precedence relationships are violated. Violations lead to infeasible routes where a vehicle arrives to deliver goods it has not yet collected.
Pairing and Coupling
Each transportation request consists of a coupled pair of locations: an origin and a destination. The same vehicle must service both nodes. This pairing constraint prevents solutions where one vehicle picks up a load and another delivers it, which would be valid in a standard Vehicle Routing Problem (VRP). Mathematically, this introduces linking constraints that tightly couple decision variables, significantly increasing the problem's computational complexity.
Capacity Dynamics
Unlike the Capacitated VRP where load monotonically decreases, PDP vehicle loads fluctuate dynamically. A vehicle's load increases at pickup nodes and decreases at delivery nodes. This creates a non-monotonic load profile along the route. Feasibility checks must verify that the vehicle's capacity is never exceeded at any point, requiring cumulative load tracking rather than a simple sum of total demand.
Time Window Intersections
PDPs frequently incorporate hard time windows at both pickup and delivery locations. A request may specify a morning pickup window and an afternoon delivery window. The travel time between the paired nodes imposes a minimum time separation, while customer requirements impose a maximum ride time. Satisfying these intersecting temporal constraints while sequencing multiple requests on a single vehicle is a core algorithmic challenge.
Dial-a-Ride Problem (DARP)
The Dial-a-Ride Problem is the passenger-transport variant of the PDP. It introduces service quality constraints absent in freight PDPs:
- Maximum ride time: A passenger cannot be on board longer than a multiple of the direct travel time.
- Maximum wait time: Limits on how long a vehicle can idle before pickup. These constraints make DARP significantly more constrained than freight PDPs and are critical for paratransit and ride-sharing services.
Solution Approaches
PDPs are NP-hard, making exact solutions impractical for large instances. Common solution methods include:
- Adaptive Large Neighborhood Search (ALNS): Iteratively destroys and repairs parts of the solution, adapting operator selection based on performance.
- Mixed-Integer Linear Programming (MILP): Formulates the problem with binary decision variables for arc traversal and continuous variables for load and time tracking.
- Column Generation: Decomposes the problem into a master problem selecting routes and a pricing subproblem generating feasible PDP routes with negative reduced cost.
PDP vs. Related Routing Problems
Key structural and constraint differences between the Pickup and Delivery Problem and its closest routing variants.
| Feature | Pickup and Delivery (PDP) | Vehicle Routing (VRP) | Dial-a-Ride (DARP) |
|---|---|---|---|
Core objective | Transport items between paired pickup and delivery locations | Deliver goods from a depot to customer locations | Transport passengers between paired pickup and delivery locations |
Precedence constraint | |||
Depot-based | |||
Pairing constraint | |||
Maximum ride time constraint | |||
Vehicle capacity constraint | |||
Time window constraint | |||
Primary application | Freight and courier services | Retail distribution and supply chain | Paratransit and ride-sharing |
Frequently Asked Questions
Clear, technically precise answers to the most common questions about the Pickup and Delivery Problem, its constraints, and its solution methods.
The Pickup and Delivery Problem (PDP) is a class of vehicle routing problems where goods or passengers must be transported between specific pickup and delivery locations, with the fundamental constraint that a pickup must occur before its corresponding delivery. This precedence constraint is the defining characteristic that distinguishes PDP from standard Vehicle Routing Problems. The objective is typically to find a set of routes for a fleet of vehicles that services all requests at minimal total cost—measured in distance, time, or number of vehicles—while respecting vehicle capacity, time windows, and maximum ride time limits. PDP models are foundational to modern logistics, powering everything from parcel delivery and ride-hailing services to the transportation of patients in non-emergency medical services.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
The Pickup and Delivery Problem (PDP) is a distinct class of vehicle routing that introduces precedence constraints between paired locations. The following concepts are essential for understanding its variants, solution methods, and real-world applications.
Dial-a-Ride Problem (DARP)
A specialized PDP variant focused on passenger transportation rather than goods. DARP adds stringent service quality constraints that are absent in cargo PDPs, including maximum ride time limits for each passenger and maximum deviation from direct travel time. The objective balances operator costs against user inconvenience, making it a multi-objective optimization challenge. Common in paratransit services and autonomous shuttle routing.
Constraint Programming
A declarative paradigm exceptionally well-suited for PDP's combinatorial complexity. Rather than specifying a step-by-step algorithm, you define variables, their domains, and the logical constraints between them. A solver then systematically prunes the search space using propagation algorithms. Constraint programming excels at handling the precedence constraints and time windows that define PDP, often outperforming mixed-integer programming on highly constrained instances.
Adaptive Large Neighborhood Search (ALNS)
A dominant metaheuristic for solving large-scale PDP instances where exact methods fail. ALNS iteratively destroys a portion of the current solution (e.g., removing random pickup-delivery pairs) and then repairs it using insertion heuristics. An adaptive layer tracks the performance of each destroy and repair operator, dynamically selecting the most effective ones. This self-tuning mechanism makes ALNS robust across diverse PDP variants without manual parameter tuning.
Service Time Window
A critical constraint in time-sensitive PDP variants. Each pickup and delivery location has a defined hard or soft time interval within which service must begin. Hard windows render solutions infeasible if violated; soft windows incur a penalty cost. In PDP, time windows are paired—a delay at pickup cascades to the delivery window, requiring algorithms to propagate temporal constraints forward. This coupling dramatically increases the problem's computational difficulty.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us