The technical part of a QR print counter takes about ten minutes. The part that determines whether customers use it takes about a month, and almost all of the guidance you will find focuses on the ten minutes. This guide covers both, in the order that actually works: hardware and code placement first, then the wording, then staff habits, then the transition period when most counters give up.
What the customer needs, and what they do not
The reason this works at a walk-in counter is that the customer requirement is almost nothing. They need a phone with a camera, which almost everyone has. That is the entire list.
- They do NOT need to install an app. A phone camera opening a browser is the whole flow.
- They do NOT need to create an account or verify a phone number.
- They do NOT need to save your number, and they do not hand over their contact details.
- They do NOT need to understand anything technical.
- If your customer flow requires any of the above, you have built something harder to adopt than it needs to be.
The test for a good counter flow is this: a customer who has never seen a QR code should complete an upload without asking a single question. If they have to ask, the wording on your sign is wrong.
Step 1: get the codes printed
Start here, because it is the part you control completely and it takes the longest in wall-clock time.
- Print at least three codes. One for the door, one for the counter itself, one for the rate board. Redundancy matters more than you think, because a code on a door is seen by people who have not yet decided to enter.
- Size: at least 3 cm square. 5 cm is better and costs nothing extra on a sheet of A4.
- Background: light and matte. White paper works. Coloured paper works if it is pale. Glossy, dark or patterned backgrounds cause scan failures.
- Add the instruction text underneath. "Scan and upload your file" in plain words, large enough to read from a metre away.
- Laminate them if the counter gets touched. A scuffed or torn code scans unreliably and you will not notice until a customer complains.
- Put one at counter height and one at eye height. A code on a low counter is invisible to someone standing.
Step 2: write the sign, carefully
The wording does more work than the code. Most counters put a bare QR code on the wall and then wonder why adoption is low. The reason is that a bare code communicates nothing about what happens next.
| Instead of | Write |
|---|
| A bare QR code | "Scan to upload your file — no need to save our number" |
| "QR CODE" | "Send us your file while you wait" |
| "Order here" | "Photocopy, print, bind — upload now, collect when done" |
| "Digital ordering system" | "Scan, upload, sit down. We will call your number" |
| "Skip the queue" | "No waiting in line to send a file" |
Every replacement above removes a piece of jargon and adds a benefit. Customers do not scan codes because they are digital. They scan because it is faster than standing in a line, and your sign should say that.
Step 3: decide what the customer sees before they arrive
The biggest time saving is not the upload — it is that the customer is not standing at your counter while a file travels. To get that benefit, the upload has to happen away from the machine, which means the code has to be somewhere they can use it before they reach you.
- Door or window code: customer uploads while walking in, waits to be called, and is not queueing at the counter to hand over a file.
- Waiting-area code: for customers who are already seated, which is common in a busy market-area shop.
- Counter code: as a fallback, and for the customer who only notices the option once they are at the counter.
Counters that put a code on the door and a code at the counter consistently see higher uptake than counters with a single code at the counter. The door code removes the queue, not just the file transfer.
Step 4: train your staff
Staff behaviour determines whether customers keep using it after the first week. Two habits matter.
- One line, every time. When a customer reaches the counter with a file on their phone, the entire script is: "You can scan this and upload it now, it is faster." Not an explanation, not a comparison with WhatsApp. One sentence.
- Do not make the customer feel they did the wrong thing. Nobody is wrong for using WhatsApp. The goal is to make scanning easier, not to make chat feel like a mistake.
- Do not print from WhatsApp while the customer watches if you can help it. Print it, quietly, without commentary, and let them notice next time. Criticism of a tool is rarely persuasive.
There is a version of this that fails badly: staff who tell customers how much more efficient the new system is. Customers did not ask to be sold to, and being lectured about a process while handing over a file is an experience they will avoid. The best staff behaviour is unremarkable — mention it once, then move on.
Step 5: set up the counter so the queue actually works
Capturing a file is not the same as managing a queue. A few things make the difference on a busy day.
- Order the queue by arrival, and let the customer see their position. Uncertainty about where you are in the line is the most common complaint about any queue.
- Separate colour work from black-and-white work. A colour job in the middle of a stack of photocopies blocks everything behind it.
- Keep small, urgent, waiting-on-the-customer jobs visible and separate. Waiting-on-the-customer is not the same as first-in-first-out.
- Let staff mark a job as reprintable rather than starting a new one. A reprint is a second copy of a job you already have, and starting a new one loses the specification.
- Do not auto-send everything. Auto-send is good for bulk monochrome and dangerous for colour, because a jam then blocks the next job too.
Step 6: the first thirty days
| Period | What to expect | What to do |
|---|
| Week 1 | Almost everyone still uses WhatsApp | Nothing. Just make sure the code is visible and staff mention it once |
| Week 2 | A few curious customers scan | Print whatever arrives, by either channel, without comment |
| Week 3 | Staff start offering it when it is genuinely quicker | This is the real turning point. Do not mandate it |
| Week 4 | A meaningful share of jobs arrive via QR | Start routing by job type and give customers a rough wait time |
| Week 5–8 | The queue becomes the normal way of working | Fix the two most common failure points you have actually observed |
Do not announce a cutover date. A sign saying WhatsApp is no longer accepted turns a convenience into a policy dispute and loses you exactly the loyal customers you most want. Make the new path easier and let it win.
What to measure
Keep it to three numbers, checked weekly. Anything more and you will stop looking at them.
- Percentage of jobs arriving by QR versus the old channel. Most counters pass 50% somewhere in month two.
- Average time from upload to print. This should fall as the queue gets used properly.
- Reprint rate. If it is not falling, something about specifications is not being captured correctly.
Where to go next
For the mechanics behind what the customer sees, our QR code printing guide explains the whole path from scan to print, including the failure points. For the channel you are moving away from, our guide to ending the WhatsApp queue is blunt about why it breaks down. And for the workflow once files are arriving properly, our print shop queue management guide covers ordering, prioritisation and the daily routine.