Should Cutlery Be Included by Default in Delivery Orders? How to Switch to On-Request Utensils Without Losing Ratings
Cutting cutlery and napkin costs does not have to mean disappointing customers. Restaurants that make this work change three layers at the same time: the ordering page (an item-level opt-in instead of an automatic bundle), the packing workflow (a separate accessory step driven by a clearly printed request), and the utensil pack itself (right-sized components matched to the dish instead of a full set in every bag). The default has already shifted in law and practice: New York City, California, and Washington State now require single-use utensils, condiments, and napkins to be provided only on request for takeout and delivery, England has banned single-use plastic cutlery outright, and a large field experiment on a food-delivery platform found that a "no cutlery" default increased no-cutlery orders by 648% while keeping the option available. This guide walks through how to redesign each layer, how to protect the small share of orders where a missed fork becomes a one-star review, and how to verify the change with a four-week pilot. Every recommendation is written so a purchasing or operations lead can put it in front of the team this week.
2026-09-02 - 13 min read

Summary
Cutting cutlery and napkin costs does not have to mean disappointing customers. Restaurants that make this work change three layers at the same time: the ordering page (an item-level opt-in instead of an automatic bundle), the packing workflow (a separate accessory step driven by a clearly printed request), and the utensil pack itself (right-sized components matched to the dish instead of a full set in every bag). The default has already shifted in law and practice: New York City, California, and Washington State now require single-use utensils, condiments, and napkins to be provided only on request for takeout and delivery, England has banned single-use plastic cutlery outright, and a large field experiment on a food-delivery platform found that a "no cutlery" default increased no-cutlery orders by 648% while keeping the option available. This guide walks through how to redesign each layer, how to protect the small share of orders where a missed fork becomes a one-star review, and how to verify the change with a four-week pilot. Every recommendation is written so a purchasing or operations lead can put it in front of the team this week.
Most delivery operators know this tension: every automatic fork, spoon, and handful of napkins adds unit cost, material waste, and carton space, yet the fear of "my food had no fork" reviews keeps the habit alive. That fear is rational — a customer who asked for utensils and did not receive them is far angrier than one who never wanted them. But regulation, platform practice, and published research all point the same way: when the request is visible at ordering and honored reliably at packing, customers adapt quickly and complaint risk stays low.
Why the "default included" model is ending
Three forces are converging on the automatic cutlery bundle.
Regulation increasingly requires "upon request"
In the United States, several of the largest delivery markets have already made the default a legal question rather than a preference:
- New York City: since July 31, 2023, food service businesses and third-party delivery apps may not provide utensils, condiment packets, napkins, or extra containers with takeout or delivery orders unless the customer requests them, and online ordering must default to not providing them. The NYC Department of Sanitation enforces the rule with escalating fines for repeat violations within a 12-month period (NYC Department of Sanitation).
- California: under Public Resources Code Section 42271 (AB 1276), a food facility shall not provide any single-use foodware accessory to a consumer unless it is requested, accessories may not be bundled so that a customer must take one type to get another, and third-party platforms must give consumers a way to request the specific items they want (California Legislative Information).
- Washington State: since January 1, 2022, utensils, straws, condiment packaging, and beverage cup lids may be provided only after the customer affirms they want them, and utensils may not be bundled in plastic in a way that forces a customer to take types they did not ask for (Revised Code of Washington 70A.245.080).
The pattern extends beyond the US. In England, supplying single-use plastic cutlery has been banned outright since October 2023, and the guidance points businesses to single-use items made from other materials, such as wood or paper (GOV.UK). Across the European Union, Directive (EU) 2019/904 requires member states to prohibit single-use plastic cutlery — forks, knives, spoons, and chopsticks — from being placed on the market (EUR-Lex summary).
The practical consequence for a multi-market operator: "utensils by default" is no longer purely an internal policy choice. If you serve these markets, the on-request model is the compliant baseline, and the real question is how to run it without hurting the guest experience.
Platforms have normalized the opt-in
Major delivery platforms already expose an accessories preference at checkout, so many of your customers have seen the pattern before. When the platform carries the opt-in interface, the operator's job shifts to making sure the preference actually reaches the packing ticket — a configuration task, not a customer-education campaign.
The evidence says defaults work
The strongest published data comes from a large field experiment on China's food-delivery industry, published in Science in 2023. Working with the Eleme platform, researchers found that changing the default to "no cutlery" — while keeping the request option available — increased the share of no-cutlery orders by 648%, and they projected that applying the approach nationally could save more than 21.75 billion single-use cutlery sets per year (He et al., 2023, Science, via PubMed). The critical design detail for operators: the nudge changed what happened when customers did nothing. It did not remove anyone's ability to get cutlery.
That is the design brief for everything below: change the default, never the availability.
Layer 1: The ordering page — make utensils an item-level choice
The ordering page is where complaint risk is won or lost. A customer who clearly saw the option and chose it rarely blames the restaurant later; a customer who never noticed anything changed blames the restaurant immediately.
Replace the bundle with item-level choices
A single vague "Add utensils" toggle recreates the waste problem in miniature — a customer eating soup at home who taps it receives a full fork-knife-spoon-napkin set and discards most of it. Where your ordering system allows it, offer exactly what can physically go in the bag:
| Option | Pack it as |
|---|---|
| Fork | single wrapped fork |
| Knife | single wrapped knife |
| Spoon / soup spoon | single wrapped spoon |
| Chopsticks | single pair |
| Napkins | small fixed count |
| Straw | single wrapped straw |
| Condiments | attached to the relevant dish instead |
Item-level structure also matches what the "upon request" laws expect: California, for example, requires that accessories not be bundled so the customer must take one type to get another.
Write copy that sounds like service, not cost-cutting
The framing matters as much as the default. Compare:
- ✗ "Utensils are no longer included." — reads as a service reduction.
- ✓ "Need utensils or napkins? Select what you need and we'll pack them with your order." — reads as a service feature.
The second version makes three things unambiguous: the customer still gets utensils, the mechanism is their choice, and the restaurant is still prepared to serve. Avoid guilt-based eco-messaging; customers who feel scolded rate the experience worse, not better.
Match the request path to each channel
- Native app / website: item-level checkboxes at cart, preselected to nothing, with the reassurance line above.
- Third-party platforms: turn on the platform's utensils preference where it exists and set the default to off; verify the selection prints on the ticket.
- Phone orders: a scripted question at the end of every call — "Would you like utensils or napkins with that?" — and a required field on the order entry screen so nothing is left blank.
- Counter / pickup: ask at handoff, or, where local rules allow, keep a self-serve station so guests who forgot to request can help themselves. New York's rule explicitly does not apply to self-serve stations inside a food service establishment, and Washington's statute likewise allows utensils to be made available through dispensers when the customer takes them by choice — so the counter dispenser remains a legitimate channel for last-minute needs in those markets.
High-risk dishes still deserve a dish-level prompt
Not all menu items carry equal risk. Soup, salads, noodle dishes, and family bundles are the orders where "no utensils" is most likely to be a mistake rather than a choice. Add a required sub-prompt on those items: "Eating on the go? Add a spoon / fork." This is not a return to the old default — the customer still chooses — but it catches the omission on the highest-risk items without adding friction to a coffee-and-pastry order.
Layer 2: The packing workflow — honor the request with a visible, checkable step
Complaints almost never come from the policy; they come from a packing mismatch — the customer requested, the kitchen forgot. The fix is structural, not motivational: separate accessory packing from food packing so that adding utensils requires a deliberate act.
Two-station flow
- Station A — food packing: pack and seal food only. Keep no utensil bins within reach. This single physical change removes the muscle-memory grab that defeats most policies.
- Station B — accessory station: the packer reads the utensil line from the ticket, adds exactly what was requested, and completes the final check before sealing.
The station separation is what makes the policy enforceable across shifts and staff turnover. When utensils live in the grab path, every new hire re-creates the old habit within a week; when they live at a labeled "Request Only" station, the habit has nowhere to form.
Make the request unmissable on the ticket
Configure the kitchen display or ticket printer to show the utensil state in a fixed, prominent position — not buried among modifier lines:
- `UTENSILS: NONE` — pack no accessories.
- `UTENSILS: FORK ×2 + NAPKIN` — add exactly this.
- `UTENSILS: 2 SETS` — family orders.
Train staff that a blank or absent line means "none" by definition, so no one ever guesses.
Add one final check and a recovery path
The last hands on the bag run a four-step check: read the utensil status, add only the requested items or confirm none, apply the matching bag label, and seal. A two-state label system — "Utensils included as requested" versus "Packed without utensils — need them next time? Select them at checkout" — turns the outside of the bag into both a packing aid and a customer reassurance, and it is the cheapest way to absorb a policy change without a printed insert.
For the small number of misses that still happen, define the recovery before launch: when a customer reports a missing requested item, staff respond through the platform, apply the business's standard remedy, and log the reason. A fast, scripted apology converts most "no fork" complaints into neutral or positive service stories; an unanswerable complaint converts into a one-star review. (For a deeper treatment of preventing packing mismatches, see our food delivery packaging acceptance checklist for restaurant teams.)
Layer 3: The utensil pack itself — right-size what you stock
Once accessories are on-request, inventory logic changes: you no longer need one bundle that fits every order; you need a small set of components that can be combined per request.
Match components to dishes
The savings come not just from sending fewer pieces, but from no longer stocking a single expensive "everything bundle" whose unused components are pure loss. If a customer opts out of cutlery but wants napkins, a fixed small count per order is enough — open-bin grabbing is where napkin cost quietly doubles.
| Dish type | Sensible default pack |
|---|---|
| Soup / ramen / congee | soup spoon (+ napkin) |
| Salads / rice bowls | fork (+ napkin) |
| Steaks / Western mains | knife + fork (+ napkin) |
| Asian noodle and rice dishes | chopsticks (+ soup spoon where relevant) |
| Family / group orders | loose quantities to match headcount, not a fixed multiplier |
| Drinks / desserts | straw or teaspoon only |
Wrapped or bulk: the hygiene and logistics trade-off
Pack format is now a purchasing decision, because it decides how the accessory station operates:
- Bulk packed (unwrapped): lowest unit cost and least packaging per piece, but unwrapped items need clean handling and a covered dispenser — best for counter self-serve or in-store use where rules allow.
- Individually wrapped (film or paper): each piece sealed — the standard choice for delivery bags, because a sealed piece survives the journey, reads as hygienic at unboxing, and can be dropped into a sealed bag without a separate sanitation step.
Wrapped single pieces are the natural fit for the on-request delivery model: each request maps to one sealed unit, nothing is opened in advance, and nothing sits exposed in the packing area.
How one catalog makes this concrete
This is not a hypothetical format choice. TakeawayPack's disposable cutlery line is structured exactly around the bulk-versus-wrapped decision: a 7-inch (approx. 178 mm) white cornstarch knife is offered in three formats — bulk packed, individually wrapped in OPP film, and individually wrapped in kraft paper — so a buyer can run wrapped knives through delivery bags and bulk pieces at a permitted self-serve counter from one product family. The same 7-inch line includes bulk forks and knives at roughly 6.5 g per piece and teaspoons and soup spoons at roughly 5.0 g, alongside shorter plant-fiber pieces (6-inch knife and fork, 4-inch Asian soup spoon) for the dish-specific packs above. Choosing one line that exists in both wrapped and bulk formats lets you standardize on a single supplier and two stock-keeping units per component instead of two parallel inventories. (Material selection is covered separately in our wooden cutlery sourcing guide and our buyer's guide for importers and distributors.)
Planning note: for custom-printed cutlery packaging or branded napkins, minimum orders generally start around 1,000 units for regular items (5,000 for bags), depending on the product and the production method — always confirm against a specific quotation.
Protecting ratings: the four safeguards that matter
- A visible choice at ordering — the single highest-leverage step. Customers forgive a policy they can see; they punish a surprise.
- A confirmation echo — the order confirmation states the selected utensil state ("packed without utensils" or "utensils included as requested"), so an error can be caught before the kitchen fires the order.
- Dish-level prompts on high-risk items — soup, salad, noodles, and family bundles get an extra ask, because those are the omissions that become reviews.
- A zero-tolerance rule for requested-but-missed — treat a missed request as a process failure with a defined remedy, never as acceptable collateral. The evidence points the same way: people accept not receiving what they never asked for, and they punish not receiving what they did.
A four-week pilot with acceptance criteria
Run the change as a measured pilot rather than a memo. A four-week window on one or two stores, or a single delivery channel, is usually long enough to expose both UX problems and packing misses.
| Week | Actions |
|---|---|
| 1 | Switch defaults in all channels; keep a small emergency utensil stock at Station B; brief staff on the recovery script; start logging the metrics below daily. |
| 2 | Review request rate by dish type; fix dish-level prompts that are missing or ignored; verify ticket lines render correctly on every platform. |
| 3 | Remove remaining habit stock from Station A; audit 20 sealed bags per store against their tickets. |
| 4 | Decide: scale the rollout, extend the pilot, or adjust the copy. |
Metrics and how to read them
Two failure signatures tell you where to fix:
- "I couldn't find the option" → a UX problem: move the control, enlarge it, or add the dish-level prompt.
- "I selected utensils and got none" → a packing problem: fix ticket visibility or the two-station flow, not the policy.
After the pilot, the purchasing payoff arrives on the next order cycle: consumption data becomes smaller cutlery and napkin volumes, freed storage space, and a component list you can actually negotiate on. For the broader measurement frame — from complaint rate to repeat purchase — see how to measure whether a takeout packaging upgrade pays back.
| Metric | Why it matters | Suggested pass bar |
|---|---|---|
| Utensil units per order | Falling units mean the default is working | Meaningful drop versus baseline; expect the majority of orders to select nothing |
| Request rate by dish / daypart | Forecasts stock; reveals dishes that need prompts | Stable after week 2 |
| Packing mismatch rate (requested but not packed) | The metric that predicts "no fork" reviews | Near zero; every instance logged and remedied |
| Utensil-related complaints and low ratings | Separates expectation failure from execution failure | No sustained upward trend; every complaint answered in-platform |
| Overall rating and completion trend | Confirms no broad checkout friction | Flat or better |
Rollout checklist
- ☐ Item-level utensil and napkin options live on the app, the website, and every third-party platform
- ☐ Defaults set to "none" on every channel, matching local upon-request rules
- ☐ Reassurance microcopy at the cart and in the order confirmation
- ☐ Dish-level prompts on soup, salad, noodles, and family bundles
- ☐ Phone script and mandatory order-entry field in place
- ☐ Accessory station physically separated from food packing
- ☐ Ticket shows a `UTENSILS:` state in a fixed position; blank means none
- ☐ Two-state bag labels printed and stocked
- ☐ Recovery script written, rehearsed, and shared with every shift
- ☐ Pilot metrics dashboard running before day one
Start the switch
Moving from "default included" to "request and deliver" is a procurement decision as much as an operations one: it changes which cutlery formats you stock, how many you need, and how they arrive. TakeawayPack works with restaurants, cafés, chains, and distributors on packaging restructuring of this kind — including cutlery in bulk and individually wrapped formats, right-sized to a delivery flow. Browse the cutlery category and the napkins and wipes category, or contact the team with your product category, material, size or capacity, estimated quantity, and customization needs to start a quotation-based conversation. To go deeper on the on-request model itself, read Should Delivery Orders Include Cutlery by Default? — and as with any packaging decision, confirm exact MOQ, lead time, and documentation requirements for your destination market against a specific quotation before ordering.

