Before the orders.
Get the basics sorted.

1. Build a menu the kitchen recognises

Use consistent item names and current prices. Write down sizes, meal choices, extras and which combinations are allowed. If a customer can choose a topping, sauce or side, decide whether that choice is required, optional or limited.

Check a complicated meal deal as carefully as a simple item. A receipt needs to make each choice obvious to the kitchen, including any extra cost. Decide how sold-out items will be removed from ordering during a shift.

2. Separate opening hours from order times

Decide when online orders can be placed, when the last collection is available and how much preparation time to allow. A shop closing at 10pm may need its final ordering time earlier.

Plan for busy periods and unusual opening days. If pre-orders are offered, make sure customers can distinguish ordering now for later from ordering for the next available collection. Test that distinction on a phone.

3. Decide how an order gets accepted

Who notices a new order? Who checks whether the kitchen can fulfil it? What confirmation does the customer receive? Agree a process for an order that arrives just as an item sells out or the kitchen falls behind.

Make the difference between “order received” and “order accepted” clear. If staff must accept orders manually, decide what happens when nobody responds and how customers will be informed.

4. Understand the payment journey

Ask the software provider when a card payment is authorised, when money is captured and how declined payments, cancellations and refunds are handled. An authorisation can appear as a pending transaction to a customer even before funds are captured.

Check who handles refund requests, what payment processing costs apply and how any platform or customer fees are shown. Run test transactions in the provider’s test environment before using live payments.

5. Make the kitchen receipt useful

A receipt should be readable at a glance: order number, collection time, item quantities, modifiers and the information staff need to fulfil the order. Keep customer details limited to what the workflow requires.

Test the actual printer and paper width. Check long item names and multi-option meals, then simulate a disconnected printer. Know how staff will recover the order without accidentally preparing a duplicate.

6. Prepare customer information

Review how customers will see allergen information, contact details, collection instructions and the total payable before submitting an order. Use current information from the business and check the official requirements that apply to your operation.

Food businesses selling at a distance should consult the government’s takeaway allergen guidance. It covers providing allergen information before purchase and when food is delivered. This checklist is a planning aid, not a complete food-law or compliance checklist.

7. Rehearse a complete shift

Place a simple order, a large order and a pre-order if supported. Try an unavailable item, a rejected order, a payment failure and a cancellation. Confirm that the website, customer confirmation, management screen and kitchen receipt agree.

Then test what happens when the internet or printer stops working. Write down who pauses ordering and how outstanding orders are checked. A small, supervised launch makes it easier to catch problems before advertising widely.

Where HappyFork fits

We’re developing HappyFork around the journey from a takeaway’s own website to the kitchen. A first pilot is being prepared; general sign-ups are not open yet.