Product-Level Affiliate Commissions: How to Handle Mixed Baskets

Product-level affiliate commissions require each purchased item to carry the information needed for its applicable rule, with amounts that reconcile to the reported sale. Before launching different product rates, verify a mixed basket in the affiliate platform. A conversion appearing in a report does not prove that every item received the intended treatment.

This guide addresses one operational question: how should a retailer handle an order containing products with different commission eligibility or rates? It covers item mapping, discount treatment and rule checks. Choosing commercial rates remains a separate business decision.

1. Define which rules belong to individual items

Start with a written distinction between order conditions and item conditions. A customer attribute may describe the whole purchase. A product category usually describes a particular item. If a promotion applies only to selected merchandise, document whether its commission treatment follows those items or the entire basket.

Use product-level commissioning when those distinctions affect the calculation. A uniform programme may need less configuration, although item reporting can still support investigation. More detailed rules create more mapping and maintenance work, so introduce only distinctions the team can explain and verify.

For every proposed rule, record its qualifying products, exclusions, effective period and fallback treatment. Assign an owner who can resolve an unfamiliar SKU. Avoid instructions such as "premium products receive the promotional rate" unless someone maintains an explicit definition of premium.

Also separate partner attribution from commission calculation. Identifying the credited publisher does not explain which merchandise value received which rate. The existing guide to exclusive voucher codes and partner credit addresses that attribution question.

2. Map purchased products to the commission structure

Awin's commission-by-product documentation requires product-level tracking for product conditions. It also requires each product's commission group code to match a tracked part code in the main sale breakdown. The product amounts should reconcile to their associated part amounts. Where they differ, Awin says it trusts the amounts in parts.

That makes a product report alone insufficient evidence. Review the connection between the purchased item, its group and the amount submitted for that group. A recognisable product name can appear while the commissioning relationship is wrong.

Build a mapping register from the identifiers your checkout actually records. Include the purchased SKU or product ID, its commission category, the intended group and the source of that classification. For variants, decide explicitly whether all versions share a rule or need separate entries.

Keep a snapshot of the classification used for each purchase in your internal evidence. Otherwise, a later catalogue change can make an older order difficult to explain. This is a proposed audit practice, rather than a claim that every platform stores historical classifications identically.

Treat bundles deliberately. Establish whether checkout reports one bundle identifier or its components, then confirm that your integration and commission configuration use the same interpretation. Do not assume that a product feed automatically supplies every field needed by conversion tracking.

3. Trace discounts through the actual integration

Write down what each submitted amount means: unit price or line total, before or after discount, and whether it includes additional charges. Have the commerce and affiliate teams review the same definitions.

Awin's product-level tracking guide defines its item price as a single-unit price after relevant discounts and before taxes or additional charges. For its documented MasterTag approach, product-level data must be declared before the MasterTag loads. The correct product data arriving too late is still an integration problem.

impact.com's conversion object reference uses different field semantics. It distinguishes unit price from line subtotal and says not to submit both. Its order discount is spread proportionally across submitted item amounts, while item discount fields describe discounts at their respective levels.

For an impact.com integration, inspect the chosen combination of fields rather than copying Awin's amount assumptions. Check especially whether checkout has already deducted a discount that the receiving platform will subtract again. Keep the comparison against the merchandise amount defined for commission, rather than the customer's full payment including unrelated charges.

Test basket-wide and item-specific promotions separately. Add a multiple-quantity purchase, because a correct single-unit result can conceal confusion between a unit discount and a line discount. Agree how rounding differences should be investigated before accepting unexplained residual amounts.

4. Decide how overlaps and unknown products behave

Awin's commission groups guide describes sequential condition matching: the first group whose conditions match wins, and the search stops. Unmatched transactions fall back to the Default group. The page is scoped to Awin Classic, with capabilities that vary by plan, so confirm availability in your account.

A product-specific rule and a broad category rule can overlap. Review their precedence explicitly. Similarly, a fallback is a commercial outcome, not merely a technical convenience. Decide whether the default is suitable for newly introduced merchandise and how unexpected use will be reviewed.

The following table proposes review decisions for common basket situations. It does not prescribe platform behaviour or commission rates.

Give each unresolved row an owner before launch. If the team cannot predict the intended result, it cannot meaningfully approve the observed one.

5. Use a mixed-basket verification checklist

A useful test follows one controlled purchase through the checkout record, submitted conversion data and resulting platform calculation. Save enough evidence to explain a discrepancy without placing another order.

Use this checklist for the product-rule portion of testing:

• Select products from different groups, including one ordinary fallback candidate.
• Record the expected classification and treatment of every line before placing the order.
• Include multiple units of one product and verify quantity handling.
• Run separate purchases for an item discount and a basket-wide discount.
• Compare purchased identifiers with the identifiers received by the platform.
• Reconcile item amounts with group amounts and the intended commissionable merchandise total.
• Inspect the applied rules and resulting commission, rather than stopping at successful conversion receipt.
• Record the configuration version, evidence and person responsible for approval.

Repeat relevant cases when changing product mappings, checkout integrations or rule precedence. A change to category naming deserves attention if commission conditions depend on those values.

These checks complement the wider affiliate tracking tests before campaign launch. They focus on the calculation inside a basket, rather than replacing checks for the full referral journey.

6. Avoid common mistakes and choose the next step

One mistake is approving the setup because the order total matches. Equal totals can conceal items assigned to the wrong groups. Another is comparing a product report with checkout while never examining the commission calculation. Check both classification and amounts.

Teams also create problems by letting catalogue administrators rename categories without reviewing dependent rules. Maintain a change process that identifies which commission mappings need attention. Keep publisher explanations consistent with the configuration so support staff can explain how a mixed order was treated.

Do not extend an item's promotional treatment to the entire basket unless that is the documented intention. Likewise, an excluded item should not silently change the treatment of otherwise eligible merchandise. Make those expectations explicit in the test record.

Returns add a later lifecycle question. Preserve the connection between items and their original treatment so the team can investigate adjustments. The guide to affiliate conversion reconciliation before commission approval covers that separate stage.

The next step is to choose one mixed basket from your own catalogue and write its expected result line by line. Ask the implementation owner to demonstrate that result in the platform using your actual account configuration. Resolve unexplained mappings or amount differences before introducing additional product rules.