Toast Loyalty vs. an Earned-Milestone Program: Which Changes Repeat Visits?
Compare Toast Loyalty with earned milestones by rewards, reporting, price, staff work, and the numbers that show whether repeat visits changed.
Toast Loyalty is the better fit when you want a native Toast ledger with points-or-visits earning, purchase-linked progress, and Toast reporting. An earned-milestone program is the better restaurant loyalty program when you want guests to earn status after repeat behavior and you will judge the design by visit frequency, average order value, referrals, and contribution margin.
| Toast Loyalty | Earned-milestone strategy | |
|---|---|---|
| Model | Native Toast POS loyalty add-on with earning by dollars or visits | Reward strategy: a guest earns status at a restaurant-specific visit milestone, then receives later milestone rewards |
| Toast required? | Yes; Toast describes Loyalty as integrated with Toast POS | No. The strategy can use any implementation that reliably identifies the guest, counts qualifying visits, delivers rewards, and produces the required records |
| Enrollment | Register, digital receipt, online ordering, or sign-up link | Enrollment starts progress; it does not grant status or the milestone reward |
| How guests earn | You choose points by dollars or visits; points track automatically with purchases | Completed qualifying visits move the guest toward a milestone chosen from your retention history |
| Status | The current product page documents reward progress, not the separate earned-status sequence compared here | Status is earned only after the guest completes the stated visit milestone |
| Reward timing | Based on the points, reward, redemption, minimum-spend, and promotion settings you configure | A larger reward at the status milestone, followed by personalized rewards every three to five later visits |
| Staff work | Points track with purchases; confirm the exact redemption, void, refund, split-check, and offline steps in your Toast setup | At minimum: identify the guest, record the qualifying visit, verify status, and redeem the right reward. Require a demonstration of which steps the software completes |
| Reporting | Real-time loyalty performance plus guest, rewards-account, rewards-transaction, and marketing-driven-sales reports; the Demand Attribution Dashboard segments attributed sales by new, active, and reactivated guests | You must calculate the four outcomes below. Require the implementation to identify which source fields populate automatically |
| What sales reporting proves | Recorded activity and marketing-attributed gross sales, not profit or causal incrementality | The same limit applies: linked or observed sales are not automatically incremental or profitable |
| Data export | Rewards Accounts can export accounts and current point balances; Toast also documents a Rewards Cards export for moving to another provider | Require a sample export showing guest key, visit history, earned status, reward history, and consent fields before buying |
| Pricing | For new customers and single locations, core POS starts at $69 per month; Loyalty is under a custom-priced option, and no current standalone Loyalty amount is published | No public price applies to the strategy itself; budget for the software or staff work used to identify guests, count visits, and deliver rewards |
| Billing terms | The $69 core POS offer is a monthly software subscription; Loyalty-specific term and billing details are not public on the captured pages | The strategy has no billing term. The chosen software agreement must state the commitment, cancellation date, and export window |
| Separate costs | Hardware and implementation vary, additional devices cost extra, and your rewards still have a food or dollar cost | Software, setup, messages, rewards, training, staff time, and any integration work |
| Support | Toast Care is included with every software subscription and is available by phone or web message 24/7/365 | The strategy has no support plan. Require the chosen implementation to state support hours and a failed-redemption path |
| Best fit | You already use Toast and want the POS to run a familiar points-or-visits ledger | You want earned status and later rewards designed around a measurable change in repeat behavior |
These options are not mutually exclusive. Toast documents visit-based earning as well as dollar-based points, so it may be able to carry part of a milestone design; the deciding question is whether your exact status, reward, reporting, and export sequence works in the configuration you can buy.
What does Toast Loyalty currently include?
Toast Loyalty gives a Toast restaurant a purchase-linked rewards ledger with several ways to enroll and with earning rules based on dollars or visits. Guests can join at the register, from a digital receipt, while ordering online, or through a sign-up link; you choose the point value, minimum spend, and reward and redemption settings.
Toast Loyalty does well at keeping earning and redemption inside the POS your team already uses. Points track automatically with purchases, and earning and redemption work in-store and online; your team is not asked to maintain a separate visit spreadsheet just to update a balance.
The reporting is also broader than a points total. Toast documents guest, rewards-account, rewards-transaction, and marketing-driven-sales reports. Its Demand Attribution Dashboard breaks attributed sales into new, active, and reactivated guest segments. Those are useful platform-attributed gross sales, but they are not a food-cost calculation, profit statement, or controlled estimate of sales that would not have happened without the marketing. The broader POS marketing-revenue comparison explains how that reporting differs across systems.
The purchase question is less tidy. For new customers and single locations, Toast's official pricing page lists core POS starting at $69 per month, while guest marketing, loyalty, and gift cards sit under a custom-priced option. Hardware and implementation vary, extra devices cost more, and the public pages do not state Loyalty-specific billing terms. Ask for one written total that separates POS software, Loyalty, hardware, implementation, messages, payment-related charges, and the rewards you fund.
What changes when status has to be earned?
An earned-milestone program makes the achievement visible: enrollment starts the trip, but status arrives only after the guest completes the restaurant's qualifying visit target. The reward is no longer merely a balance waiting in an account; it marks progress toward becoming a recognized regular.
A restaurant owner described the difference in plain language:
“Instead of points, if you visit six times or 10 times, you get this instead. I personally believe that's a lot better. It's like a punch card, but digital.”
A restaurant owner comparing the two approaches
The number in that quote is an example, not a universal target. Build the sequence from your own records:
- Create a stable guest record. Decide which identifier connects enrollment, visits, checks, status, and rewards without exposing guest information in public reports.
- Find the visit milestone in your history. Look for the point after which guests have shown a high chance of returning, then use that as the proposed threshold.
- State what counts. Define a qualifying completed visit, minimum spend if any, location rules, refund treatment, and the date range. Display the target to the guest.
- Make enrollment the starting line. The guest begins at zero completed qualifying visits. Do not hand out member status or the milestone reward for signing up.
- Grant status after the threshold. When the qualifying visit posts correctly, mark the guest as having earned status and deliver the promised reward.
- Continue with later milestones. Personalized rewards every three to five later visits can introduce menu items the guest has not tried, instead of turning every visit into a discount event.
A shareable reward may create a referral opportunity, but sharing and measurement are different. To report a referral, your records need to connect the member, the referred guest, and that guest's first completed check. A group reward without that identity chain is a redeemed reward, not a measured referral.
Toast's captured public Loyalty pages document enrollment, earning, redemption, balances, and loyalty reporting, but they do not document an inviter-to-referred-guest workflow or a referral-sales report. If referral reporting matters, verify that separate identity link instead of inferring it from a shared reward.
The reward still has to work on the check
A memorable milestone can still lose money or create an operations problem if the promised item is costly, scarce, or easy to stack. Price the reward from food cost and likely redemption, then test the edge cases before showing it to guests.
One owner rejected a proposed reward because it targeted the dish he could least afford to discount:
“I'm giving away something I'm making the best money on right now, and I already run out.”
A restaurant owner reviewing a milestone reward
Write the reward as if a new employee and a determined guest will read it literally. Specify eligible items, party limit, one-per-person rules, minimum spend, alcohol exclusions if applicable, stacking, expiration, locations, dine-in or takeout treatment, and what happens after a void or refund. Then calculate the restaurant's cost of the promised reward, not its menu price.
The reward is ready only when the economics work at the highest reasonable redemption rate and the kitchen can fulfill it without displacing the items you most need to sell. If it fails either test, change the item, party rule, or threshold before changing the copy.
For a deeper reward design, see how a dinner for four can create a referral opportunity without pretending the invitation itself proves a referred sale.
Run four checks before calling either program better
The better program is the one that changes the intended behavior after reward and program costs, not the one with the most enrollments or points issued. Freeze the cohort, comparison period, and calculation before launch so a strong month cannot rewrite the test.
| Outcome | Calculation | What it can tell you |
|---|---|---|
| Visit frequency | Completed qualifying visits ÷ identified guests in the cohort, over equal pre- and post-enrollment periods | Whether the cohort visited more often in the observed data |
| Average order value | Net sales ÷ completed checks for the same cohort and periods | Whether average check size changed; it does not identify the cause |
| Referred guests | Referred guests with a verified first completed check ÷ members who made a trackable invitation | Whether the measured invitation path produced paying guests; omit the rate if you lack the inviter link |
| Earned status | Guests who reached the milestone ÷ guests enrolled long enough to have had a fair chance to reach it | Whether guests progressed from enrollment to the defined status |
Toast's marketing-driven-sales report belongs beside those outcomes, not on top of them. Label it Toast-attributed gross sales and keep the new, active, and reactivated segments Toast reports. Do not rename it incremental sales or profit.
Use contribution margin only after you have a credible incremental-sales estimate:
estimated incremental net sales × contribution-margin rate − reward food cost − software − messages − added labor − allocated implementation cost = estimated program contribution
If you only have before-and-after results, call the difference observed. Season, menu prices, hours, promotions, construction, and dozens of other changes may have moved sales at the same time. You can still use the observation to decide what to test next; you cannot use it to prove the loyalty design caused the full change.
Make both options pass the checkout test
Do not choose either option from a sales screen alone. Run the real enrollment-to-export sequence with your written earning and reward rules before a full rollout.
Use a test guest and record the expected result before each action:
- Enroll through every path you plan to offer and confirm that the same guest is not duplicated.
- Complete a qualifying in-store purchase and, if applicable, an online purchase; verify the correct points or visit progress.
- Redeem the reward through the actual register flow and confirm the receipt, balance, status, and report agree.
- Void one test check and refund another; compare the resulting progress and reward availability with your written policy.
- Split a test check and confirm whether the program counts the intended guest, visits, and spend once.
- Test the documented offline flow, reconnect, and verify that no earn or redemption event is missing or duplicated.
- Repeat the earn and redeem steps at another location if the program will span locations.
- Export a sample. Confirm that the file contains the fields you need to preserve balances, visits, status, rewards, and consent.
The test passes when guest-facing progress, staff actions, the completed check, the loyalty record, and the export all match your written rule. If any one disagrees, do not train the full team yet. Change the configuration or the rule, ask support to resolve the mismatch, and rerun the whole sequence rather than patching the report by hand.
Toast documents exports for rewards accounts, point balances, and a third-party move, but you should still inspect your own sample before relying on it for a milestone migration. If you replace an existing program, freeze new accruals and publish how current balances will be honored before moving guests; the loyalty-program sunset plan covers that separate transition.
Which option should you choose?
Choose Toast Loyalty when the job is to keep earning and redemption inside Toast, use points or visits, and work from Toast's loyalty and marketing reports. Its native purchase link, multiple enrollment paths, current-balance export, and included support are real advantages.
Choose the earned-milestone strategy when the job is to make status a visible achievement and test whether a restaurant-specific visit target changes frequency, average order value, referred purchases, and contribution. The strategy is not a software feature by itself, so reject any implementation that cannot pass the checkout and export tests.
The best restaurant loyalty programs and apps can help with the next software decision. Keep this one centered on the reward behavior and records you need.
Feast can implement the milestone strategy after the design is clear
Feast is one implementation path for an earned-milestone program, not evidence that every milestone design will outperform Toast. Its documented strategy makes status follow a restaurant-specific visit threshold and can continue with personalized rewards on later milestones.
Feast's current public pricing page documents POS-linked campaign sales and CSV exports of the guest list, campaign history, and attributed revenue. It does not document an inviter-to-referred-guest ledger, and those attributed sales are not profit or automatic proof of causal lift. If referral reporting matters, require a live demonstration of the exact member-to-referred-guest-to-check record before buying.
[Book a demo of Feast](/restaurant-marketers) to test the earned-status, checkout, reporting, and export sequence with your restaurant's data and rules.