What a restaurant-owned ordering website actually needs

01

Start with one complete order path

Write the journey in plain words before choosing screens or providers.

• Customer opens the restaurant link.
• Customer browses the menu and chooses item options.
• Cart checks price, fulfilment and availability.
• Customer selects pickup or an approved delivery route.
• Payment opens through the restaurant’s approved account.
• The order reaches the named restaurant owner or team.
• The restaurant accepts, prepares and updates the order.

02

What the customer needs

• Recognisable restaurant branding and a readable mobile menu.
• Current prices, item availability and clear choice rules.
• A cart that shows the full order before payment.
• Address or pickup details collected at the right moment.
• A checkout route with useful success and failure states.
• A clear way to see or receive restaurant-confirmed updates.

03

What the restaurant needs

• A named place where new orders arrive.
• One role responsible for accepting or declining an order.
• Preparation, ready and fulfilment states the team can actually maintain.
• Written rules for pickup, delivery, cancellation, refund and support.
• A simple escalation path when a provider or connection fails.

04

Accounts and connections

The restaurant should control its core business accounts. Every connection must be named in the scope because availability, approval, fees and technical limits differ.

• Restaurant-approved domain and merchant account.
• Scoped maps, messaging, POS or delivery provider.
• Named access owner and recovery method.
• Known setup, usage and transaction costs.

05

What must be tested

• Real phone widths and common browsers.
• Menu, option, quantity, cart and availability rules.
• Payment success, cancellation and return states in the approved test mode.
• Restaurant alerts and the staff acceptance path.
• Customer status updates and safe failure messages.
• Launch redirects, analytics, access and handover.

06

What is not automatic

A website creates an owned route. It does not automatically create customers, supply riders, guarantee POS compatibility, remove provider charges, replace marketplace discovery or guarantee financial results.