JournalGuide
Guide / RC JOURNAL

Does a Gatineau restaurant need its own website if it uses delivery apps?

Use your own site as a clear, maintained source for the menu, hours and contact path, then link to the ordering channels you actually support.

Illustration of a restaurant menu page on a phone beside a takeout bag and separate ordering cards

A diner in Gatineau sees your restaurant on a delivery app. They want to check today’s menu, ask about an ingredient, or find out whether they can pick up an order in Hull. The app may handle the transaction, but it may not answer those questions in your own words. Does the restaurant still need a website?

Usually, a small, maintained site is useful even when ordering happens elsewhere. Give diners one place to find the current menu, hours, address, pickup instructions, contact details and links to the channels you actually use. The site does not need a custom checkout just to do that job. If the team cannot keep an additional menu current, start with a concise page and a clearly labelled link to the maintained menu rather than publishing a second stale version.

This is a choice about information and operations, not a claim that a website will bring in more orders. In Statistics Canada’s Table 21-10-0249-01, 62.4% of Canadian food-service and drinking-place business locations that reported ecommerce sales in 2022 used a third-party website, while 50.4% used a company website. A location could use more than one method, so the percentages do not divide the market into exclusive groups. The surveyed portion excluded the smallest firms by revenue, and the data are national and historical. They do not measure Gatineau restaurants, the value of either channel, menu accuracy or profit.

Decide what each channel is for

A delivery platform can be the right place to place and pay for an order. Your own site can answer questions before the customer chooses a channel: what is available, where the restaurant is, whether pickup is offered, and how to reach a person. Google Business Profile can help people discover hours and a menu link. These are different jobs, and the same restaurant may use all of them.

Write down the customer paths you actually support. Can someone dine in, reserve a table, order for pickup, request delivery, or only call? For each path, name the system that accepts it, the staff member who monitors it, and what confirmation means. If pickup orders are accepted only by phone, say so. If a delivery app handles a delivery order, label the outbound button with that app’s name. Do not make an external order link look like the restaurant’s own checkout.

A simple site is enough when the menu is short, the opening hours are stable, and staff can update a page when something changes. A more involved site may help when there are several menus, changing availability, catering inquiries, reservations or locations with different hours. That is a scope decision, not a reason to buy features in advance.

Make the menu readable and assign an owner

Put the menu in ordinary page text where possible. Diners should be able to scan sections, item names, descriptions and prices on a phone without pinching a photograph. A PDF or image can supplement that page, but it is a poor sole source when the text is tiny or prices change often. If you use a PDF, check it with a phone and a keyboard, and make sure staff replace the old version everywhere it appears. Our guide to using PDFs on a small-business website explains when a download helps and when page content is easier to maintain.

Decide who approves menu changes and who publishes them. Use one internal list of current items, prices and availability as the working record. When a dish is removed or its price changes, update the site, ordering platforms and any downloadable menu together. Record who made the change and check the public pages afterward. A site that lists an unavailable meal can create avoidable calls and disappointment; a platform menu that disagrees with your site creates the same problem.

Do not promise that a menu description resolves an allergy question. Give customers a way to contact the restaurant and have staff use the current ingredient information and preparation process when they answer. If an item can be changed, describe only options the kitchen can reliably provide. Avoid a generic assurance about being “allergy safe” that the team cannot verify for an individual order.

Keep the public trail consistent

List the restaurant’s full address, contact number, ordinary hours and any separate pickup hours on the site. Say where a pickup customer should go and how they will know an order is ready. If the dining room closes before delivery ordering does, separate those hours. When a holiday or temporary closure is planned, update the site and each public profile that diners rely on; do not assume one system updates another.

Google’s Business Profile hours guidance describes how an owner can edit public hours. Its menu editor guidance says food businesses may add menu items, descriptions and prices, upload menu photos or a PDF, and add a menu URL. Google may also show other menu sources, including customer-uploaded photos; the owner can review the public result, choose a preferred menu source and flag an obsolete photo. The guidance says edits can take time to appear, so check the public profile after a change. This is platform documentation about available controls, not a promise that any particular profile will display exactly as intended.

For a Gatineau restaurant, check the path in French as well as English if both are offered. The Office québécois de la langue française says customers of businesses active in Quebec have the right to be informed and served in French, and it describes access to a complete French website. That guidance is broader than a restaurant menu. A useful review covers the menu, hours, pickup instructions, buttons, form errors and the message after an order or inquiry. Link to a genuinely maintained French menu rather than leaving the French page with an outdated English-only handoff. Our Gatineau website language guide covers the wider site question. Ask the OQLF or a qualified adviser about an obligation that is unclear for your particular business; this article is not legal advice.

Keep ordering choices clear

If the site sends people to another company to order, name that company on the button and let the destination show its current prices, fees and terms. Check the link on a phone. If the restaurant itself accepts online orders, decide who maintains availability, who receives a failed payment or duplicate order, and who contacts the customer if an item cannot be fulfilled. A link that opens a cart is not the whole process.

Quebec’s Office de la protection du consommateur explains the information a merchant generally needs to show before an online purchase, including a detailed description, price, fees, taxes, total cost and applicable delivery or cancellation terms. It also notes that some rules differ for goods that spoil quickly. Review the current rules for the transaction you actually offer before adding your own checkout. If a third party takes the order, review what the customer sees there too, while keeping the restaurant’s own menu and pickup promises accurate.

There are legitimate reasons to keep ordering on a platform: the team may already rely on its dispatch, payment and support process. There are also reasons to consider an owned order path: control over the customer journey, clearer pickup information or integration with an existing system. Compare the actual ongoing fees, staff work, refunds, technical upkeep and support terms of the options under consideration. A lower advertised transaction fee by itself does not prove the owned path is cheaper, and moving orders does not guarantee a business result.

Test a real diner journey

Ask someone who has not worked on the site to use a phone to find a current item, its price, the day’s hours and the right pickup or delivery path. Have them switch languages if the business publishes both. Follow the order or inquiry through to the confirmation and to the staff record. Try a temporarily unavailable item and a closed period. The team should know whether the system rejects the order, holds it for approval or needs a manual response.

Then check the public trail: your site, Google profile, any delivery platform, social profile and printed QR code. Record the date of the review and who will repeat it when the menu or hours change. A simple maintained site can be better than a larger one whose information diverges across channels.

If a Gatineau restaurant needs help planning a website around its menu, languages and actual ordering process, see Red Comet’s web design work in Gatineau. Start with the customer tasks and the team’s capacity to maintain the result.

Sources

WHAT COMES NEXT

Have a project in mind?

Explore what we make and how we can help shape your next idea.

Explore our services