Schemes are rule-based pricing applied by the pricing engine rather than typed in by a cashier. That is what makes a promotion analysable afterwards.
Defining a scheme
- Scheme group — which group the scheme belongs to.
- Description — what the promotion is.
- From date and end date in Bikram Sambat — promotions expire on their own rather than needing to be remembered.
- Discount percentage and common percentage.
- Sales term — ties the scheme to the term engine so the discount posts to the right ledger.
- Is scheme for all products / for all customers — or map specific items and customers.
Customer groups and class-wise discounts
Customer groups let you attach discounts to a segment rather than to individuals. You can set discounts by customer group and class, by product group, and mark a discount as bill-wise with its own adjustment term so it applies to the bill total rather than per line.
Why not just discount at the till
Manual counter discounts are where margin quietly disappears. They cannot be analysed by promotion afterwards, they are hard to attribute, and they invite habit. If a discount is a policy, make it a scheme. Keep manual discounts for genuine exceptions, and require approval above a threshold.
Checking the cost
Because a scheme is applied by the engine and posts through its sales term, you can report what the promotion actually cost in margin rather than estimating it.
Did this answer your question? If not, our support team can look at your actual configuration.
Contact support