Delivery
Quick answer - Delivery helps restaurants manage platform orders, in-house delivery, prep timing, and handoff. Keep menus synced, accept orders quickly, prepare accurately, mark orders ready at the right time, and pause delivery when the kitchen cannot keep up.
Use this guide when - Managers, kitchen leads, delivery staff, and anyone responsible for platform or in-house delivery.
Before you start - Confirm menu accuracy, prep times, platform connections, payment rules, delivery zones, and who watches incoming orders during service.
Delivery types
| Type | Meaning |
|---|---|
| Platform delivery | Orders from partners such as Deliveroo, Just Eat, Uber Eats, or a local platform where connected. |
| In-house delivery | Orders your own team delivers where enabled. |
| Collection | Guest picks up from the restaurant. Collection is usually managed in Orders, but it affects kitchen timing like delivery. |
| First-party online ordering | Orders placed through your own booking or ordering link where enabled. |
Your account may not use every type.
What delivery orders show
A delivery order usually includes:
- Platform or channel.
- External order ID.
- Customer or masked customer reference.
- Items, variants, and modifiers.
- Allergy or delivery notes.
- Order value.
- Requested time.
- Prep status.
- Rider or driver timing where available.
Check notes carefully. Platform notes can include allergy information, address context, or handoff instructions.
Accept a platform order
- Open Restaurant.
- Choose Delivery, Orders, or the dashboard delivery panel.
- Open the new platform order.
- Review items, modifiers, and notes.
- Confirm the kitchen can make the order.
- Choose Accept.
- Send or confirm the order on the Kitchen display.
Accept quickly, but do not accept an order that the kitchen cannot make.
Prepare and mark ready
- Track the order on KDS or the delivery screen.
- Start prep based on requested time and platform timing.
- Pack the order carefully.
- Check items against the ticket.
- Include drinks, sauces, cutlery, or extras if required.
- Mark Ready only when the order is packed and at handoff.
- Complete the handoff when the rider, driver, or customer collects.
Marking ready too early can cause riders to arrive before food is packed. Marking ready too late can hurt platform performance.
Pause or throttle delivery
Pause delivery when:
- The kitchen is overloaded.
- Stock is missing.
- A key station is down.
- Delivery wait times are damaging service.
- Staff cannot watch delivery orders safely.
If Resk supports pause or throttle controls:
- Open delivery settings or the platform panel.
- Choose the channel to pause.
- Set the pause duration or new prep time.
- Tell the floor and kitchen.
- Reopen when capacity returns.
Keep menus synced
Menu mismatch is one of the biggest delivery problems.
Check:
- Prices.
- Item names.
- Descriptions.
- Modifiers.
- Allergens.
- Sold-out items.
- Photos.
- Prep time.
If menu sync is enabled, confirm which system should hold the main menu record. Do not edit the same item in two places without a process.
In-house delivery
If in-house delivery is enabled, check:
- Delivery zones.
- Delivery fees.
- Minimum order value.
- Driver assignment.
- Delivery time estimates.
- Payment rules.
- Refund process.
Make sure staff know the difference between delivery, collection, and dine-in order handling.
Common mistakes
- Accepting every order even when the kitchen is already overloaded.
- Marking orders ready before they are packed.
- Forgetting drinks or extras because they are not checked against the ticket.
- Letting platform menu prices drift from Resk menu prices.
- Leaving sold-out items active on delivery channels.
- Mixing delivery tickets with dine-in tickets without clear priority rules.
If something goes wrong - Check Orders, Kitchen display, Menu management, and Payments overview.
Related articles - Restaurant dashboard and analytics, Inventory, Restaurant settings.
Last updated: April 2026