CALCULATED PRICING - Price Tiers Calculated from Tier 1

Anthony Smith

I know this has been brought up before, but I want to add support because this would be a huge improvement for anyone managing multiple price tiers.

Currently, calculated pricing only functions as a markup from the cost. What we really need is the option for tiers to be calculated as a discount percentage from Tier 1 (MSRP). For example, if Tier 1 is $100:

  • Tier 2 (MAP): 5% off → $95
  • Tier 3 (Bronze): 20% off → $80
  • Tier 4 (Silver): 25% off → $75
  • Tier 5 (Gold): 30% off → $70
  • Tier 6 (Platinum): 35% off → $65

The benefit is simple but powerful: instead of manually updating every tier’s price, we’d only need to change one number (Tier 1). All other tiers would automatically update based on their discount percentage.

The system already supports calculated pricing from cost, so this seems like it could be built into the same framework — just with the option to base it on Tier 1 instead. It would save a ton of time, reduce errors, and make tiered pricing far more consistent.

I’ve seen multiple users asking for this, so hopefully this can gain more traction as a feature enhancement.

6

Comments

3 comments

  • Comment author
    Chris

    That sounds useful / reasonable to me. So you would want in the Product > Prices

    • Type Column = Markdown %
    • Use = Reference “Tier 1” price for markdown calculation

    Something along those lines by the sounds of it.

     

    0
  • Comment author
    Nicolas Noakes

    We have implemented all our pricing calculations externally via the API due to limitations in Cin7.

    1) While we don't work “backwards” with out pricing ourselves, the original post here shows that some customers would use that functionality. This could be implemented either as additional Types (Markup, Markdown, Append, Subtract) or by allowing a negative value in the in Value field and leaving the Types as they are.

    2) Adding Tier 1 through Tier 10 as base value options in the Use column would allow “stacked” pricing. From an implementation point of view, this means that the price calculation algorithm needs to be able to iterate until all Tiers are priced, since any one can be dependent on another, potentially circularly. In our use case, we have a “Estimated landed cost” tier and a “Retail” tier - in the real world these are compounded but in Cin7 we have to have them completely independently.

    3) There needs to be some way to “lock” which supplier's Fixed/Latest price is used for a product. A “preferred supplier” setting perhaps? We occasionally source products from an alternative supplier when our primary/official supplier has a stock outage, which are then obviously supplied at a different price. But we don't want our retail prices to jump around in this situation, but it does because Cin7 only calculates based on the most recent supplier. Retail price should be consistently based on our primary supplier's pricing.

    0
  • Comment author
    Nicolas Noakes

    We have implemented all our pricing calculations externally via the API due to limitations in Cin7.

    1) While we don't work “backwards” with out pricing ourselves, the original post here shows that some customers would use that functionality. This could be implemented either as additional Types (Markup, Markdown, Append, Subtract) or by allowing a negative value in the in Value field and leaving the Types as they are.

    2) Adding Tier 1 through Tier 10 as base value options in the Use column would allow “stacked” pricing. From an implementation point of view, this means that the price calculation algorithm needs to be able to iterate until all Tiers are priced, since any one can be dependent on another, potentially circularly. In our use case, we have a “Estimated landed cost” tier and a “Retail” tier - in the real world these are compounded but in Cin7 we have to have them completely independently.

    3) There needs to be some way to “lock” which supplier's Fixed/Latest price is used for a product. A “preferred supplier” setting perhaps? We occasionally source products from an alternative supplier when our primary/official supplier has a stock outage, which are then obviously supplied at a different price. But we don't want our retail prices to jump around in this situation, but it does because Cin7 only calculates based on the most recent supplier. Retail price should be consistently based on our primary supplier's pricing.

    0

Please sign in to leave a comment.