Fiscal QR, four markets
Ukraine, Slovakia, Kazakhstan and Uzbekistan. The list is closed — there is no "and others".
Channel
A printed code needs no integration at all
The fastest working setup is a QR configured on a staff login and printed as many times as you like: table tents, counter stickers, washroom signs, staff badges. Put it where the experience happens.
The same link can also be requested through the API and printed by your till, placed in a delivery bag, or shown on a checkout screen. Where the code ends up is a placement, not a different product.
At a glance
- Permanent QR
- Configured on a staff login, printed once
- Receipt QR
- Your POS asks the API for the link
- Fiscal Receipt Scanning
- Ukraine, Slovakia, Kazakhstan, Uzbekistan
- Delivery Inserts
- The same link on a card in the bag
Updated
Four placements, two mechanics
The first two are the same permanent link printed in different places. The last two involve the receipt — one ours, one the tax authority's.
The permanent link
- Table tents and stickers
- A printer. Scanned without any purchase at all
- Staff badges
- One staff login per person if you want per-person ratings
- Washrooms and back rooms
- A sticker, often used to call cleaning rather than to rate
- Direct messages
- The same link sent by email, SMS or messenger
Receipts
- Receipt QR
- The POS calls the API, gets a link and prints it
- Delivery Inserts
- A printed card in the bag — no courier integration
- E-commerce final screen
- The link placed on your own checkout confirmation
- Fiscal Receipt Scanning
- The customer scans the tax QR; no integration needed
Detail that travels
The receipt route carries the purchase with it
A code that came from the receipt knows the till, the location, the shift, the time and what was bought. That is the difference between "someone was unhappy in March" and "table six, Tuesday evening, this dish".
It costs no scan quota
Opening the feedback page from a fiscal QR is a separate event from earning a stamp, and does not consume it.
One mechanic, many places
Receipt, insert, kiosk screen, checkout page: one API call, one link, one page.
A useful trick
How to measure table tents against the till
Analytics report the location and the staff login on every submission. They do not report which channel the customer used, and we do not describe channel analytics as something that is coming.
The workaround is free and takes a minute: give the table tents their own staff login. The channel then appears as a login in the reports, through exactly the same mechanism that gives a waiter their own ratings.
The same trick separates the drive-through from the counter, the reception desk from the treatment room, or one franchise partner's site from another's.
Common questions
What is 7Feedback?
7Feedback is a standalone customer feedback product. It collects a one-tap rating and an optional comment, photo or video where the visit ends — the payment terminal, the Self-Service Kiosk, a printed QR, the receipt or a chat-bot — and delivers every submission to the business with the location attached.
Do we need to integrate with our POS?
No. The terminal application installs next to your other Android apps and does not touch the payment flow, so it needs no payment-side certification. A printed QR or a fiscal receipt QR needs no integration at all. A deeper API integration exists for partners who want the question inside their own payment screens.
Does the customer have to install anything?
No. Scanning the code or tapping the terminal opens a web page. Rating takes one tap; a comment, a photo or a video is optional and never required, so the rating on its own is already a finished submission.
How often is the same customer asked?
Not more often than once every few days, set per location. The frequency cap is blind to the rating: it exists to protect a regular from fatigue, not to protect the business from criticism.
Next step
Print the code this afternoon
No integration, no deployment, no meeting with your POS vendor. A staff login and a printer is the whole list.