In Pepper, a printed QR code is a named link on your own installation. You can change where it leads after printing, give it your brand colours and logo, and make one for every table in a single step. Its results show up beside the enquiries, quotes, invoices and payments it brought.
This page is for owners who print codes on menus, tables, packaging, windows, flyers and business cards. The widget manual has every step and limit.
Send a code where it is useful today
A code can open a published widget, a page of your Pepper website, a web page, a file, a place on a map, a colleague's business card or your app in the App Store or Google Play. You can change any of these after printing. The code on the table stays the same.
A café can print one code per table. In the morning the code opens the breakfast menu widget. After a change in Pepper, the same code opens the lunch menu. Nobody reprints anything.
Two kinds hold their content inside the code: Wi-Fi access and a plain contact card. Pepper says Cannot change after printing beside them, because no system can change what is printed in the code itself.
Print a code for a page of your website
Open a page in the website editor and click New code under QR codes. The code takes the page title as its name and leads to that page. You need no widget.
A page code never leads to a dead end. It follows the page when you rename it or change its address or the website address. If you remove the page, scans open the website's home page in the same language. The code then shows that state with Choose a page, so you can point it at another page in one step. Visits from the code appear under Page codes in the website figures, with the code's campaign and channel.
Make the code look like your business
Choose a style once for every new code: Classic, Rounded, Dots, Brand or Brand with logo. Change the colours, module and corner shapes, add your logo and a frame with a short call to action such as "Scan to book". A single code can have its own style.
Pepper refuses a style that risks a failed scan, before you save it. The contrast must be at least 4.5 to 1 with a darker code on a lighter background. A logo can cover at most 12% of the code, and it raises error correction to the highest level. SVG, PNG and print sheets use the same style. Test one printed copy with your visitors' phones before a large print run.
Make a code for every table, room or package
A set makes up to 500 codes in one step. Number them with a pattern such as Table {n}, or upload a CSV file with a name, channel, destination and tag per row. Pepper shows which rows it will create and which it will skip, and why, before it saves anything.
Download the set as A4 label sheets for common label layouts, or as a ZIP of SVG and PNG files. If you made a set by mistake, undo it in one step while no code in it has been scanned or used.
Give your team the same business card
A card standard sets the layout, accent colour, logo, legal footer and one shared button for every colleague's card. Each person still chooses their own fields and publishes their own card. You can invite each person once to make their card. Each published card gives its person an email signature with the card link and its code.
Cards at work compares the cards over the last 30 days. A person who manages people and can view analytics sees each card published in that period: opens, saved contacts and call or email taps, with the change from the previous period and a team total. A colleague with analytics access sees only their own card. Figures from 1 to 4 stay withheld, and message contents never appear. Export the same figures as CSV.
If you set up your own Apple certificate or Google service account, visitors can save a card to Apple Wallet or Google Wallet. Without that setup, cards show no wallet button and Pepper contacts neither company.
See what a code brought
Each code is a placement in Pepper's analytics. Compare codes, sets of codes and print runs. Open a figure to see the records behind it.
The register shows opens, results and paid money per code and per set, beside the previous period. Opens are counted page views and scans, not people. Pepper counts scans only when you turn on audience measurement. Per 100 printed relates opens to the printed copies. The register also lists codes that nobody scanned yet. The widget's publishing kit shows the same 30-day figures beside each code.
For example, a window code at a studio in Rotterdam leads to a quote request. The studio accepts a EUR 1,200 quote and records the payment. A table code at a restaurant in Austin leads to a catering request, and the restaurant invoices USD 850. Pepper links those records to their codes and keeps each currency separate.
Revenue tracing uses explicit record links within 30 days and shows first and last touch. It does not prove that a code caused a sale. Read how Pepper traces revenue.
What stays private and what Pepper does not do
- Pepper uses no outside link shortener. The code points at your installation's address.
- Pepper keeps nothing about the person who scans: no address, device or identifier. Scans count only when you turn on audience measurement.
- Scans of a web page, file, place or app count once at the redirect. A request after an outside page shows source unknown. Wi-Fi and contact codes cannot be counted.
- Pepper promises no scans, visitors or sales.
Your codes work while your installation is online at the same address. If you move to a new address, keep the old one redirecting, or printed codes stop working.
Compare this with a hosted service in Pepper or a hosted QR platform?. Then read the QR studio steps.