How New Zealand Online Marketplaces Should Allocate Risk in Customer Contracts

Online marketplaces sit in an awkward spot. You are often not the seller of record, but customers still see your brand, use your checkout, and complain to you first when something goes wrong.

That creates a real contract problem: if your customer terms do not clearly allocate risk, your marketplace can end up carrying losses you never priced for.

Founders often make the same mistakes. They copy generic platform terms from overseas, they rely on broad disclaimers that may not work under New Zealand law, and they leave key issues vague, such as refunds, chargebacks, delivery failures, product defects, and account suspensions. Another common trap is assuming your supplier or vendor agreement solves the issue, while the customer contract says something different.

The answer is not to push every risk onto the customer. The answer is to allocate risk carefully, in plain language, and in a way that matches how your marketplace actually operates. This guide explains what risk allocation means in a customer contract for a New Zealand online marketplace, which legal issues to check before you sign, and the contract drafting mistakes that most often cause disputes.

Overview

A well-drafted marketplace customer contract should identify who is responsible for each part of the transaction, when your platform steps in, and where your liability should stop. In New Zealand, that drafting also needs to sit alongside consumer law, fair trading rules, privacy obligations, and the practical reality that customers usually deal with the platform first.

• Define whether your business is an agent, intermediary, reseller, or direct supplier in each transaction.
• Spell out responsibility for listings, pricing, fulfilment, delivery, refunds, chargebacks, and customer support.
• Use liability caps, exclusions, and indemnities that are clear, proportionate, and consistent with New Zealand law.
• Check that your customer terms match your vendor or seller agreements, payment provider terms, and operational processes.
• Address consumer protection, misleading statements, privacy handling, and account suspension powers in plain English.

What Risk Allocation Customer Contract Online Marketplace Means For New Zealand Businesses

Risk allocation is the part of the customer contract that says who wears the cost when something goes wrong. For an online marketplace, that usually means dividing responsibility between the platform, the customer, and the third party seller or service provider.

This matters because marketplace businesses are structurally exposed. Even if you never hold stock, customers may still expect you to fix late deliveries, poor quality goods, payment issues, data incidents, and fraudulent listings. If your contract is silent or inconsistent, your business may be pulled into disputes that should have sat elsewhere.

Your contract should match your business model

A marketplace can operate in several different ways. Some platforms only introduce buyers and sellers. Others process payments, set marketplace rules, manage communications, arrange shipping, or handle refunds. Some businesses look like a marketplace on the front end but act more like a reseller behind the scenes.

The legal drafting has to reflect that reality. If you say you are only a facilitator, but your marketing promises a guaranteed buying experience and your support team approves refunds, the contract may not line up with what customers were led to expect.

Before you sign a contract or publish terms, be clear on questions such as:

• Who forms the sale contract with the customer?
• Who sets the price and product description?
• Who takes payment and when?
• Who arranges delivery or performance of services?
• Who handles returns, refunds, and complaints?
• Who bears the loss if a seller breaches the rules or disappears?

Typical risk areas in marketplace customer terms

The main risk is rarely one single disaster. It is usually a string of smaller disputes that cost time, refunds, staff effort, processor fees, and reputational damage. Good customer terms deal with those pressure points directly.

Common risk allocation issues include:

• Product or service quality, including defects, delays, or services not performed properly.
• Accuracy of listings, stock availability, and pricing errors.
• Payment failures, chargebacks, and fraudulent transactions.
• Delivery losses, damaged goods, or missed service appointments.
• Platform outages, booking system failures, and messaging issues.
• Misuse of accounts, suspicious conduct, and breach of marketplace rules.
• User-generated content, reviews, and seller representations.
• Privacy and data handling across the platform and third party sellers.

New Zealand law still limits what you can contract out of

Your contract can allocate risk, but it cannot simply erase legal obligations. If your marketplace deals with consumers, New Zealand consumer law may still apply regardless of what the terms say. The Consumer Guarantees Act 1993 and the Fair Trading Act 1986 are especially relevant in many marketplace settings.

For example, broad wording that says the platform is never responsible for anything may not be enough if your conduct, branding, or checkout experience makes customers reasonably think they are dealing with you. Claims about product quality, delivery timing, or refund rights also need to be accurate and not misleading.

If you are dealing business to business, there may be more room to negotiate and limit statutory protections in some cases, but that needs to be done properly and with clear written terms. This is where founders often get caught, especially before they accept the provider's standard terms or roll out a one-size-fits-all contract to both consumers and business users.

Risk allocation is not just about limiting liability

A strong contract does more than cap claims. It also sets process rules that reduce disputes in the first place. That can be just as valuable as a liability clause.

Useful process provisions often cover:

• How and when customers must report a problem.
• What evidence is required for refunds or complaints.
• When the marketplace may investigate and pause payouts.
• How account suspensions and cancellations work.
• What happens if a seller does not respond.
• When the platform can remove listings or reverse transactions.

If those mechanics are missing, your team may end up making case-by-case calls under pressure, which creates inconsistency and increases legal risk.

Legal Issues To Check Before You Sign

Before you sign, the customer contract should say plainly what your marketplace is promising and what it is not. The safest drafting comes from mapping real operational risk, not from pasting in a generic limitation clause.

1. Contract structure and who the parties are

The first issue is basic but often missed: who is actually contracting with whom? If a customer buys from a third party seller through your platform, your terms should explain whether the sale contract is between the customer and the seller, and what separate role the marketplace plays.

If your platform also offers its own products or services, that should be distinguished clearly. Mixed models need careful contract drafting so customers can tell when they are buying from the marketplace and when they are buying from another seller.

2. Consumer Guarantees Act and Fair Trading Act exposure

Consumer law can override overconfident disclaimers. If customers are consumers, the way your platform is marketed and operated may affect whether obligations attach to you, the seller, or both.

Check whether your contract and customer-facing communications align on:

• who supplies the goods or services;
• who is responsible for repair, replacement, or refund pathways;
• what delivery or performance timeframes are promised;
• whether any statements could be misleading about quality, availability, or rights.

If the practical experience says “buy from us”, a clause buried in the terms saying “we are only an intermediary” may not solve the problem.

3. Liability caps and exclusions

A liability clause works best when it is specific. New Zealand businesses often weaken their own protection by using sweeping language that a court may read narrowly, especially if the clause is hard to understand or does not match the surrounding terms.

Think about allocating liability by category. You may want one approach for platform downtime, another for seller misconduct, and another for payment processing issues. You should also consider whether the cap should be tied to fees paid through the platform, a fixed dollar amount, or a claim-specific measure.

Common drafting points include:

• excluding indirect or consequential loss where appropriate;
• capping direct loss to a sensible amount;
• carving out matters you should still stand behind, such as your own fraud or deliberate misconduct;
• making sure the clause works with refund provisions and dispute processes.

4. Indemnities and reimbursement rights

Indemnities can shift loss back to the party that caused the problem, but they need to be used carefully. A customer indemnity might help where a user posts unlawful content, breaches marketplace rules, or causes losses through fraud. A seller indemnity is often even more important where the seller controls product quality, fulfilment, and legal compliance.

The key is to draft indemnities around specific risks, not as a vague catch-all. Overly broad indemnities can be harder to rely on and may create unnecessary friction in negotiation.

5. Refunds, chargebacks, and payment allocation

This is where many marketplaces lose money quietly. If your customer contract says one thing, your seller agreement says another, and your payment processor takes a third position, the platform often absorbs the gap.

Before you rely on a verbal promise from an operations provider or payment partner, make sure your documents cover:

• when a customer is entitled to a refund;
• whether marketplace fees are refundable;
• who bears chargeback losses and investigation costs;
• whether payouts can be delayed or clawed back;
• what happens if fraud is suspected.

6. Suspension, termination, and platform discretion

Your contract should give the marketplace room to act quickly where there is fraud, safety risk, repeated breaches, or legal exposure. At the same time, the power should not look arbitrary.

Spell out the circumstances in which you may suspend an account, remove a listing, pause an order, or terminate access. Include what happens to pending transactions and stored credits or balances. These termination rights matter most when a serious issue has already happened, so ambiguity is expensive.

7. Privacy and data sharing

Marketplaces often collect customer data at the platform level and then share some of it with sellers to complete orders or services. That creates both contract and Privacy Act issues.

Your customer terms should be consistent with your privacy notice on what data is collected, why it is shared, and who is responsible for handling it once shared. If sellers receive personal information, your seller-side arrangements should also deal with acceptable use, security, and complaint handling.

8. Dispute handling and evidence

A dispute process is part of risk allocation. If the contract says nothing about evidence, timeframes, or who makes the first decision, the platform may be stuck mediating every disagreement without a clear basis for action.

Useful provisions may cover notice periods, evidence standards, internal review steps, temporary holds on funds, and the marketplace's right to make a final operational decision pending further resolution.

Common Mistakes With Risk Allocation Customer Contract Online Marketplace

The most common mistake is pretending the marketplace has no real role in the transaction when the customer experience says otherwise. Courts and regulators tend to look at substance as well as labels.

Using overseas marketplace terms without NZ tailoring

Many founders start with terms built for the United States, the United Kingdom, or a global software platform. Those documents often use legal concepts, consumer law assumptions, and enforcement language that do not fit New Zealand.

Even where the clause looks familiar, the legal effect may be different here. New Zealand customer contracts should be checked against local consumer law, fair trading rules, and the way local businesses handle refunds and complaints.

Separating customer terms from operational reality

This is where founders often get caught before they accept the provider's standard terms. The legal document says the marketplace never handles refunds, but the support team has authority to issue them. The contract says delivery is solely the seller's problem, but your brand promises tracked shipping and delivery support.

If your operations team does one thing and the contract says another, the written terms become much less useful in a dispute.

Drafting liability clauses too broadly

A clause that tries to exclude every possible claim can backfire. It may be hard to read, easy to challenge, and less persuasive than a narrower clause that clearly allocates specific risks. A court is more likely to respect sensible, targeted drafting than sweeping language that looks unfair or unrealistic.

Forgetting seller-side consistency

Your customer contract is only half the picture. If your seller agreement does not mirror the customer-facing risk allocation, the marketplace can become the default payer.

Examples of mismatch include:

• the customer contract promises refunds, but the seller agreement does not require the seller to reimburse them;
• the platform can remove listings, but the seller contract does not allow withholding payouts after a breach;
• the customer terms allocate listing accuracy to sellers, but the seller contract does not include a matching warranty or indemnity.

Ignoring edge cases

Standard transactions are easy. Disputes usually arise from unusual facts, such as partial delivery, fake accounts, duplicate orders, promotional pricing errors, cross-border sellers, or allegations that a review is defamatory or false.

Your contract does not need a clause for every imagined problem, but it should give the platform enough discretion and process control to manage edge cases fairly.

Relying on contract wording instead of clear communication

Risk allocation starts before the customer clicks “accept”. Pricing pages, checkout copy, FAQ text, and support messages can all shape expectations. If the headline promise is broader than the contract, the promise may drive the dispute.

That is especially relevant under fair trading rules. Marketing and help centre wording should be reviewed with the contract so they all tell the same story.

FAQs

Can an online marketplace in New Zealand say it is never liable for seller conduct?

Not safely in every case. A marketplace can limit its role, but broad “no liability” wording may not hold up if the platform's branding, checkout, or support model makes customers think they are dealing with the marketplace itself, or if consumer law applies.

Do customer terms need to be different for consumers and business users?

Often, yes. Consumer-facing terms usually need extra care because statutory protections may apply and cannot simply be waived. Business to business arrangements may allow more flexibility, but the drafting still needs to be clear and fair.

Should refunds be dealt with in the customer contract or only in seller terms?

Both. The customer contract should explain the customer's process and rights, while the seller agreement should say who funds the refund and when the platform can recover losses or pause payouts.

What is the biggest drafting issue for marketplaces?

The biggest issue is inconsistency. If your customer terms, seller terms, payment processes, and support practices do not match, the platform usually ends up carrying the commercial risk.

Do privacy issues affect risk allocation?

Yes. If customer information is shared between the marketplace and sellers, the contract should reflect who collects it, why it is shared, and what each party must do to handle it properly.

Key Takeaways

• Risk allocation in a customer contract decides who bears loss when a transaction on your marketplace goes wrong.
• Your contract should reflect your actual business model, especially whether you act as an intermediary, agent, reseller, or direct supplier.
• New Zealand consumer and fair trading laws can limit how far you can rely on disclaimers and liability exclusions.
• Clear drafting on refunds, chargebacks, delivery issues, suspensions, and dispute processes often prevents more problems than a generic limitation clause.
• Your customer terms must line up with seller agreements, payment provider arrangements, support scripts, and public marketing statements.
• Practical, specific clauses usually work better than broad “we are not responsible for anything” wording.

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