Reload, not gifting
In most restaurants a card is bought by one person, given to another, and redeemed once. In coffee the buyer and the user are the same person, and the card is drawn down over weeks of daily visits. Every assumption behind a traditional gift card program has to be re-set for that.
Breakage — value loaded and never spent — is close to zero. Redemption frequency is high, and the average redemption is small. Float is short, because a $50 load is gone in ten visits rather than sitting on your balance sheet for a year.
That is a different revenue model, not a worse one. The value of a coffee card is not the money customers forget to spend, it is switching cost. A regular carrying a live balance with your name on it walks past the shop across the street. They visit more often, they are less price-sensitive on a single drink because it is already paid for, and each reload is a fresh commitment. You collect cash before the coffee is poured, and you collect it repeatedly from the same person rather than once a December.
Judge a coffee program on reload rate, visit frequency, and share of tickets paid by stored value. Those numbers tell you whether it is working. Breakage does not.
Seconds at the counter during the morning rush
At 8am there are twelve people in line and one espresso machine. Every second added to a transaction is multiplied by the queue behind it, and a slow payment step costs walkouts from exactly the customers who were going to come back tomorrow.
Redemption has to be a tender, not a process. The card is scanned or tapped at the terminal the barista is already using, the balance draws in real time, the remainder — if any — is charged to another payment method on the same check, and the drawer closes. No separate device, no second screen, no app the customer has to unlock and load.
Balance lookup is the other pressure point. A customer who does not know whether they have enough left should get an answer instantly, either from the receipt line printed on their last visit, from their phone before they reach the counter, or from the terminal in a single step. What kills a queue is a barista phoning a support line or logging into a browser to check $3.40.
Test this before you sign with any provider. Stand at the register during a rush and time the redemption. If it is not as fast as a tapped credit card, your baristas will stop offering it, and a program your staff avoid is a program that does not exist.
Fee structure on a $6 ticket
A per-transaction fee that is invisible on an $80 dinner check is material on a $6 latte bought four times a week. Coffee is the one segment where you should model the fee structure arithmetically before committing, because the ticket is small and the transaction count is enormous.
The comparison that matters is a percentage fee against a flat per-transaction fee. A percentage scales with the ticket, so it stays proportional whether the sale is $6 or $60. A flat fee does not: on a $6 ticket, a flat charge is many times the effective rate it would be on a full-service check. Run both against your own numbers — monthly stored-value transactions multiplied by your average ticket — and compare the total cost, not the headline rate.
Worked example, using your real volume: [X] stored-value transactions per month at a [$6] average ticket is [X × $6] in monthly redeemed value. Under a percentage fee the cost is that value times the rate. Under a flat per-transaction fee the cost is [X] times the fee, regardless of ticket size. At low tickets and high counts, the flat structure is usually the more expensive one.
[FILL IN REAL FEE STRUCTURE BEFORE PUBLISHING] — replace the bracketed figures above with the current Factor4 rate card and a completed calculation before this page goes live.
Auto top-up and keeping regulars loaded
The single biggest failure mode in a coffee card program is a customer discovering an empty balance mid-order. They pay another way, the card goes back in the drawer at home, and the habit ends. Everything about reload design exists to prevent that moment.
Reloading at the register is one transaction: scan the card, enter the amount, take payment, and the balance is live before the drink is made. Reloading from a phone removes the counter entirely — the customer checks their balance on the way in and tops up before they are in line.
A white-label branded mobile app is where this gets strongest. Carrying your name and artwork, it holds the card, shows the current balance, takes a reload, and pays at the counter from the same screen. The customer stops thinking about whether the card has money on it, which is the entire point.
There is a direct economic argument too: app-based payments carry lower transaction fees than card-present payments. In a business defined by a high count of small tickets, moving even part of your regulars' daily volume into the app changes your cost per transaction on precisely the transactions you have the most of.
One balance across drinks, beans and merch
Coffee shops are half café and half retail store. A regular who buys a latte five mornings a week also buys a twelve-ounce bag on Saturday, a grinder in November, and a branded tumbler as a gift. Stored value should cover all of it.
Because the balance is applied as a tender against the check in Toast, it pays for whatever is rung on that check: drinks, pastries, retail bags, brewing equipment, cups, and apparel. There is no separate retail card, no rule about what stored value can be spent on, and no need to split a ticket because part of it is merchandise.
This matters more than it sounds. Retail is the highest-margin thing most cafés sell and the hardest to prompt. A customer with $40 sitting on a card is measurably more likely to add a bag of beans, because the money is already spent from their point of view. A loaded card is a standing invitation to increase the basket.
Reporting reflects the same reality: you can see stored value redeemed against retail versus café tickets and use it to decide what to stock and when to push a reload promotion.
Multiple cafés, one balance
Small local coffee chains live on customers who use more than one of your shops — the one near the office on weekdays, the one near home on Saturday. If a balance is trapped at the location where it was loaded, your best customers hit the wall first.
Balances sit in a single pool at the program level. A card loaded at one café is spent at any other in real time, with no transfer, no lookup, and nothing for the barista to verify. The customer never has to know which shop they loaded it at.
Attribution stays intact underneath. Every load and every redemption is recorded against the location where it happened, so you can see which café is generating loads, which is absorbing redemptions, and how balances move between them — the numbers you need for internal accounting between shops and for deciding where a new location makes sense.
It also removes friction from growth. Opening a fourth café adds it to the existing program on day one, with the same cards, the same balances, and no reprint.
If not every location runs Toast
Coffee groups rarely end up uniform. The roastery has a wholesale counter on a system that was chosen for invoicing rather than for espresso. A second café came with an acquisition and kept the POS it was already trained on. The airport or lobby kiosk runs whatever the landlord specified. Toast's native gift cards only work inside Toast, so in a mixed setup a card loaded at your main café is dead weight at the counter two miles away.
Factor4 is POS-agnostic and integrates across a wide range of point-of-sale platforms, so the program follows your brand instead of your terminals. One card design, one balance pool, one report. A card reloaded at the Toast café is spent at the roastery counter or the kiosk, at the same balance, in real time — which matters most for the daily regular who does not know or care which of your counters runs which system.
It also keeps future decisions cheap. Buying another café, opening a kiosk, or moving one site onto a different POS does not fragment the program, strand outstanding balances, or force you to reissue cards to customers who are carrying live value every morning.
Setting it up through Toast
Nothing about the counter workflow changes when the program goes live, which is the point. The card becomes one more tender button on the screen your baristas already touch two hundred times a morning.
Three things get the integration enabled. Toast Partner Integrations access has to be on the account — it ships with the Restaurant Management Essentials and Pro suites, and gets added first on lower tiers. Your Toast Restaurant GUID identifies the café or the group. Factor4 then runs the configuration with Toast Integrations Support and confirms the go-live date with you.
Time the cutover deliberately. Toast allows one gift card provider per restaurant group, so every café switches on the same date and outstanding balances migrate that day — in a business where hundreds of regulars are carrying live balances, pick a slow morning and brief your staff in advance.
Afterward, the numbers you care about — reload rate, redemption frequency, outstanding liability, per-card history, balance movement between cafés — come from the Factor4 back office rather than Toast's native gift card reports. The transactions themselves still land on your Toast checks and daily sales as a tender.
Questions, answered