Offer a free item only after deciding what happens when it sells out. Name the eligible item, set a clear availability limit, choose an alternative you are willing to honor, and assign someone to update staff when stock changes. Then test whether a guest can still try to redeem the original reward after the last item is gone.
The earning threshold and the stock decision are separate. A guest may have earned a reward without the advertised item being available at that moment. Your process needs to handle both facts fairly, whether the guest orders at the counter or starts an online order.
Decide what the free item promises
Start with the service conditions that can change availability: a short production run, a seasonal ingredient, a busy delivery period, or an item that is only prepared at certain times. An item that rarely sells out may suit a simple free-item offer. A limited batch needs a more specific plan.
Give one role ownership of the offer and another ownership of each shift. The manager who sets up the reward decides the eligible item, terms, and approved alternative. The shift lead checks availability, tells the team when it changes, and handles exceptions. In a small restaurant, one person may hold both roles; the handoff still needs to be explicit.
Decide what the guest sees before earning and redeeming. “Free cookie, while supplies last” sets a limit, but it does not explain what happens next. If you intend to offer another item or let the guest save the reward, say so in the terms wherever the offer appears. Only promise an alternative if staff can actually provide it under the stated conditions.
Also decide whether an unavailable item affects an order already submitted. Ask your software provider how staff can identify and resolve that situation. A guest who discovers the shortage after placing an order needs a different response from someone who sees an item marked unavailable before checkout.
Build a stock-to-reward worksheet
Use one row for each condition that changes the guest’s choice. The following example is hypothetical. A café offers one free chocolate chip cookie as a loyalty reward. Its manager approves a brownie bite as the alternative when cookies are sold out, provided brownie bites are available. If neither is available, the guest may keep the reward for a later visit.
| Stock status | Guest-facing terms | Alternative and decision | Owner |
|---|---|---|---|
| Cookies available | One free chocolate chip cookie; availability may change. | Offer the cookie. No substitution needed. | Shift lead confirms stock; cashier handles redemption. |
| Cookies sold out; brownie bites available | If cookies sell out, choose a brownie bite or keep the reward for later. | Offer the bite; do not substitute without the guest’s choice. | Shift lead announces the change; cashier explains the choice. |
| Both items sold out | If neither item is available, keep the reward for a later visit. | Do not promise a third item unless a manager approves it. | Shift lead directs staff and records the exception. |
| Stock status uncertain | Availability is confirmed before redemption. | Check the physical supply before offering either item. | Cashier checks with the shift lead. |
The table connects the actual stock condition to a guest-facing promise and a staff action. It is not enough to print these terms if the ordering screen still presents an unavailable cookie as redeemable. The manager must decide how the message and the selection will be updated in each ordering channel.
Comparable does not have to mean identical. A guest may value the brownie bite differently from the cookie because of dietary needs, preference, or portion size. Give the guest the option to keep the reward rather than treating the alternative as an automatic replacement. Before launch, check that the terms, button labels, and staff script all describe the same choices.
For a sense check on reward economics beyond availability, use the loyalty reward cost guide. The cost of an alternative matters, but so does whether the guest can actually choose and redeem it.
Choose an approach your team can operate
There are several ways to manage the same promise. Compare them using your busiest shift, not just a quiet setup session.
- Staff-managed availability: The shift lead tells staff when the reward item sells out, and staff explain the alternative. This can work for counter-only redemption with a small team. It adds communication work and depends on every cashier receiving the update.
- Vendor-managed availability: Ask whether the reward can be made unavailable in each relevant channel when the item is sold out, and who must trigger the change. A single update may reduce staff work, but only if the behavior covers the places guests can redeem.
- Limited-time or limited-batch offer: Set terms around a defined service period or quantity. Staff still need a way to stop or resolve redemption when the supply runs out earlier than expected.
- Alternative or later redemption: Offer an approved substitute, or let the guest keep the reward. Ask whether the system can support the guest’s choice without consuming the original reward incorrectly.
For the hypothetical café, staff-managed availability is a reasonable starting choice if rewards are redeemed only at the counter and the shift lead can reliably brief both cashiers. If online redemption is added, that assumption no longer holds: the café should first establish how the online offer is updated or provide a different process that does not advertise an unavailable choice.
Keep costs in the comparison. In a separate hypothetical estimate, suppose a cookie costs $1.10 in ingredients and packaging, while a brownie bite costs $0.80. If ten guests choose bites instead of cookies, the variable item cost is $8.00 rather than $11.00, a $3.00 difference. That is a comparison of item costs, not profit or a promise of savings. It excludes fixed software and labor costs, variable payment or other order costs, and exception costs such as a manager’s time resolving a complaint. Add those costs to your own operating estimate when they apply.
Ask vendors for a written explanation of setup charges, recurring charges, staff controls, and any additional costs that apply to your workflow. For Fleksa’s current plans, consult pricing and plans, checked in November 2026; confirm the quote and relevant setup before deciding.
Ask how the offer behaves in each channel
List every place a guest might encounter or redeem the reward: a message, an online ordering screen, a printed sign, or a conversation at the register. A message may remain visible after the item sells out, so include terms that remain useful even when the stock status changes.
For each channel, ask the provider to show who can change availability, how quickly the change appears, and what happens to a reward already selected. Can staff offer an alternative in that channel? Can the guest retain the reward if they decline it? What can the team see when a guest says a reward was unavailable? Get answers for the actual configuration you intend to use, rather than assuming all channels behave alike.
Fleksa describes loyalty points for eligible orders and marketing tools including email and SMS campaigns. Review its loyalty documentation and campaign documentation, then ask which parts of your stock and substitution workflow can be configured. Access to a guest’s contact details is separate from permission to send marketing messages; check your contact and consent processes before sending an offer.
Test the last-item exception before launch
Run a simulation with a demo or other non-live setup. Do not use a real payment, send a guest message, or dispatch a courier. Have the manager act as the guest and the shift lead act as the operator. If the provider cannot demonstrate a step safely, ask for a walkthrough and record the unanswered question.
- Set the starting state. Use the hypothetical café offer with one eligible cookie remaining and a brownie bite available. Confirm the visible terms and who is responsible for changing the stock status.
- Simulate the last sale. Have the operator mark or otherwise communicate that the last cookie is gone. Check the counter process and each planned digital redemption path separately.
- Try to redeem. The simulated guest attempts to select the cookie. A pass means the guest is not led to believe the unavailable cookie will be provided, sees or receives the agreed choice, and can retain the reward if they decline the alternative. The outcome must match the terms and the staff procedure.
- Check the record. Note the screen or staff action, the time of the stock change, what the guest was told, and whether the reward remained available or was used for the approved alternative. A screenshot from the demo and a short shift-lead note are useful evidence.
- Repeat the exception. Simulate both items being unavailable, then simulate a stock update that a cashier has not yet heard about. The shift lead should correct the message and explain the guest’s options without inventing a new promise.
A fail includes an unavailable cookie still appearing as an available choice without a workable resolution, a reward being consumed contrary to the agreed choice, or staff giving conflicting answers. Record the failure and the owner responsible for fixing it. Do not treat a successful counter simulation as proof that an online flow works.
If the system cannot support the desired behavior, choose a fallback before launch. For example, restrict the offer to a counter process your team can control, with terms that say the guest may keep the reward when both items are unavailable. Confirm how staff will preserve the reward in practice. If they cannot do that reliably, revise the offer rather than promising it.
After the simulation, a live service pilot is a separate decision. Brief the team, use the actual approved offer and terms, and have the shift lead watch for stock updates and guest questions during a limited service period. Real guest orders should follow the normal live process, not be created as practice transactions. Review exceptions before expanding the offer.
Compare this worksheet with your current process, then ask Fleksa to demonstrate the applicable capabilities for your channels and staff roles. Start with its restaurant marketing automation tools and bring your last-item scenario to the conversation.
Frequently asked questions
Should a restaurant automatically substitute a free reward?
Give the guest a choice when possible. An alternative may be comparable in cost but unsuitable for the guest. State the options in the offer and train staff to follow them.
What if both the reward and its alternative sell out?
Use the fallback you stated in advance, such as allowing the guest to keep the reward for later. Confirm that staff can carry it out in the relevant redemption channel.
Does earning a reward guarantee that the item is in stock?
No. Earning and item availability are different conditions. Explain availability before redemption and make the next step clear if the item sells out.
