Price Lists, Product Attributes, UoM and GST in One ERP for Indian SMEs

The Pricing and Product Chaos Most Indian Teams Live With

If you run a distribution or manufacturing business in India, your product data probably lives in five places at once. The sales team keeps a price sheet in a spreadsheet. The warehouse tracks stock in pieces and boxes on a whiteboard. The purchase team buys by the kilogram. Accounts applies GST in a legacy desktop accounting tool at month end. When a customer asks for a quote, three people open three files to answer one question.

The cracks show up fastest at the invoice. A distributor in Pune sells the same item to a retailer at one price and to an MSME buyer at another, but both get pulled from a single flat column called Rate. A manufacturer in Coimbatore defines a carton as 24 pieces on the shop floor and 20 pieces in the sales sheet, so every bulk order needs a manual recount. An attribute like color or size exists only in a product photograph, so the team cannot tell whether they have stock of the red variant or the blue one.

Research on Indian small and medium enterprises shows the scale of this mess. In filing-error studies, roughly 70 percent of SMEs report Input Tax Credit mismatches, 56.7 percent cite incorrect invoice details, and 43.3 percent flag wrong tax calculations. The root cause is rarely the GST math itself. It is that price, unit, attribute, and tax data sit in separate silos and never reconcile until an auditor forces them to. The ERP that was supposed to be one source of truth has become five sources of disagreement.

GST 2.0, with its consolidated slabs and revised HSN schedule, makes the silo approach impossible to defend. Every time a rate changes, your team has to reopen the price sheet, recheck the unit conversions, reconfirm the attributes, and reapply the tax. If any one of those four masters is stale, the invoice is wrong, the e-invoice may be rejected, and the buyer's credit gets blocked.

What Changes When Price, Unit, Attribute, and GST Live Together

A modular ERP built for the India market ties these four masters together so a single product record carries everything downstream systems need. Kikan System implements each of these as a first-class module, and the design follows how distribution and manufacturing teams actually work.

Price Lists With Rule-Based Overrides

Instead of one Rate column per product, the platform stores named price lists. A price list is a collection of pricing and discount rules. Each rule has a type that controls how its value is applied. A fixed price rule overrides the product's base price entirely. A discount percentage rule takes 0 to 100 percent off. A discount amount rule takes a flat rupee amount off. The source entities live in the pricelist and price rule modules, and the engine returns the final unit price after the rule runs.

Rules can target a specific product or an entire product category, with category rules walking up the category hierarchy so the closest ancestor wins. Each rule also carries a minimum quantity and valid-from and valid-to dates, so volume breaks and seasonal pricing are configuration, not spreadsheet maintenance. The pricing result exposes the base cost alongside the final price, so margin is visible at quote time rather than discovered after the deal closes.

The precedence is deliberate and auditable. A customer-specific price list takes priority, then the customer's default price list, then the product base price. The result even records where the price came from, so when a buyer disputes a rate, your team can show the exact rule that produced it.

Units of Measure With Bidirectional Conversion

Units of measure are defined as a hierarchy, not a flat list. A unit carries a name, a symbol for documents, and a contain quantity that says how many of a reference unit it holds. A box contains 10 pieces. A case contains 12 boxes. A pallet contains 10 cases. The conversion service walks this hierarchy in both directions, so converting 2 pallets into pieces or 500 pieces into boxes is one operation, not a lookup table your staff maintains by hand.

Crucially for India, units attach to products and to packaging units. A product has its own stock unit, and each alternate sellable packaging unit carries a conversion factor relative to that stock unit, plus a flag for the default transaction unit. So one product can be bought in kilograms, stocked in pieces, and sold in cartons, and every quantity reconciles back to the same base. This is the foundation for clean GST returns, because the taxable quantity and the invoiced quantity are always consistent.

Product Attributes and Variant Generation

Attributes like size, color, or grade are master records, not free text. An attribute owns a list of values, and attribute lines attach attributes to a product template. The variant generation service takes the cartesian product of selected values and creates one stockable product per combination. Choose Color with red and blue and Size with small and large, and four variants are generated automatically, each with its own SKU.

This matters because GST and inventory care about variants. A wrong-variant shipment is a return, a restocking cost, and a GST credit note. When the variant matrix is generated from structured attributes, the warehouse picks the exact SKU, the price list can hold a rule per variant, and the invoice line carries the correct HSN and rate for that specific item.

GST Through a Configurable Tax Engine

Tax in the platform is a separate, configurable master, not a column buried inside pricing. A tax setting carries a name, a rate from 0 to 100 percent, a sales tax liability account, and a purchase tax asset account, with account subtypes validated at write time. Each product attaches its tax setting, so a reduced-rate item defaults to its slab and a standard item to another, and the rate is correct on entry instead of being re-keyed downstream.

The architecture is intentional about separation. The price calculation returns the unit price, the cost, and any discount applied, and it excludes tax. Tax is resolved through the dedicated product tax path. This split is what makes GST clean: the taxable value is never accidentally inflated by a discount, and the discount is never distorted by a tax inclusion. At invoice time the two streams combine correctly, which is exactly the structure GST 2.0 reconciliation expects.

A Real-World Scenario

Consider a mid-size electrical goods distributor in Ahmedabad with about 180 active SKUs and three customer tiers. Retailers buy in cartons and get a list price. MSME buyers buy in cases and get an 8 percent discount off list. Two large institutional buyers have negotiated fixed prices on 12 high-volume SKUs.

Before adopting a modular ERP, this team maintained three price spreadsheets, a conversion cheat sheet taped to the warehouse wall, and a GST rate column that someone updated by memory. Every GST slab change meant two days of reconciliation, and every quarter the chartered accountant found at least a dozen invoices where the unit and the rate did not match the HSN.

With price lists, units of measure, attributes, and tax settings connected in one ERP, the same business runs differently. The distributor sets up three price lists, one per tier, plus dedicated price lists for the two institutional buyers. Each high-volume SKU gets a fixed price rule in the buyer's price list, so the negotiated rate applies automatically and the base price is never exposed to the sales order screen. Volume breaks use minimum quantity rules, so an order of 50 cartons triggers the bulk price without a phone call to the owner.

Units of measure handle the packaging reality. The stock unit is a piece. A case of 20 and a carton of 240 are packaging units with conversion factors, so a sales order entered in cartons converts correctly to the stock unit the warehouse picks, and the GST invoice reports the right quantity and UQC. Attributes define the voltage and color variants, and each variant inherits its parent's tax setting while carrying its own SKU and stock.

The tax engine ties GST to the product, not the clerk. When the 18 percent slab applies, it applies because the product's tax setting says so, and the sales tax posts to the liability account and the purchase tax to the asset account on entry. At period close, the taxable values reconcile to the invoice lines because they were never split across spreadsheets in the first place. For an MSME working capital cycle, that reconciliation speed is the difference between claiming input credit this month and waiting until next quarter.

Is This Right for Your Business?

This approach fits Indian distribution and manufacturing teams that have outgrown a single price column and a flat unit list. If you sell the same product at different prices to different buyer types, if you buy and sell in different units of measure, if you manage variants by photograph, or if GST slab changes turn into multi-day fire drills, the four-master model is built for your operating reality.

It is less essential if you carry a handful of SKUs at one price in one unit. But most growing Indian businesses pass that threshold quickly, and the cost of catching up after years of spreadsheet drift is far higher than starting with structured masters from day one.

Frequently Asked Questions

Can I keep different prices for retailers, MSME buyers, and large institutional customers?

Yes. You create separate named price lists, and a customer's dedicated price list takes priority during pricing, falling back to the customer's default price list and then the product base price. Fixed price, discount percentage, and discount amount rules let you model negotiated rates, tier discounts, and seasonal pricing in the same system.

How does the ERP handle units of measure like pieces, boxes, cases, and kilograms?

Units form a hierarchy where each unit defines how many of a reference unit it contains. The conversion service walks this hierarchy in both directions, so converting between stock units and packaging units is automatic. Each product can have multiple sellable packaging units with conversion factors, and a flag marks the default transaction unit.

How is GST applied so it stays clean for returns and audit?

Tax is a separate configurable master. Each tax setting carries a rate from 0 to 100 percent and links to a sales tax liability account and a purchase tax asset account, with subtypes validated at write time. Each product attaches its tax setting, so the correct GST rate defaults on entry. The price calculation returns the taxable price and excludes tax, which is resolved separately, keeping the taxable value and the discount clean for reconciliation.

Key Takeaway

Price lists, product attributes, units of measure, and GST are not four problems to solve in four tools. They are one product master seen from four angles. When your ERP models them as connected modules, your team stops reconciling spreadsheets and starts trusting the invoice, the pick list, and the GST return to agree by design.

Stop Reconciling Price, Unit, and Tax by Hand

Kikan System brings price lists with rule-based overrides, a bidirectional unit of measure hierarchy, attribute-driven variant generation, and a configurable GST tax engine into one modular ERP. Start on the free plan, which supports up to 2 users with no credit card required, and configure your product master the way your business actually operates. Get started with Kikan System.