Food delivery · From menu to accepted order

Website Development for Food Delivery

The buyer of delivery does not want to call to confirm whether you will bring the order, how much it costs and whether the payment has been made. These answers the site should give before and after purchase. We create sites for the delivery of pizza, sushi, ready meals, lunches and restaurant menu: with a catalogue, basket, address, payment and an agreed process for transferring the order to the team. We begin with the rules.

Example of a food delivery site with photos of dishes and basket
An example of a delivery site with a basket and a choice of dishesExample of the interface: menu categories, order composition and clear transition to the address and payment. The final rules of registration depend on your delivery.
  • 01

    Order without unnecessary clarifications

    The buyer sees the warehouse, options, additions and the final amount. The address and terms of delivery are checked before he spends time on payment.

  • 02

    Payment has the correct status

    The system distinguishes the created order from the paid one. Repeated messages of the payment service should not create a second order or duplicate the transfer to the kitchen.

  • 03

    The team receives the required data

    The dishes, modifiers, address, method of receipt and comment are transferred to the agreed place. We provide confirmation and actions in case of inaccessibility of integration.

Start with the address, menu and real conditions

Where delivery depends on the area, confirm the address or zone before the final checkout step. Otherwise customers may fill a basket only to learn that delivery is unavailable. For several kitchens, we establish which serves the address, the available menu and the effect on timing. Collection shows the location, opening hours and procedure.

The dish card helps to choose the size, weight, composition and additional ingredients. Mandatory options are different from optional. If the buyer adds cheese or changes the size of pizza, the price should be immediately updated. Do not hide the cost of packaging or delivery to the last screen. Photo, description and availability of dishes before launch is checked by your team.

Rules of delivery that need to be determined before development

The technical task begins with answers to operational questions. Can I order for tomorrow, when the kitchen stops accepting orders, how does the minimum amount work, or are discounts sad? If these rules are left uncertain, the site will only transfer confusion online. We fix them in a clear table and check the boundary situations together with the manager.

Rule Example of solution What the Buyer Sees
Geography Agreed zones and self-delivery points Is it available at his address?
Pricing Tariff by zone or basket conditions Final amount before payment
Time Current opening status and preorder availability Time options available without fictional accuracy
Stop-list Unavailable meals cannot be ordered Current menu and clear replacement
Promotions Agreed terms of use Reason why the discount is valid or not valid
The route from the choice of food to the execution of the order
  1. MenuCategories and available dishes
  2. MealComposition, portions and additions
  3. BasketQuantity and final cost
  4. ReceivingAddress, zone, time or pickup
  5. PaymentAn agreed method and confirmation
  6. StatusClear order status

Online payment: check more than successful payment

The payment service is selected in accordance with your business and available methods of receiving funds. The site should receive a confirmation of payment on the server and verify its authenticity. It is the return of a person to the gratitude page that does not prove that the money was received. These cards do not need to be sent to the manager or stored in the usual enquiry of the site.

We test bank refusal, closed tab, retry and delay of payment notification. One order should have a stable number and clear status history. Separately, we agree what happens when you pay for an order that the kitchen can no longer fulfill, and who is responsible for returning. Commissions and terms of service are separate expenses of the business.

Where orders are received and who confirms them

At a small start, orders can arrive to the manager in an agreed channel along with an entry in the system. For a larger stream, you need to connect to the accounting or the kitchen workplace. It is important not only to send a message, but also to know that the order is accepted. If integration is temporarily unavailable, we assume the visible status of the error and the agreed backup process.

We do not promise a courier card with real-time movement if there is no source of such data. First, we divide the statuses that the team can support: received, confirmed, prepared, transferred, completed. The manager needs convenient actions, and the buyer needs reliable information. Excess messages about each minor event can interfere, so we agree on their set.

What has the most impact on the budget

The price depends on the number of working rules, not just the number of dishes. Ten positions with complex sets, additions and different zones may require more work than a large simple catalogue. For the first version, we choose the necessary scenarios and separate them from the loyalty program, personal account and complex logistics. So the budget remains related to the benefits.

Part of the system A simpler scenario A more complex user flow
Menu One catalogue and fixed portions Designers, kits and dependent add-ons
Delivery A few clear areas Many kitchens and different rules at the address
Payment One agreed service Multiple ways and additional return scenarios
Accounting Manager's work in the administrative interface Synchronization with cash register, warehouse or kitchen
Re-purchases Contact form without cabinet History, bonuses, personal offers

How to accept the finished order system

Before launch, we make a set of control purchases: delivery inside the zone, address outside it, pickup, inaccessible dish, changed basket and payment error. We check the final amount in the interface, order and payment service. On the phone, we test the entering of the address, return to the basket and readability of messages. Important fields should not disappear after an accidental error.

After the technical check, the team goes through a short rehearsal of work: who sees the new order, who calls when necessary and who closes the status. In analytics, we divide the addition to the basket, the beginning of registration and the confirmed purchase without passing the address or other unnecessary personal data there. Next, you can evaluate where people stop and what is worth improving.

Frequently asked questions

Is it possible to accept both online payment and payment upon receipt?

Yes, if these methods are allowed by your rules and supported by the delivery process. They require different payment statuses so that the manager and courier do not confuse the paid order with the one for which you still need to receive money. The conditions are shown before confirming the purchase.

We do not have an accounting system. Can we start?

You can run a consistent simpler process with the management of orders on the site and messages to the manager. First, we determine the expected flow and capabilities of the team. If manual processing already creates errors, it is advisable to solve the accounting issue together with the launch, rather than postpone it.

How to turn off the dish that has ended?

We provide accessibility management in the editor or we receive it from the accounting system. It is important to determine the main data source and the frequency of updating. If the dish has become unavailable while the buyer makes a basket, the site should notify about the change before accepting the order.

Does the customer need an account?

Not necessarily. For the first order, a short registration without registration is often enough. The cabinet becomes useful for purchase history, repeat orders or bonuses, but needs support for access and personal data. Add it when there is a clear use case.

Can you show the courier’s exact arrival time immediately?

Only if the system receives data that allow it to reasonably calculate. Without such integration, it is better to show the agreed time interval and report changes. A beautiful random number timer will create incorrect expectations and additional enquiries to the manager.

Prepared by the Cartel Digital team. The examples illustrate possible solutions; we agree the scope around your business needs.

START WITH YOUR TASK

Describe how the order goes from buyer to kitchen

Send a menu, delivery areas and a list of systems used by the team. We will schedule the process for understandable steps and determine the scope of development.

Discuss your project