A customer orders six monitors, two docks and a spare cable. If you promise trees per product sold, your team needs to know exactly which of those units qualify. That small definition connects what the sales team promises to what you fund and report.
Trees per product sold means assigning an agreed number of trees to each eligible unit. It can sit within ForestNation’s planting programme for orders and products. This guide focuses on product codes, units and channel reporting, so your commitment stays clear as orders grow.
Key Takeaways
- Define eligible product codes and the tree allocation for each unit.
- Count units separately from orders, especially for bundles and mixed baskets.
- Choose the qualifying sale stage so distributors and suppliers do not count the same commitment twice.
- Agree returns, replacements and reporting periods before the customer promise goes live.
- Philips Monitors provides a qualifying-product example; Image Source and Solution Group demonstrate different order and spend models.
How is a unit-based programme different from trees per order?
An order is a transaction. A unit is an item within it. If a basket contains three eligible products, one tree per order creates a different commitment from one tree per eligible unit.
A product-based rule can also use different allocations for different models. That requires a maintained product list, often identified by SKU, the stock-keeping unit or product code. The customer-facing promise should say which products qualify and what contribution is attached to them.
For the broader setup process, use the planting-per-purchase guide. Keep this page’s unit calculation as the specification that feeds that process.
What does the Philips Monitors example show?
Philips Monitors’ programme links qualifying monitor purchases to tree planting with ForestNation. The relationship began in 2020, and its forest has grown beyond 60,000 trees. The case describes launch Tree Kits and a Galtec partner campaign using digital Gift Stories for corporate customers.
The useful lesson is the connection between a defined product purchase and a contribution a partner can discuss with a customer. Do not infer that every Philips monitor worldwide carries the same number of trees. Confirm the eligible model, market, quantities and campaign terms for the proposal in front of you.
A distributor can present an agreed planting contribution alongside the product specification and service offer. It adds a concrete action to the conversation. It does not establish that the product’s environmental performance is better overall or that the contribution will win the contract.
What should your product eligibility list contain?
Build a short, versioned list that the sales and reporting teams can both use. Suggested fields are:
- Product code and description: the exact eligible item.
- Eligibility dates: when the rule starts and ends, including the relevant time zone where needed.
- Market or channel: the locations and sales routes included.
- Tree allocation: the agreed number for one qualifying unit.
- Qualifying status: ordered, shipped, invoiced, paid or another agreed event.
- Exceptions: bundles, samples, warranty replacements, returns and cancelled lines.
- Approval: who owns the rule and which version is active.
These are planning fields, not a claim about a required ForestNation integration. Product eligibility normally starts in your own sales records. Agree how the totals will reach ForestNation and what record you will receive in return.
How do you calculate mixed orders?
Calculate eligible units by product line, apply the agreed allocation, then add the line totals. Keep the underlying detail so that another person can reproduce the result.
Here is an illustrative example, not Philips pricing or a real customer order:
- Four units of eligible Model A at two trees each: eight trees.
- Two units of eligible Model B at five trees each: ten trees.
- Three units of an excluded accessory: no trees under this rule.
- Total contribution for the order: eighteen trees.
If one Model B unit is cancelled before the qualifying stage, the calculation becomes thirteen trees, assuming the agreed cancellation rule excludes it. A bundle needs its own definition: does the bundle count once, or do its eligible components count individually? Record one rule and apply it consistently.
Should you count sales to distributors or end customers?
A supplier may recognise the sale into a distributor; another programme may recognise the distributor’s sale to the end customer. These are often called sell-in and sell-through. Choose which event qualifies for your programme.
Counting both stages can duplicate a single planting commitment unless two separate contributions have been explicitly funded. Give the programme a reference that follows the allocation through the channel, and agree who approves the total.
Also separate planting allocation from customer recognition. A customer may receive recognition connected to a wider company forest. That does not automatically mean a second batch of trees has been planted. The proposal should explain whose forest holds the contribution and what the end customer receives.
How should you handle returns and replacements?
Decide the treatment before launching. A return before the qualifying stage may remove a unit from the count. A return after a funded batch requires a documented correction process. Do not silently reduce an already published planting total or imply that planted trees are reversed by a refund.
Warranty replacements, exchanges and samples need explicit rules too. A replacement may fulfil the original sale rather than represent a new qualifying purchase. Ask the data owner to identify those records so they are not counted automatically as ordinary sales.
At the reporting cut-off, save the eligible units, exclusions, tree calculation, approval and submission reference. Keep a corrections record linked to the original period. A monthly or quarterly total can remain simple while its supporting calculation stays available.
Which alternative model might be simpler?
Image Source plants one tree per order and builds branded client forests, including for Microsoft and Mercedes-Benz. That order model avoids a separate tree ratio for every merchandise item.
Solution Group plants 100 trees for every €5,000 of client spend, with more than 134,000 trees for clients including L’Oréal Italia, LVMH and Henkel. A spend threshold may suit projects with many different line items.
Happily has grown beyond 100,000 trees through event-linked planting, with RSVP planting used for selected events. These examples are different triggers, not interchangeable definitions of a product sold.
How do you budget and explain the commitment?
Multiply the expected eligible units by their tree allocations and use a current quotation to price the programme. Include any agreed recipient or communication services. Review the budget against a busier sales period as well as an average one.
A clear proposed customer message might read: “For each eligible Model A unit purchased during this campaign, we will fund two trees through ForestNation in Tanzania. See the qualifying products and programme details here.” Replace the illustrative terms with the actual approved scope before use.
If you include carbon information, cite the current impact methodology. Its annual estimate is about 25kg CO2 per tree, or 0.025 tonnes, with a 30% uncertainty discount applied. The calculation is derived from field measurements and modelling. It does not establish that a product’s emissions have been neutralised.
Imagine your account manager answering a customer’s question without chasing three departments. They can show the eligible product, the agreed contribution and the forest record. Your commitment is understandable because the detail behind it is organised.
Plan planting for your qualifying products with your product list, expected units and preferred reporting period.
Research and References
- Philips Monitors case study: qualifying purchases and partner campaigns.
- Image Source case study: per-order planting.
- Solution Group case study: client-spend model.
- Happily case study: event-linked planting.
- ForestNation impact methodology: estimates and uncertainty.
Frequently Asked Questions
What does trees per product sold mean?
It means assigning an agreed tree contribution to each eligible product unit. Specify the product, qualifying sale stage, dates and allocation rather than treating every item as automatically eligible.
Is one tree per product the same as one tree per order?
No. An order can contain several products. A per-unit calculation counts eligible items; a per-order calculation counts qualifying transactions.
Can different products have different tree allocations?
Yes, a proposed programme can define different allocations for eligible products. Agree the rule and budget with ForestNation and keep an approved product list for sales and reporting.
How should distributors avoid counting twice?
Choose the qualifying stage, such as the supplier sale or the end-customer sale, and give the contribution a shared reference. Separate funded planting from customer recognition.
What happens when a product is returned?
Apply the return rule agreed before launch. Record corrections against the original period and confirm treatment of already funded batches before changing a reported total.
