How drivers handle customer pickup requests
Delpack Logistics
October 26, 2026
10 min read
Verify an unplanned customer return request against assigned pickup work before accepting the physical parcel.
A driver delivers a parcel and the customer asks them to take a different box as a return. There is a printed label on the box, but no pickup appears on the driver's route. The customer says the store told them a driver would collect it today. How drivers handle customer pickup requests starts by checking whether the pickup belongs to the assigned work and whether the parcel can enter a traceable custody process. A label and a sincere request do not by themselves authorize an unlisted pickup.
This guide covers a request made during an ordinary delivery stop. It differs from comparing return-pickup duties in a job offer and from following a route that already includes planned pickup stops. The immediate driver decision is whether the specific box can be accepted under a current assignment. If the answer is uncertain, the driver should keep the delivery and proposed pickup as separate events, contact the employer, and avoid taking custody until the request is resolved.
Carriers use formal pickup systems. USPS describes scheduled Package Pickup, eligibility conditions, and confirmation notices. FedEx describes a process for scheduling a return pickup. Those are examples of carrier-specific services, not evidence that this customer has a Delpack pickup or that this driver can add one. The employer's live assignment, parcel identity, and proof rules control the stop.
Check pickup authority before taking the box
Pickup authority means the driver has an assigned or approved instruction to collect this parcel. Look for a pickup task linked to the address, time window, package or request ID, and service. If none appears, ask dispatch or the designated support owner. Do not treat a delivery task at the same address as a pickup task. The driver may be authorized to bring a parcel to the customer but not to take an unrelated return away.
Ask the customer for the pickup confirmation or return request information the employer permits them to share. A confirmation number can help support locate the job, but the driver should not accept it as proof by itself if it belongs to another carrier, date, address, or service. Compare the actual request with the current route assignment. A screenshot from a retailer may refer to a scheduled collection by a different company.
State the boundary plainly and respectfully: the driver needs an authorized pickup on the route or live approval before taking the parcel. Avoid promising to "make it work" by placing the box in the van and asking dispatch later. Once the driver takes custody, the customer may believe the return is in transit. An unscanned box could become difficult to trace or hand off at the depot.
If dispatch confirms an eligible pickup, ask for the exact task identity and required proof before touching the parcel. A verbal "yes" without a parcel ID, route update, or documented fallback may still leave the acceptance event unresolved. Repeat back the address, box count, label ID, and handoff method. The driver should know what record the customer will receive and what the depot expects at return.
If the employer cannot verify the request while the driver is at the door, decline the ad hoc collection and give the customer the approved scheduling or support path. Do not tell them that their retailer was wrong; the request may exist in another system. The driver can report the information to support while leaving the box with the customer. A pending investigation is not a completed pickup.
Match the return label and package identity
The return label should be checked against the authorized task, not accepted as a generic permission slip. Read the carrier, tracking or return ID, destination, and any instructions without exposing unnecessary customer information. A prepaid label may be for drop-off rather than driver collection. It may also be expired, duplicated, or attached to a box that does not match the scheduled request. The assigned owner should determine whether the label is valid for this pickup.
Keep physical identity clear when the customer has several returns. A pickup request for one box does not authorize the driver to take three. Count the cartons and confirm each label or package ID under the employer's process. If two boxes share a return authorization, ask how each physical piece will be recorded. Do not scan one ID repeatedly to cover multiple boxes without an approved multi-piece workflow.
Check whether the package is ready for transport under the service's packaging and content rules. The driver can observe a torn, open, leaking, or unlabeled carton and report it. They should not open a sealed box or certify its contents on personal judgment. A scheduled pickup can still need a hold or support decision if the physical parcel does not meet the assigned acceptance process.
Compare the return box with the delivery parcel. They may belong to different orders, shippers, or carriers. Do not use the delivery tracking ID to create a pickup record for the return. If the customer says "it's for the one you just brought," ask for the return identity required by the employer. The new outbound parcel has its own custody chain even when the transaction began with today's delivery.
USPS says its scheduled pickup service is limited to eligible package types and addresses. That illustrates why a label or customer expectation may not settle pickup eligibility. Delpack's route may have different rules, but the driver still needs an approved task for the particular item. If the label belongs to USPS, FedEx, UPS, or another carrier, do not assume the driver can collect it just because both companies deliver to the same building.
Confirm the route assignment and timing
A route assignment should state whether the driver is to collect the parcel now, return later, or leave it for another pickup. The customer may have selected a day rather than a time, or the pickup may be assigned to a different vehicle. Ask dispatch to verify the job's effective date and route. A driver should not add an unscheduled stop to their own workload without the employer's approval and capacity check.
Check whether the route app can accept the pickup task while the driver is at the address. If support adds it, confirm the task appears under the correct address and package ID before scanning. If the system is delayed, use only an employer-authorized offline or exception procedure. Do not create a delivery exception as a substitute for a pickup event. The two directions of movement need separate records.
Consider the remaining route load. The box may be too large for the available van space or require handling the current vehicle cannot provide. A valid pickup request does not make a physical load safe. Tell dispatch the parcel size, observed condition, and remaining capacity. The route owner can assign another vehicle, a later collection, or a controlled hold if the service permits. The driver should not wedge the box into a walkway to keep a promise made at the door.
Record any timing change. If the customer request is assigned for tomorrow, the driver can explain the confirmed next step without taking the parcel today. If support authorizes a same-day pickup at this stop, the system should show that decision and the driver should capture the acceptance at the actual time. Do not backdate a pickup to the time the customer submitted a retailer return form.
Some pickup services require a driver-provided label or receipt; others use a customer label. The driver must follow the assigned service. Do not print, rewrite, or attach a label on personal initiative unless the employer's task instructs it. An unverified label can send the box to the wrong destination and obscure the original customer handoff.
Capture acceptance proof for an authorized pickup
Acceptance proof should identify the box the driver actually took, the pickup task, time, address, and any required customer receipt. Use the employer's scan, signature, photo, or other approved method. Tell the customer what confirmation is available under the service. Do not promise that a retailer refund begins immediately; the pickup event only records the transfer into the delivery operation's custody.
At the handoff, count the physical pieces and compare them with the accepted task. The driver should retain control of the box after the scan and place it in the assigned part of the van. A scan followed by leaving the parcel on the customer's porch would create a false custody record. Conversely, taking the box without completing the required acceptance record leaves the customer with no reliable proof that it was collected.
Keep the customer's delivered parcel separate in the system. If the driver successfully delivered P18 and accepted return R44 at the same door, the route should contain a P18 delivery event and an R44 pickup event. One signature may not satisfy both roles under the service rules. The driver should not mark the return as delivered or the delivery as returned to compress the stop into one task.
At depot return, hand the collected box to the authorized inbound or return owner and confirm its ID. The driver should not leave it among undelivered route parcels. If the depot cannot accept it, contact support for a secure hold and record the unresolved custody. A successful customer pickup is the beginning of the parcel's return movement, not proof that it reached the retailer or final return destination.
Handle a declined request without losing the customer
A declined request should be explained as a missing or unverified pickup assignment, not as a rejection of the customer. Tell them how to confirm or schedule collection through the appropriate carrier, retailer, or employer support channel. If dispatch identifies another pickup date or route, share only the approved details. The driver should avoid inventing a fee, pickup window, or refund promise.
Record the encounter if the employer expects a note. Include the address, customer-provided request ID if permitted, label carrier, box count, and dispatch response. Make clear that the driver did not take custody. A note saying "pickup attempted" may be inaccurate if no assigned pickup existed; use the employer's inquiry or support category instead. The customer can then contact the scheduling owner without a false collection scan already in the system.
Do not tell the customer to leave the box outside for a future driver unless the responsible carrier and service explicitly authorize that placement. A return may require a person-to-driver handoff or another approved location. The driver should not convert an unplanned conversation into a standing site instruction. An accurate referral protects the parcel from being left unattended without a scheduled pickup.
Work the unlisted return-box case
The driver delivers P18 at 1:20. The customer brings out a sealed return box labeled R44 and asks the driver to take it. The route has no pickup at that address. The customer shows a retailer email that says "return approved" but does not show a collection time or carrier. The driver keeps P18's delivery proof separate and asks dispatch to look for an R44 pickup assignment. The box stays with the customer during the check.
Dispatch finds no assigned pickup and confirms that the label is for a drop-off return. The driver tells the customer the approved support or drop-off path and does not collect R44. The route records only the P18 delivery and, if required, a support note about the inquiry. There is no R44 acceptance scan. The customer still has physical custody and can follow the actual return instructions.
In another outcome, dispatch finds a valid same-day pickup assigned to a second route but reassigns it to this driver through the approved system. R44 appears with the correct address and proof requirements. The driver checks the label and box condition, scans the authorized acceptance, gives the customer the required confirmation, and secures the box in the van. At depot return, R44 is transferred to the return owner. Each step has a real parcel identity and custody event.
Change one fact: the box is leaking. Even if dispatch confirms the pickup, the driver should report the condition and use the employer's handling and safety process before taking it. Authorization to collect an item is not permission to accept a package that cannot be safely transported under the assigned service. The next action may belong to a specialized team or a repackage decision.
Close the pickup question
How drivers handle customer pickup requests depends on a verified assignment and a traceable physical handoff. For an authorized job, match the parcel and capture acceptance proof. For an unassigned request, leave the box with the customer and provide the approved scheduling path. A delivery stop does not automatically carry a return-pickup obligation.
Readers can explore related route guidance in the driver guide hub and local opportunities on the Fort Wayne driver careers page . The record should show either an authorized pickup with custody transferred or an uncollected request that remains with the customer. Taking an unassigned box before the system has a task would leave its custody unclear.
Continue with Delpack
Review the Fort Wayne career overview or contact Delpack with a question about the company.
Topics
Browse Topics
All Guides
346
Job Search, Applications & Offers
79
Role Types & Job Fit
83
Schedules, Policies & Work-Life
40
Route Operations & Performance
91
Logistics & Warehouse Operations
53
Delpack Logistics Delpack Logistics is an Amazon Delivery Service Partner and last-mile logistics company serving the Fort Wayne market. Explore Welcome Meet Delpack Fort Wayne Delivery Driver Careers Driver Resources Contact Delpack Delpack News Legal Terms of Service Privacy Policy SMS status Contact info@delpacklogistics.com 260-306-5806 View market and mailing address © 2026 Delpack Logistics . All rights reserved.