Azcarte

QR codes

Why one QR code is a wasted opportunity, how to place several, and how to read the scan numbers each one gives you.

QR codes

The QR Code tab holds the codes for your active menu. The banner at the top tells you which menu and location you are creating codes for.

Make several codes, not one. Most venues create a single QR code, print it everywhere and never think about it again. That works — but it throws away the one piece of information the codes can give you for free: which spot in your venue actually brings people to the menu.

Why more than one code

Every code points at the same menu. The difference is that Azcarte counts each one separately.

With one code used everywhere, you get a single number: 2,400 scans. True, and useless. You cannot tell whether people scan at the window before deciding to come in, or at the table after they have already sat down. Those are completely different things, and they point to completely different decisions.

With four codes — window, bar, table, printed menu — the same 2,400 scans become a picture of how people actually use your venue.

You cannot split this apart afterwards. If one code has been on every table and in the window for six months, those scans are one undifferentiated number forever. The only way to get the breakdown is to have made separate codes in the first place — which costs you nothing.

A placement per code

A good starting set, all pointing at the same menu:

PlacementLabel itWhat a scan there means
Window or entranceFront windowSomeone outside is deciding whether to come in
BarBarSomeone waiting, or drinking, browsing food
TableTable cardA seated guest using it as the actual menu
Inside the paper menuPaper menu insertA guest who wanted more than the paper gave them
Takeaway bag or receiptTakeawaySomeone considering coming back

Create a separate code per type of placement. One Table card code across all your tables is usually enough — you do not need one per table unless you genuinely want to know which tables scan most.

What the numbers tell you

This is the part most venues never get to, so here is what to actually do with it.

The window code is busy. People are reading your menu before they walk in — your window is doing sales work. Put your best dishes and prices where that code is, keep the display current, and make sure the menu is published and looks good on a phone in daylight.

The table code dominates. Guests are using the digital menu as the menu, not as an extra. That is the moment to spend effort on photos and the featured section — they are being seen by everyone who sits down.

The bar code is dead. Almost always a physical problem, not a demand problem. It is too low, behind bottles, catching glare, or has nothing telling people what it is for. Move it, add a line of text, and watch the next 30 days.

Takeaway scans are climbing. People are looking you up again after leaving. That is your returning-customer signal.

Nothing is scanning anywhere. The codes are too small, too dark, badly lit, or there is no reason next to them to scan. See the printing checklist below.

The real payoff is comparison over time. Move one code, change one sign, add one line of text — then look at that code's last 30 days. With separate codes you can tell whether it worked. With one code you are guessing.

Where to see the scan counts

Scan counts are in the advanced interface, not the mobile manager:

  1. Account → Advanced interface (it is built for a larger screen — a laptop is easier than a phone here).
  2. Open QR Codes.
  3. The list shows a Scans badge for every code, next to its Label and Placement.
  4. Click a code to open it for Total scans and a Scans — last 30 days chart.

Scan counts are included on every plan, Free as well.

Create a code

Tap New QR Code and fill in:

  • Label (required) — how you will recognise it in the list. Bar, Front window, Table card.
  • Placement (optional) — where it physically lives. Table 5, Window counter.

Tap Add QR Code.

Name codes by where they are, never QR 1 / QR 2. In three months you will be reading this list trying to remember which was which, and the label is the only clue you get.

Edit a code

Tap the pencil on a code to change its Label, its Placement, or the Table code switch, then Save. The printed code itself never changes, so copies you already stuck on tables keep working: move Table 5 to the terrace and just rename it.

Table codes: let guests call staff

Turn on Table code — guests can call staff for codes that sit on a table. Guests who scan one can call a waiter or ask for the bill from the menu, and staff see which table it came from. Use the table number as the Placement: it's what staff will read. Leave it off for window, flyer and takeaway codes. Guest requests are part of the Pro plan; see Guest requests.

Download and print

Tap Download on a code to get an SVG file.

SVG is a vector format: it stays sharp at any size, so the same file works for a table card and for a poster. Any print shop will take it.

Printing checklist

  • Size — at least 2 × 2 cm. Bigger for anything guests scan standing up, and bigger again for a window, where people scan from further away.
  • Contrast — keep it dark on a light background. Coloured or low-contrast codes fail in dim restaurant light.
  • Quiet zone — leave clear space around the code. Do not crop to the edge.
  • Finish — matte, not gloss. Glare defeats more scans than anything else.
  • Say why — a bare code gets ignored. "Scan for photos of every dish" gets scanned. This matters more than anything else on this list.
  • Test it — scan the printed proof with a real phone before you order 200.

Codes keep working

A QR code points at Azcarte, not at a fixed copy of your menu. Change a price, add a dish or swap the whole menu around and every printed code stays correct. You never reprint because the menu changed.

A code pointing at a draft menu will not show your dishes. Publish the menu from Home before printing.

Preview and delete

  • Preview menu opens what a guest sees when they scan it. Worth doing once per code.
  • Delete QR code removes it permanently, and its scan history with it — the confirmation says "Scan analytics for it will also be lost." If you are just retiring a placement, keep the code so its history survives for comparison.
Copyright © 2026