You launch the app, the first support email lands, and it's not flattering. The customer says the product does something your homepage promised, but your EULA says the usual legal wall of text should protect you. It won't. If you sell to people in New Zealand, the Consumer Guarantees Act 1993 sits under your product whether you like it or not, and that matters for SaaS, bundled hardware, support, and all the messy bits in between.
That is why consumer guarantees act nz is not a dusty retail topic for founders. It's a live operating rule. The Act came into force on 1 April 1994 and remains in force in its latest version as at 24 January 2026 as set out in the legislation itself. The more practical point is that 89% of respondents in the 2024 New Zealand Consumer Survey said they were aware of it, so your customers are not wandering in blind MBIE survey series. They know the name. Many know the playbook.
If you're building for NZ consumers, treat this like a product constraint, not a legal curiosity. Build for it early, or you'll be reverse-engineering support, refunds, and warranty language after the complaints start.
The first mistake founders make is treating their terms of service like they override everything else. They do not. A SaaS subscription, a mobile app, a hardware bundle, or a setup service sold in New Zealand can trigger the Consumer Guarantees Act 1993 automatically, because the law applies to goods and services supplied by businesses trading here official legislation. Your EULA, your footer, and your “all sales final” line do not erase that.
That is why the first angry email often lands harder than founders expect. The customer does not care how tidy your contract is. They care that the product did not do what was promised, or that it failed when they needed it most. The law focuses on the same thing.
Founders usually spot the problem only after they have shipped. Avoid that mess by building your launch process around consumer-law duties from day one. If you are still setting up the basics, start with this NZ business setup guide and make sure your refund path, support scripts, and escalation process already fit the way NZ consumer law works.
Practical rule: if you are trading with New Zealand consumers, run your operations as though the CGA applies, because it usually does.
MBIE's survey work shows how normal this has become. In the 2024 New Zealand Consumer Survey, 54% said they successfully resolved problems in the previous two years, up from 47% in 2022, while 38% said issues were resolved to their satisfaction in 2024, versus 31% in 2022 MBIE survey series. That tells you the market is active on consumer rights, and businesses are getting better at handling complaints, even if slowly.
For founders, the takeaway is operational. A support team that understands the CGA is faster, calmer, and cheaper than one that tries to improvise after the third complaint.
A tech founder can get the CGA wrong in a hurry by focusing on the contract and ignoring the actual customer experience. For goods, the law is not asking whether the product is merely “not faulty”. It requires acceptable quality, plus fitness for purpose, matching description, and the other consumer guarantees in NZ guidance. For services, including software support, app maintenance, onboarding, and setup work, the service must be carried out with reasonable care and skill, within a reasonable time, and fit the purpose agreed or implied Consumer Protection guidance.
That sounds legal, but the operational takeaway is dead practical. If your API is sold as production-grade, then “it mostly works” is not a good answer. If your onboarding team promises a three-day setup and drags it into week three, that is not just bad service. It can become a consumer-law problem.
For hardware, peripherals, and bundled devices, the description matters. If your landing page says the device works with a certain platform, or your packaging leans hard on durability, those claims can become part of the standard the product is judged against. Tech founders get caught out here all the time. The product was shipped. The promise was not met.
Keep your marketing claims tight and supportable. Do not write cheques your engineering team has not signed. If the device has known limitations, say so plainly. If a product needs a companion app, update dependencies, or firmware support, that belongs in the product story from day one, not buried in a support FAQ nobody reads.
For SaaS, the service side matters just as much as the software itself. A broken onboarding flow, a botched migration, or a support desk that leaves tickets sitting for days can all sit inside the CGA frame if the customer is buying for personal or household use in NZ Consumer Protection guidance. “Reasonable time” is not a vibes-based metric either. Your team needs a real process, not a hopeful shrug.
If your service promise lives in sales decks, your support team needs to know that promise exists.
That is the bit founders miss. The CGA does not sit in legal only. It belongs in product, sales, support, and ops. If those teams are not talking, your risk goes up fast.
Software is where the Consumer Guarantees Act starts to bite in a practical way. Acceptable quality is not a yes-or-no label. It asks whether the product is fit for purpose, free from minor defects, safe, durable, and acceptable in appearance and finish, judged against what a reasonable consumer would expect for that kind of product, including its nature and price. For digital products, that means your app, platform, or bundled device is assessed in context, not as a piece of abstract code.
A lower-priced consumer app will not be judged the same way as a premium platform with premium support. That matters. If you charge more, promise more, and market more, you take on a stricter test. Founders often dislike that. It still applies. Price sits inside the legal analysis.
If your homepage promises “works smoothly across the latest iPhone and Android devices”, that is not just sales copy. It becomes part of the standard your product is measured against if there is a dispute. The same goes for durability claims, repairability claims, and compatibility claims. Say it plainly, and you own it.
Keep a tight line between what you can prove and what you sell. Real-world software gets hit by OS updates, browser changes, API shifts, and the occasional vendor tantrum. That is normal. The legal risk comes from overselling stability you cannot control, or hiding known limitations behind polished copy.
Third-party services change. App store rules shift. Apple and Google roll out updates. You already know this. A dependency failure does not make the customer's problem disappear.
If your app relies on a third-party API and that API changes in a way that breaks core functionality, you still need a plan. The same applies when an OS update knocks out a feature your product depends on. Good founders deal with this through testing, release monitoring, and support scripts that explain the issue clearly instead of sounding defensive. Customers do not care whose API caused the mess. They care whether your product still does the job.
For mobile products, the build and release process needs discipline, not heroics. The practical points in this mobile development guide line up with that reality, especially if your app lives or dies on updates, compatibility, and support handling.
If your checkout or subscription flow also has recurring billing, make sure it is built to comply with California renewal law as well, because sloppy renewals create the same kind of trust problem that bad product quality does.
A SaaS product, a mobile app, or bundled hardware can all sit inside the Consumer Guarantees Act if you are selling in trade for personal or household use. NZ guidance treats software and digital products as part of that picture, so a product never needs to pass through a warehouse to fall under the Act Consumer NZ guidance. Founders who sell digital tools should treat that as the default, not the exception.
The boundaries still matter. Private sales between individuals are outside the Act. Business-use purchases can be contracted out in writing. Auction purchases are also excluded from several key guarantees Consumer NZ guidance. On paper that sounds tidy, but mixed-use customers make the world messier.
A freelancer buying your project management tool for both personal and business use is not a clean edge case you can ignore. The same problem shows up when one account mixes free personal usage with paid business seats. If you do not define the channel upfront, your team will end up arguing about labels instead of solving the complaint.
Get the sales flow, account setup, and terms right before the dispute starts. If your product is business-only, say so plainly and make the paperwork match. If you sell to consumers as well as businesses, assume the consumer channel will pull you into the CGA unless you have a clear written basis for excluding it. Sloppy segmentation turns support into a debate about definitions.
The cleanest way to judge exposure is to ask three questions. Is the product sold in trade. Is the buyer using it for personal or household use. Is there a clear written business-use exclusion. If the answer points toward consumer use, the CGA is likely in play.
That is why founder terms need to reflect the actual channel, not just the legal wrapper. A B2B onboarding form, a consumer checkout, and a reseller agreement need different treatment. If your supply chain is split across software, devices, and fulfilment partners, supply chain compliance for NZ tech companies needs to be mapped alongside the contract terms. It is boring work, but it saves real pain later.
Once a guarantee fails, the clock starts. Under the CGA, the consumer can seek a repair, replacement, or refund at no charge within a reasonable time official legislation. That sounds straightforward until you run a live support queue with hardware returns, billing disputes, angry emails, and a customer who wants an answer yesterday.
So design the remedy path before you need it. If a problem is minor, the supplier can usually choose the remedy. If it is substantial, the consumer may choose. That distinction matters because it affects how your team speaks, what your scripts say, and how quickly you need to move.
Start with a front-line triage rule. Is this a service defect, a product fault, or a misuse issue. Has the customer lost the core benefit they paid for. Is there a repair path that is realistic. Those questions keep your team from promising the wrong thing too early.
Then put the outcome in writing. Not in a defensive way, just cleanly. Record the complaint, the assessment, the remedy offered, and the time it took. If you ever need to show that you acted within a reasonable time, your records matter.
Your incident response timelines are not just customer success fluff. They are part of the legal machinery. If your team says they will respond in 24 hours, or your hardware swap process depends on a courier pickup, that should be mapped against what a reasonable remedy looks like in practice. Slow systems create legal risk, not just grumpy reviews.
For teams handling subscriptions, refunds, or recurring billing, it's also smart to compare consumer-law remedy timing with other regulatory timing rules. A useful reference point is Revcover's guide to comply with California renewal law, because it shows how subscription businesses can get trapped by sloppy cancellation and notice handling. Different law, same operational lesson. If your billing and support flows are messy, you are inviting trouble.
Short version: if a customer has a valid CGA complaint, make the remedy path boringly easy.
That is the goal. Not glamorous. Not clever. Just fast, documented, and fair.
Hardware founders, IoT teams, and importers need to pay close attention here. NZ consumer guidance makes it clear that manufacturers need spare parts and repair facilities reasonably available for a reasonable time after sale, and imported goods can still fall within the manufacturer definition. That pushes responsibility upstream to the entity controlling the product lifecycle, which is where the primary risk sits.
For a SaaS-linked device, this gets messy fast. You may see yourself as a software business, but once your bundle includes hardware, repair and spare-parts obligations sit right beside your app roadmap. Offshore manufacturing and a small local support team make that harder, not easier.
If you are mapping inventory, suppliers, and service commitments for the NZ market, this supply chain resource is a useful starting point.
If you're bringing devices into New Zealand, do not leave the importer role vague. Spell out who handles warranty claims, who funds replacements, who keeps spare units on hand, and who talks to customers when something fails. The CGA follows the supply chain, not just the logo on the box.
Australian companies expanding into NZ often treat this as a copy-and-paste exercise. It is not. Same language, similar customer expectations, different consumer-law obligations, different operational pressure. Your distributor agreement should reflect that reality, because the first broken unit will expose any gap immediately.
A device with sealed components, special batteries, or niche parts is a future support promise, whether you meant it that way or not. If you cannot replace a part reasonably, you are building a compliance gap into the product itself.
That is why founders should bring operations in early, not after launch. Your parts plan, service partner model, and support staffing need to work together. If they do not, the business model looks neat until the first repair batch lands.
Start with the product page. Every claim should be defensible, especially claims about compatibility, durability, support response times, and what the product does. Then check the checkout flow, the T&Cs, and the refund language. If those three things disagree with each other, fix them before launch.
The other move is simple. Revisit the setup whenever you change product scope, pricing, or supply chain structure. A product that started as pure software can drift into hardware, services, or subscriptions with very different risk. Founders do this all the time without noticing, then wonder why support got harder.
If you're not sure whether a specific customer flow or product bundle sits inside the Act, get proper legal advice early. That's cheaper than a fight, and a lot less annoying. You can also keep an eye on official NZ guidance from MBIE and Consumer Protection, because the rules don't live in your head, they live in the market.
NZ Apps helps founders and operators keep track of the NZ tech market, with practical coverage for SaaS, apps, and startup growth across New Zealand and Australia. If you're building for local customers and want more grounded guidance like this, visit NZ Apps and use it as a source of regional context while you sharpen your product, support, and compliance playbook.
Add your NZ or Australian app or tech company to the NZ Apps directory and get discovered by founders and operators across the region.
Get ListedReach tech decision-makers across New Zealand and Australia. Sponsored and dofollow editorial links, permanent featured listings, and sponsored articles on a DA30+ .co.nz domain.
See Options