In brief
To print Wi-Fi coupons on receipts, export the coupon pool as CSV and load it into the POS receipt template. One code per receipt, same-day validity, and what to do when a code is reused.
In cafés and restaurants the most elegant way to hand out Wi-Fi is to print the code on the receipt. The guest orders, the bottom of the receipt reads "Your Wi-Fi code: 7K3P-2M", and they connect without asking. Staff do not look up codes, no password hangs on the wall, and the shop next door does not use your line. This post walks through the setup step by step, lists the operating rules and shows what to do when you notice a code being reused.
Why printing on the receipt works
- Only guests who order get internet. The neighbour connecting from outside, the passer-by, and devices that visited once and never left are filtered out.
- The verification detail enters the record. For a guest signing in with a coupon, the record holds the coupon code, device MAC address, internal IP and session times. It is also a practical route for foreign guests who cannot receive SMS.
- No load on staff. The POS prints the code; there is nothing for the waiter to memorise, say or write.
You do not have to remove SMS sign-in. The SMS code stays in front on the portal; the coupon is the second route for guests holding a receipt. Both work at the same time.
Setup step by step
1. Pick the plan
Our Standard template suggestion for a café: 10/5 Mbps, 2-hour session, 15 minutes idle, 2 devices, 1 GB/day. Two hours per order is plenty for a coffee. The values are lab suggestions; adjust to your load.
2. Generate the coupon pool
Generate coupons in bulk from the panel: single-use, validity same day (or until the end of the day the receipt is printed), batch named with date and till: "Till 1, 12 October". Add a small margin over your daily order count; use daily or weekly batches instead of a single batch of a thousand.
3. Export as CSV
Download the generated pool as a CSV file. The file holds the code and the validity details. This is the file you load into the POS; there is no need to move codes from the box to the POS any other way.
4. Load it into the POS receipt template
Most POS software can add a variable field to the receipt footer and pull values in order from a list. Load the CSV into that list and add three lines to the receipt template:
Free Wi-Fi: connect to the "Cafe-Guest" network
Enter this code on the page that opens: {WIFI_CODE}
Valid today · 2 hours · 2 devices
The field name depends on the POS; what matters is that each receipt pulls a fresh code from the list. If your POS cannot do this, small printed cards are still a valid option: print them from the box and staple one to the receipt.
5. Test it
Print three receipts and sign in with all three from different phones. Check that the portal accepts the code, that a second device gets in, and that a third does not. In the reports, check coupon sign-ins in the sign-in method breakdown.
Operating rules
| Rule | Why |
|---|---|
| One code per receipt | The same code going to two tables muddies the "who" question |
| Same-day validity | The receipt goes in the bin; the code must not work tomorrow |
| Per bill, not per table | If a table of four does not want four receipts, the plan is 2 devices and 2 hours; one code covers one guest, the others sign in by SMS |
| Refill before the pool runs out | When the POS list ends, the receipt shows an empty field; put it on the weekly checklist |
| Cancelled receipts | If a receipt with a printed code is cancelled, the code does not count as used, but it is not worth checking; same-day validity solves it on its own |
| Cashier changes | Because the batch is named by till and date, "which till did this code come from" is already answered |
When a code is reused
A single-use coupon opens for the first guest up to the plan's device count and closes to everyone else. You may still see these situations:
Same code, same day, a third device. The guest shared the code with a friend; the device limit is already in force and the third device does not get in. Nothing to do; the plan did its job.
Same code, different day. This should not happen; validity should have been same day. Check the batch setting. If the validity was entered wrongly, cancel the batch from the panel and generate a new one.
Unused codes running out early. The CSV file or the printed list may have leaked. Cancel the batch, generate a new one, and keep the CSV where only the person who set up the POS can reach it. The audit trail shows who generated the batch; the file's onward journey is yours to track.
Coupon sign-ins outside opening hours. Someone outside can see the network and holds a valid code. Shorten the validity and consider time scheduling for the guest SSID on the AP side.
Suggestions for the receipt text
- Put the network name and the code in the same place so the guest does not look in two spots.
- Say "code", not "password"; guests take it for the network password and go into their Wi-Fi settings.
- Print the validity and the device count; it heads off complaints.
- You can add a short line at the bottom: "Terms of use and privacy notice on the sign-in page." That way the texts are not squeezed onto the receipt but read on the portal.
Example scenario
A neighbourhood coffee shop with two tills. Every morning a batch of 150 coupons is generated, the CSV is loaded into both POS units, and the batch is named by till and date. The receipt carries three lines of Wi-Fi information. Some guests sign in by SMS, some with the code on the receipt; the reports show the two separately. One day the report showed coupon sign-ins continuing after closing; the owner changed validity to "3 hours from printing" and began switching the guest SSID off at 23:00 on the AP. The problem was gone the next day.
Plan suggestions for cafés and restaurants are on the Industries page; for coupon generation and report screens see Box + Software. If you want help with the POS setup, get in touch.