What is an OEM agreement?
Our OEM agreement covers three kinds of deal. In a software product deal, the OEM bundles the software into its own software, such as a text-recognition (OCR) engine inside a document-management system. In a device deal, the OEM installs it in hardware, including as firmware, such as the code inside an alarm panel or a vehicle tracker. In an embedded SaaS deal, the OEM hosts the software and offers its functions as part of its own online service.
SaaS (software as a service) is software that customers use over the internet. The royalty is paid per unit, per unit in advance, or as a share of the OEM’s sales.
The OEM’s customers accept the provider’s own end-user licence directly, or take a sublicence from the OEM that protects the provider at least as well. A sublicence is a licence the OEM grants under its own licence from the provider.
The OEM gives its customers first-line support: it is their first point of contact for help. The provider gives the OEM second-line support: the deeper technical help behind it.
We draft the agreement for either side, the provider appointing an OEM or the OEM signing up. How an OEM deal compares with white-label, reseller and value-added reseller deals is in our guide to choosing a software channel agreement.
One naming trap: in manufacturing, “OEM supply” also describes a factory that makes goods for a brand owner to sell. That is a different contract, a manufacturing & supply agreement.
How an OEM deal works
Follow each line from the party it starts with. Pick another deal to see what changes.
Name on the product
The OEM’s. The provider’s only if co-branding is agreed.
The customer buys from
The OEM, as part of its own product only.
Terms the customer accepts
The provider’s licence terms, or a sublicence from the OEM that the provider approved.
Money between the two
The OEM pays the provider a royalty: per unit, prepaid or a revenue share.
Help for the customer
The OEM, at first line.
The provider gives the OEM second-line support.
Is an OEM agreement legally binding in South Africa?
Copyright. Under section 11B of the Copyright Act 98 of 1978, only the copyright owner may copy or adapt a computer program, or authorise others to. Every unit or installation the OEM ships carries a copy, so the licence must cover every copy.
Section 22(8) is what makes the customers’ licences work: use that the OEM authorises, within the terms of its own licence, counts as licensed by the provider. Our agreement keeps the copyright licence non-exclusive, even when the OEM’s appointment is exclusive. If a deal does grant an exclusive licence, section 22(3) gives it effect only if it is in writing and signed by the licensor.
Who owns new code written during the deal depends first on who controlled its making, because the author of a computer program is the person who exercised control over making it. A business that directs and approves a contractor’s work can be the author (Haupt v Brewers Marketing Intelligence [2006] ZASCA 40, para 41). Giving requirements, reviewing progress and testing the result is not enough (Bergh v Agricultural Research Council [2020] ZASCA 30). So we never rely on authorship: a signed agreement decides who owns custom work.
Competition. The provider and the OEM are in a vertical relationship, “the relationship between a firm and its suppliers, its customers or both” under section 1 of the Competition Act 89 of 1998.
Exclusivity and non-compete terms between them are judged on their effect under section 5(1). Stricter rules apply where the provider is dominant in its market (s 8), or where the provider and the OEM compete with each other (s 4). Setting a minimum price for the OEM’s product is banned outright (s 5(2)). Our guide to competition law in software channel deals covers these rules.
Consumer protection. Under the Consumer Protection Act 68 of 2008 (CPA), goods include “software, code or other intangible product written or encoded on any medium, or a licence to use any such intangible product”. A business is a “producer” if, “by applying a personal or business name, trade mark, trade description or other visual representation on or in relation to the goods”, it has created a reasonable expectation that it made them (s 1). So by branding the finished product, the OEM is likely to be treated as its producer.
Under section 61, if unsafe or defective goods harm a consumer, the producer, importer, distributor and retailer in the chain that supplied that consumer can be liable without proof of negligence. That is subject to the defences in section 61(4). The OEM agreement cannot take that liability away from an injured person. It can only decide which side finally carries the loss.
Our agreement also records the facts that decide whether the deal is a franchise under the CPA, and we do not use it where the deal would be one: see when a software partner deal turns into a franchise.
Cross-border deals. Royalties paid to a foreign provider raise withholding tax, and moving intellectual property across the border raises exchange control: see our guides to withholding tax on international software payments and exchange control for software deals.
“(3) No assignment of copyright and no exclusive licence to do an act which is subject to copyright shall have effect unless it is in writing signed by or on behalf of the assignor, the licenser or, in the case of an exclusive sublicence, the exclusive sublicenser, as the case may be. … (8) Where the doing of anything is authorized by the grantee of a licence or a person deriving title from the grantee, and it is within the terms, including any implied terms, of the licence for him to authorize it, it shall for the purpose of this Act be deemed to be done with the licence of the grantor and of every person, if any, upon whom the licence is binding.”
“a person may because of his control over the making of a computer program be the author of that program even if the creator of the program is an independent contractor.”
“(1) Except to the extent contemplated in subsection (4), the producer or importer, distributor or retailer of any goods is liable for any harm, as described in subsection (5), caused wholly or partly as a consequence of— (a) supplying any unsafe goods; (b) a product failure, defect or hazard in any goods; or (c) inadequate instructions or warnings provided to the consumer pertaining to any hazard arising from or associated with the use of any goods, irrespective of whether the harm resulted from any negligence on the part of the producer, importer, distributor or retailer, as the case may be. … (3) If, in a particular case, more than one person is liable in terms of this section, their liability is joint and several. (4) Liability of a particular person in terms of this section does not arise if— … (b) the alleged unsafe product characteristic, failure, defect or hazard— (i) did not exist in the goods at the time it was supplied by that person to another person alleged to be liable; … or (d) the claim for damages is brought more than three years after the— …”
“The practice of minimum resale price maintenance is prohibited.”
When you need an Original Equipment Manufacturer Agreement
- You make a product — a software package, a device or an online service — and want to build in another company’s engine, toolkit, library or firmware and supply the result under your own brand.
- You own a software component and want software houses, device makers or online services to build it into their products for a royalty, without losing control of your code or your brand.
- A partner asks to be your only OEM in a territory, and you need to price that exclusivity with a minimum royalty.
- The finished product will reach consumers — a vehicle tracker, a security or medical device, a smart-home gadget — so a fault in the built-in software could injure someone or damage property.
- The product is connected to the internet, so security updates must reach units and customers already in the field on a fixed timetable.
- The royalties cross a border: a South African OEM paying a foreign provider, or a South African provider licensing its software to an OEM abroad.
What an Original Equipment Manufacturer Agreement should contain
Licence: copy, supply and pass on to customers
The agreement lets the OEM copy your software as needed to build, test, install and support its products. It gets object code only, the machine-readable form. It may supply the software only as part of those products. Each customer must accept your end-user licence or a sublicence you approve. The agreement names each product the software goes into, and a new product is added only by a signed change. Every copy shipped is a reproduction, which section 11B of the Copyright Act reserves to you, so the licence must cover every unit. The OEM may use contract manufacturers and its usual distributors. They must be bound by terms that protect you as well as the agreement does.
Royalties, statements and audit
Choose one royalty model: per unit, per unit paid in advance, or a share of the OEM’s net sales. The rates are stated amounts, adjusted each year only by the consumer price index if the agreement says so. The OEM sends a signed royalty statement for every reporting period and an annual reconciliation, and you may audit its records once a year. Royalties are paid within 30 days of your invoice. You may suggest a price for the OEM’s product, but only as a recommendation: the OEM sets its own prices.
Exclusivity, the minimum royalty and competing products
The appointment can be exclusive, meaning you appoint no other OEM in the territory, though you may still supply your own customers. An exclusive appointment always carries a minimum royalty, and a shortfall has one stated consequence. A promise that the OEM will not sell competing products applies only while the agreement runs, names the kinds of functionality it covers, and records your reason for it. We never include it where you and the OEM compete with each other, and there is no restraint after the agreement ends. On a non-exclusive appointment we first check your position in the market, because a dominant business faces stricter rules. The rules behind this are on our competition law page.
Support, updates and security patches
The OEM gives its customers first-line support and you give the OEM second-line support, with response times from 1 hour for a critical fault. Support is included in the royalty or charged as an annual fee. You give the OEM every update, upgrade and new version at no charge beyond the royalty and any support fee. You flag each security update. The OEM ships it within a period set by the model: 7 days for embedded SaaS, 14 days for a software product and 30 days for device firmware. You support the current major version and the one before it for at least 36 months, then give 12 months’ notice before stopping.
Warranties, open source and indemnities
You warrant that each release matches its documentation for 6 months. You also warrant that it contains no malicious code and that you may license it. You list the open-source components and give a software bill of materials with each release. You cover the OEM against claims that your software infringes someone else’s rights, including claims against its customers that the OEM must meet. The OEM covers you against claims about its own components, harm its product causes other than through your software as supplied, and promises it makes beyond your terms. Each side’s liability is capped, with a higher cap for infringement, confidentiality, personal information and indemnity claims.
Branding and the franchise check
Under white label, the OEM’s marks alone appear on the product. Under co-branding, the OEM shows your marks and an agreed credit, such as “powered by” your brand, under a free trade mark licence, your brand guidelines and your approval of its marketing. Under section 38 of the Trade Marks Act 194 of 1993, use of your registered mark under licence counts as your own use. Either way, the OEM keeps the copyright and open-source notices built into the software. The agreement records the facts that decide whether the deal is a franchise, and each side must report a change within 10 business days.
Personal information
You may handle personal information for the OEM, for example when you give support by remote access. If so, the two of you sign a separate data processing agreement before you start. In an embedded SaaS deal, the OEM may handle its customers’ personal information for them while you handle it for the OEM. You are then the OEM’s sub-operator under POPIA (the Protection of Personal Information Act): a business that handles personal information for another business that itself handles it for its customers. You must then report a data incident to the OEM within 24 hours, a period set by the contract. Our POPIA in software channel deals page explains the roles.
Ending, escrow and the installed base
The agreement runs for a fixed term, with or without renewal. Customer licences granted before the end continue, and you keep earning the royalty on them. Unless you cancel for the OEM’s breach, your support continues for a monthly fee, and the OEM may sell remaining stock during any sell-off period the agreement sets. Escrow means an independent agent holds a copy of your source code. If the agreement includes it, the agent releases the code to the OEM only on the events the escrow agreement lists, so the OEM can keep supplying its existing customers. The OEM keeps paying for that supply, less the cost of the support you no longer give. An OEM building your software into devices or an online service should ask for escrow.
OEM vs white-label vs reseller vs value-added reseller (VAR) agreement
| Agreement | What the customer buys | Whose customer terms apply | Whose brand the customer sees | Who supports the customer | How the provider is paid |
|---|---|---|---|---|---|
| OEM agreement | The OEM’s own product, with the provider’s software built in and supplied only as part of it | The provider’s end-user licence, or the OEM’s sublicence that protects the provider at least as well | The OEM’s. The provider’s only if co-branding is agreed | The OEM at first line, the provider at second line | A royalty: per unit, per unit in advance, or a share of the OEM’s net sales |
| White-label agreement | The provider’s whole hosted platform, sold as the partner’s own service | The partner’s own customer contract, which must carry the provider’s minimum terms | The partner’s. The provider is hidden, credited as “powered by”, or co-branded. Some legal notices may still name it | The partner at first line, the provider at third line. Second line as agreed | Per user, per customer, a revenue share or a committed amount |
| Reseller agreement | The provider’s own product, bought from the reseller in the reseller’s name | The provider’s end-user terms, unchanged | The provider’s | The provider. The reseller gives at most first-line support | The agreed price the reseller pays for each product; the reseller sets its own resale price |
| Value-added reseller (VAR) agreement | The provider’s product, resold by the VAR with its own integration, hardware, services or hosting | The provider’s terms, unless the provider approves a sublicence by the VAR | The provider’s | The VAR at first line, with the provider’s second-line support behind it where agreed | Fees for each product the VAR resells; the VAR earns its margin and charges for its own work |
Common South African pitfalls
- Using a reseller, value-added reseller or white-label template for an OEM deal. Those agreements assume the customer buys the provider’s own product or platform. An OEM deal needs a licence to copy the software into every unit, customer terms that reach the OEM’s customers, a royalty and support that runs behind the OEM. Get the structure wrong and the OEM may ship units it had no right to copy.
- A licence that forgets the customers. Some grants let the OEM build the software in but say nothing about the customers’ licences, or let them end with the OEM agreement. That puts every installed unit at risk. Section 22(8) of the Copyright Act protects only use the OEM was entitled to authorise, so the customer terms and their survival after the end must be written in.
- Exclusivity agreed informally, or without a price. Exclusivity promised on a call or in an unsigned term sheet is hard to prove and easy to dispute. Put the exclusive appointment, its territory and products, and the minimum royalty that pays for it in the signed agreement. If an exclusive copyright licence is granted instead, it has no effect unless it is in writing and signed by the licensor (Copyright Act, s 22(3)).
- Treating the minimum royalty as a sales target. A clause that obliges the OEM to sell a set number of units, and lets the provider claim damages when it does not, invites a fight about penalties. We draft the minimum as part of the price, with no duty to sell and one stated consequence for a shortfall.
- Pricing clauses that breach the Competition Act. A clause fixing a minimum price for the OEM’s product is minimum resale price maintenance, which section 5(2) prohibits outright. A suggested price must be clearly a recommendation only. Where the provider and the OEM compete, a promise not to sell competing products, or a split of customers or territories between them, can be prohibited outright.
- Assuming a business-to-business deal escapes the Consumer Protection Act. Software and a licence to use it can be goods under the CPA, and the OEM, by branding the product, is likely to be treated as its producer. If the product harms a consumer, businesses in the chain that supplied that consumer can be liable without proof of negligence, subject to the statutory defences. Without indemnities split by cause, insurance and a quick-reporting duty, the OEM can end up paying for a defect in the provider’s software.
- No deadline for security updates. A provider that fixes a vulnerability achieves nothing until the fix reaches devices and customers in the field. Our agreement sets shipping periods by model, shortest for online services and longest for device firmware, instead of one period for every product.
- Forgetting tax on cross-border royalties. Before a South African OEM pays royalties to a foreign provider, check withholding tax: see our guide to withholding tax on international software payments.
Frequently asked questions
What are the three kinds of OEM deal: software product, device and embedded SaaS?
Our OEM agreement takes one of three models. In a software product deal, the original equipment manufacturer (OEM) bundles your software into its own software. In a device deal, it installs your software in hardware, including as firmware: the built-in software that runs a device. In an embedded SaaS (software as a service) deal, it hosts your software and offers its functions in its own online service, without giving customers a copy. Each model needs its own agreement.
What is the difference between an OEM agreement and a white-label agreement?
A white-label partner sells your whole hosted platform under its own brand, as its own service. An original equipment manufacturer (OEM) builds your software into a bigger product of its own, such as text-recognition software inside a document system, or the built-in software of a device. It supplies your software only as part of that product and pays you a royalty on what it sells. Our guide to choosing a software channel agreement compares every model.
Is an OEM a value-added reseller (VAR) if it is exclusive or adds its own work?
No. A value-added reseller (VAR) resells your software under your brand, alongside its own work. An original equipment manufacturer (OEM) builds your software into its own product and supplies it only as part of that product. On our agreements, a partner that embeds your software signs an OEM agreement, whether or not it is exclusive and whatever it adds. An exclusive reseller goes onto our VAR agreement, but an exclusive OEM stays on our OEM agreement. That is how we draft, not a rule of law.
How are OEM royalties worked out: per unit, prepaid or revenue share?
Our OEM agreement uses one of three models. Per unit: a fixed rand amount for each unit sold, such as R450 for each device the software is installed on. Prepaid: the same per-unit royalty, paid in advance as a lump sum. Each unit sold uses up part of it, and a new lump sum is paid once it runs out. Revenue share: a percentage of the original equipment manufacturer’s net sales (sales less the deductions the agreement allows). The percentage can change at set rand levels as sales grow. Rates are stated amounts, never whatever the provider’s price list says at the time.
What is a minimum royalty in an OEM deal, and is it a sales target?
A minimum royalty is the least the original equipment manufacturer (OEM) pays you in a royalty year, the yearly period the agreement sets. It is not a sales target: our agreement says the OEM need not make any level of sales. We draft it as part of the price, and an exclusive appointment always needs one. The agreement picks one consequence for a shortfall. Either the OEM pays the difference, or it loses exclusivity unless it pays, or it loses the agreement unless it pays. You cannot claim damages for it, and a shortfall you caused does not count.
How do royalty statements and audits work in an OEM deal?
A royalty statement, or royalty report, is the original equipment manufacturer’s signed account of what it sold and the royalty due. Our agreement requires one for each monthly or quarterly period, within 15 business days, even when nothing is due. It shows units, sales, deductions and any tax withheld. Once a year a reconciliation checks that the year’s statements add up. You may audit once in any 12 months, on 20 business days’ notice, through an independent chartered accountant. The OEM pays for the audit if it underpaid by more than 5%.
What can an OEM deduct from net sales before it pays a royalty?
Only what the agreement lists, and nothing else. The allowed deductions are VAT and other taxes on the sale; trade, quantity and cash discounts; credits for returned products; and bad debts written off. A bad debt counts as a sale again if it is later recovered. Each deduction must appear on an invoice or credit note and actually be given. Deductions other than taxes can be capped, for example at 15% of gross sales. Sales between companies in the original equipment manufacturer’s own group count either at the price an outside customer would pay, or only when the group company resells.
Can the provider raise the royalty rate during an OEM deal?
Not on its own. Our OEM agreement fixes the royalty as stated amounts and does not allow a “current rate” or a one-sided price change. The only built-in increase is a yearly rise in line with inflation, measured by the consumer price index (CPI) published by Statistics South Africa, if the agreement includes it. Each 1 January, the per-unit rate and the minimum royalty then move with CPI. Any other change needs both sides to agree in writing.
If I appoint an OEM exclusively, does it get an exclusive licence to my software?
No. Under our OEM agreement the OEM can be your only OEM in the territory (an exclusive appointment). But its permission to copy your software, the copyright licence, is always non-exclusive. Exclusivity is your promise not to appoint anyone else to build your software into products in the territory. You may still supply your own customers there. An exclusive appointment always comes with a minimum royalty. If a deal does grant an exclusive copyright licence, the Copyright Act gives it effect only if it is in writing and signed by the licensor, the one granting it.
Do the OEM’s customers have to accept the provider’s licence terms?
Yes, one way or another. Under our OEM agreement, each customer either accepts your end-user licence directly, or takes a sublicence from the original equipment manufacturer (OEM) on terms that protect you at least as well and that you approve. A sublicence is a licence the OEM grants under its own licence from you. Under the Copyright Act, what the OEM permits its customers to do, within its own licence, is treated as done with your permission. So the OEM’s right to sublicense must be in the agreement.
Can the provider change its end-user licence for products the OEM has already shipped?
No. Under our OEM agreement, you may issue a new version of your end-user licence on 60 days’ written notice, or 90 days for devices. The new version applies only to products supplied to customers after the notice period. Units made, or promised to customers in writing, before then keep the old terms. A new version may not reduce the rights of the original equipment manufacturer (OEM) or significantly increase its obligations.
Who supports the OEM’s customers, the OEM or the provider?
The original equipment manufacturer (OEM). It gives first-line support, meaning it is the customer’s first point of contact: installation help, recording faults, first diagnosis and support of its own components. It may not send customers to you unless you agree. You give the OEM second-line support, the deeper technical help behind it: you diagnose the faults it passes on to you and provide a fix or a workaround (a temporary way around the problem). Response times run from 1 hour for a critical fault to 2 business days for a minor one.
How fast must an OEM ship the provider’s security updates?
Within set periods that depend on the model. When you release an update, you say whether it is a security update, meaning it fixes a vulnerability rated critical or high, or one being actively exploited. The original equipment manufacturer (OEM) must then get it to customers within 7 days for embedded SaaS, 14 days for a software product or 30 days for device firmware. Other updates get 30 days for embedded SaaS, 90 days for a software product and 180 days for device firmware. A longer period for a particular update can be agreed in writing.
How long must the provider keep supporting software built into an OEM’s product?
At least 36 months from delivery, under our OEM agreement. In that time you may stop support only by cancelling the agreement because the original equipment manufacturer (OEM) breached it. You support the current major version and the one before it. After 36 months, you must give 12 months’ written notice before stopping. If the agreement ends, support continues for a monthly fee. It runs until 36 months from delivery or 12 months after the end, whichever is later. If the OEM chose to leave, it may ask for up to 6 months.
How long is the warranty on software supplied to an OEM?
Six months from delivery of each release, under our OEM agreement. During that time you promise (warrant) that the software matches its documentation and specifications. The original equipment manufacturer (OEM) reports a fault within 20 business days of finding it, and you fix or replace the software within 20 business days. If you do not, the OEM may end the agreement for the affected products and get back fees paid in advance. Malicious code, such as a virus, must be removed within 5 business days.
What happens to open-source code inside the software an OEM builds in?
Open-source code is software anyone may use, copy, change and share under its licence. Our OEM agreement makes you list each open-source component, with its version and licence. With each release you give a software bill of materials (SBOM): a list of every component with its supplier, version and licence. Some open-source licences could force the original equipment manufacturer (OEM) to publish its own code. Code under such a licence needs the OEM’s written approval, after legal review. You replace a component that breaks its licence within 20 business days.
How does an OEM deal work when the OEM hosts the software in its own online service?
This is embedded SaaS, or software as a service. The original equipment manufacturer (OEM) hosts your software on servers it controls, or a hosting provider controls for it, and offers its functions as part of its own service. Customers never get the software itself. The royalty is counted per agreed unit, such as each vehicle subscribed to the service each month. Security updates must reach the service within 7 days. When the agreement ends, the OEM may keep serving existing customers until their current subscription ends, still paying the royalty.
What does a “powered by” credit mean in an OEM deal?
It means the original equipment manufacturer (OEM) names your software in its product, for example “Powered by” your brand on a screen or the packaging. Our OEM agreement offers two branding models. White label: only the OEM’s trade marks (its brand names and logos) appear, and it may name you only where the law requires or you consent. Co-branding: the OEM shows your marks and the agreed credit under a free licence to use your trade marks, your brand guidelines and your approval of its marketing. The OEM never trades under your marks.
What happens if the provider is bought by the OEM’s competitor?
Under our OEM agreement, each side must tell the other within 10 business days when someone takes control of it, for example by buying it. If the new owner competes with the other side’s business, that side may end the agreement on 60 days’ written notice. It must give that notice within 60 days after it is told or learns of the change. So an original equipment manufacturer (OEM) whose provider is bought by a rival can leave, and the same applies the other way round. Customers’ licences continue after the end.
Who is liable if a product with the provider’s software built in injures someone?
Possibly both. Under the Consumer Protection Act, software and a licence to use it can be goods, and a business that brands a product is likely to be treated as its producer. If unsafe or defective goods harm a consumer, the producer, importer, distributor and retailer in the chain that supplied that consumer can be liable even if no one was careless (without proof of negligence), subject to defences the Act allows. Where more than one is liable, the consumer may claim the full amount from any of them. Our agreement splits the loss by cause, but cannot reduce the consumer’s claim.
Can the OEM or the provider end an OEM agreement early, and what does it cost?
Yes, if the agreement allows ending for convenience, meaning leaving without any breach. Either side may then give at least 90 days’ written notice. Each side’s termination charge is stated separately, as a percentage of the fees for the rest of the term. Those fees are worked out from the average monthly royalties and other fees over the past 12 months. One of our sample agreements uses 25% for the original equipment manufacturer (OEM) and 35% for the provider. A charge may be zero, but the agreement must always state it.
What happens to customers’ devices and installations when the OEM agreement ends?
They keep working. Under our OEM agreement, customer licences granted before the end continue on their terms, and you keep earning the royalty on them. In an embedded SaaS deal, the original equipment manufacturer (OEM) may keep serving existing customers until their current subscription ends. Unless you cancel for the OEM’s breach, your support continues for a monthly fee, and the OEM may sell remaining stock during any sell-off period, 90 or 120 days in our sample agreements.
Who owns the integration work and customisations in an OEM deal?
Our OEM agreement leaves ownership where it starts. You keep every right in your software, documentation and source code, including every release. The original equipment manufacturer (OEM) keeps every right in its own components and in the parts of its product that are not your software. The agreement transfers no ownership. For new code nobody has agreed on, the author is usually the first owner. For a computer program, the author is whoever controlled its making. Directing and approving a contractor’s work can amount to control. Giving requirements, reviewing progress and testing does not. That line is hard to draw, so record who owns custom work in a separate agreement, signed by the side transferring the copyright.
Does a South African OEM have to withhold tax on royalties it pays a foreign provider?
Usually, yes: see our guide to withholding tax on international software payments, which explains when a payment by an original equipment manufacturer (OEM) to a foreign provider is a royalty and how the tax is withheld.
Sources & authority
- Copyright Act 98 of 1978, ss 11B and 22(3), (8)
- Haupt t/a Softcopy v Brewers Marketing Intelligence (Pty) Ltd and Others (118/05) [2006] ZASCA 40; 2006 (4) SA 458 (SCA) (29 March 2006)
- Bergh and Others v Agricultural Research Council (93/2019) [2020] ZASCA 30
- Consumer Protection Act 68 of 2008, ss 1 (“goods”, “producer”) and 61
- Competition Act 89 of 1998, ss 1, 4(1)(b), 5, 7 and 8(1)(d)
- Trade Marks Act 194 of 1993, s 38 (permitted use by a licensee)
- Income Tax Act 58 of 1962, ss 49B(1)(a) and 49E(1) (withholding tax on royalties, extract)
This guide is general information, not legal advice. It reflects the law as at November 2026.