A cloud kitchen website needs a recognizable brand, a readable menu with prices, clear delivery or pickup details, current hours, and an obvious way to order. With no customer-facing storefront, the website has to answer those questions before it sends someone to an ordering service.
Map the journey from discovery to order: check the service area, choose food, select pickup or delivery, then reach the right ordering service. Make it clear where checkout and order confirmation happen, and don’t imply the website handles delivery, payment, or fulfillment when another provider does. For the broader page structure, see the complete guide to restaurant websites, or explore Nommy’s cloud kitchen solution.
What should a cloud kitchen website include?
A cloud kitchen website should make the brand, menu, service area, operating hours, and order route easy to find from a phone. Put the details that decide whether someone can order near the menu and order button.
| Website detail | What to show | Why it helps |
|---|---|---|
| Brand | Name, cuisine, short description, current food photos, and photos of the real packaging | Customers can tell which virtual restaurant they found and see what will arrive at the door |
| Menu | Categories, item names, descriptions, prices, and available options | Customers can compare dishes before opening an order service |
| Service area | Delivery zones or a clear area-check link | Customers can see whether delivery is available where they are |
| Hours | Order hours, last-order time if different, and temporary closures | Customers do not mistake a closed kitchen for a broken link |
| Order route | Pickup, delivery, or marketplace links with clear labels | Each button sets the right expectation for the next step |
| Contact and policies | A monitored contact method and useful notes on substitutions or allergens | Customers know where to ask about an order or a dietary concern |
Keep essential details as readable page text, not only inside a menu image. A restaurant website builder designed for food businesses can keep the menu, service notes, and links together. The kitchen still needs to confirm each order route and business detail.
How should a cloud kitchen website handle order links?
The order button should name the service customers will use and lead to the current menu for that brand. “Order delivery” is clearer than “Click here,” and a button that names the delivery app tells customers that checkout happens on another platform.
If the kitchen accepts orders through more than one channel, explain the choice instead of showing several identical buttons. Separate delivery and pickup, or label each marketplace link by name. Check that the provider’s menu, prices, hours, and availability match the website before sending customers there. If marketplace prices are higher to cover commission, decide whether to explain the difference; the guide on charging higher prices on delivery apps covers that trade-off.
The guide to adding online ordering to a restaurant website covers the setup sequence, and the food delivery platforms guide helps weigh marketplaces against direct orders.
When the website sends customers to another service, treat the site as the guide and that service as the transaction point. If orders begin by chat or phone (see WhatsApp ordering for restaurants), say whether staff must confirm them before preparation. Make clear which details the team needs—items, quantities, pickup or delivery, address, and payment method—so a click is not mistaken for a confirmed order.
Which delivery details belong beside the menu?
Show the operating details that can change a customer’s decision: delivery zones, minimum order if one applies, fees when known, pickup instructions, and the hours when orders are accepted. If a provider calculates the final fee or confirms availability, say so before the customer leaves the website.
Fees may vary by zone, time, or provider. If the final total appears only at checkout, state that clearly instead of showing an amount that does not apply to every customer.
Keep menu notes specific. State whether a dish is available only at certain times and whether a listed portion serves one or more people. Explain how customers can ask about an allergen concern. Avoid broad safety promises unless the kitchen can verify them for every recipe and preparation step.
The problem: A cloud kitchen sends Instagram visitors to a PDF, its packaging QR code to one marketplace, and its website button to an old order form. Returning customers cannot tell which menu is current.
The real-world fix: Choose one live menu page as the source of truth, then check the hours, service area, and order links on every bio, marketplace profile, and printed QR destination whenever those details change.
How can one kitchen present several virtual brands?
Give each virtual brand its own recognizable name, short description, menu, and order route, even when the concepts share a production kitchen. A customer looking for a rice bowl should not have to sort through a second brand’s dessert menu.
For one concept, a single page may be enough. For multiple concepts, give each brand its own recognizable web presence, menu, and ordering route. A parent brand-selection page can help customers choose between concepts, but delivery-only brands should each have a distinct website to meet Google’s virtual food brand requirements. A noodle brand and a dessert brand, for example, can share a pickup process while keeping their menu, photos, and prices distinct. Put shared details—such as a pickup location or customer-service contact—in a clearly labeled section, and repeat only the information that differs by brand.
Google has separate rules for virtual food brands. Delivery-only brands need distinct branded packaging and a distinct website, and each brand’s Business Profile must specify its service area and hide its address. Multiple brands operating from one kitchen may require additional verification. For pickup operations, signage and address-display rules differ. Review Google’s virtual food brand guidelines before creating or updating a profile for each brand. The guide to claiming a Google Business Profile covers the broader eligibility and verification process.
What should be tested before a cloud kitchen website goes live?
Open the site on a phone and test the route from the first page to the order destination. Before launch, check that:
- The brand name and food type are clear without relying on the logo alone.
- Menu names, descriptions, prices, and availability match the ordering service.
- The delivery area, hours, pickup instructions, and order cutoff are current.
- Every order button reaches the right brand and channel.
- A printed QR code or social bio opens the intended live page.
- Contact details and dietary notes are accurate and monitored.
Recheck the route after a menu change, provider switch, service-area adjustment, or temporary closure. Test every printed QR code before ordering packaging; the QR menu creation guide explains how to choose a stable destination.
Keep menus, service details, and order links together on a Nommy website. Start free with Nommy and build a customer-facing page around the order route already in use.
Before launch, tap every link a customer could reach from your site, bio, and packaging, and confirm each one lands on the same live menu.