Why a Vancouver dining room is different

Three things separate a Vancouver room from an equivalent room in Toronto or Calgary, and none of them is the weather.

The privacy regulator is provincial. British Columbia is one of a small number of provinces with private-sector privacy legislation of its own, so the phone number your host takes at the door is governed by the provincial Personal Information Protection Act and supervised by the provincial Information and Privacy Commissioner. Practically the obligations rhyme with the federal ones, but the guidance you should be reading, and the office that would contact you, are not the ones a national blog post points at.

The licence class is a floor plan decision. BC separates food-primary establishments from liquor-primary ones and attaches different terms to each. A waiting policy built on “have a drink at the bar and we will find you” quietly assumes a licence that a food-primary room may not hold. This is the single most common wrong assumption imported from American waitlist software.

The room turns twice on a summer weekday. Vancouver’s daytime demand is unusually front-loaded by ship calls and by a downtown core that empties into a small number of dining streets. A tool tuned for one evening peak will be idle at eleven and useless at one.

What the law requires when you text a guest in Vancouver

Purpose, and only that purpose. Provincial privacy law is built around a reasonable purpose stated at collection. A number taken so that someone can be told their table is ready is not a number taken so that they can be told about a new tasting menu. Ask separately, store the answer separately, and let a guest end one without ending the other. Our restaurant waitlist privacy guide sets out the whole join screen wording.

Retention that ends. A queue entry stops being useful the moment the party leaves. Keeping walk-in phone numbers indefinitely because the software makes it easy is the failure mode the provincial commissioner’s office writes about most often, and it converts a good tool into a liability you have not priced.

Accommodation, today, not when the standards land. The Accessible British Columbia Act created a framework and its accessibility standards have been introduced through the public sector first, so a small independent restaurant is generally not yet directly captured. Human rights law already requires accommodation, though, and the operational version is unglamorous: nobody should have to stand in a doorway to hold their place, and the host should be able to see an access note without asking the guest to repeat it in front of a queue.

The Vancouver dining calendar

  • April to October — cruise season at Canada Place. Ship calls drop very large lunch parties into a few downtown blocks with a hard boarding deadline. Quote conservatively: a party that misses the ship remembers your restaurant for the wrong reason.
  • June to August — patio and long daylight. Service stretches later, but the second turn is unreliable because guests linger while it is still bright at nine.
  • Late autumn and winter — rain, not snow. The vestibule problem here is different from the prairie one. Guests will happily wait outdoors in the cold; they will not wait in horizontal rain, and the walkaway rate tells you exactly when it started.
  • Convention weeks downtown. Weekday dinner behaves like a Saturday and Saturday behaves like a Tuesday, which breaks any staffing rule based on the day of the week.

The POS and reservation stack you will meet in Vancouver

There is no provincial certification requirement on a restaurant till in British Columbia, so the checkout market is open and most rooms run whatever their payment provider sold them. The constraint that actually shapes operations is licensing, not tax hardware.

If you hold a food-primary licence, your waiting area, your patio and your bar are not interchangeable spaces with different furniture — they are areas with different terms. Before you promise a guest they can wait with a drink, confirm what your own licence says. Get that wrong and the fix is not a software setting.

The second thing you will meet is a reservation platform that wants to own the guest record, priced per cover or per seat. For a room that is genuinely walk-in led, that is an expensive way to buy a queue. The trade-off is laid out in the SevenRooms alternatives comparison.

How StoveOps fits a Vancouver room

Guests join from their own phone by QR code or link, wait wherever they like, and get an SMS, WhatsApp message or email when the table is ready. The host works one list across the dining room, the patio and the bar, and the entry carries the notes that matter — access requirement, boarding time, party that must sit together.

The guest record belongs to the restaurant. StoveOps is not a marketplace, does not resell your list and does not charge per cover, which is what makes retention a decision you control rather than a term in someone else’s contract. For the national picture see restaurant waitlist software for Canada, and for a bar-led room the mechanics differ enough to be worth reading on their own in waitlist software for bars.

Vancouver operator checklist

  1. Read your liquor licence class before you write any waiting policy.
  2. Confirm which areas of the room the licence actually covers.
  3. State the purpose of the phone number on the screen that asks for it.
  4. Set a retention period for queue entries and hold yourself to it.
  5. Keep marketing permission separate from the waitlist permission.
  6. Let a guest register an access need without saying it out loud at the host stand.
  7. Build a separate midday quoting rule for ship-call days.
  8. Track walkaways against rainfall, not against temperature.
  9. Review whether accessibility standards have reached your sector this year.
  10. Re-test the join screen on a phone with a weak signal in your own doorway.