Uber Eats DeliverZero Reusable Container Pilot: What We Know So Far

Uber Eats and DeliverZero ran a U.S. reusable-container pilot that began in New York City in 2023 and was later described as expanding to Colorado, greater Los Angeles, and the San Francisco Bay Area. The historical record shows a customer opt-in flow built around a roughly $1 fee and return options, but it does not verify that the program is operating now or establish a universal 70% return rate. For a restaurant operator, the case study is most useful as a framework for testing return convenience, settlement rules, kitchen workflow, and measurement before joining any reuse network.

Estimated reading time: 7 minutes

The pilot was a dated effort to add reusable food containers to selected Uber Eats orders in the United States. At launch in 2023, the New York City pilot was described as Uber Eats’ first U.S. reuse pilot, with more than 80 participating restaurants. A March 2024 announcement described the partnership as operating in New York and Colorado before expanding its focus to greater Los Angeles and the San Francisco Bay Area, with more than 130 restaurants included in that West Coast expansion announcement.

Those figures describe announced pilot scope at specific points in time. They are not proof that every named market, restaurant, ordering flow, or offer remains available today.

The reported flow was designed to sit alongside a normal delivery order:

1. A customer found a participating restaurant through DeliverZero labeling in the Uber Eats experience.
2. Before checkout, the customer selected reusable containers.
3. The reports described a charge of approximately $1, with pricing varying by merchant.
4. The courier picked up and delivered the order through the usual delivery flow.
5. After the meal, the customer received return instructions by text and could return containers to a participating restaurant or arrange a separate pickup.

For an operator, the important point is not that this exact flow can be replicated everywhere. It is that a reuse offer depends on several connected handoffs: ordering, packing, customer communication, return intake, collection, cleaning, and inventory reconciliation.

Not based on the available material. The 2023 and 2024 descriptions call it a fee or charge of about $1; they do not describe it as a refundable deposit. A fee and a deposit are different commercial mechanisms. A fee is normally retained, while a deposit usually needs a stated authorization, return condition, refund process, and exception policy.

A single-location restaurant should therefore not assume that selecting a reusable option means a deposit is being held or later refunded. The provider and ordering platform should confirm the actual customer charge, who receives it, whether any amount is refundable, and how exceptions are handled.

Before joining a program, ask for written answers to these questions:

• Is the customer charge a fee, a refundable deposit, a temporary card authorization, or something else?
• When is the amount charged, and who is the merchant of record?
• If money is refundable, what event triggers the refund and how long can it take?
• What happens when a container is returned late, returned to a different location, or cannot be matched to an order?
• Who handles customer questions, disputes, refunds, and chargebacks?
• How are amounts reported in the restaurant’s sales, platform statements, and accounting records?

These details determine whether the offer is easy to explain at the counter and manageable after a busy service period.

The often-repeated 70% figure needs careful wording. Contemporary reporting indicated that about 70% of existing DeliverZero customers returned packaging at a participating restaurant rather than scheduling a pickup. That is a reported choice of return channel among DeliverZero customers; it is not, on the historical evidence available, a verified overall return rate for the Uber Eats New York pilot.

It should not be converted into a promise that 70% of a specific restaurant’s reusable containers will return, nor into a claim that 70% of all customers chose or completed the program. The initial pilot plan called for Uber Eats to monitor first-time versus repeat users and return rates before deciding next steps, which shows that those measures still needed observation.

A restaurant should agree on the definitions before the first order is packed. Useful questions include:

• What counts as an opt-in: a reusable selection, a packed order, or a completed delivery?
• What counts as a successful return: a container handed over, scanned, received by the network, or cleared for reuse?
• What is the return window, and how are overdue containers counted?
• How will store drop-offs and scheduled pickups be tracked separately?
• What is the expected reconciliation process when the restaurant’s container count and the network’s count differ?
• Who receives a weekly view of orders, returns, outstanding containers, customer contacts, and any charges?

A percentage without a denominator, a time window, and a return definition does not tell an operator whether the system is workable at one location.

The historical record supports a limited reading. In 2023, the New York launch was reported with more than 80 participating restaurants, a roughly $1 reusable-packaging charge, customer text instructions, and two return routes: a participating store or a separately arranged pickup. A 2024 announcement described a later West Coast expansion and said the New York partnership had kept more than 11,000 single-use containers from landfills; it attributed related water and emissions estimates to DeliverZero.

Those are reported pilot observations and partner-reported estimates from 2023–2024, not current operating facts or independent lifecycle findings. This historical record does not verify present-day Uber Eats–DeliverZero availability, current merchant enrollment, current fees, return windows, pickup terms, or program status in any market. A restaurant that is interested now should obtain current written confirmation directly from the relevant platform and reuse-network contacts.

Pilot announcements are useful for seeing what was tested. They are less useful for deciding what a restaurant can enroll in today. A sound decision separates three questions:

1. What was reported then? This includes the historical launch flow, stated restaurant counts, and reported customer-return behavior.
2. What is being offered now? This requires current market eligibility, commercial terms, and operating instructions.
3. What can this location measure? This requires a local baseline and agreed reporting definitions rather than assumptions drawn from another city.

Keeping these questions separate prevents a past case study from being treated as a current program specification.

The available evidence is not enough to give a blanket yes or no. A single location should join only if the current offer fits its service pattern and the responsible parties can document how containers, payments, customer support, returns, and reconciliation will work.

Ask where customers can return containers, whether nearby participating locations are open during relevant hours, whether pickup is available, and who pays for or coordinates collection. A return route that looks clear on a map may be inconvenient for customers whose orders are primarily delivered to homes, offices, or hotels.

Map the routine from order acceptance to handoff. Who sees the reusable selection? Which menu items are eligible? Where are the containers staged? How does the team prevent a reusable order from being packed in the default format? Who receives returned containers, and where are they held before collection? The provider should supply current instructions that match the restaurant’s point-of-sale and delivery workflow.

A restaurant should request a written explanation of charges, fees, credits, inventory responsibility, loss handling, pickup obligations, and customer-service ownership. It should also clarify whether the platform, network, restaurant, or customer is responsible at each handoff. If these answers are vague, the restaurant cannot assess the operational exposure of joining.

Start with a small, defined evaluation period and a written scorecard. Record eligible orders, reusable selections, completed deliveries, store returns, pickups, outstanding containers, staff exceptions, and customer-service contacts. Review the data at a fixed interval with the platform or network and decide in advance what evidence would support continuing, changing, or ending the trial.

The communication should be equally precise. Tell customers what to select, where to return the container, when to return it, and where to get help. Do not make environmental, cost, or performance conclusions unless the program’s current measurement method and the restaurant’s own results support them.

A reuse pilot and a conventional packaging RFQ are separate decisions. If a restaurant is reviewing its regular takeaway packaging alongside a reuse evaluation, it can use TakeawayPack to begin an RFQ discussion covering product category, material, size or capacity, expected quantity, printing or logo needs, and destination market. Confirm the exact SKU and any required documentation for the intended market before making a purchasing decision.