Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
- Overview
FAQs
- Do food delivery platforms in Australia need separate terms for restaurants and customers?
- Can a food delivery platform avoid responsibility for bad food?
- Who owns customer data collected through a food delivery app?
- Can a platform change its commissions whenever it wants?
- What should restaurants check before signing a food delivery platform agreement?
- Key Takeaways
If you run a food delivery marketplace, app or ordering platform, the main legal risk is often hidden in the fine print you did not negotiate properly. Founders regularly sign standard platform agreements without checking who is liable for refunds, who owns customer data, whether restaurants can be removed without warning, or whether delivery delays will be treated as the platform’s problem. Another common mistake is assuming website terms alone are enough, when the real commercial exposure usually sits in your merchant agreement, courier terms and privacy policy settings.
For Australian businesses, terms of trade for food delivery platform arrangements need to do more than set out fees. They should allocate risk clearly between the platform, the restaurant, the courier and the customer. They also need to work alongside Australian Consumer Law, privacy obligations and any payment, subscription or cancellation settings built into your app.
This guide explains what these terms usually cover, the legal issues to check before you sign, where founders get caught, and the clauses that matter most when you are building or using a food delivery platform in Australia.
Overview
Terms of trade for a food delivery platform are the contractual rules that govern how orders are placed, accepted, fulfilled, paid for, refunded and disputed. For Australian businesses, the right terms can reduce confusion between restaurants, drivers, platform operators and customers, while poor contract drafting can leave you carrying risk you never priced in.
- Who the contract is actually between for each part of the order journey
- Commission, payment timing, chargebacks and fee deductions
- Refunds, cancellations, failed deliveries and customer complaints
- Responsibility for food quality, allergens, safety and menu accuracy
- Courier obligations, delays, lost orders and insurance
- Use of customer data, marketing rights and privacy compliance
- Suspension, termination and what happens to pending orders
- Exclusivity, minimum sales commitments and territory restrictions
- Intellectual property, branding and use of restaurant content
- Dispute resolution, indemnities and liability caps
What Terms of Trade for Food Delivery Platform Means For Australian Businesses
For Australian businesses, terms of trade for food delivery platform arrangements are not just boilerplate. They are the commercial rules that decide who gets paid, who bears the loss when something goes wrong, and how much control the platform has over merchants and delivery partners.
The exact structure differs depending on your business model. A marketplace that simply introduces restaurants to customers has different risk settings from a platform that processes payments, controls delivery logistics and handles customer support. Before you sign a contract, or before you issue your own terms, you need to be clear about where your business sits in that chain.
Common platform structures
A food delivery business can operate in several ways, and the legal terms should match the model.
- A software platform that lets restaurants accept orders directly, with no delivery services included
- A marketplace model where the platform markets restaurants, processes orders and passes them on
- A full-service platform that also arranges drivers or riders
- A white-label ordering service for hospitality businesses using the platform under their own branding
- A hybrid model with subscriptions, advertising packages or premium placement for merchants
Each model changes the contract position. If your platform takes payment from customers, you will usually need clear payment authority, refund rules and chargeback handling. If your platform controls delivery, you need stronger courier terms, insurance settings and delay allocations.
Who contracts with whom
This is where founders often get caught. If the customer thinks they bought from your platform, but your merchant agreement says the restaurant is solely responsible for the meal, you can still face complaints, refund pressure and reputational damage if your customer-facing terms are unclear.
Most food delivery platforms need more than one set of terms:
- merchant or restaurant terms
- customer terms and conditions
- courier or driver terms, if delivery services are offered
- privacy disclosures dealing with customer and location data
- payment processor terms where third party payment services are used
These documents need to fit together. A platform should not promise customers automatic refunds in one place if its merchant agreement says merchants decide all refund outcomes. Misalignment creates disputes and can also create Australian Consumer Law issues if statements to customers are misleading.
Australian Consumer Law still applies
Your contract cannot override consumer guarantees. If meals are not delivered, are unsafe, or do not match what was ordered, the business model and facts will matter, but businesses cannot simply contract out of statutory consumer rights where those rights apply.
This matters for:
- refund and replacement policies
- claims about delivery times
- menu photos and descriptions
- service uptime claims in the app or on the website
- subscription or membership features tied to delivery benefits
Businesses should also be careful with unfair contract term risk. Standard form contracts used with small business merchants can be challenged if they contain one-sided termination rights, broad unilateral fee changes or harsh liability settings that are not reasonably necessary to protect legitimate interests.
Privacy and data use matter more than many founders expect
Food delivery platforms often collect names, addresses, phone numbers, order history, payment information and live location data. If you share customer details with restaurants and drivers, your privacy wording needs to explain that clearly.
Before you sign with a technology provider or issue terms to merchants, think about:
- who owns or controls customer data
- whether restaurants can use customer data for their own marketing
- whether the platform can send promotions after an order
- how delivery location tracking is handled
- what happens if there is a data breach
In practice, customer data rights are often commercially sensitive. A restaurant may expect access to customer details as part of fulfilling orders, while the platform may want to restrict later marketing contact. That position should be set out expressly, not left to assumptions.
Legal Issues To Check Before You Sign
Before you sign a food delivery platform agreement, you should identify where money, customer complaints and operational failures will land. The contract should answer those points directly, because they are usually the areas that cost the most when the relationship breaks down.
Fees, commissions and deductions
The payment clause should do more than state a commission percentage. It should explain how gross sales are calculated, what deductions can be made, when payouts occur and how disputed amounts are treated.
Check the agreement for:
- setup fees, onboarding fees or subscription charges
- marketing fees or sponsored listing charges
- payment processing fees
- delivery service charges and surge pricing rules
- chargeback deductions and administration fees
- the right to change pricing on notice, or without notice
If the platform can deduct any amount it considers appropriate, that is a red flag. The merchant should know the basis for deductions and have a process to dispute them.
Refunds, cancellations and no-show orders
Refund disputes are one of the fastest ways for a platform relationship to sour. The agreement should state who decides whether a refund is given, who pays for it and what happens when fault is shared.
This area should cover:
- restaurant-prepared food errors
- late delivery caused by the courier
- customer input mistakes, such as wrong address details
- orders cancelled after preparation starts
- failed deliveries where the customer cannot be contacted
- partial refunds, credits and platform-funded goodwill gestures
Without clear rules, the platform can end up making customer service promises first and arguing with merchants later.
Food quality, compliance and product information
The restaurant is usually best placed to control food preparation, ingredients, allergens and labelling statements, but the contract still needs to say that clearly. If menu descriptions in the app are inaccurate, both the merchant and the platform may face complaints.
Merchants should usually warrant that:
- their food complies with applicable food standards and local requirements
- menu descriptions, pricing and allergen information are accurate
- they hold any registrations or approvals needed to operate their food business
- they will notify the platform promptly of recalls, contamination issues or safety incidents
If your platform edits menu content, creates promotional copy or republishes product claims, the risk position becomes more complicated. Before you make product claims, check who approved the wording and who is carrying liability if the claim is wrong.
Delivery responsibility and courier terms
If the platform organises delivery, the courier side of the arrangement is just as important as the restaurant terms. Delays, accidents, spoiled meals and lost orders usually trigger customer complaints against the platform first.
Key points include:
- pickup windows and delivery time targets
- temperature control expectations and packaging requirements
- proof of delivery rules
- insurance arrangements
- what happens if a rider cannot complete a delivery
- liability for vehicle incidents or third party property damage
Where drivers are engaged as contractors, businesses should also think carefully about the real nature of the arrangement. Worker classification is a separate issue from the platform terms themselves, but the drafting should not create unnecessary confusion about obligations and control.
Data, privacy and marketing rights
The contract should say exactly what data each party can collect, use and keep. This is especially important where a platform wants to retain customer relationships while merchants want direct marketing access.
Before you sign, check:
- whether customer data can be used outside order fulfilment
- whether de-identified analytics can be used by the platform
- whether merchants can contact customers after a transaction
- how consent for promotions is obtained
- who must respond if a privacy complaint or data incident occurs
These issues should line up with your privacy policy and app permissions. If the documents contradict each other, customers and merchants may challenge the arrangement.
Suspension, termination and account control
The termination clause often tells you how balanced the deal really is. A platform may need the right to suspend a merchant for safety issues or fraud concerns, but very broad rights can be difficult for a merchant to accept, especially if pending orders and accrued payments are not addressed.
Look for:
- termination for convenience and the notice period
- immediate suspension rights
- withholding of payouts after termination
- removal of listings and menu content
- customer communication after a merchant leaves the platform
- return or deletion of confidential information
Before you spend money on setup, app integration or menu photography, make sure you know how easily the arrangement can be ended.
Liability caps, indemnities and dispute resolution
Liability clauses decide who pays when things go wrong. Broad indemnities in favour of the platform can shift significant risk to merchants, while low liability caps can leave merchants with little practical recourse if the platform causes a serious issue.
Review:
- whether the platform excludes liability for downtime or system errors
- whether indirect loss is excluded
- the dollar amount of any liability cap
- whether the cap applies to privacy breaches, unpaid fees or personal injury claims
- which party indemnifies the other for consumer complaints, food safety issues or intellectual property claims
- how disputes must be notified and resolved
A low cap may be workable for minor software issues, but not where the platform controls high-volume order processing or payment flows.
Common Mistakes With Terms of Trade for Food Delivery Platform
The most common mistakes happen when businesses rely on generic terms that do not match the actual service model. In food delivery, small drafting gaps quickly become expensive because several parties are involved in a single transaction.
Treating one contract as enough
A founder may have solid website terms but no proper merchant agreement or courier terms. That usually leaves major parts of the order flow undocumented.
If your business has restaurants, customers and riders all interacting through the same platform, separate terms are often needed for each relationship.
Using vague refund wording
Saying refunds will be handled on a case-by-case basis sounds flexible, but it often creates arguments. Staff need a rule they can apply when an order arrives late, damaged or incomplete.
Good drafting sets out decision pathways for common situations. That is far easier than negotiating every complaint from scratch.
Ignoring small business contract risk
Many platforms issue standard terms to independent restaurants and assume bargaining power will protect them. That can backfire if the agreement gives the platform unilateral rights to increase fees, change ranking logic, hold payments or terminate on short notice without a fair reason.
Terms should still protect the platform, but they need to be justifiable and proportionate.
Claiming all responsibility sits with the merchant
Some platforms try to push every possible issue back onto restaurants, even where the platform controls customer messaging, payment collection or delivery logistics. That approach can create practical and legal problems.
If your app promises delivery by a certain time, or your support team handles complaints directly, customers may look to you regardless of what the merchant terms say.
Forgetting data rights are a commercial issue
Restaurants care deeply about customer ownership. If the contract is silent, disputes often arise later about remarketing, loyalty programs and access to order history.
This should be negotiated upfront, especially before you sign with a platform provider or white-label partner.
Missing operational detail
Founders sometimes focus on legal labels and miss practical clauses that matter every day. The agreement should reflect how orders actually move through the system.
Useful operational points often include:
- order acceptance cut-off times
- estimated preparation windows
- what happens if an item is out of stock
- who updates menu prices
- what support is available during service interruptions
- how promotional discounts are funded
When these points are absent, teams start making informal workarounds that may conflict with the written contract.
Not reviewing the agreement as the platform evolves
A platform might begin as a pure software listing service and later add payments, subscriptions, driver management or priority placement. If the contract does not evolve too, the legal position drifts away from the actual business.
That is a common problem for growing startups. A contract that was acceptable for 20 orders a week may be a poor fit once the platform expands into multiple suburbs or states.
FAQs
Do food delivery platforms in Australia need separate terms for restaurants and customers?
Usually, yes. Restaurant terms deal with commission, menu accuracy, refunds and platform access, while customer terms deal with ordering, payment, cancellations and consumer-facing rules. If delivery partners are involved, separate courier terms are also often needed.
Can a food delivery platform avoid responsibility for bad food?
Not entirely. A contract can allocate responsibility to the restaurant for preparation, ingredients and food safety, but customer expectations, platform conduct and Australian Consumer Law can still affect the outcome. The wording needs to reflect the real role the platform plays.
Who owns customer data collected through a food delivery app?
The answer depends on the contract and privacy settings. Many disputes arise because the platform assumes control over customer data while the restaurant expects direct access for repeat marketing. The agreement should state what each party can do with personal information and order history.
Can a platform change its commissions whenever it wants?
It depends on the contract, but broad unilateral pricing powers can be risky, especially in standard form agreements with small businesses. Clear notice periods and transparent variation clauses are safer than open-ended discretion.
What should restaurants check before signing a food delivery platform agreement?
They should review fees, payout timing, refund allocation, data rights, termination rights, exclusivity, liability clauses and what happens to customer relationships if the account is suspended or closed.
Key Takeaways
- Terms of trade for food delivery platform arrangements should clearly allocate responsibility between the platform, the restaurant, the courier and the customer.
- The most important clauses usually cover fees, refunds, delivery failures, food quality, data use, suspension rights and liability limits.
- Australian Consumer Law and privacy obligations still apply, even if the contract tries to shift risk to another party.
- Standard form agreements should be reviewed carefully for unfair or one-sided terms, especially where small business merchants are involved.
- Separate terms are often needed for merchants, customers and delivery partners, and the documents should be consistent with each other.
- Founders should revisit their contracts as the platform adds payments, logistics, subscriptions or new service features.
If you want help with merchant agreements, customer terms, privacy compliance, liability and refund clauses, you can reach us on 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.





