Set product-level commission overrides

Updated May 22, 2026

When you track an order through the API, you can include a product object with each request. Yaplet stores it as metadata on the commission for reporting; the actual override amount comes from the commission value your e-commerce system computes and passes in the same request. Useful for rewarding partners more generously on high-margin products or new SKUs you want to promote.

How product overrides work

Commission calculation follows a priority order:

  1. Partner override (highest priority) — if the partner has Ignore Product Rate enabled, the partner's own rate is always used, regardless of the product passed.
  2. Custom commission in the API request — if your API call includes a commission value, that exact amount is used, unless Rule 1 already applied.
  3. Partner rate — if the partner has a rate set and Ignore Product Rate is off, the partner rate is used.
  4. No commission — if none of the above apply, commission is 0.

Pass product data in the tracking API call

Include the product field and an explicit commission in your POST request:

POST https://yaplet.com/api/affiliates/track/{affiliate_code}

{
  "order_id": "order_789",
  "total_amount": 249.00,
  "customer": { "email": "[email protected]" },
  "product": {
    "id": "prod_premium",
    "name": "Premium Plan",
    "category": "subscription"
  },
  "commission": 37.35
}

In this example, a custom commission of 37.35 is passed explicitly — useful when your e-commerce system has already calculated the correct amount for that SKU.

Control partner-vs-product priority

Per-partner, you can toggle Ignore Product Rate in the partner settings. When this is on, the partner's own rate always wins — even if you pass a product object or a commission value in the API. Use this for partners who have a negotiated flat deal that should never be overridden by product rules.

What's next

See Use the partner tracking API for the full request reference and code examples in JavaScript, PHP, and Python.

Did this article answer your question?