Trade Show QR Codes: One Per Rep, Updated From One Place
Print a QR code for each rep that points at a page you can still edit after the print run, rather than at a URL that has to be final on press day. Give every rep their own fixed address so a scan reaches the person the visitor actually met, and keep the offer, demo booking link and follow-up content on that page so you can change them the morning the doors open. With Biotree for Organizations, one Partner API call issues a managed page per rep, and any shared button on those pages points at a redirect the company repoints once for everyone.
The show is in three weeks. The printer wants final artwork on Friday: badges, lanyard cards, the banner behind stand 412, and two thousand leave-behind cards. Someone asks the obvious question. What does the QR code go to?
That is usually where it stalls, because nothing downstream is settled. The launch offer is still with legal. The demo booking link is moving when the new scheduler goes live. Nobody has decided whether the leave-behind asset is the case study or the pricing one-pager. Print deadlines land weeks before an event, but the content those codes point at keeps moving right up to the morning of the show, and then changes again the moment the show ends and you switch from "come see us at stand 412" to "thanks for stopping by".
So the requirement is not a cleverer QR code. It is a destination you can repoint after the ink is dry, and one that knows which rep the visitor was standing in front of.
Why print deadlines break QR codes
A QR code is just an encoded URL with error correction wrapped around it. Once it is printed, it is frozen. Everything flexible has to live on the other side of that URL.
Two failure modes show up at almost every event. The first is the deep link: someone encodes yourcompany.com/summer-launch-2026/demo because that was the plan in March, the campaign gets renamed in April, and by the time the show opens half the printed material points at a 404. The second is the over-cautious opposite: someone encodes the homepage, so a visitor who just had a ten-minute conversation about warehouse integrations lands on a corporate carousel with no mention of the event, no mention of the offer and no mention of the person they were talking to.
There is a third problem that only appears later. Banners and pull-up stands get reused for two or three shows. Badge inserts get reprinted, lanyards do not. Anything you print has a longer life than the campaign it was printed for, so the destination needs to keep being sensible for a year, not a weekend.
What a trade show QR code should point at
The choice is really about two properties: can you change what sits behind it after printing, and does it tell you (and the visitor) which rep the scan came from.
| QR destination | Changeable after printing? | Identifies the rep? | Trade-off |
|---|---|---|---|
| Company homepage | Yes, but only by changing the homepage | No | Safe and useless. The visitor lands somewhere generic and has to search for the thing they were just shown. |
| Campaign landing page URL | Only if you keep the URL alive forever or add redirects later | No | Ties printed material to a campaign name that marketing will rename. |
| Rep's LinkedIn profile | Yes, but the rep controls it, not you | Yes | Off-brand, no event offer, and it walks out the door with the rep. |
| A managed page per rep at a fixed handle | Yes, edited centrally at any time | Yes | Someone has to provision and maintain the pages. Worth it above roughly five reps. |
The last row is the one that survives contact with a print schedule. The address is stable, so the artwork can be finalised in week one, and the contents are editable, so the offer can be finalised in week three.
One page per rep, not one page for the booth
This is the part event teams underrate. A visitor talks to Dana for eight minutes, takes her card, and scans it on the train home. If the code goes to a booth-wide page, she is anonymous by then. If it goes to her own page, they see her photo, her name, her role, a way to reach her directly, and the event offer sitting on top.
The mechanics are simple with a managed model. Each rep gets their own address, and the page carries their photo, a short bio, their contact links and the shared event buttons. Because the organization provisions the page rather than the rep, the layout, background and style are the same for all of them, which is what stops the usual drift where every rep's links end up looking different. Setting one up is the same work as building branded profile pages for every sales rep for the rest of the year, with an event section added on top.
Optionally, a page can carry a verified member badge showing the person's role and location and linking to their official profile on your own site. It also emits verified Person and ProfilePage structured data marking them as working for your organization. That matters more than it sounds at an event: a stranger who met someone for eight minutes and is about to send purchasing details wants a signal that the person is who they said they were.
Repointing every rep's event link at once
Per-rep pages create an obvious risk. If there are fourteen reps and the offer changes on the morning of the show, are you editing fourteen pages from a hotel lobby?
No, because shared buttons should not hold real URLs. They hold a redirect address, such as biotree.bio/go/{org}/event-offer, and the organization repoints that one destination through the API. Every member page follows instantly. Nothing on the page changes, nothing gets re-published, and nobody edits anything individually. That is the same indirection used to update one link across every employee page and to send every rep the same links and update them once.
In practice an event uses two or three of these slots:
- Event offer — points at a "see you at stand 412" holding page before the show, the live offer during it, and the post-show version afterwards.
- Book a demo — points at whatever scheduler you are actually using this quarter, including the one you migrate to two days before the doors open.
- Leave-behind asset — the case study, the pricing sheet, the recorded session. Decide late, change often.
The rhythm is: repoint to the live offer the morning the show opens, repoint again on the Friday for follow-up week. Two API calls, fourteen reps, no reprints. ProLend, a private lending business in South Africa, runs the same pattern outside events entirely, issuing a branded page to every independent consultant so head office can change a shared destination without chasing anyone.
What per-rep scans actually tell you
Be realistic here. Giving each rep their own address makes attribution clearer, not automatic. Because the addresses differ, you can see which rep's page got traffic and which links on it were clicked, so "Dana's page got 60 scans and Tom's got 9" is a real, useful signal about who was working the floor.
What you do not get from the page itself is a lead record. Biotree gives you basic page views and clicks. It is not a CRM, it does not run lead capture forms, and it does not build a pipeline report. If you need scan-to-opportunity attribution, put per-rep UTM parameters on the destinations the buttons point at, so your own analytics and CRM record which rep's page sent the booking. The page identifies the rep; your existing stack does the counting.
When a rep leaves before the next show
Printed material outlives employment. Two thousand cards with Dana's code went out in March, and Dana resigns in June. A scan in September should not land on a live company-branded page with a departed person's face and a phone number nobody answers.
Because the organization owns the page, revoking it takes it down. The page is unpublished, but the content is preserved, so if the person returns or the page is reassigned, re-granting restores it rather than making you rebuild it. The rep's personal Biotree page, if they have one, is a completely separate asset that is never converted, absorbed or taken down by the company. Company pages are provisioned on the work email, and the organization can only touch pages it created. That is the whole argument for company-owned rather than employee-owned bio pages, and it is worth reading what actually happens to a rep's company page when they leave before the next print run.
What this does not do
Being straight about the boundary saves you a procurement conversation later.
- Biotree is not a QR code generator. You get a stable URL. Generate the code with any generator, or hand the URL to your printer and let them place it at the size and contrast the substrate needs.
- It is not lead retrieval. The badge scanners that read visitor badges at your stand are rented from the show organizer and feed their own export. That is a separate system.
- It is not NFC. Biotree does not sell physical NFC or plastic smart cards, and it does not do vCard contact-file exchange or tap-to-save-my-contact. If your reps want a card someone taps to drop a contact into their phone, that is a different kind of product, and plenty of teams run both: the tap saves the contact, and the card's printed code points at the page you can still change. How QR code business cards actually work for teams covers where that line sits.
A three-week timeline before the doors open
The point of this model is that only the first step has a hard deadline.
- Week 3 (artwork week). Provision a page per attending rep. One API call each creates the account, the page, the handle, photo, bio, links and style. Add the shared event buttons pointing at redirect slugs that currently go to a simple holding page. Send the printer the per-rep URLs. Artwork is now final.
- Week 2. Reps check their own page on a phone: name spelled right, photo current, direct contact links working. Fix anything centrally.
- Week 1. Finalise the offer and the asset at your leisure. Nothing printed depends on it.
- Show day. Repoint the event slots to the live offer and the booking link. Every rep's badge and card now leads there.
- The Friday after. Repoint the same slots to the follow-up content. The two thousand cards in strangers' bags keep working, and now say the right thing.
If you are running one stand with three people, honestly, a single well-made event page is enough and you should not build machinery for this. Above roughly five reps, or across more than one show a year, the per-rep model pays for itself the first time an offer changes. The wider pattern is covered in our guide to link in bio for teams and organizations.
If your next show is already on the calendar, see how Biotree for Organizations issues a page per rep and repoints every one of their event links from a single call.
Related guides
Frequently Asked Questions
Can you change what a printed QR code points to after it's printed?
Not the code itself, but you can change what the visitor sees. A printed QR code encodes a fixed URL permanently, so the trick is to point it at a page or redirect address you control and can edit afterwards. If the QR goes to a page you can edit centrally, you can change the offer, the booking link and the follow-up content at any time without reprinting anything.
Should each sales rep have their own QR code at a trade show?
Yes, above about five reps. A per-rep code means the person who scans a badge or card later lands on the page of the rep they actually spoke to, with that rep's photo, role and direct contact details, instead of a generic company page. It also makes it clear which rep's material generated the traffic, since each page has its own address.
How do you update every rep's event link at once during a show?
Point every rep's shared event button at a single redirect address rather than at the real URL, then repoint that one destination centrally. With Biotree for Organizations the button points at an address like biotree.bio/go/{org}/event-offer, and one API call changes where it lands for every member page instantly, with no per-page edits.
Does Biotree generate QR codes?
No. Biotree gives you a stable page address for each person; you generate the QR code with any QR generator or hand the URL to your printer. The value is on the destination side, since the page is the part you can update after printing and take down later.
What happens to a rep's trade show page if they leave the company?
If the organization provisioned the page, it can revoke it, which unpublishes the page so old printed cards no longer lead to a live page for a departed employee. The content is preserved, so re-granting restores the page if the role is refilled or the person returns. Their personal link-in-bio page, if they have one, is a separate asset the company never touches.
Can a trade show QR code save my contact details to someone's phone?
Only if you use a product that supports vCard or NFC contact exchange, which is a different category. Biotree pages are web destinations, not contact files, so they don't do tap-to-save-my-contact. Many teams use both: an NFC card for saving contacts and a printed QR pointing at a managed page they can update centrally.