Marketplace terms and conditions, the essential clauses for Australian platforms

Every marketplace launches with the same moment: a draft set of terms arrives from a solicitor, or you pull a template down and start editing, or a software provider hands you its standard terms and asks you to adopt them. Before you accept any of those, it is worth understanding what the document is actually doing, because the decisions buried in it decide who wears the cost when a sale goes wrong, who owns the content, and who gets named in the proceedings.

Marketplace terms and conditions are the contract between the platform operator and every user, buyer and seller alike. Their operational job is to fix the platform's role as an intermediary, allocate risk between the operator and its users, and make disputes between users a matter between users. What they cannot do is contract the operator out of the Australian Consumer Law (ACL), which is Schedule 2 of the Competition and Consumer Act 2010 (Cth) (the CCA). The ACL's consumer guarantees cannot be excluded by any term, and an unfair term in a standard form consumer or small business contract is void and can now attract a pecuniary penalty. That constraint shapes every clause below.

The essential clauses

Stating who the platform is, and who it is not

The first clause a reader should look for is the one that states the platform's role. It should set out the purpose of the marketplace, the categories of users (sellers, buyers, service providers, clients), and how each category is permitted to interact. For an e-commerce marketplace, that means mapping what sellers can list and what buyers can do in response, whether that is buying at a stated price, bidding, or booking a service.

The central drafting choice is the intermediary statement. The terms should say, in plain language, that the platform operator is not a party to any agreement between users, that users contract directly with each other, and that the operator only provides the facility through which they deal. That clause is the foundation for the disclaimers and liability caps that follow, and it tells users where to direct their complaints.

The trap is treating that clause as a magic shield. Whether the operator is treated as the supplier of goods listed on the platform under the ACL depends on the substance of what it actually does, not the label in the terms. An operator that takes title to goods, sets prices, or handles fulfilment as principal can be treated as a supplier regardless of what the contract says. The role clause must therefore match the operating model, and the operator's own statements about its role must not be misleading, because misleading or deceptive conduct is prohibited by s 18 of the ACL.

Setting the ground rules for accounts and conduct

If the platform has user accounts, the terms need to spell out who can hold one and what each type of account allows. A seller's merchant account will usually permit uploading products or services for sale and advertising; a buyer account typically only permits purchasing and communicating.

The clause should cover:

• Eligibility and verification: who can join, what information must be provided, and whether the operator can require identity or business verification.
• Prohibited listings: sellers must warrant that what they list is legal, that they hold the licences and rights to the goods, services and content, and that listings meet the platform's criteria.
• Suspension and termination: the operator's right to suspend or remove accounts, with a stated process and reasonable notice where funds or listings are affected.
• Sellers' own terms: sellers may adopt their own delivery, returns and refund terms, and the platform should require them to publish and honour those terms, without taking responsibility for them.

The drafting trap here is one-sidedness. An account clause that lets the operator suspend a seller and hold funds indefinitely, without notice or process, is exactly the kind of term that can be challenged as unfair, particularly when the seller is a small business. State the trigger, the process and the timeframe.

How the platform gets paid

Payment terms depend on the platform's model. The main structures are:

• Freemium: free use of the marketplace, with fees for optional extras such as promoted listings or advertising.
• Subscription: access on a recurring basis, usually monthly, payable in advance by direct debit.
• Transaction fees: payments direct between users, with the operator taking a percentage for facilitating the transaction.

Whatever the model, the terms should state the fee, when it is charged, and who pays it, and users should warrant that they are authorised to make the payments they initiate. Where the platform facilitates payment, it should also allocate risk for the payment channel: the operator will usually disclaim liability for non-payment between users and for failures of third-party payment gateways such as Stripe or PayPal, and should say expressly who bears chargeback costs and reversal losses. A user who pays a subscription by direct debit should be told how to cancel, because renewal and cancellation mechanics are a common source of complaints.

Who owns the content on the platform

Intellectual property clauses do two jobs. First, they protect the platform's own assets: the software, the database, the branding and the underlying analytics. Users should get a limited, revocable licence to use the platform for its intended purpose, and an express prohibition on copying content, scraping the database, or building a copycat platform from the data.

Second, they deal with user generated content. Users typically own the content they upload, or warrant that they have the rights to it, and grant the operator a licence to host, display and reproduce it for the purpose of operating the marketplace, including the right to remove it. Without that licence, the operator can infringe copyright simply by republishing listings. The terms should also require users to warrant that their content does not infringe third-party rights, and the platform should maintain a process for handling takedown requests for allegedly infringing content.

Where the platform's responsibility ends

The disclaimer section is where the intermediary role clause pays off. It should state that all interactions and agreements between users, including sales, communications and the quality of goods or services supplied, are matters between users, and that the platform operator is not liable for them. From that flow the specific disclaimers:

• no liability for the condition, legality, suitability or content of goods or services listed by sellers;
• no endorsement of any user, product or service advertised on the marketplace;
• users are responsible for providing true and accurate information, and the operator accepts no liability for the accuracy of information uploaded by users.

The limit on this section is that disclaimers only work where the operator genuinely is an intermediary. They cannot cover the operator's own services, conduct or representations. A platform that tells users it has no responsibility for anything, while processing payments, holding funds and promoting sellers, will find the disclaimer under pressure. The ACCC's action against Valve Corporation shows the regulator's approach to terms that overstate a platform's rights and understate consumers'. Valve's Steam subscriber agreement represented that consumers had no entitlement to refunds in any circumstances, the Federal Court found the representations misleading, and Valve was ordered to pay a penalty of $3 million: Australian Competition and Consumer Commission v Valve Corporation (No 7) [2016] FCA 1553.

Capping how much the platform will pay

On top of the disclaimers, the terms should cap the operator's liability. The standard structure is an aggregate cap for all claims equal to the fees paid by the user in the preceding 12 months, or a nominal amount where no fees have been paid, together with an exclusion of indirect and consequential loss.

Two constraints apply. The first is the unfair contract terms regime. A term of a standard form consumer or small business contract is void if it is unfair, which means it causes a significant imbalance in the parties' rights and obligations, is not reasonably necessary to protect the legitimate interests of the party advantaged by it, and would cause detriment if relied on: s 23 and s 24 of the ACL. Since 9 November 2023, proposing or relying on an unfair term is itself a contravention carrying a pecuniary penalty: s 23(2A) and s 23(2C) of the ACL. For a body corporate the maximum is the greater of $100 million, three times the benefit obtained, or 30% of adjusted turnover, and for an individual it is $2.5 million: s 224 of the ACL. A cap that is transparent, proportionate to the fees the user pays, and does not swallow statutory rights is far more defensible than a blanket exclusion.

The second constraint is s 64 of the ACL: a term is void to the extent it purports to exclude, restrict or modify the consumer guarantees. The narrow exception in s 64A of the ACL allows a supplier of services not of a kind ordinarily acquired for personal, domestic or household use to limit liability for a guarantee failure to re-supplying the services or paying the cost of re-supply, but only where it is fair and reasonable to rely on the term. In practice this means the cap should be tiered rather than blanket: full compliance with guarantees for consumers, a s 64A-style re-supply limit for business users, and a fees-based cap for everything else.

The guarantees the platform cannot contract out of

This is the section most marketplace terms get wrong. The platform supplies services to its users, whether that is hosting listings, matching buyers and sellers, processing payments, or providing the platform itself, and where those services are supplied to a consumer, the guarantees in ss 60 to 62 of the ACL apply: services will be rendered with due care and skill, be fit for the purpose made known, and be supplied within a reasonable time.

If the platform's services fail those guarantees in a way that is a major failure, the consumer's rights are statutory and cannot be removed. Under s 268 of the ACL a failure is a major failure where, for example, the services would not have been acquired by a reasonable consumer fully acquainted with the nature and extent of the failure, or where they are substantially unfit for their common purpose and cannot be easily remedied within a reasonable time. Where there is a major failure, the consumer may terminate the contract and obtain a refund for the part of the services not yet consumed: s 267 and s 269 of the ACL. Alternatively, the consumer may keep the contract and recover compensation for the reduction in the value of the services below the price paid.

Any term that tells consumers they have no rights, or that frames the guarantees as discretionary, is void under s 64 of the ACL and is now a compliance risk as well. Valve's $3 million penalty was for exactly this drafting failure: a platform agreement that said consumers had no entitlement to refunds in any circumstances. The lesson is to state the guarantees accurately, set out a refund and complaint process that honours them, and never ask consumers to waive them.

The promises users make back to the platform

Indemnities run the other way. An indemnity is a promise to hold the platform harmless, meaning the user pays out if a third party makes a claim against the operator because of the user's conduct. The two that matter most for a marketplace are:

• Seller indemnity: the seller indemnifies the operator against claims by buyers arising from the seller's goods, services or conduct, for example a claim about faulty goods.
• General user indemnity: each user indemnifies the operator against loss arising from the user's use of the marketplace or breach of law, including infringement of third-party rights such as uploading content the user does not own.

The drafting points are scope and interaction. The indemnity should state whether it is capped, whether it survives termination, and how it interacts with the liability cap. An indemnity is also only as good as the indemnifier's capacity to pay, which is why seller verification, and in some models holding funds or escrow, matters: a dissolved seller cannot indemnify anyone.

How disputes between users are resolved

The terms should set out a dispute resolution path so that most disagreements are handled between users, with the operator playing a defined and limited role. A typical structure is an internal complaint process on the platform, then mediation or another form of alternative dispute resolution, then the courts, with governing law and jurisdiction stated, for example the laws of New South Wales.

The trap is requiring consumers to give up access to the courts. A mandatory binding arbitration clause, or a clause forcing users into expensive private dispute processes or foreign forums, can be challenged as an unfair term in a standard form consumer contract. Draft the clause to give the operator a facilitation role, not a gatekeeping one, and keep the consumer's statutory remedies intact.

Optional clauses worth adding for specific marketplaces

These clauses are not essential for every platform, but they are worth adding where the operating model touches them:

• Privacy collection notice: most marketplaces collect personal information about users, so link a privacy policy and comply with the Australian Privacy Principles under the Privacy Act 1988 (Cth).
• Auto-renewal and subscription terms: if users pay by subscription, set out the renewal date, notice period and cancellation method in plain language, which also helps the terms withstand an unfair terms challenge.
• Ratings and reviews policy: state who may post reviews, what is prohibited, and how removal requests are handled, to manage defamation and fake-review risk.
• Chargeback and fraud allocation: assign who bears chargebacks, reversal costs and fraud losses between the operator, the seller and the buyer.
• Platform downtime and service levels: allocate risk for outages, maintenance windows and degraded performance, particularly where users pay for access.

How an Artificer Legal practitioner would review your marketplace terms

An Artificer Legal practitioner starts by mapping the operating model, because the terms must match the mechanics. Who takes payment, who holds funds, who handles fulfilment, who resolves disputes: if the document says one thing and the platform does another, the mismatch creates the exposure the terms were meant to prevent.

From there we would review the risk-bearing clauses in a set order. First the role and intermediary statements, because everything else hangs off them. Then the liability architecture: the disclaimers, the cap, and the consumer guarantee clauses, checked against s 64 and s 64A of the ACL and the unfair contract terms regime. Then the indemnities, making sure they are capped and consistent with the liability clause. Then the payment mechanics and the boilerplate: variation, termination, governing law and dispute resolution.

We would push back on blanket "not liable for anything" drafting, unilateral variation clauses without notice, indemnities that swallow the cap, and mandatory arbitration for consumers. We would insist on tiered liability, transparent caps, a functioning dispute ladder, and indemnities that align with how the platform actually vets its sellers. Given the penalty regime that now attaches to unfair terms, and the ACCC's active interest in platform practices, this is not drafting to leave to a template.

Draft the liability clause as a layered defence, not a blanket

The clause that most often decides whether a set of marketplace terms works is the liability clause, and it is also the one most often misdrafted. Operators reach for a blanket exclusion of everything, which is void against the consumer guarantees, exposed under the unfair contract terms regime, and useless in the one dispute that matters, because a court will simply disregard it. A layered clause, which honours the guarantees for consumers, uses the s 64A re-supply limit for business users, caps other claims at fees paid, and is transparent about what it does, is enforceable and does the job the operator actually needs: ringfencing genuine intermediary risk without pretending statutory rights do not exist.

Summing up, a set of marketplace terms should state the platform's role as intermediary, set the ground rules for accounts, payments, content and conduct, disclaim responsibility for user-to-user dealings, cap the operator's liability in a way that survives the ACL, honour the consumer guarantees, take indemnities from users, and provide a workable dispute path. Drafted together, those clauses keep most problems between users, where the operator wants them.