Below hold some important logic we need to understand in order to successfully load rebates and sell throughs whether this be how navision accrues sell throughs or how the pricing algortyhmn treats the them  f

Sell-Thru Rebate Calculation 

more info here

Example SKU: ETLW70B
Kit BOM: Yes
Active Sell-Thru Rebates: 2 rebates configured

A new Sales Order (SO05483993) is created for item ETLW70B.

Sales Order Rebate Calculation Logic

1. Rebate Selection:

   • NAV checks for active Sell-Thru rebate entries based on the “Starting Date” and “Ending Date”

   • If no date filters are specified, the rebate is considered active at all times
     
     

2. Calculation Based on Rebate Type:

   • If the rebate is defined as a Rebate %, NAV uses the Last Purchase Invoice Price (Last Direct Unit Cost) to calculate the rebate amount

   • This price is determined at the time of invoicing  the sales order , not order creation

   • No posting date filters are applied when determining the Last Purchase Invoice

3. Example:

   • For Vendor V05494:
     Last PI = PI1576441, Last Direct Unit Cost = 296.40

   • For Vendor V08617:
     Last PI = PI1578613, Last Direct Unit Cost = 293.06
     
     

Kit BOMs and Rebate calculation 

​To clarify the KitBOM loading process:

In order to correctly absorb support into both website pricing and claim calculations, rebates must be loaded on both the parent and child SKUs.

1. Loading support on Child SKUs

• When a KitBOM is exploded on a sales order, the parent SKU does not appear on the sales line. Instead, only the child SKUs are listed. As a result, all financial calculations including rebates are applied at the child SKU level. Therefore, rebates will only be captured and sent to the Frenis team through the child SKUs.

• Additionally, even when SKUs are assigned to a parent code, they may still be sold separately online. For example, SKUs BBF7645SA and BTR7942SA make up BMF7645SA, but each is listed online as an individual product. To ensure we are capturing all applicable sell-through claims, support must be loaded on each individual component SKU.

2. Loading Support on Parent SKUs

• Our current pricing algorithm will apply support at the parent level only if the parent SKU is live and has components attached. If only the component SKUs are live (and not the parent), the system will use only the support loaded directly on the individual child SKUs. The parent-level rebate will not be applied in this case.  

Note: For any sales processed manually by a salesperson (i.e., not through the website), only the child SKUs listed on each sales line will be captured for rebate and reporting purposes.