Risk Allocation in Customer Contracts for New Zealand Food Delivery Platforms

Food delivery platforms sit in the middle of a messy chain: the customer places the order, the restaurant prepares it, a driver collects it, and your platform gets blamed when anything goes wrong. That is why risk allocation in a customer contract matters so much. Many founders make the same mistakes early on. They copy overseas terms that do not fit New Zealand law, they assume a broad disclaimer will protect them from every refund claim, or they leave key points vague, such as who is responsible for delays, missing items, or food quality.

If your customer terms do not clearly divide responsibility between your platform, the merchant, and the delivery partner, disputes become expensive and hard to resolve. You can also create problems under the Consumer Guarantees Act, Fair Trading Act, and Privacy Act if your wording overreaches or does not match how the service actually works. This guide explains how risk allocation in customer contract food delivery platform clauses usually work in New Zealand, what to check before you sign or roll out terms, and where founders commonly get caught.

Overview

A New Zealand food delivery platform should use customer terms to clearly explain what the platform does, what the restaurant does, what the courier does, and which risks sit with each party. Good drafting does not eliminate all liability, but it can reduce confusion, improve dispute handling, and make your commercial position much easier to defend.

• Define whether your platform acts as agent, principal, or a hybrid for order processing and payment collection.
• Spell out who is responsible for food quality, allergens, preparation errors, delivery delays, address mistakes, and customer unavailability.
• Make refund, credit, cancellation, and complaint processes precise, including timeframes and evidence requirements.
• Check that any liability limits or disclaimers fit New Zealand consumer law and do not overpromise or mislead.
• Align your customer contract with your merchant agreement, courier agreement, app flows, and privacy notice.

What Risk Allocation Customer Contract Food Delivery Platform Means For New Zealand Businesses

Risk allocation is the part of your customer contract that decides who carries the commercial and legal consequences when something goes wrong. For a food delivery platform, that usually means drawing clear lines around payment issues, service interruptions, food defects, delays, and customer claims.

This matters because a platform often looks like the single business the customer is dealing with, even when multiple parties are involved behind the scenes. If your contract is silent or inconsistent, the customer may still look to you first, and your suppliers may point the risk straight back at you.

The main risk categories

Before you sign a contract with a restaurant group, onboard drivers, or update your app checkout, identify the main categories of risk that can arise in a delivery transaction:

• Food preparation risk, such as wrong items, allergens, contamination, poor packaging, or cold food due to preparation delays.
• Delivery risk, such as late drop-off, damaged meals, theft, spillage, or delivery to the wrong address.
• Customer-side risk, such as incorrect addresses, unavailable recipients, chargebacks, or misuse of promotions.
• Platform risk, such as payment processing errors, app outages, system bugs, pricing glitches, or failure to pass on order details.
• Regulatory risk, such as misleading advertising, unfair contract wording, privacy failures, or poor complaint handling.

Why platforms need careful role definitions

Your contract should answer a basic question in plain English: what exactly is your platform providing to the customer?

Some platforms position themselves mainly as a marketplace that connects customers with food merchants and independent couriers. Others are more involved in payment collection, customer support, delivery allocation, and refund decisions. Many sit somewhere in between.

That distinction affects risk allocation. If your platform takes payment in its own name, controls pricing, decides refund outcomes, and presents the whole service as a single branded offer, it may be harder to argue that all food quality responsibility sits elsewhere. A clause that says, “we are only a technology provider”, may not carry much weight if the rest of the customer journey says the opposite.

How this works in founder terms

Picture a Friday night order where the restaurant misses a listed allergen, the driver gets stuck, the customer receives the meal late, and then asks your support team for a refund. Your contract needs to help answer all of these questions:

• Who promised the accuracy of menu descriptions?
• Who is responsible for preparation standards and allergen information?
• Who bears the risk once the order is picked up?
• What happens if delay is caused by traffic, weather, or the restaurant running late?
• Can the customer get a refund, replacement, app credit, or nothing at all?
• What evidence can you ask for before processing a claim?

If those issues are not allocated clearly, your team usually ends up making inconsistent ad hoc decisions, and that is where costs and complaints multiply.

Consumer law still sets the outer limits

A customer contract can allocate risk, but it cannot simply erase rights that New Zealand law gives consumers. If your platform deals with consumers, the Consumer Guarantees Act may apply to the services you provide, and the Fair Trading Act may affect how you describe the service and your legal position.

That means broad statements such as “we are never responsible for anything that goes wrong” are risky. They may be unenforceable, misleading, or both. The better approach is to define the service accurately, limit liability where the law allows, and avoid pretending your platform has no role where it clearly does have one.

Legal Issues To Check Before You Sign

The safest time to fix risk allocation is before you sign a contract, onboard merchants, or release new customer terms in your app. Once complaints start coming in, poor drafting becomes much more expensive.

1. Service description and legal characterisation

Your customer terms should match the real operating model. If you are acting as an agent for merchants for some steps, say so clearly. If you collect payment, administer refunds, or arrange delivery, explain those functions accurately.

In practice, founders should review:

• how the checkout page describes the purchase,
• whose name appears on invoices and receipts,
• who sets prices and promotions,
• who handles complaints and refunds,
• whether the platform or the merchant contracts with the courier.

If the contract says one thing and the user journey shows another, that mismatch creates risk.

2. Refunds, cancellations, and credits

Refund clauses are usually the first place customers look when there is a problem. Vague wording causes friction, especially where a problem may be partly caused by the merchant, the courier, or the customer.

Your customer contract should cover:

• when an order can be cancelled before preparation starts,
• whether cancellation is possible after acceptance by the merchant,
• how missing items, incorrect items, spoiled food, and late delivery are handled,
• whether the remedy is a refund, partial refund, redelivery, or platform credit,
• how quickly a customer must raise the issue,
• what photos or other evidence may be required.

Be careful with “sole discretion” language. You can retain reasonable discretion, but if the process looks arbitrary or inconsistent with consumer rights, it may create problems.

3. Liability caps and exclusions

Liability limits can be useful, but only if they are targeted and realistic. The main aim is usually to cap exposure for indirect or remote losses, while still addressing the kinds of direct issues that actually arise in food delivery disputes.

Founders often want to exclude everything, including illness, damaged property, app failures, or non-delivery. That approach can backfire. A more credible structure may:

• exclude indirect or consequential loss where appropriate,
• cap liability to a defined amount, such as the order value or a stated maximum,
• carve out liability that cannot lawfully be excluded,
• separate food preparation liability from platform service liability, if that reflects the business model.

The wording should be reviewed against New Zealand consumer law and, where needed, a contract review of the actual way the service is delivered.

4. Merchant and courier alignment

Your customer contract only does part of the job. The merchant agreement and courier agreement must support the same allocation of responsibility.

For example, if your customer terms say the merchant is responsible for allergen information and food quality, your merchant agreement should include clear warranties, indemnities, complaint handling obligations, and response times. If your customer terms say the courier bears delivery risk after pickup, your courier contract should deal with handover, delay reporting, and loss or damage in transit.

This is where founders often get caught. They spend time polishing customer terms but leave supplier-side contracts thin, making it difficult to recover losses when the platform absorbs a refund.

5. Consumer Guarantees Act and Fair Trading Act issues

Your terms should not suggest that customers have fewer rights than the law gives them. They also should not make promises your platform cannot consistently deliver.

Review your wording for statements about:

• guaranteed delivery times,
• menu accuracy,
• freshness or temperature promises,
• allergen safety assurances,
• “no refund” rules.

If your marketing says one thing and your legal terms say another, the marketing usually creates the real headache. Operational claims and legal drafting need to line up.

6. Privacy and complaint evidence

Food delivery complaints often involve customer photos, contact details, location information, and communications with drivers or merchants. If your platform collects and uses that information for investigations, your privacy notice and data protection position should be clear.

You should explain what information is collected, why it is used, and who it may be shared with, such as merchants, payment providers, or delivery partners. Your internal process should also control how long complaint evidence is retained and who can access it. This is not just a privacy issue, it also affects how well you can defend or resolve disputes.

7. Payment failures and chargebacks

Chargeback risk is easy to underestimate until volumes increase. Customer contracts should state what happens if a payment is reversed, flagged as suspicious, or processed incorrectly.

Useful clauses often address:

• authority to charge the stated amount and approved adjustments,
• what happens when payment authorisation fails after food has been prepared,
• how duplicate transactions are corrected,
• whether fraudulent use may lead to account suspension.

Your payment terms should also fit your merchant settlement process so losses do not get trapped with the platform.

8. Force majeure and service interruption

Storms, road closures, app outages, and public events can affect delivery performance. A force majeure or service interruption clause can help, but it should be drafted with practical scenarios in mind, not as boilerplate.

If severe weather prevents deliveries in Auckland or Wellington for a few hours, your terms should support pausing services, cancelling affected orders, and offering a fair remedy where payment has already been taken. The wording should be specific enough to be useful in a real incident.

Common Mistakes With Risk Allocation Customer Contract Food Delivery Platform

The most common mistake is trying to push all risk away from the platform on paper, while the business model keeps control over pricing, payments, customer support, and order management. Courts and regulators usually look at substance as well as wording.

Using imported terms that do not fit New Zealand law

Many food delivery businesses start with overseas templates. The trouble is that references to foreign consumer laws, waiver language, or dispute processes may not fit a New Zealand customer relationship. Even where the drafting looks polished, key assumptions can be wrong.

This shows up in clauses that try to exclude non-excludable rights, rely on unfamiliar legal concepts, or use language that feels disconnected from how New Zealand consumers are treated.

Leaving key operational triggers undefined

Founders often say a refund will be available for “material issues” or “delivery failures” without defining what those terms mean in the written terms. Support teams then improvise, and merchants complain that the platform is too quick to credit customers.

Better drafting gives concrete examples and thresholds. If a customer reports a missing drink, a 10 minute delay, or a meal delivered slightly cooler than expected, your process should not depend entirely on whoever answers the ticket.

Failing to separate merchant fault from courier fault

A late order is not always a delivery problem. Sometimes the merchant accepted too many orders, delayed preparation, or packaged items poorly. Sometimes the courier took an inefficient route or waited too long to collect. Sometimes the customer entered the wrong address.

Your contract should reflect these distinctions. So should your internal records. If every issue gets coded simply as “platform complaint”, your ability to allocate cost later becomes weak.

Overpromising in marketing and underdelivering in the contract

“Fastest delivery”, “guaranteed hot meals”, and “perfect order every time” may sound like harmless marketing, but they raise expectations that your legal terms may not be able to contain. The main risk is not just a disappointed customer, it is creating a mismatch between public claims and contractual limitations.

Before you sign a major merchant deal or spend money on setup for a wider rollout, review advertising language alongside the legal terms and your actual operational data.

Ignoring allergen and food safety communication risk

Platforms sometimes assume that food safety is entirely the merchant’s problem. Often the merchant does carry the core responsibility for preparation and ingredient accuracy, but the platform can still create risk if it displays stale menu data, hides warnings, or presents allergen filters in a misleading way.

If your app lets customers rely on dietary tags or allergen notes, your contracts and your product design should deal with:

• who supplies the ingredient and allergen information,
• how often it is updated,
• whether the platform verifies or merely republishes it,
• what customers are told to do where severe allergies are involved.

Not matching legal terms to customer support scripts

Even a well-drafted contract can be undermined by support staff promising full refunds in every case, or telling customers the platform takes full responsibility for merchant errors. Customer communications, standard macros, and escalation rules should match the legal position.

That does not mean taking a hard line with every complaint. It means handling claims consistently and without creating accidental admissions.

Forgetting business-to-business use cases

Some food delivery platforms also service offices, events, or corporate accounts. If you have both consumer and business customers, the risk allocation may need separate treatment. A one-size-fits-all contract can create confusion about who gets what remedies and whether any business-to-business carve-outs apply.

This is especially relevant before you sign catering-style supply arrangements or larger recurring order programmes.

FAQs

Can a food delivery platform contract out of all responsibility to customers?

No. A platform can allocate responsibility carefully, but it cannot simply remove rights that apply under New Zealand law or use misleading wording about its role.

Who should be responsible for food quality, the platform or the restaurant?

Usually the restaurant carries primary responsibility for food preparation, ingredients, and packaging quality, but the platform may still carry risk for how the service is presented, sold, supported, and refunded.

Should customer terms and merchant agreements say the same thing?

They should align closely. If your customer terms promise one remedy but your merchant agreement does not let you recover that cost, the platform often ends up wearing the loss.

Do we need special clauses for delivery delays?

Yes. Delays are one of the most common sources of complaints, so your contract should explain what counts as a delay, when estimates are only estimates, and what remedy applies.

Are app screenshots and photos enough evidence for complaints?

Often they help, but your contract should say what evidence may be requested and your privacy process should explain how that information is handled and shared.

Key Takeaways

• Risk allocation in a customer contract should clearly divide responsibility between the platform, the merchant, the courier, and the customer.
• Your terms need to match the real operating model, especially around payments, order management, customer support, and refunds.
• Liability caps, disclaimers, and refund rules should be drafted with New Zealand consumer law in mind, not copied from overseas templates.
• Merchant agreements and courier agreements should back up the same allocation of risk, including indemnities, warranties, and complaint processes.
• Operational details matter, such as allergen information, delivery delays, evidence requirements, and support team scripts.
• Review the legal terms together with marketing claims, app flows, privacy disclosures, and internal dispute handling before problems scale.

If you want help with customer terms, merchant agreements, liability clauses, privacy wording, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.