How to Offer Delivery and Pickup From Your Own Website

Taking an order on your own website is the easy half. Getting the food to the customer, on time and at a cost that does not swallow the margin, is where most direct ordering setups succeed or stall. This article is written for owners and managers who already have an ordering page, or are about to publish one, and need to make the fulfilment decisions: which areas to serve, what to charge, how long pickup takes, who carries the bag, and what to say when the customer calls.

Start with pickup, even if delivery is the goal

Pickup is the lowest-risk way to open a direct channel. There is no rider to find, no address to validate, and the customer comes to you. It also exercises the whole order flow: menu accuracy, payment, the order screen, prep times, packaging and handover. If pickup runs smoothly for two weeks, delivery is a smaller step.

Three decisions make pickup work:

1. Lead time. The time between the order being placed and it being ready. Set it per service, not per day. A café that can turn a sandwich around in eight minutes at 10am may need twenty at 1pm.
2. The promise. Show a ready time, not a vague “soon”. When the kitchen marks the order ready, the customer should know.
3. The handover spot. A shelf or counter where the bag goes with the order number visible, so a customer can collect without interrupting whoever is taking payments.

The takeaway and pickup page covers how pickup orders appear on the order screen and what the customer sees.

Draw a delivery area you can actually serve

The temptation is to accept any address and sort it out later. Resist it. A delivery area should be defined by the time a rider needs to reach the far edge during your busiest hour, with the food still worth eating when it arrives.

Practical ways to define the area:

• Radius from the kitchen. Simple to explain, but a 3 km radius can mean a 7-minute ride in one direction and a 25-minute one across a river or ring road.
• Named zones or postcode and pincode lists. More work to set up, but they follow real roads and let you charge differently by zone.
• Start small and widen. Launch with the area you are sure about. Expanding is easy; shrinking an area after customers have ordered from it is awkward.

Tuckly lets you set delivery areas and charges on your ordering page, and shows the charge before the customer reaches payment, which is the single biggest factor in whether an order gets abandoned at checkout.

Charge for delivery with the numbers in front of you

Delivery costs something whether or not the customer sees a line for it. The question is who pays and how.

Approach	How it works	Suits
Flat fee	One charge for every delivery order	Small areas where trip cost barely varies
Fee by zone	A different charge per zone or distance band	Wider areas with real differences in trip time
Free above a threshold	No charge on orders over, say, ₹600	Nudging order value up without discounting food
Built into prices	No visible fee; delivery menu prices are higher	Customers who react badly to fees, at the cost of transparency

To pick a number, work out what a trip costs you. For your own riders that is wages, fuel and vehicle costs divided by trips per shift. For a third-party rider it is the per-trip fee. The delivery fee calculator does this arithmetic and shows what each approach does to your margin at your average order value.

Distance-based pricing that changes automatically with the address is a feature some ordering systems offer and others do not. Check what your provider supports before you design a scheme around it.

Choose who carries the bag

There are three ways to fulfil a delivery order from your own site, and most restaurants use more than one.

Option	Strengths	Limits
Your own riders	Full control of handover and customer experience; cheapest per trip at steady volume	Riders are paid whether or not there are orders; recruiting and insurance
On-demand rider via Porter (India, where Porter operates)	No fixed cost; scales with demand	Availability varies by city and hour; the automated parts of the Tuckly workflow are still being validated
Pickup only	No delivery cost at all	Rules out customers who will not travel

With Tuckly, fulfilment is chosen per order. You can assign your own rider to one order and request a Porter rider for the next, or switch a delivery order to pickup if the customer calls to say they are passing anyway. For the detail on Porter, including which parts of the integration are live and which are pending validation, read the Porter integration page. For running your own team, see self-delivery.

Pack for the journey, not the pass

A dish that leaves the kitchen perfect and arrives steamed in its own container will not be reordered. Packaging is part of fulfilment, not an afterthought.

• Vent containers for fried food. A small gap keeps the batter crisp.
• Separate sauces and dressings. A side pot costs pennies and saves a soggy salad.
• Seal the bag. Tamper-evident stickers reassure customers and reduce “something was missing” disputes.
• Label the bag with the order number and the customer’s first name, so a rider carrying three orders does not mix them up.

Put a card with your direct ordering link inside every bag. It is the cheapest marketing you will ever do. The QR code generator produces a print-ready code.

Communicate times you can keep

Customers are patient with a long ETA and furious with a missed one. The honest way to quote delivery time is prep time plus travel time plus a buffer.

Say the kitchen takes 15 minutes for most orders at 7pm, the trip to the edge of your area is 12 minutes, and handover takes 3. Quote 35 to 40 minutes, not 25. Then keep the order status moving: accepted, preparing, out for delivery, delivered. Each status change is a small reassurance that stops the phone ringing.

Be careful with live tracking. Customers have been trained by marketplace apps to expect a moving dot on a map. Only promise it if your delivery setup provides it. For Porter deliveries, tracking is one of the pieces still being validated in Tuckly’s integration, so until that is confirmed, status updates are the honest tool.

Handle the “where is my order” call

It will happen. The difference between a lost customer and a loyal one is usually the first thirty seconds of that call.

Have the order open before you answer. Tuckly’s order screen keeps the customer’s contact details and the order status on the order itself, so whoever picks up the phone can see whether the order is still in the kitchen or already with a rider. Then:

1. Confirm the order number and what they ordered.
2. Tell them exactly where it is: “It left with our rider four minutes ago” or “It is being packed now, the rider is waiting.”
3. Give a new time and keep it.
4. If you are at fault, say so and offer something specific, such as a free side on the next order. Note it on the customer’s record so the next order honours it.

Keep a short log of late orders with the reason. After a month you will see the pattern: a zone that is too far, a dish that takes longer than its prep time, a rider shortage at 8pm on Saturdays. Fix the pattern, not the individual complaint.

A week-one checklist

• Pickup lead times set per service and tested with real orders
• Delivery area drawn around a realistic ride time, not a wish
• Delivery charge chosen with the calculator and shown before payment
• Rider plan for each service: own, Porter where available, or pickup only
• Packaging tested on your three slowest-travelling dishes
• Order screen staffed, alert audible, customer contact visible
• Insert cards printed with the direct ordering link

What to do next

Open with pickup, add delivery in the area you can serve well, and let the data from the first month set the next change. The delivery management page explains how each fulfilment option works in Tuckly, including the parts that are still being validated, so you can plan around what is actually live.