When a guest switches a cart from pickup to delivery, the ordering system should keep valid selections, collect the delivery details it needs, and recheck the order against delivery rules. It should then show what changed and the revised total before the guest submits the order.
The cart should not quietly retain a pickup time that cannot work for delivery, charge an unexplained fee, or discard a customized meal without telling the guest. Some choices may need to change, but the guest should be able to see why and decide what to do next.
Use the checklist below to evaluate a switch before checkout. It also gives you practical questions to ask a provider when comparing restaurant online ordering options.
Change the delivery fields, time, and fees
Start with the information the restaurant needs to decide whether it can fulfill the order. A pickup cart may have a selected location, pickup time, guest contact information, and payment choice. Delivery adds a destination and may change the available time slots, minimum order, charges, and payment options.
The guest supplies the address and any delivery instructions. Your restaurant supplies its service area, hours, lead times, delivery minimums, and fee rules. If a delivery provider is involved, agree on which system supplies delivery availability and the charge shown to the guest. The ordering system then needs to apply those inputs to the cart.
Ask what happens when the guest switches modes before entering an address. Ideally, the cart remains visible while the guest supplies the missing information. Once an address is entered, the system should determine whether the restaurant can serve it and whether the selected time is available.
If the address is outside the service area, the guest needs a clear next step: correct the address, return to pickup, or choose another available option. Do not let an undeliverable cart look ready to submit. Similarly, if delivery is closed at the chosen time, show available times or explain that delivery is unavailable.
Review the handoff information too. A pickup name and phone number may still be useful, but the guest may need to add an apartment number or drop-off instruction. Ask whether instructions are passed to the people actually handling delivery, and whether the guest can review them before ordering.
Recheck the whole cart against delivery rules
A switch can affect more than individual item availability. The restaurant may have a delivery minimum, a different service window, or a limit on how far it delivers. The system needs to evaluate the whole cart under those rules, not merely add an address field to a pickup order.
Decide what counts toward the minimum. For example, does it apply to the food subtotal before a delivery charge and other fees? Tell guests the rule and, if they fall short, show how much more qualifying food they need. A delivery charge should not appear to satisfy a food minimum unless that is actually how your restaurant applies the rule.
Next, check the requested time against the restaurant's delivery hours and preparation capacity. A pickup time of 6:15 p.m. does not automatically mean a delivery can arrive at 6:15 p.m. Ask the provider whether the displayed time represents an estimated arrival, a delivery window, or some other commitment. Your staff and guests need the same understanding.
If an item or selection cannot be delivered at the chosen time, identify it clearly. The guest might change the time, remove the affected item, or return to pickup. Avoid making the guest rebuild the entire cart when only one part needs attention. Equally, do not allow an invalid cart through simply because the other items are available.
For a broader look at channel and operating choices, the online ordering buying guide can help. For this decision, keep the focus on what happens to an existing cart at the moment the mode changes.
Preserve valid choices and explain exceptions
A useful switch preserves the work the guest has already done: quantities, valid modifiers, special instructions, contact details, and any applicable offers. Preservation is conditional. If a choice is no longer valid for delivery, the guest should see the affected choice and the action needed before submission.
Consider this hypothetical example. A guest has two $12 bowls and one $4 side in a pickup cart. One bowl has a no-onion instruction. The food subtotal is $28. The guest switches to delivery, enters an eligible address, and selects an available delivery window. Assume the delivery minimum is $25 in food and the delivery charge is $5.
The $28 food subtotal meets the $25 minimum. If all three items and the instruction remain valid, the system should retain them and show $33 before any other applicable charges. The $5 delivery charge is a customer charge, not proof of what the restaurant pays for dispatch.
In this example, item prices and the delivery charge are included. Taxes, tips, payment-related charges, fixed subscription costs, and exception costs are excluded, so $33 is not a final payable total. The actual checkout should calculate and display every applicable amount before the guest submits. The example does not describe a particular provider's features or pricing.
Now change one assumption: the side is unavailable for the selected delivery window. If the guest removes it, the food subtotal falls to $24, which is $1 below the assumed minimum. The system should identify both issues: the unavailable side and the remaining minimum shortfall. It should not silently remove the side and present the order as ready. The guest could select a valid item worth at least $1, choose another available time, or return to pickup.
Ask how the system handles promotions during a switch. A pickup-only offer may no longer apply; a delivery offer may have different conditions. The guest should see any change in the discount and the reason. Also ask whether switching back to pickup restores eligible choices or requires the guest to select them again. Do not assume that a cart can recover every removed choice.
Check the revised total and handoff before launch
Before the guest submits, the checkout should make the revised order understandable: fulfillment mode, destination, timing, items and instructions, discounts, fees, and total. If the guest changes the address or time again, the relevant checks should run again. A fee or minimum based on an old address is not a reliable basis for a delivery order.
Use the table as an acceptance checklist with your provider. The expected result is a buying requirement to discuss, not a claim that every ordering system supports it.
| Check | Action to simulate | Expected result |
|---|---|---|
| Address and service area | Switch a pickup cart to delivery and enter an ineligible address. | Delivery cannot be submitted for that address; the guest gets a clear way to correct it or return to pickup. |
| Time and minimum | Choose an unavailable window, then a valid window with a cart below the delivery minimum. | The guest sees the timing issue and, separately, the amount needed to meet the stated minimum. |
| Cart choices | Add an item with a modifier and instruction, then switch modes. | Valid choices remain visible. Any invalid choice is identified with a next step. |
| Total and handoff | Apply the delivery charge and review the order before submission. | The guest can see the revised charges and total; staff can identify the order as delivery with the needed details. |
Run these as simulated checks in a safe practice environment with the provider. Stop before any real payment, guest message, or courier dispatch. Ask how to inspect the staff-facing order without sending it into a live fulfillment queue. Include an address change and a switch back to pickup, because both can expose stale fees or missing choices.
After simulated checks pass, agree on a separate live service pilot with your team and provider. Define who watches incoming orders, how staff will handle an exception, and how to pause the pilot if needed. A simulation can show how a cart behaves under selected conditions; it cannot prove that every real address, time, or handoff will work.
Compare what the guest sees with what the kitchen and delivery team receive. Can staff see the fulfillment mode, promised timing, address where appropriate, and item instructions? Who resolves an address question? A clear checkout matters, but the order also has to reach the right people in a usable form.
Your restaurant website should make it easy for guests to find the ordering flow, but the switch itself deserves its own review. Use this checklist on your current setup, then ask Fleksa about direct ordering and verified US availability, including how it handles the specific transitions you need.
Frequently asked questions
Should a pickup cart be emptied when a guest selects delivery?
Not as a default buying requirement. Valid items and choices should remain where possible. If something cannot carry over, the guest should see what changed and how to resolve it.
When should the delivery fee appear?
Show it once the information needed to determine it is available, and include it in the reviewed total before submission. If an address change affects the fee, update the total and make the change clear.
What if the cart is below the delivery minimum?
Explain which subtotal the minimum uses and how much more qualifying food the guest needs. Let the guest add an eligible item or return to pickup rather than submitting an order that does not meet the rule.
