Total Cost of Running Online Ordering

The total cost of online ordering includes software, payment, fulfilment, staff time, failures and supplier exit. A low headline monthly fee can still produce an expensive operating model.

Use a lifecycle cost structure

Include internal labour

Record time spent on menu updates, promotions, customer support, settlement reconciliation, supplier meetings, privacy requests, staff training and incident recovery. “Included in salary” is not the same as free; the work displaces another task.

Separate direct and marketplace economics

Direct ordering may replace commission with software, payment, marketing and delivery cost. Marketplace value can include customer discovery and outsourced fulfilment. Compare like with like and avoid treating all marketplace fees as avoidable.

Model scale and thresholds

Some costs are fixed, some variable and some step-fixed. A system may be economical at one order volume but require new hardware, staff or support at another. Include peak and failure scenarios rather than one annual average.

Check supplier terms

• Contract length and renewal
• Transaction minimums
• Support level
• Integration ownership
• Data export
• Price increases
• Store and domain ownership
• Exit assistance

Practical next step

Create a three-year cost model with setup, monthly, transaction, internal, failure and exit rows. Reconcile the first year to actual invoices and payroll evidence before using it for channel decisions.

Build the model by supplier and responsibility

For every cost, record who contracts for it, who can change the price and how it appears in invoices or statements. A payment fee may be collected by the ordering supplier, the gateway or a marketplace. Support may be included only during business hours. Hardware may be rented, financed or owned but dependent on proprietary software.

Include internal dependencies such as bookkeeping, data protection, menu approval and incident management. These tasks often remain with the restaurant even when a supplier describes the service as fully managed.

Use a quarterly reconciliation

1. Compare contract and invoice.
2. Rebuild transaction charges from representative orders.
3. Match settlements to the bank.
4. Review unused modules and duplicate tools.
5. Check renewal and notice dates.
6. Update the three-year forecast and exit provision.

Do not wait for annual renewal to discover that a low headline fee has become expensive through per-order charges, support work or parallel systems.

Report cost per useful outcome

Alongside cost per order, report cost per completed profitable order, cost per repeat customer and cost per resolved support case where relevant. This prevents high failed-order or refund volumes from making a cheap-looking platform appear efficient.

Use renewal as a decision point

Before renewal, compare actual cost with the original case, current alternatives and the cost of exit. Do not allow automatic renewal to substitute for a value review.

Related guides

• Business Planning and Finance — the main guide for the wider topic.
• Cost Analysis for Digital Operations — the broader guide that frames this implementation.
• Break-Even Analysis for a Takeaway App — a closely related operational control to review alongside this page.

Sources and date checked

Guidance checked: 24 July 2026. Recheck official guidance, local requirements and supplier documentation before changing a live operation.

• HMRC: business records
• CMA: price transparency guidance