The Trade-Offs Between Delivery Apps and Direct Ordering

The phrase “third-party delivery” hides several arrangements. A marketplace helps customers discover restaurants and place orders. A delivery service moves food after the restaurant takes the order. A hosted storefront supplies ordering technology on a restaurant's own digital property. One provider may offer all three.

That matters because the commercial relationship changes with the product. The provider that introduces the guest may also control the account, the order messages and the next recommendation. A fulfilment provider may enter the journey only after the restaurant has already taken the order.

The distinction appears in the factual record of the US case DoorDash, Inc. v. City of New York, decided in August 2026. The court described different customer-data arrangements for Marketplace, Drive and Storefront. That is a product distinction worth understanding before applying a broad label such as “platform-owned customer”.

Begin a channel review by drawing the actual route. Where does the guest discover the restaurant? Where do they place and pay for the order? Who delivers it? Who answers when something goes wrong? Which service sends the invitation to order again?

The result may be a mixed arrangement rather than a simple choice between a platform and a website. That is entirely workable. The restaurant needs to understand which parts it controls and what it relies on someone else to provide.

“We own our customer data” sounds decisive, but it leaves too much unresolved. A restaurant may receive a phone number for delivery coordination while having limited permission to use it for marketing. It may see order information in a portal without being able to export a usable history.

Ask about specific actions. Can the restaurant identify repeat customers? Can it contact them about an order? Can it invite them to join a separate loyalty programme? Can it export the information, correct an error or honour a deletion request? What happens to access when the agreement ends?

The guest's permission matters alongside the commercial contract. A number provided to arrange delivery should not automatically become a promotional audience. Treat service communication and marketing as separate purposes, then establish how the required preferences are captured and respected.

DoorDash's published Storefront privacy and consumer terms exhibits describe collection, use and sharing through a template. They illustrate the range of responsibilities involved. The restaurant still needs to examine its completed agreement and actual customer notices.

Include the practical form of access in the review. An export that omits stable order references may be difficult to reconcile. A loyalty integration that cannot apply a changed preference creates work elsewhere. Information has operational value when the restaurant can use it appropriately and maintain it accurately.

The better question is which customer commitments the restaurant can fulfil with the permissions and systems it has.

A channel comparison should follow the money far enough to include the work around the order. The advertised fee is only one component.

Start with net sales received and subtract the costs attributable to that order: ingredients, packaging, channel charges, payment processing, delivery support and any restaurant-funded discount. Include refunds and the staff effort required to resolve channel problems where those can be measured reliably.

Direct ordering brings its own costs. The restaurant may pay for software, attract visitors, maintain the menu, answer enquiries and arrange delivery. Some costs occur per order; others continue even when order volume is low. Keep that distinction visible.

Then examine whether the channel brings additional demand. A marketplace order from someone who would otherwise never find the restaurant has a different role from a regular guest moving between channels. Neither can be judged from the fee alone.

For a hypothetical example, a neighbourhood restaurant might use a marketplace to reach unfamiliar nearby households while offering a direct collection route to regular guests. The direct service may have a narrower menu and scheduled collection slots that the kitchen can manage well. Its success would depend on repeat use and dependable fulfilment, rather than on immediately replacing every marketplace order.

Avoid averages that conceal the difficult orders. Compare by service period, basket type and fulfilment method. A large delivery order at a quiet time may make a different contribution from a heavily discounted small order at peak capacity.

This is a basis for a measured channel strategy. It gives the owner a way to weigh demand, cost and operating capacity together.

A restaurant's desire to pay less is not, on its own, a customer proposition. Guests choose channels for reasons such as familiarity, payment convenience, delivery visibility or saved details. A direct route needs to provide a credible experience of its own.

The benefit might be reliable collection, a complete menu, straightforward group ordering or a clearly explained loyalty offer. Choose something the restaurant can sustain. Permanent discounting can make the new channel expensive before it has established any other value.

Keep the first direct journey focused. A guest should be able to confirm the branch, understand availability, select items, see the complete charge and receive a clear outcome. If account creation is required, explain its purpose. If an order needs staff acceptance, say so.

Connect the service to the kitchen before promoting it. Square's DoorDash integration documentation shows that menus, modifiers and order handling require coordination across products. The same care is needed when introducing a restaurant's own ordering route.

Give the direct service an accountable owner. Someone must maintain the menu, review failed orders and ensure staff know how to answer enquiries. A website can launch in a day; dependable service requires continuing attention.

Promotion should reflect the agreements governing each channel and the choices guests have made. Build a direct audience through appropriate invitations and a service worth using. Access to someone else's order record is not a substitute for that relationship.

A late order exposes the boundaries between restaurant, platform and courier. The guest wants a resolution. Each organisation may hold only part of the information.

Before choosing a channel, rehearse a few incidents. The restaurant accepts an order but an item becomes unavailable. A courier arrives before the food is ready. An order is marked delivered but the guest reports it missing. The guest requests a refund after preparation has begun.

For each incident, establish who can contact whom, who authorises a remedy and where the outcome is recorded. Staff need access to the relevant order details without having to borrow an owner's account. The guest needs a clear contact route instead of being passed between organisations.

Direct ordering increases the restaurant's visible responsibility. Even if another company supplies the delivery or payment service, the guest may reasonably approach the restaurant first. Include that workload in the service design and the economic comparison.

Also examine the information retained after resolution. Repeated complaints about one collection arrangement may point to a process problem. A refund reason recorded only inside a platform can be difficult for the restaurant to learn from. Access to suitable reporting may therefore be more valuable than another promotional feature.

Control is most valuable when it comes with the ability to act. A restaurant gains little from receiving more messages if the team lacks the authority or information to resolve them.

Give each channel a job. One may introduce new guests, another support regular collection and another serve larger planned orders. Write down the result expected from each and the service responsibilities that accompany it.

Pilot a direct route within a manageable scope. Choose a branch, service period or order type with a clear operating owner. Keep existing demand routes available while the team learns whether the new service is dependable and whether guests choose it again.

Review contribution, repeat use, preparation delays, support effort and unresolved incidents together. A growing order count can still overload the kitchen. A modest direct channel may be valuable if it serves a distinct group well and is economical to maintain.

Revisit the agreements as the business changes. Additional branches, loyalty integrations or new marketing practices can alter what the restaurant needs from its providers.

The objective is a deliberate mix of access and responsibility. The restaurant should know what each channel contributes, what it can promise the guest and which relationships it is equipped to maintain. That makes the next investment easier to justify than a blanket campaign to move every order away from a platform.