When an item is missing from a restaurant order, decide loyalty points from the final eligible amount, not just the original order total. A practical default is to award points for the items the guest receives after the order is adjusted. If points were already added, correct the difference before issuing a reward.
That rule needs two things: a clear definition of eligible spending and a person responsible for checking the balance. It also needs a fallback for orders that are edited after points have posted. The right setup is the one your staff can explain to a guest and carry out during a busy service.
Choose the rule and who owns it
Start by writing down when points are earned. Are they calculated when the guest places the order, when the kitchen confirms it, or after the final adjustment? Ask the vendor which events can trigger a points calculation and what happens if the order changes afterward.
For most operators, a final-amount rule is easy to defend: the guest earns on the eligible items they receive. Decide separately whether taxes, delivery charges, tips, discounts, or other fees count. Put those choices in the written policy rather than leaving each shift to guess.
Then assign ownership. The person handling the unavailable item should record the adjustment. A shift lead can check any points correction that the system cannot make or explain automatically. If the guest asks about a reward, the person issuing it should verify the current balance first.
Service conditions matter. A missing item discovered before points post may require only an accurate final order. A problem found the next day may require a balance correction and a clear account note. If a reward has already been issued, stop and follow a separate exception process; do not assume the system can safely reverse a redeemed reward.
Your loyalty program rules should tell staff what to do when an order record and a guest's visible balance disagree. They should also say who can make a manual adjustment and who approves an exception.
Work through a two-item order
The following example is hypothetical. The restaurant awards one point per dollar of eligible food spending. Taxes, tips, delivery charges, discounts, and payment-processing fees are excluded from the points calculation. The restaurant has chosen a reward that requires 100 points; reaching 100 points establishes eligibility under this example, but the guest must still redeem the reward under the program's rules.
A guest starts with 80 points and orders two items: a $12 meal and a $6 side. The side is unavailable, so the staff member handling the order removes it and records an adjusted eligible food amount of $12. The guest receives the meal. There are no other items or discounts in this example.
The decision worksheet below shows the order of work. The point amounts are not dollars and are not a measure of the restaurant's reward cost.
| Step | Owner | Expected result |
|---|---|---|
| Record original order | Order taker | $18 eligible food amount; 18 potential points |
| Remove unavailable side | Order taker | $6 removed; adjusted eligible amount is $12 |
| Check points | Shift lead | 12 points earned; balance is 80 + 12 = 92 |
| Check reward eligibility | Staff member issuing rewards | 92 is below 100; do not issue the reward |
If the system had already posted 18 points, the visible balance would temporarily be 98. The correction is six points, leaving 92. Staff should be able to connect that correction to the removed $6 item rather than simply telling the guest that points disappeared.
The operator's decision is to use the adjusted $12 amount, verify the correction, and wait to issue the reward. This follows the stated rule and avoids treating an unfulfilled side as earned spending. If the restaurant chooses to give goodwill points instead, record them as a separate exception so the order calculation remains understandable.
This worksheet covers point arithmetic, not an all-in operating cost. It excludes fixed software charges, variable payment and messaging costs, the cost of providing a future reward, and staff time or goodwill points for exceptions. Use the restaurant loyalty reward cost guide to build a separate cost estimate.
Compare the ways to handle an adjustment
Ask each vendor to walk through the same missing-item case. A promising screen is not enough: find out what staff must do, what the guest sees, and whether the final balance can be explained.
Calculate after the order is final
Under this approach, points are calculated on the final eligible amount. It can reduce correction work when missing items are discovered before the calculation. The trade-off is timing: guests may have to wait longer to see points. Ask what marks an order as final and what happens if a later correction is needed.
Post early and correct later
Early posting may make points visible sooner, but it creates a correction step when an item is removed. Ask whether the correction is automatic, who can see it, and whether the guest sees both the original award and the adjustment. If staff must correct balances manually, estimate the time involved during a busy shift and how often a lead must approve the change.
Keep the original points as goodwill
An operator may decide that the guest keeps points associated with an unavailable item. That is a service choice, not a calculation based solely on fulfilled food. It may be easier to explain in an individual case, but repeated exceptions can change reward costs and make the program less consistent. Define who can approve the extra points and how they are recorded.
Compare these approaches against your order volume and staffing, not just a feature list. Ask for a written quote covering software charges, processing where applicable, and any charges for messages or adjustments. A quoted processing fee alone is not the all-in cost of operating loyalty. The restaurant marketing automation page describes Fleksa's marketing tools; ask which loyalty workflow is available for your setup.
Run a staff explanation test
Before selecting or changing a system, use a simulated order to rehearse the missing-item workflow. Use test records and simulated actions only. The practice must not trigger a real card payment, guest message, reward issuance, or courier dispatch. Ask the vendor how to keep the demonstration contained.
Give the staff member the hypothetical starting balance, original order, missing item, and points rule. Do not give them the final answer. Ask them to show the order adjustment, find the resulting balance, and explain to a pretend guest whether a reward can be issued.
Pass: The staff member identifies the final eligible amount as $12, explains that the order earns 12 points, and gives the correct balance of 92. If 18 points were posted first, they can show or describe the six-point correction. They also say the 100-point reward is not yet available.
Fail: The balance is wrong, the staff member cannot trace it to the adjusted order, or they issue the reward before verifying eligibility. A correct number without an explanation is not a pass: the next shift needs to be able to resolve the same question.
Record what happened in the simulation: the order before and after adjustment, the points history or screen shown, the steps staff took, and any permissions or approval needed. Note where the workflow required a vendor or manager to intervene. This gives you a useful comparison when two systems both claim to support loyalty.
Also ask to see what happens when an adjustment is made after points post, when a reward has already been issued, and when the order is changed by a different staff member. If a scenario cannot be simulated, ask the vendor to explain the expected behavior and the controls available. Do not treat an unanswered question as a capability.
Set a fallback before going live
If the system cannot produce an explainable balance, use a controlled manual process while you decide whether it is workable. Have the order handler record the final eligible amount and flag the account for a shift lead. The lead checks the starting balance, earned points, and any correction against the order record before approving a reward. Keep the reason and approver with the adjustment.
If staff cannot verify the balance, pause reward issuance and give the guest a clear follow-up route. Set an internal deadline for the lead to resolve the case. Avoid asking frontline staff to guess or silently add points to make the screen look right.
A live service pilot is different from the simulation. If you choose to run one, use your normal order and payment controls, train the participating staff, and review exceptions with a lead. Agree in advance how guests can get help and how you will stop the pilot if staff cannot reconcile balances. Do not use live guests or payments for the practice test.
Compare this workflow with your current process, then ask Fleksa to demonstrate its applicable loyalty capabilities using the missing-item scenario. Bring your points rule, reward threshold, and manual approval requirements to the conversation.
Frequently asked questions
Should a guest earn points for an unavailable item?
A straightforward policy awards points on the final eligible amount for items received. You can choose to let the guest keep extra points as goodwill, but record that separately from earned points.
What if points were added before the item was removed?
Check the original award against the adjusted order and correct the difference under your policy. If the system cannot show an understandable correction, have an authorized staff member document and verify it before issuing a reward.
Can a guest redeem a reward as soon as points appear?
Only if the verified balance meets your program's threshold and its other redemption rules. Points shown temporarily before an order correction may not represent the final eligible balance.
