For an order placed now and fulfilled later, award usable loyalty points at fulfillment if your priority is to keep guests from spending points on an order that may never be completed. If you want to recognize the order earlier, consider showing points as pending at placement or payment, but keep them unavailable for redemption until your chosen earning event.
The right trigger depends on how your restaurant handles scheduled orders and what your software can actually control. Decide when points are earned, when they become spendable, and what staff and guests see if the order is canceled. Those are separate decisions, even if a vendor presents them under one loyalty setting.
Choose the event that makes points available
Start by defining the events in your own operation. Placement means the guest submits the order. Payment means the order reaches the payment status your business accepts as paid. Fulfillment means the order reaches a defined completed status, such as picked up or handed off, depending on the workflow.
Placement is the earliest trigger. Guests see an immediate benefit, and the rule is easy to explain. The trade-off is that a future order can be changed or canceled after points are already usable. If a guest spends those points first, staff may need to resolve a negative balance or another adjustment.
Payment is a stronger signal than placement, but it does not mean the guest has received the order. A prepaid catering pickup scheduled for next week can still be canceled. Ask whether an authorization and a completed payment are treated differently, and which status actually starts earning.
Fulfillment ties the award to the completed order. It reduces the chance that a canceled future order creates spendable points, but it also delays the reward. The rule works only if the relevant completion status is recorded reliably. If a pickup stays open because an employee forgets to close it, the guest may wait for points despite receiving the food.
A pending balance can make the wait more understandable: show what the guest is expected to earn without letting them spend it yet. Ask vendors whether pending is a distinct balance, an informational estimate, or simply points that are already redeemable. The label alone does not answer that question.
Work through a canceled scheduled order
Hypothetical example: A guest places a $40 pickup order on Monday, pays immediately, and schedules pickup for Friday. The restaurant's example rule awards one point per eligible dollar. A guest can redeem 100 available points for a $5 reward. Assume the full $40 is eligible and the guest already has 60 available points.
The order represents $40 in sales before cancellation, not profit or a processing fee. The example estimates no operating cost: fixed costs, variable costs such as processing, and exception costs such as staff time are all excluded. The $5 reward is redeemable only when the guest has 100 available points; 40 pending points are not a $5 reward on their own.
The table traces the same order under three possible rules. In each case, the guest cancels on Wednesday, before pickup. The result depends on whether points can be spent before cancellation and on the vendor's adjustment settings.
| Rule | Monday | Wednesday cancellation | Decision for the owner |
|---|---|---|---|
| Available at placement | 40 points become available; balance reaches 100. | The system must address the 40 points already awarded. The guest may have spent them. | Choose a correction rule and check what happens after redemption. |
| Available at payment | 40 points become available after payment; balance reaches 100. | The same correction issue arises because payment came before cancellation. | Define the qualifying payment status and treatment of canceled prepaid orders. |
| Available at fulfillment | 40 points may appear as pending; available balance remains 60. | The order does not reach fulfillment, so those 40 should not become available. | Confirm cancellation removes or updates the pending display and blocks redemption. |
For this restaurant's stated priority—avoiding spendable points on an unfulfilled order—the fulfillment rule is the better fit, provided staff can record completion consistently and the system can keep pending points separate. If immediate recognition matters more, an earlier trigger can work, but only with a correction process the owner is willing to support.
This choice concerns the initial earning event. A refund after a completed order raises a different question: whether and how to reverse points already earned. Ask about that rule separately rather than assuming the cancellation setting covers it.
Run a safe acceptance test before launch
Write the expected result before asking a vendor to demonstrate the workflow. Use a sandbox or other isolated simulation with test records. The practice scenario must not create a real payment, send a guest message, or dispatch a courier. If the vendor cannot provide a safe simulation, review the workflow with them before arranging any live service pilot.
- Set the starting balance. Use the hypothetical rule above: 60 available points, with 100 needed for a $5 reward. Record the balance before the simulated order.
- Create the future order. Simulate placement and payment of an eligible $40 order scheduled for later. Under a fulfillment trigger, expect 60 available points and, if supported, 40 clearly marked pending points.
- Attempt redemption. In the simulation, try to select the $5 reward before fulfillment. Pass only if the reward is unavailable while the balance is 60 available points. A visible pending balance must not count toward the threshold.
- Cancel before fulfillment. Simulate cancellation. Expect the 40 pending points to disappear or be marked canceled, the available balance to remain 60, and the reward to remain unavailable.
- Repeat through completion. With a separate simulated order, reach the agreed fulfillment status. Expect the 40 points to become available once, bringing the balance to 100 and making the reward selectable.
Also check an order that is edited before fulfillment. If the eligible amount changes, ask when the pending estimate updates and which amount determines the final award. Repeat a status update or reopen the order in the simulation to see whether points are awarded twice. Record the actual result, the expected result, and who will resolve any difference.
After a simulation passes, a live service pilot is a separate operational decision. Agree on staff roles, guest communication, monitoring, and a stop procedure before using real orders. Do not treat a simulated pass as proof that every live workflow will behave the same way.
Check what staff and guests can see
The balance is only part of the workflow. A guest may see an order confirmation, a loyalty screen, or a receipt at different times. Ask where the expected points appear, whether the display says pending or available, and whether it explains the event that releases them. If no pending display is offered, consider how staff will answer a guest who asks why points have not arrived.
For cancellations, ask what the guest sees and whether the order record shows the reason for the change. If the restaurant awards at placement or payment, ask how an adjustment appears after a guest has already redeemed the points. Does the account show a negative balance, does staff make a manual adjustment, or is there another process? Decide who has permission to make that correction and how it is recorded.
Ask the same questions for partial order changes, failed payments, and orders marked complete by mistake. A useful staff view should make it possible to connect a points change to the relevant order without relying on memory. Check whether staff can correct a status and whether the points record updates when they do.
Keep any guest explanation short and consistent with the actual rule. For example, if points become available after pickup is marked complete, say that rather than promising points immediately after an order is paid. If messages are sent automatically, check which event triggers them and whether a canceled order can still generate a misleading message.
Put the rule into your buying checklist
Ask each vendor to demonstrate the full path for a scheduled order: placement, payment, pending display, attempted redemption, cancellation, and completion. Specify which order channels matter to your restaurant; do not assume every channel follows the same loyalty rule. Also ask whether the trigger can be configured by the restaurant or is fixed by the product.
Check the wider workflow around your restaurant ordering system, including who marks pickup or delivery complete. A loyalty rule tied to fulfillment is only as dependable as that operational step. For reward economics beyond the timing decision, use the related buying guide to examine the value and cost of a reward separately.
Fleksa's marketing tools include loyalty points for eligible orders. Ask which earning and availability triggers apply to your intended setup, and have the team demonstrate the cancellation and redemption scenarios above. Review current plan details on Fleksa's plans page; pricing was checked in November 2026. Confirm a current quote and any separate charges before comparing operational totals.
Next step: Choose your preferred trigger, write down the acceptance results you expect, and compare them with the workflows available through Fleksa's restaurant marketing automation.
Frequently asked questions
Should a paid scheduled order earn points immediately?
It can, if the restaurant accepts the correction work that may follow a cancellation. Payment happens before fulfillment, so a paid order is not necessarily a completed order. For a stricter rule, make points available after the defined fulfillment event.
Can guests redeem pending points?
That depends on the system's actual balance rules. If pending points are meant to be an estimate rather than spendable points, test that a guest cannot use them to reach a reward threshold before fulfillment.
What if staff forget to complete an order?
Points tied to fulfillment may remain unavailable. Give staff a clear completion step and a way to review orders left open. Ask the vendor how a corrected status affects the points record and what the guest will see.
