Price Category Master

1How to work in this page #

1. Find (F2): search by name or description.
2. Add (F3): create a new category. Cursor lands on Name.
3. Modify (F4): edit the loaded category.
4. Delete: remove the current category (view mode), with confirmation.
5. Save (F5): commit the add / modify. Name is required and must be unique.
6. Cancel (Esc): discard the current edit.

2Step by step #

Price categories are the named price levels — Retail, Wholesale, Std. Purchase Price — every product can carry a rate for.

1. Press Add (F3) and name the level — Wholesale .
2. Press Save (F5) and confirm.
3. Enter each product's rate for the level on the Product master's price block, and point the voucher types that should bill at it to this price type.

3About the fields #

• Formula Variable Name: short token (max 10) used to reference this price in other formulas.
• Formula String (Master): formula evaluated at master level.
• Formula String (Trans.): formula evaluated at transaction level.
• Is MRP?: marks this category as the maximum retail price.
• Sequence: display / processing order.

4Tokens available in formulas #

The Formula String is evaluated when pricing a product (Product Master price grid and Stock-Group custom prices). It may reference:

• Other price types — by their Formula Variable Name (e.g. MRP , WSP ). A formula resolves to that price type's current price. Evaluation order follows Sequence , so a formula can build on price types defined earlier.
• Tax / opening tokens: OPSTK (opening stock), OPVAL (opening value), OPRATE (OP rate), IGSTRate , SGSTRate , CGSTRate , GSTRate (= IGST), TX / TXR (rate of tax — from the product's tax class).
• Any numeric product field — by its field name, e.g. OpStock , OPRate , OpValue , MinStock , MaxStock , Rlevel , Weight , Height , QtyInPack , ConToSmallerUnit , perAdditionalCost .

Tokens are case-insensitive. Examples: MRP * 0.9 , OPRATE * (1 + GSTRate/100) , MRP - (MRP * SGSTRate/100) . An unknown token leaves the price unchanged (no error), and a price type that has a formula is shown read-only and auto-computed in the pricing grids.

5Rules and integrity #

• The price-type name must be unique; a duplicate is refused before saving.
• Only one price type should be marked as MRP.
• Sequence sets the order in which prices are calculated, so a price type whose formula refers to another must sit after it.
• Price types are used throughout product and group pricing. Deleting one that is already in use removes those prices, so retire an obsolete price type rather than deleting it.