Redemption has to survive the drive-thru and the app
In fast casual, the counter is only one of three checkouts. Orders arrive at the register, at the drive-thru window, and inside your mobile and online ordering flow, and a gift card that only works cleanly at one of them is a program your guests stop trusting. Test all three before you choose a provider.
At the window, the redemption is a tender selection and a swipe or scan — the same keystrokes as a credit card, with the balance returned in real time so the cashier can call out the remainder while handing over the bag. There is no manual lookup, no second screen, and no pause while a separate gift card system responds. At the pace a drive-thru runs, a two-second delay per transaction is the difference between a program staff use and one they discourage.
On mobile and online orders, the card is applied at checkout, the balance draws before the order fires, and the remainder is charged to the card on file. The guest arrives, takes the bag off the shelf, and leaves — the redemption already happened. That is the flow most of your highest-frequency guests will use, and it is the one that most often breaks on providers that bolted gift cards onto in-store hardware.
Digital cards matter more here than in any other segment. A card delivered by text and saved to a phone is redeemable at a window where a guest is not going to dig a plastic card out of a wallet. When a card is lost, balance lookup in the Factor4 back office finds the account by card number, purchaser name, or phone number and applies the value without the plastic.
Frequency and a low average ticket change the math
A steakhouse sells a gift card to someone who visits twice a year. A fast casual brand sells one to someone who eats lunch with you nine times a month. That difference rewrites what the program is for.
Start with the ticket. If your average check is $11 and a guest loads $50, that card is roughly a month of lunches, not a single occasion. It gets spent quickly and then reloaded, which makes the program recurring prepaid revenue from people who were coming anyway — collected before you make the food. Denominations should follow that math: $10 and $25 cards move volume, $50 and $100 loads come from regulars and from employers buying in bulk, and any amount should be reloadable rather than fixed.
Reload is the mechanic that matters. In QSR, a guest with a loaded balance is a guest who has already made the decision — they are not comparing your menu board price against the place across the parking lot. Loaded guests visit more often, decide faster at the point of order, and spend above the balance more often than not, because a $9.75 bowl against a $25 card is a rounding decision, not a budget one.
Do not build the business case on breakage. In a high-frequency, low-ticket concept, cards get spent — often within weeks — so unredeemed value will be lower than in almost any other segment. That is the right outcome. Breakage is a one-time accounting gain from a guest who never came back; redemption is a guest walking in with a reason to choose you, spending above the balance, and reloading afterward.
Bulk and corporate sales sit on top of this. Office lunch programs, shift-meal cards, employee recognition, and local business bulk buys all convert well in fast casual precisely because the ticket is low enough that a $25 card is a complete, useful gift. Those batches are tracked separately from retail sales, so you can see what a given corporate account bought, what has been redeemed, and what remains outstanding.
Franchise ownership and multi-unit pooling
QSR and fast casual are the most franchise-dense segments in restaurants, and gift cards expose that ownership structure faster than anything else in the operation. A guest who buys a card at the unit near the office expects it to work at the unit near home. If it does not, the card produces a complaint at the window instead of a visit.
One account holds the value for the entire brand, so any card is good at any unit the moment it is presented — no manual lookup, no call between owners, and no "that one was sold at the other store" conversation while three cars wait behind.
Settlement is where separately owned units need clarity. When ownership is shared, centralized pooling is simplest: liability sits at the entity level and units are internal cost centers. When franchisees are separate owners, decentralized settlement applies — the selling unit holds the liability until another unit redeems the card, and the two settle on the reporting cycle the system agrees to. Because every transaction records both the selling and the redeeming location, the settlement report is produced from the data rather than negotiated. Franchisees do not have to trust each other's counts.
The same structure covers marketing programs the brand runs system-wide: promotional cards, recovery cards handed out for a bad order, and grand-opening loads can be issued centrally and redeemed anywhere, with reporting that shows which units absorbed them.
If not every unit runs Toast
Growing QSR systems are rarely uniform. A franchisee signed with a different POS, an acquired set of units came with their own stack, or a high-volume drive-thru location runs a system built around order timing. Toast's native gift cards only work inside Toast, so in a mixed system they create exactly the outcome you were trying to avoid: a card that works at some of your units and not others. That is the problem a true multi-location gift card program solves.
Wondering what any of this costs before you talk to anyone? We wrote the invoice side out in full: what a gift card program actually costs on Toast.
Factor4 is POS-agnostic and integrates across a wide range of point-of-sale platforms, so the program is defined by your brand rather than by your terminals. One card design, one balance pool, one report. A card sold at a Toast unit redeems at a unit running something else, at the same balance, in real time.
That matters more going forward than today. Adding units, converting a franchisee's POS, or acquiring a small system does not fragment the program, strand outstanding balances, or force a reprint. For a brand that expects to keep opening, that stability is the whole argument.
Setting it up through Toast
Turning the program on is a paperwork exercise, not a project. Your units keep operating normally throughout, and nothing changes about how orders are rung.
What Toast requires is Partner Integrations access on the account. If you subscribe to the Restaurant Management Essentials or Pro suite, you already have it; below those tiers it gets added before anything can be enabled. Your Toast Restaurant GUID — the identifier attached to each unit or to the group — is the only other thing we ask you for. Factor4 works the configuration through Toast Integrations Support and tells you the date it goes live on your terminals. You are never the middleman between two vendors.
Plan around two rules. Toast allows a single gift card provider per restaurant group, so every unit moves together on one date — the same date outstanding balances transfer from your old provider. And gift card numbers move to the Factor4 back office afterward: card history, liability, corporate batch performance, and cross-unit redemption all report there, while the tender itself still lands on your Toast checks and daily sales like any other payment.
Questions, answered