Most advice about selling digital downloads assumes the buyer is alone with a screen. But many sellers also sell face to face: pattern designers at craft fairs, authors at conventions, indie makers at pop-up markets. The setting changes almost everything about delivery. There is no search traffic to optimise — there is a person in front of you, holding a phone, deciding in about twenty seconds.
In-person selling removes the hardest problem in digital sales — getting a stranger to trust an unknown checkout; you are right there. It adds physical problems instead: signage, queues, dead wifi, and a buyer who has to receive a file while standing at your table. This is a playbook for those problems, in the order you will meet them.
1. The QR code is your checkout — build it like one
The mechanism is simple: every product gets a public buy page, you generate a QR code that points at that page (any free QR generator will do — this is a code you make yourself, not a special feature of your delivery tool), and the buyer scans, pays on their own phone, and receives the file by email. No card reader, no till, no handling anyone else's payment details.
Simple does not mean casual. Four details decide whether it works on the day:
- One code per product, not one code for the whole shop. A buyer who scans a code and lands on a catalogue still has to find the item they were just holding a sample of. A code that lands directly on the product they want removes that step at the exact moment their patience is shortest.
- Print the short link under the code. Some phones, some lighting, and some cracked screens defeat QR scanning. A short, readable link typed by hand is the unglamorous backup that saves those sales.
- Test with the venue's lighting, not your kitchen's. Glossy lamination under hall spotlights can make a printed code unreadable. Matte print, generous size, and a test scan from a metre away are worth more than any other stall decoration.
- Put the code where the product is, not only at the till. Interest happens at the sample, the demo screen, or the printed example — not at the payment point. A code beside each displayed product lets a buyer act on the impulse where it occurs, including buyers who never queue.
2. Signage has to answer the question nobody asks out loud
The first question every in-person buyer has about a download is some version of: "But what do I actually get, and how?" Most will not ask it. They will smile, nod, and buy something physical from the next stall instead. Your signage has to answer it before the doubt forms.
One clear line per product does most of the work: what it is, what format, and how it arrives. "Knitting pattern — PDF, delivered to your email in about a minute" settles format, delivery channel, and timing in nine words. Add the file's requirements where they matter ("needs a printer", "works in GoodNotes and Notability", "Windows and Mac") and you have pre-answered the three support questions in-person sellers hear most.
Price signage matters differently in person too. An unpriced product requires a conversation to evaluate, and many visitors ration their conversations. Price everything visibly, and where you sell physical and digital versions, show the relationship honestly — the printed pattern for one price, the PDF for less — because that silent comparison is one of the strongest reasons a browser becomes a buyer.
3. No stock is the advantage — sell like it
A download stall never sells out, never needs a van, and never has a damaged-in-transit problem. Sellers sometimes apologise for having "nothing to hand over", which undersells the actual offer. What the buyer gets instead is worth stating: the file is on their phone before they reach the car park, it cannot be left on a train, and a lost copy can be re-sent in a way a lost physical purchase cannot.
This also changes what belongs on the table. Since the product needs no space, the table is entirely for demonstration: a printed sample of the finished object, a tablet looping the template in use, the ebook open at its best page. You are displaying outcomes, not stock — and one physical example of what the file produces outsells a grid of cover images, because it answers the quality question with evidence.
It also means your code can travel — a flyer in another seller's bag, a line in the event programme — anywhere a link can go, with no stock to move.
4. Plan for the wifi to fail, because eventually it will
Event wifi is a shared resource under maximum load, and mobile signal inside exhibition halls is famously unreliable. If your whole stall depends on a live connection — the buyer's phone loading your checkout — a bad network hour is a lost selling hour. Plan for it in layers:
- The buyer's connection matters more than yours. The scan, checkout, and payment all happen on the buyer's phone, on their data plan. That is mostly good news: hundreds of individual connections fail less completely than one venue network. Encourage the scan early rather than after a long chat, so any connection problem surfaces while the buyer is still with you.
- Take the email, offer the follow-up. When a payment genuinely cannot go through, the fallback is not a lost sale — it is an email address and an honest sentence: "Leave me your email and I will send you the buy link tonight, with the fair price held." Then actually send it that evening, while the event is still fresh. A simple list, kept on paper at the table, outperforms any app when the network is down.
- Everything you control should work offline. Your samples, demos, and price list should live on your devices, not in a cloud dashboard you need to log into. If your product demonstration needs the internet, download it the night before.
- Screenshot your own buy page. If a buyer cannot load it, showing them exactly what the page and delivery email look like tells them what to look for in their inbox later.
5. Delivery happens standing up — make the last metre easy
In online sales, a delivery email arriving five minutes later is unremarkable. At a stall, the buyer is watching for it, phone in hand, while a queue forms. Two friction points dominate.
The first is the email address itself. Checkout on a phone, typed one-handed in a noisy hall, produces typos — and a delivery email sent to a mistyped address looks exactly like a delivery that never happened. Say it out loud as part of the sale: "It will land in the email you just typed — worth a quick check of the spelling on the confirmation screen." That one sentence prevents the commonest in-person delivery failure.
The second is the spam folder. The delivery email is automated, from a sender the buyer has never received mail from, arriving while they are distracted. Tell buyers, before they walk away, to check spam or promotions if it is not there in a couple of minutes — and stay findable for the ones who come back. The sellers who do well at fairs treat the two minutes after payment as part of the product. Watching a buyer's face when the file opens on their phone is also the best product research you will ever get: you see exactly where they hesitate.
6. The event ends; the delivery support does not
Expect a small wave of messages in the forty-eight hours after an event: links not found, files downloaded to a phone and now wanted on a laptop, the buyer who paid and cannot remember what for. These are not failures — they are the in-person equivalent of normal download support, concentrated. Prepare for it the way you would for any launch: keep the event's dates in your support head, have your re-send process ready, and answer quickly while goodwill from meeting you is still warm.
Then learn from having watched people buy. Which sign got read? Which product did people scan and abandon, and at what step? Which question did you answer ten times that should have been on a sign? Write it down the same evening — a fair gives you observed, unfiltered buying behaviour that no analytics dashboard provides.
None of this requires a different product — just treating the stall as a delivery channel with its own rules: a code that lands on the right product, signage that answers the unasked question, a demonstration instead of stock, a paper fallback for the network, a spoken check of the email address, and support that expects the post-event wave. Do those six things and the strange part becomes how many physical sellers envy a stall that never sells out and packs into a single bag.
Closing note: the playbook above is tool-agnostic seller practice. The delivery behind my own buy pages is FileFreight: payments run through your own Stripe account, each buyer gets a personal expiring download link, PDFs are stamped per buyer on first download, a license key is issued per paid order, and a refund revokes access automatically (Pro $19/mo at 0% per sale; Free plan 5%). Honest caveats: it is new and small; it is not a merchant of record and does not handle sales tax or VAT; there is no importer yet, though the first 20 sellers get a free white-glove migration; it is not a Shopify app; and it is delivery-only, with no marketplace discovery. The QR codes themselves are ones you generate and print, pointing at your buy page — no special feature required.
Top comments (0)