Black Friday10% off any legal service

Website Development Contract Checklist For Ecommerce Sites

byAlex Solo9 min read

Am I signing a website build contract that actually protects my online store? Yes, if it deals with the things that make ecommerce different from an ordinary brochure website.

A standard website developer agreement can be a useful starting point, but an online store has extra moving parts: payment gateways, product data, stock feeds, shipping rules, platform accounts, privacy, and launch timing. If those details are vague, you can end up paying for a site that looks finished but can't take orders properly.

The good news is this doesn't have to be complicated. A clear ecommerce build contract should tell everyone what is being built, who owns what, what happens if something is delayed, and what support you get once the site goes live.

What Should An Ecommerce Website Development Contract Cover?

Your ecommerce website development contract, sometimes called a website development agreement, should cover the scope, price, timing, ownership, integrations, testing, handover and post-launch support. If you're searching for an ecommerce website development contract in NZ, this is the practical starting point.

An ecommerce site is usually more than pages and design. Your contract should spell out the store features that affect sales, including checkout, discount codes, product filters, abandoned cart emails, stock levels, payment options and shipping rules.

Templates often miss these details because they're written for general websites. A template can help you organise your thoughts, but the final document should be tailored to your platform, products and launch plan.

Fill-In Outline For Your Ecommerce Build Contract

  1. Parties: Write the legal names, NZBNs if relevant, and contact people for your business and the developer.
  2. Platform: Name the platform, such as Shopify, WooCommerce, BigCommerce or a custom build, and who will hold the account.
  3. Scope: List each page, feature, integration, product import, checkout requirement and reporting function.
  4. Milestones: Set dates for discovery, design approval, development, testing, content loading, launch and handover.
  5. Fees: State the fixed fee or rate, what is included, when invoices are issued and when payment is due.
  6. Changes: Explain how out-of-scope work is requested, quoted and approved before work starts.
  7. IP And Data: Say who owns code, design files, content, product data, customer data and custom features.
  8. Third-Party Tools: Identify plugins, themes, stock images, hosting, payment gateways and licences.
  9. Testing And Acceptance: Set out the tests the site must pass before you accept it and pay the final amount.
  10. Support: Include warranty periods, response times, maintenance, security updates and handover materials.

If you're engaging an individual freelancer rather than a development company, also think about contractor status. The Employment Relations Act 2000, including 2026 changes introducing a contractor gateway test, can affect whether a worker is treated as a contractor or employee. The label in the contract helps, but it isn't the only thing that matters.

Who Owns The Website IP And Product Data?

You shouldn't assume you own everything just because you paid for the website. Your contract needs clear IP ownership and digital product licence terms, especially for code, design, copy, images and product data.

In New Zealand, copyright is governed by the Copyright Act 1994. Ownership can depend on what was created, who created it, whether it was commissioned, and what the contract says. For an ecommerce build, the safest approach is to state the ownership position clearly in writing.

Your contract should deal with three buckets of IP.

  • Your business materials: Your logo, brand name, product descriptions, product photos, customer lists and product database should remain yours.
  • Custom work created for you: If the developer creates custom code, design files, templates or content for your store, say whether ownership transfers to you on payment or whether you receive a licence.
  • Developer tools and third-party assets: Developers often use pre-existing code libraries, themes, plugins, open source software and stock media. You may only receive a licence to use these, and that licence may have conditions.

Product data deserves its own line. If your developer imports 1,200 SKUs, rewrites product descriptions, cleans up variants and maps stock codes to your inventory system, the contract should say who owns the finished product database and who can export it.

Trade marks are separate again. If you're launching a new brand, you can search and apply through IPONZ. Your developer shouldn't register domains, social handles or platform accounts in their own name unless the contract requires them to transfer them to you.

How Should You Set The Project Scope And Launch Dependencies?

Your project scope should be detailed enough that both sides can tell whether the site has been delivered. Vague wording like build ecommerce website is rarely enough.

Start with the outcome you need, then break it into concrete deliverables. For example, rather than saying product catalogue, say 350 products imported from CSV, including product name, SKU, price, GST setting, images, variants, stock status and collection tags.

Scope Items To Confirm

  • Number of pages, templates and product types
  • Product import format and who cleans the data
  • Variant rules, such as size, colour, bundles or subscriptions
  • GST, shipping, discount and gift card settings
  • Search, filters, related products and upsell features
  • Customer accounts, guest checkout and email notifications
  • Reporting dashboards and analytics setup
  • Training, admin access and handover documents

Launch dependencies are the tasks that must happen before the site can go live, but aren't always fully controlled by the developer. These might include your bank approving a merchant account, your courier account being activated, your product data being ready, or your team approving content.

Say you run a Wellington homewares store and agree to a $18,000 ecommerce build. The developer's contract says launch is 1 May, with a 40 percent deposit, 30 percent after the staging site is ready, and 30 percent on launch. If your product spreadsheet is two weeks late and the payment gateway approval is still pending, the developer may not be able to launch on 1 May. A good contract says how the timeline moves when a delay is caused by missing information or third-party approval, rather than leaving you to argue about it later.

This is where a software project scope checklist earns its keep. It turns assumptions into decisions before work starts.

What Should The Contract Say About Payment Gateways And Integrations?

The contract should name each payment gateway and integration, then explain who is responsible for setup, approvals, testing and ongoing fees in your customer contracts. This is one of the biggest differences between a normal website build and an ecommerce build contract.

Your site may need to connect with several systems, including:

  • payment gateways such as Stripe, Windcave, PayPal or Afterpay
  • merchant accounts or bank facilities
  • POS and inventory systems
  • accounting software
  • shipping and courier platforms
  • email marketing tools
  • Google Analytics, Meta Pixel or other advertising tags
  • marketplaces or social commerce channels

For each integration, ask four practical questions.

  1. Who owns the account? Your business should usually own key accounts, not the developer.
  2. Who pays the fees? Platform fees, plugin subscriptions, gateway fees and app charges should be clear.
  3. Who supplies access? The contract should say what logins, API keys or permissions you need to provide.
  4. What does tested mean? A payment gateway should be tested with successful payments, failed payments, refunds and order confirmation emails.

Privacy also matters here. If your website collects names, addresses, phone numbers, payment information or browsing behaviour linked to a person, the Privacy Act 2020 applies. Your contract should require sensible security measures, limit access to customer information and make the developer tell you promptly if there's a suspected privacy or security incident.

If a privacy breach is notifiable under the Privacy Act 2020, your business may need to notify the Privacy Commissioner and affected people as soon as practicable. Your developer's cooperation can be crucial, so build that cooperation into the contract.

What Happens If The Build Is Delayed Or The Site Has Bugs?

Your contract should set out what happens when there's a delay, defect or missed milestone, rather than leaving it to goodwill. Ecommerce launch delays can affect marketing campaigns, seasonal stock and cash flow.

A fair contract usually separates delays into categories. Developer delays might include slow development, missed review deadlines or a failure to fix agreed defects. Client delays might include late product data, slow approvals, missing brand assets or delayed payment gateway setup. Third-party delays might include hosting outages, app issues or merchant account approval.

For bugs, focus on severity and response. Not every issue should stop launch, but checkout problems usually should.

Bug Categories That Work Well

  • Critical: Customers can't place orders, payment fails, customer data is exposed, or the site is unavailable.
  • High: A major feature doesn't work, such as shipping rules, product filters or stock syncing.
  • Medium: The site works, but there are issues with layout, emails, analytics or minor functionality.
  • Low: Cosmetic issues that don't stop sales or core operations.

The contract should say how long the developer has to fix each type of bug. If you don't want to use fixed timeframes, at least require urgent attention for critical checkout, payment and security issues.

You should also include an acceptance process. For example, you might have five business days to test the staging site and provide a single list of issues. If the developer fixes the agreed issues and the site passes the acceptance tests, the final milestone becomes payable. This keeps feedback organised and makes it harder for either side to move the goalposts.

If something has already gone wrong, keep records first: project emails, approved scope, invoices, screenshots, test results and dates of missed milestones. Then compare the issue against the contract before deciding your next step.

What Support, Security And Compliance Terms Do You Need After Launch?

You need support terms that cover the first few weeks after launch, plus any ongoing maintenance you expect the developer to provide. The launch date isn't the finish line for an ecommerce site.

Your website terms and agreement should say whether support is included, how long it lasts, and what counts as support rather than new work. For example, fixing a checkout bug discovered after launch may be included, while adding a loyalty programme may be a paid change request.

Post-Launch Terms To Include

  • Warranty period: A period for fixing defects in the delivered work.
  • Response process: Where you lodge issues, who responds and what information you need to provide.
  • Security updates: Who updates plugins, themes, platform settings and software versions.
  • Backups: Who is responsible for backups and restoring the site if something breaks.
  • Admin access: Your level of access to the platform, hosting, domain, analytics and integrations.
  • Training: What training is provided so your team can update products, prices, promotions and content.
  • Exit support: What happens if you move to another developer later.

Legal compliance should also be addressed, but be realistic about who is responsible for what. Your developer can build fields, checkboxes, links and checkout flows, but your business is usually responsible for the actual legal content and claims on the site.

For an online store in New Zealand, your site should be set up to support compliance with laws such as the Fair Trading Act 1986, Consumer Guarantees Act 1993, Privacy Act 2020 and Unsolicited Electronic Messages Act 2007. That might include clear pricing, accurate product descriptions, accessible website terms and conditions, privacy notices, marketing consent wording and unsubscribe functions.

If the developer is also writing product copy or promotional claims, the contract should say those claims must be accurate and based on information you approve. Under the Fair Trading Act 1986, misleading pricing or product claims can create problems for your business even if a contractor drafted the words.

Key Takeaways

  • An ecommerce website development contract should go beyond design and pages. It needs to cover checkout, payments, products, integrations and launch dependencies.
  • Don't assume you own all website IP, code, design files or product data. Put ownership and licence terms in writing.
  • Your scope should list practical deliverables, such as product imports, shipping rules, payment testing and analytics setup.
  • Payment gateways and integrations need clear responsibilities for account ownership, fees, access, approvals and testing.
  • Use a clear process for delays, bugs, acceptance testing and post-launch support so your store can keep trading.
  • Your website build should support New Zealand compliance obligations, especially privacy, consumer guarantees, fair trading and marketing consent rules.

If you'd like help with your ecommerce website development contract, IP ownership terms, privacy and launch compliance, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

Alex Solo
Alex SoloCo-Founder

Alex is a co-founder of Sprintlaw. 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.

Need legal help?

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.