Prepaid orders generally reduce the risk of making food that nobody pays for, but they can create refund work and payment-processing costs. Pay at pickup gives guests another way to order, while leaving the restaurant exposed if an accepted order is prepared and never collected.
For most owners, the decision starts with four questions: When is an order accepted? When does the kitchen start work? What happens if the guest does not arrive? And who can resolve a payment problem during service? Compare those answers before choosing one method or offering both.
Map the order and payment states
Start with the actual path an order takes, from checkout to handoff. An order can be accepted without being paid, and a payment can be taken before anyone has started cooking. Those differences determine who carries the risk at each step.
- Submitted: The guest has sent the order. Confirm whether this is only a request or whether it is already binding in your workflow.
- Accepted: The restaurant has agreed to prepare it, either through a staff action or an automatic setting. Identify what the guest sees at this point.
- Paid or payment pending: For a prepaid order, determine whether the payment has actually been captured or is only authorized. For pay at pickup, the amount may still be entirely outstanding.
- In preparation: Ingredients, packaging, and staff time may now be committed. Set a clear point at which a cancellation needs a manager's decision.
- Ready, collected, or uncollected: Staff need a way to tell a completed handoff from an order still waiting on the shelf.
- Canceled or refunded: Record whether the kitchen stopped work, whether money was returned, and whether a processing fee remained.
Ask the ordering provider to show which statuses are visible to staff and guests, how acceptance works, and whether payment and order statuses can disagree. Ask your payment provider when funds are captured and what happens if a payment fails. Your shift lead can identify when the kitchen normally starts making a pickup order and who handles exceptions.
For example, an accepted pay-at-pickup order for a later time may be low risk while it is still untouched. Once the kitchen has made it, cancellation can mean wasted food and packaging. A prepaid order can reach the same kitchen state, but the next question is whether your refund policy calls for returning the payment.
If you are also evaluating the ordering channel itself, the online ordering buying guide covers the wider purchase. Keep the payment-timing decision separate from hardware: a card reader at the counter does not answer when an online order becomes a commitment.
Compare the risk under each method
Use the matrix below with your own order history and written provider quote. Neither column is automatically cheaper: the result depends on uncollected orders, refunds, processing terms, and how your staff handles exceptions.
| Decision point | Prepaid online | Pay at pickup |
|---|---|---|
| Uncollected food | Payment may cover some or all of the loss, depending on refunds and fees. | The restaurant may absorb prepared food and packaging if no payment is collected. |
| Guest cancellation | Someone may need to cancel the order and issue a full or partial refund. | Staff must stop preparation where possible; there may be no payment to return. |
| Payment failure | Check whether the order reaches the kitchen if online payment fails. | Check the counter procedure if the guest cannot complete payment. |
| Service workload | Review payment status, refund requests, and payment disputes. | Collect payment at handoff and identify orders left on the shelf. |
| Provider costs | Ask about online transaction and refund fees. | Ask about counter transaction fees and any order-platform charges. |
The table separates the cost of preparing an uncollected order from the cost of returning money. A refund is not the same thing as a processing fee: one returns guest funds, while the other is a charge under the payment provider's terms.
A hypothetical shift comparison
Suppose a restaurant accepts 100 pickup orders at $30 each. Under the prepaid option, assume four guests cancel early enough that the kitchen makes only 96 orders. All four receive full refunds. Under pay at pickup, assume the kitchen makes all 100 orders and ten are never collected. These are separate assumed outcomes, not a forecast or a comparison of the same guests.
Assume food and packaging cost $12 per prepared order. Also assume a $1 processing fee for each prepaid transaction, including the four refunded transactions, and $1 for each payment collected at pickup. The provider's actual fee and refund terms could be different.
- Prepaid: $3,000 collected minus $120 refunded leaves $2,880 in retained sales. Subtract $1,152 for 96 prepared orders and $100 in processing fees. The remainder is $1,628.
- Pay at pickup: 90 collected orders produce $2,700 in sales. Subtract $1,200 for 100 prepared orders and $90 in processing fees. The remainder is $1,410.
Under these assumptions, prepaid leaves $218 more toward the restaurant's other costs. That supports considering prepaid first in this example, not a general claim that it will earn more. The comparison includes the assumed variable food, packaging, and processing costs, plus the four refunds and the food made for ten uncollected orders. It excludes fixed costs, labor, platform charges, taxes, disputes, and any other exception costs. It also assumes payment timing does not change order volume or order value.
Run the same calculation with your own cancellation timing. If cancellations arrive after preparation, include that food cost. If refunds or disputes carry extra fees, include those too. A lower no-show count or different fee quote can change the result.
Make the choice clear before checkout
A guest should not have to infer when payment is due. Name each available option plainly, show the amount due, and explain what happens if the order is canceled or not collected. Put the relevant information where the guest selects a method, not only in a long policy elsewhere.
For example, the checkout could describe one option as “Pay online now” and another as “Pay when you pick up.” If your restaurant accepts only certain payment methods at the counter, say so before the guest places the order. State your actual cancellation and refund terms in clear language; do not imply that every canceled prepaid order is automatically refundable unless that is your policy.
Also check the confirmation. It should help the guest understand the pickup time, location, order total, payment status, and how to contact the restaurant about a problem. Ask the provider which details can appear there and whether the wording can be changed.
Walk through a practice order
Before changing your live setup, use a sandbox, demo, or other non-live mode with your provider. A manager can act as the guest while a shift lead follows the order on the staff side. Use simulated transactions only: the practice must not charge a real card, send a guest message, or dispatch a courier.
- Select prepaid and check the wording before submitting. Simulate a successful payment and a failed payment. Does the kitchen see only the orders your process intends it to prepare?
- Select pay at pickup. Confirm the guest-facing amount due and the staff-facing payment status. Can staff distinguish it from an already-paid order?
- Simulate a cancellation before preparation and another after preparation. Identify who changes the order status and who is authorized to approve a refund.
- Simulate an uncollected order at closing. Decide how staff record it and who reviews it the next day.
A simulation checks the workflow without affecting guests or real funds. It cannot establish how staff will perform during a busy service. If you later run a live pilot, treat it as a separate, controlled service decision: brief the team, monitor real orders, and use your normal procedures for real payments and guest communications. Set a review date rather than assuming the practice run settles the question.
Your restaurant website can also help guests find pickup instructions and contact details. Make sure those details match what the ordering flow actually offers.
Check terms, costs, and local requirements
Ask each provider for a written explanation of both payment paths. A quoted processing fee is only one part of operating cost. Compare the applicable platform charges, transaction fees, refund or dispute fees, and staff work alongside the expected cost of uncollected food. Keep fixed charges separate from per-order charges so you do not mistake one for the other.
- When is an online payment authorized, captured, and paid out to the restaurant?
- If a guest is refunded, is the original processing fee returned? Are there separate refund or dispute charges?
- Can staff cancel or partially refund an order, and what permissions or steps are required?
- What does the guest see if payment fails, and what does the kitchen see?
- Can the restaurant offer both payment timings, restrict either option, or change the wording shown at checkout?
- How are uncollected orders and payment exceptions shown in reports or exports?
- Are there separate fees for online ordering and counter payments, and what other recurring or transaction charges apply?
Write down who owns each exception on a busy shift. The ordering provider may control order statuses, while a separate payment provider handles settlement or disputes. Your restaurant still needs a person who can find the order, communicate the policy, and escalate a problem.
Review your cancellation and refund wording against applicable local requirements with a qualified adviser when needed. Ask the adviser about contract, legal, or tax treatment rather than assuming that an order-system setting settles those questions.
Finally, review a sample of your own orders after a set period. Count uncollected pay-at-pickup orders, prepaid cancellations, refunds, and payment problems separately. Note whether food had already been made and how much staff time each exception took. Use those observations to adjust the method or policy, rather than deciding from transaction fees alone.
Use this checklist on your current setup, then ask Fleksa about US availability and the payment-timing options relevant to your restaurant's online ordering setup.
Frequently asked questions
Does prepayment eliminate no-show losses?
No. A restaurant may still refund an order, incur processing or dispute fees, or prepare food before a cancellation. The outcome depends on its policy and provider terms.
Should a restaurant offer both payment timings?
It can be worth considering if guests need a choice and staff can manage both workflows. Compare the added checkout and handoff complexity with the risk of uncollected orders before deciding.
What should staff do when a pay-at-pickup order is not collected?
Follow a documented closing procedure: identify the order, record that it was uncollected, and note whether it was prepared. A manager can review recurring problems and decide whether the restaurant's policy needs to change.
