IP Assignment Clauses for Software Resellers in New Zealand

If you resell software in New Zealand, an IP assignment clause can quietly rewrite who owns what in your deal. Founders often sign reseller terms assuming they are only getting permission to market and distribute the product, then later discover the contract says all adaptations, customer feedback, implementation materials, or even locally developed integrations belong to the vendor. Another common mistake is treating an assignment clause as interchangeable with a licence. It is not. A licence gives permission to use IP, while an assignment transfers ownership.

This matters most before you sign a contract, before you accept the provider's standard terms, and before you rely on a verbal promise that "you still own your custom work". If you are building add-ons, localising software for the New Zealand market, preparing training content, or investing in customer-facing materials, the wording can affect your business value, your bargaining position, and your ability to keep servicing clients if the relationship ends. This guide explains what an IP assignment clause for software reseller arrangements usually covers, the legal issues to check, and the mistakes that catch businesses out.

Overview

An IP assignment clause decides whether ownership of certain intellectual property moves from one party to another. In a software reseller agreement, that can affect more than the core software code. It can also reach implementation documents, custom developments, local branding assets, technical know-how, customer-requested modifications, and reseller-created content.

• Check exactly what IP is being assigned, including source code, object code, documentation, templates, integrations, data structures, training materials, and derivative works.
• Confirm the difference between ownership and permission to use, and whether you are receiving a licence back after any assignment.
• Review whether customer feedback, bug reports, feature requests, and improvements automatically become the vendor's property.
• Look at termination clauses to see what happens to assigned IP, customer support rights, and access to materials after the reseller arrangement ends.
• Make sure confidentiality, privacy, moral rights, and third party IP obligations line up with the assignment wording.
• Check whether the clause is consistent with how the parties actually work, especially where the reseller creates local collateral, custom code, or implementation workflows.

What IP Assignment Clause for Software Reseller Means For New Zealand Businesses

An IP assignment clause for software reseller deals is about ownership, not just access. If the clause is broad, you may hand over valuable assets you assumed were part of your own business.

In plain English, a software reseller usually sits somewhere between pure sales agent and technology partner. Some resellers simply market a vendor's product and pass orders through. Others install, configure, customise, train, support, or build connected tools around the software. The more work you do around the product, the more important the IP wording becomes.

Assignment versus licence

A licence lets someone use intellectual property under set conditions. An assignment transfers ownership. That distinction matters because ownership usually includes the right to control, modify, enforce, sell, and license the IP.

If your agreement says you assign all rights in improvements, localisation materials, custom scripts, onboarding documents, or reseller-developed modules, those assets may no longer be yours even if your team created them. If the clause instead says the vendor gets a licence to use those materials, you may still retain ownership while allowing the vendor to use them in defined ways.

What counts as intellectual property in these deals

Founders often think only about software code. In practice, IP in a reseller arrangement can be much broader.

• Copyright in code, manuals, training guides, screenshots, videos, and support content
• Trade marks, logos, product names, and brand assets
• Databases, taxonomies, workflows, and system architecture
• Custom connectors, APIs, plug-ins, and implementation scripts
• Product improvements, modifications, and derivative works
• Know-how, methods, and internal documentation

Under New Zealand law, IP ownership often starts with the creator or, in some employment situations, the employer. But contracts can change the commercial position significantly. That is why a signed software reseller agreement matters more than assumptions made during sales discussions.

Typical reseller scenarios where the clause matters

The clause becomes commercially important when the reseller adds something of its own. This is where founders often get caught.

For example, you might create a New Zealand specific compliance template, redesign the onboarding flow for local customers, write training modules for a niche sector, or build a connector into a local payments platform. If your agreement assigns all modifications, derivative works, and related materials to the vendor, those outputs may be transferred automatically.

That can affect:

• Your ability to reuse the materials with other clients
• Your leverage in renegotiating the reseller arrangement
• The sale value of your business if a buyer expects you to own your implementation assets
• Your ability to keep supporting customers after termination
• Your exposure if you promised customers rights you did not actually have

Why New Zealand businesses should care early

In smaller markets like New Zealand, resellers often wear multiple hats. You may be the local sales channel, implementation partner, trainer, and first line support team all at once. That means your team creates commercially useful material around the software, sometimes without realising it has standalone value.

If you sign broad vendor paper before you invest in branding, before you build support resources, or before you commit developer time to integrations, you can end up funding assets that someone else owns. The issue is not only legal. It can also shape margins, customer retention, and exit value.

Legal Issues To Check Before You Sign

The main legal question is simple: what exactly are you giving away, and what rights do you keep? The safest approach is to map each type of IP in the relationship and match it to a clear ownership and licensing outcome.

1. Define the assigned IP precisely

Watch for vague phrases like "all intellectual property connected with the services" or "all works arising out of the relationship". Those phrases can sweep in far more than intended.

The contract should state clearly whether the assignment covers:

• The vendor's pre-existing software only
• Reseller-created modifications to that software
• Separate tools or scripts created by the reseller
• Marketing materials, demo environments, and training content
• Implementation templates and customer documentation
• Feedback, ideas, requests, and suggestions

If the clause is too broad, ask for a schedule or carve-out for your pre-existing materials and any independent tools your business uses across multiple clients.

2. Separate pre-existing IP from new IP

Your business may already own templates, playbooks, connectors, and internal deployment methods before the reseller deal starts. Those assets should be identified as your background IP and excluded from any assignment unless you genuinely intend to sell them.

New IP created during the relationship should also be split into sensible categories. For example, the vendor might own changes to its core platform, while the reseller keeps ownership of generic implementation tools, training decks, and reusable customer success resources.

3. Check whether there is a licence back

If you do assign anything, you may still need ongoing rights to use it. Without a licence back, you could transfer ownership of materials that you need to service clients.

Before you sign, confirm whether the contract gives you:

• A perpetual or fixed-term right to use assigned materials
• The right to modify and update those materials
• The right to use them for existing customers after termination
• The right to sublicense use where necessary for customer delivery

This is especially important where the vendor wants ownership of localised training material or custom workflows that your team needs in day to day delivery.

4. Review derivative works and improvements language

Derivative works clauses are often where the real transfer happens. A clause that gives the vendor ownership of all improvements and derivative works can capture a lot of practical output.

Look closely at whether "improvements" includes:

• Configuration changes
• API mappings and field structures
• Plug-ins and middleware
• Client-specific reporting setups
• Industry templates and standard operating procedures

If your business model depends on creating repeatable implementation assets, this wording needs careful negotiation.

5. Consider moral rights and authorship issues

Where individuals create copyright works, contracts sometimes ask them to consent to certain acts affecting moral rights. This can matter for developers, designers, and content creators involved in the reseller relationship.

The key point for the business is consistency. If your company promises to assign materials created by staff or contractors, your own internal contracts should already give you the rights you need. Otherwise, you may promise the vendor ownership that your business does not fully control.

6. Check contractor and subcontractor chains

Many resellers use freelance developers, implementation consultants, or specialist trainers. If those people create part of the relevant IP, your agreement with them should clearly deal with ownership, confidentiality, and permitted use.

Before you rely on a verbal promise, make sure your contractor documents cover:

• Who owns work product created for your business
• Whether pre-existing contractor tools are excluded
• The right for your business to assign or license deliverables onward
• Confidentiality and data handling obligations

7. Align the clause with privacy and customer commitments

Software reseller relationships often involve customer data, implementation records, and support logs. An IP clause should not accidentally suggest ownership of personal information or customer content in a way that conflicts with privacy obligations.

Under the Privacy Act 2020, businesses handling personal information need clear and lawful practices around collection, use, storage, and disclosure. IP ownership and data rights are different concepts. The contract should not blur them, and should align with any privacy notice provided to customers.

8. Match the clause to termination rights

Termination is where assignment clauses become painful. If the reseller relationship ends, can you still support current clients, use training documents, or maintain integrations you developed?

Check the post-termination position for:

• Existing customer contracts
• Access to assigned or licensed materials
• Rights to continue support for a transition period
• Obligations to return or destroy confidential materials
• Use of brand assets and product references

If the contract cuts off all rights immediately, your operational risk may be far higher than expected.

9. Review representations, warranties, and indemnities

If you assign IP or promise that deliverables do not infringe third party rights, that promise should match reality. Overly broad warranties can expose your business if an integration, code library, image asset, or contractor deliverable contains third party rights you did not fully clear.

The Fair Trading Act 1986 can also matter if reseller marketing overstates what rights customers receive. Sales teams should not promise ownership, transferability, or custom rights that the contract does not support.

Common Mistakes With IP Assignment Clause for Software Reseller

The biggest mistake is assuming the vendor's template reflects how your business actually operates. Standard reseller terms are often drafted for maximum control, not for the reseller's long term value.

Confusing ownership with permission to use

Many businesses see wording that allows them to "use" materials and assume that means they still own them. It does not. You need to identify whether the contract says licence, assignment, transfer, or vesting of rights.

If the vendor owns the asset and merely allows you to use it while the agreement lasts, your position can disappear when the relationship ends.

Ignoring locally created value

Resellers often invest heavily in local adaptation. That may include New Zealand spelling and terminology, sector-specific templates, onboarding scripts, customer FAQ packs, and support workflows.

These assets may look operational rather than legal, but they can become part of your intellectual property stack. If you give them away without thinking, you may reduce what makes your business distinctive.

Failing to carve out pre-existing materials

A broad assignment clause can swallow tools you built long before the reseller relationship. This is common where businesses use standard implementation templates or reusable code snippets across products.

Your pre-existing IP should be identified clearly. If possible, attach a schedule or define background materials in the agreement.

Overlooking customer-facing promises

The reseller agreement is only one part of the picture. Your own customer contracts also matter.

If your customer terms say the client will own custom work, but your vendor agreement says the vendor owns all derivatives and improvements, you may be stuck in the middle. This mismatch can trigger disputes, rework costs, and awkward renegotiations.

Not checking contractor paperwork

Founders sometimes negotiate a careful reseller contract, then lose control because a contractor retained ownership of key code or documents. The chain of title has to work from creator to your business, and then from your business to the vendor or customer if required.

This is particularly relevant if you use offshore developers or ad hoc consultants to build integration components or implementation materials.

Accepting broad feedback clauses without limits

Some agreements say all ideas, suggestions, and feedback you provide become the vendor's property with no payment and no restrictions. That may be acceptable for casual product comments, but less so where your team is effectively contributing strategic product development insights.

If your business creates significant know-how through client work, consider whether feedback wording should be narrowed or balanced.

Forgetting the exit scenario

Founders often focus on getting the deal signed and assume the relationship will continue smoothly. But before you sign, you should test what happens if the vendor changes channel strategy, raises fees, or ends the arrangement.

If you cannot keep using implementation assets, support tools, or local documentation after termination, your customer relationships may be exposed.

FAQs

Is an IP assignment clause the same as an IP licence?

No. An assignment transfers ownership. A licence gives permission to use IP under stated conditions while ownership stays with the original owner unless the contract says otherwise.

Can a software reseller own customisations it creates for clients?

Yes, sometimes. It depends on the contract wording. A reseller agreement can say the vendor owns all customisations, or it can let the reseller keep ownership and grant the vendor a licence. The customer contract may also affect the commercial arrangement.

Does an IP assignment clause cover training materials and onboarding documents?

It can. If the definition of assigned IP includes documentation, derivative works, or materials created in connection with the services, training content and onboarding documents may be included unless they are carved out.

What should New Zealand resellers do before signing standard vendor terms?

Review ownership, licence back rights, pre-existing IP carve-outs, contractor IP arrangements, termination rights, and customer contract consistency. Do this before you accept the provider's standard terms and before you invest time creating local assets.

Can a reseller keep using assigned materials after the agreement ends?

Only if the contract allows it. Some agreements grant ongoing rights for existing customers or a transition period, while others stop use immediately on termination.

Key Takeaways

• An IP assignment clause for software reseller arrangements can transfer ownership of much more than software code, including documentation, integrations, templates, and improvements.
• The key legal issue is whether the contract creates an assignment or a licence, and what rights the reseller keeps after any transfer.
• Before you sign, identify pre-existing IP, define new IP categories clearly, and check whether there is a workable licence back.
• Make sure your contractor agreements, employee arrangements, customer contracts, confidentiality terms, and privacy position all line up with the reseller agreement.
• Termination rights matter. If the relationship ends, you need clarity on support rights, existing customers, and continued use of materials.
• Standard vendor terms often overreach. Negotiating carve-outs and practical usage rights early is usually much easier than fixing the issue later.

If you want help with reseller agreements, IP ownership carve-outs, contractor IP clauses, and termination rights, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.