BambooForge Labs

Docs › Sales › Field Sales Schemes for Distributors: Secondary Orders and Claims

Field Sales Schemes for Distributors: Secondary Orders and Claims

Trade schemes apply to the orders a distributor fills, and what the distributor gave away is claimed back as a credit note - installed by itself alongside Trade Schemes and Distributors.

Buy on the Odoo Apps StoreOpen the live demo
Runs onOdoo 16 to 20Community or Enterprise, self-hosted or Odoo.sh
NeedsOdoo only; includes field sales distributor, field sales schemesno Enterprise module
Price626 EURone-time, per series, on the Odoo Apps Store
Demodemo20.bambooforge.devlogin page already filled in
Supportsupport@bambooforge.devfirst reply within one business day
Version20.0.1.0.3bambooforge_field_sales_schemes_distributor
Store page per series:Odoo 16.0Odoo 17.0Odoo 18.0Odoo 19.0Odoo 20.0

Key facts

Not for
Follow a change to the order. A use is written when the scheme is applied. If a line is changed afterwards, the claim still pays what was written. Press Apply Schemes again while the order is new.; Pay the distributor. The credit note stays in draft for the accountant.
Manual last updated
2026-11-11

With both Trade Schemes and Distributors installed on Odoo 20, the schemes a shop is entitled to apply to its order whoever fills it, and what the distributor gave away is claimed back as a credit note. This module installs by itself when both are there.

This page is the complete manual of that bridge.

Overview

For whom. A brand that runs trade schemes and sells through distributors. It needs Field Sales Trade Schemes and Field Sales Distributors, on Odoo 20.

What it does

  • Schemes on secondary orders. A secondary order gets the shop's schemes: percent off on its lines, free units as a line at 100%, an amount off, charged to the same budgets.

  • Apply Schemes on a new secondary order in the office.

  • Scheme claims. What a distributor's delivered secondary orders gave away, added up and turned into a credit note for the distributor, one line per scheme and without tax.

  • Each use claimed once. Cancelling a claim frees its uses for the next one.

What it does not do

  • Follow a change to the order. A use is written when the scheme is applied. If a line is changed afterwards, the claim still pays what was written. Press Apply Schemes again while the order is new.

  • Pay the distributor. The credit note stays in draft for the accountant.

What it needs

  • Field Sales Trade Schemes and Field Sales Distributors on Odoo 20, Community or Enterprise.

  • Scheme Claims is for supervisors; invoicing users can read and update claims.

Concepts

Use on a secondary order. One application of a scheme to a distributor's order.

Claim. A distributor's request to be paid back for what its delivered orders gave away.

Credit note. The draft document a claim becomes.

Install and first run

  1. Install both apps: this module installs by itself.

    Expected: Field Sales > Distributors > Scheme Claims, and the button Claim the Schemes Given on a distributor.

  2. Take an order on the phone at an outlet served by a distributor, with a running scheme that fits.

    Expected: the phone names the scheme, and the secondary order shows what it earned.

Uninstalling

Uninstalling removes claims and the schemes' link to secondary orders. Credit notes stay.

Flows

One thing you do with the bridge.

Claim what a distributor gave

  1. Mark the secondary orders delivered.

  2. On the distributor, tab Distributor, press Claim the Schemes Given, or open Distributors > Scheme Claims.

  3. The claim lists every use not claimed yet on its delivered orders, up to its day. Add What Came In Since adds later ones.

  4. Make the Credit Note writes a credit note in draft for the distributor.

  5. Cancel deletes a credit note still in draft and frees the uses; a posted one is reversed in accounting first.

How it works

What a claim counts

A claim adds up the cost of each use as the scheme recorded it: the discount given, the free units at list price or cost, or the amount. A use on a cancelled order no longer counts against the budget.

Who reads and writes what

  • Supervisors create claims; invoicing users read and update them.

  • The credit note is made as the superuser, in the claim's company.

How we make sure it works

Before every release, 11 automated checks run against this app on Odoo 16, 17, 18, 19 and 20. Among them:

  • A posted credit note is reversed not cancelled.

  • Applying again gives the same once.

  • An order no scheme fits says so.

  • A delivered order keeps its schemes.

  • A cancelled secondary order gives the budget back.

The complete list is in the source you receive.

For managers

This bridge has no analysis of its own: what a claim adds up shows under Distributors > Scheme Claims and in Scheme Spend.

Troubleshooting and FAQ

Questions people ask

Does the shop pay the discounted price? The secondary order says so; what the distributor bills the shop is in its own books.

Can a use be claimed twice? No, unless its claim was cancelled.

Support

Write to support@bambooforge.dev with your Odoo series and what the screen said.

Changelog

20.0.1.0.3

  • Every field has a help text; a search view on claims; a text on the empty list.

  • This manual.

Reference

Generated from the module's own code (version 20.0.1.0.3, series 20.0) on 2026-11-12; every menu, field, setting, scheduled action, group, rule, report and endpoint below is read from the files, not written by hand.

Models

bf.fs.scheme.claim (uses mail.thread)

Scheme Claim from a Distributor

Field

Technical name

Type

Help

Flags

Name

name

Char

computed

Distributor

distributor_id

Many2one to res.partner

The distributor claiming back what it gave the shops.

required

Up To

date

Date

Uses dated up to this day are claimed.

required

Uses Claimed

use_ids

One2many to bf.fs.scheme.use

The scheme uses this claim pays back.

Amount

amount

Monetary

The cost of the uses this claim pays back.

computed

State

state

Selection: Draft (draft), Credit Note Made (credited), Cancelled (cancel)

Draft: being put together. Credit Note Made: a draft credit note exists. Cancelled: its uses can be claimed again.

required

Credit Note

refund_id

Many2one to account.move

The credit note made for the distributor, in draft until the accountant posts it.

readonly

Company

company_id

Many2one to res.company

Currency

currency_id

Many2one

related to company_id.currency_id

bf.fs.secondary.order (extends bambooforge_field_sales_distributor's bf.fs.secondary.order, uses bf.fs.scheme.document)

Field

Technical name

Type

Help

Flags

Schemes Applied

scheme_use_ids

One2many to bf.fs.scheme.use

The trade schemes applied to this order, with what each cost.

bf.fs.secondary.line (extends bambooforge_field_sales_distributor's bf.fs.secondary.line)

Field

Technical name

Type

Help

Flags

Discount %

discount

Float

The percent off this line.

Scheme

bf_scheme_id

Many2one to bf.fs.scheme

The trade scheme that added this line: a free product or an amount off.

readonly

Discount From a Scheme

bf_scheme_discount

Boolean

Ticked when the line's discount was set by a trade scheme.

readonly

Scheme Percent

bf_scheme_pct

Float

The percent a trade scheme gave this line.

readonly

Quantity (schemes)

product_uom_qty

Float

related to qty

Unit price (schemes)

price_unit

Float

related to price

Subtotal (schemes)

price_subtotal

Float

related to subtotal

bf.fs.scheme.use (extends bambooforge_field_sales_schemes's bf.fs.scheme.use)

Field

Technical name

Type

Help

Flags

Secondary Order

secondary_id

Many2one to bf.fs.secondary.order

The distributor's secondary order the scheme was applied to.

Distributor

distributor_id

Many2one

related to secondary_id.distributor_id

Claim

claim_id

Many2one to bf.fs.scheme.claim

The claim that pays this use back. Empty: not claimed yet.

readonly

bf.fs.visit (extends Odoo's bf.fs.visit)

Adds no fields.

res.partner (extends Odoo's res.partner)

Adds no fields.

Security

Access rules

Model

Group

Read

Write

Create

Delete

bf.fs.scheme.claim

bambooforge_field_sales.group_bf_fs_supervisor

yes

yes

yes

yes

bf.fs.scheme.claim

account.group_account_invoice

yes

yes

no

no

bf.fs.scheme.claim

everyone (no group)

yes

yes

yes

yes

bf.fs.scheme.use

account.group_account_invoice

yes

no

no

no

Record rules

Rule

Model

Groups

Domain

Operations

Scheme claim: multi-company

bf.fs.scheme.claim

everyone (no group)

['|', ('company_id', '=', False), ('company_id', 'in', company_ids)]

read, write, create, delete