When a restaurant’s direct online orders increase after a website launch, it is tempting to credit the new design. But a typical launch changes several things at once: ordering software, menu structure, payment flow, promotion, staff routines, and how pickup or delivery is handled. The result may be commercially interesting without isolating which part caused it.
Owner.com’s customer story about Doo Dah Diner, a family-run diner in Kansas, reports direct online sales moving from $3,000 per month to $7,000 per month and average check rising from $45 to $52 after the diner adopted a new site and commission-free online ordering. The story also describes an ordering app and delivery as part of the setup (case study). This is an outside platform customer case, not a controlled experiment. The platform publishes the reported outcome, and the package includes more than a visual redesign.
What the result can reasonably suggest
The story suggests that direct ordering can become a meaningful channel for some restaurants when customers can place orders through an accessible route and operations can fulfill them. A clearer menu and a shorter path may contribute. So may the ordering tool, fees, customer outreach, or a change in how orders are promoted.
The rise in average check is also worth separating from the sales increase. If customers order more per transaction, total direct sales can grow even if order volume changes less. The reported figures are monthly sales and average check, but the public summary does not provide a controlled comparison, traffic counts, number of orders, margin, or exact timeline. Avoid turning the percentage change into a prediction for another restaurant.
The operating context matters because a restaurant is a live service environment. A digital order has to reach the correct station, respect prep capacity, and include customer modifications clearly. Delivery requires dispatch and handoff. If those pieces fail, a technically successful online transaction can become a late order, refund, or dissatisfied guest. The story’s outcome should prompt operational questions as much as a design discussion.
Ask what the case leaves unanswered
Was online ordering previously unavailable or simply difficult to use? Did the diner introduce the platform to existing customers? Did the new system include delivery that was not available before? Were operating hours, menu, pricing, or promotions changed? How did commission savings compare with software and delivery costs? The case summary cannot answer all of these questions.
Those omissions do not make the story useless. They define what a restaurant should measure locally. A customer story can show a plausible path and a reported outcome, while a controlled experiment would be needed to isolate specific causal effects. Do not describe this as a test of “website design” unless the source demonstrates that design was the only meaningful variable.
Build a baseline before switching channels
Record existing phone, marketplace, and direct orders separately. Track number of orders, average order value, contribution margin after fees and fulfillment, cancellations, refunds, repeat rate, and staff time. Document which menu items are eligible for each channel and what delivery promises the kitchen can reliably meet.
Ask customers why they currently order through a marketplace or by phone. Some value a marketplace’s discovery, loyalty program, or delivery logistics. Others may prefer direct ordering if the menu is easier to understand or pickup timing is reliable. These are hypotheses to validate with your own customers, not assumptions to impose.
Treat the launch as a service change
Make direct ordering easy to find from the restaurant’s website and other channels. Ensure menu names, modifiers, prices, sold-out items, taxes, and fees are accurate. Test the order on a phone and verify the kitchen receives it correctly. Train staff to handle substitutions, late orders, and system interruptions. Explain the benefits of ordering directly only when they are real and valuable to the customer.
For a pilot, choose one location, menu segment, or promotion if operations allow. Compare outcomes with a similar period and note concurrent changes. If using an A/B test, keep the offer and traffic source consistent enough that the ordering experience is the meaningful difference. Most small restaurants will not have enough volume for a fine-grained experiment; a transparent before-and-after analysis is still useful if its limits are stated.
If a new ordering provider also changes payment processing or dispatch, record those differences separately. Calculate the full cost of each channel, including platform fees, discounts, labor, packaging, refunds, and delivery. A sales increase can coexist with lower contribution margin. Make the internal question explicit: is the goal to reduce commissions, make ordering easier, increase repeat purchase, relieve phone load, or reach new diners? Each goal requires different evidence.
Measure channel health, not just gross sales
Direct sales can rise while margin falls if marketing and delivery costs are high. The goal is not to move every order away from a marketplace. A mixed channel strategy may be rational if third-party platforms bring new diners. Review customer acquisition, repeat behavior, fulfillment workload, and customer satisfaction alongside sales.
The Diner case is best used to ask whether a direct path could fit your restaurant and what operational pieces it requires. The outcome is encouraging for that business as reported by its platform provider. The evidence does not establish that a new website by itself will produce the same result elsewhere.