Illinois White Label Agreement Template FAQ

How do you define a “defect” versus an “enhancement” request?

A defect is usually a failure to meet an agreed specification or documented behavior, while an enhancement is a new feature, improvement, or additional capability outside that baseline. The safest approach is to tie “defect” to a written specification or acceptance criterion and treat anything else as a change request with separate pricing and approval. If the product is a service, you can also define defects as failures to meet availability targets or material performance metrics. Clear definitions reduce arguments when a reseller reports an issue and the provider believes it is a product roadmap request.

What is an acceptance process and when should it be used?

Acceptance processes help when deliverables are complex or when the reseller must confirm that a branded version is ready for customers. The agreement can define an inspection or test method and a short rejection window after delivery or provisioning. If the reseller does not reject within the window, the deliverable can be deemed accepted. This approach prevents indefinite uncertainty about whether the provider met obligations. It also encourages both parties to document what “done” looks like — such as passing tests, correct branding elements, and matching the agreed specifications.

How should inspections and audits be handled without disrupting operations?

A balanced approach is to limit inspections to reasonable times and scopes, and to focus on documentation that confirms conformity — QA reports, batch records, release notes, or service change logs. If on-site or live-system inspection is requested, the agreement can require notice, limit frequency, and protect confidentiality. The goal is verification, not control of the provider’s business. By making inspections structured and bounded, resellers get confidence in quality while providers avoid open-ended requests that interfere with production or service delivery.

Who pays for rework, replacements, or corrections?

Cost allocation should track fault and scope. If a confirmed defect exists, providers often cover repair, replacement, or re-performance within the warranty remedy. If the issue stems from reseller inputs — incorrect brand assets, inaccurate instructions, or late approvals — the reseller may bear the cost. Some parties adopt shared costs for gray areas, like expedited shipping requested by the reseller after a delay. When the agreement includes a corrective-action log, it becomes easier to connect costs to documented causes and agreed resolutions.

Can the reseller request quality assurance documentation?

Yes, and it can be a practical compromise between “trust us” and intrusive audits. The agreement can list which documents can be requested, how often, and in what format. Providers may also want to exclude highly sensitive information, and instead provide summaries or attestations. If the reseller is selling to enterprise customers, QA documentation can reduce sales friction and shorten procurement cycles. Defining the document set in advance prevents repeated renegotiation every time the reseller needs proof of quality for a new customer.

What is the difference between direct and consequential damages in this context?

Direct damages typically relate to the immediate cost of the product or service and the value of what was actually purchased. Consequential damages are secondary effects — lost profits, reputational harm, or downstream customer losses — that can be large and difficult to predict. Many white label agreements limit liability to direct damages and cap the total amount, which helps both parties price the deal without taking on unbounded risk. If a party needs stronger protection, it’s often better to negotiate specific remedies or credits rather than expanding broad damage categories.

How do renewals and term endings usually work?

Some agreements run for a fixed term and then either end automatically or renew on the same terms unless notice is given. Others use an initial term followed by month-to-month continuation. Whatever you choose, it helps to define what happens to open orders, ongoing support, and the use of brand assets at the end of the term. A clear end-state prevents “zombie” relationships where one side assumes the contract is still active while the other acts as if it expired. Term clarity also supports clean pricing updates at renewal points.