Most agarbatti brands sell through a chain of distributors and retailers, with a sales team visiting the market on fixed routes, schemes to push volume and a lot of business done on credit. The factory side may be well run, but once cartons leave the gate, price, discount and payment are often decided in conversations nobody records. The result is margin that leaks a little on every order and outstanding that nobody fully trusts.
This guide is for owners and sales heads of Indian agarbatti, dhoop and incense brands. It covers where margin leaks after the factory gate, how to set up price groups and schemes so they can be measured, how to plan beats, how to get field collections into the books the same day, and which numbers to review every week. For the factory side, see our agarbatti manufacturing ERP guide.
Where Agarbatti Margin Leaks After the Factory Gate
The margin on a carton is decided twice: once in the factory, by yield, perfume and rejects, and again in the market, by price, scheme, credit and collection. The second set of decisions is usually spread across many people: the owner agrees a price with a large distributor, the sales head announces a festival scheme, each salesman decides how to apply it, and accounts find out when the claims and the cash arrive.
Each of those decisions can be reasonable on its own. The problem is that they are not recorded in one place, so nobody can see their combined effect on an order, a distributor or a month. A scheme that looked affordable on paper becomes expensive when it stacks with a special price; a distributor who looks profitable is not, once the extra credit days are counted.
Key Takeaway: You cannot control what you do not record. Price, scheme and collection need to be captured on the order and the invoice, not in conversations, before anyone can tell which schemes and distributors actually make money.
7 Distribution Problems Agarbatti Brands Face
Problem 1: Different Prices for the Same Carton, With No Rule
The Problem: Over the years, different distributors end up on different prices: one negotiated hard, one was given a rate to open a new area, one was never moved to the new price list. When prices live in old invoices and memory, the same carton is sold at many prices for no reason anyone can explain.
How ERPDrive Solves It: Customers sit in groups, and each group has its own pricing. The price on a sales order comes from the customer's group, not from what the salesman remembers.
The Result: Price differences become deliberate decisions, visible and reviewable.
Problem 2: Schemes Promised but Not Recorded
The Problem: Buy ten cartons and get one free, a discount for the festival season, an extra incentive to clear a slow product. If a scheme is announced on the phone or in a WhatsApp group, it is applied unevenly, claimed late, and its real cost is never known.
How ERPDrive Solves It: Trade schemes are set up in the system and applied on sales orders, so each order carries the scheme it received.
The Result: The cost of every scheme can be added up, order by order and distributor by distributor.
Problem 3: Discounts That Stack Below Cost
The Problem: A group price, a scheme and a special discount can each be sensible on their own and still take an order below cost when they are combined. Nobody notices at the time because nobody is looking at the margin on that one order.
How ERPDrive Solves It: A margin floor is checked after discounts, so an order that would go below the floor is caught before it is confirmed.
The Result: Schemes stay schemes, and do not quietly turn into losses.
Problem 4: Beats Nobody Plans
The Problem: When each salesman decides his own route, some distributors are visited every week and some once a month, new areas are left uncovered and two salesmen sometimes visit the same distributor. Nobody can say which distributors were due a visit and missed it.
How ERPDrive Solves It: Territories and journey plans (beats) are set up in the system, defining which distributors each member of the sales team covers and when.
The Result: Coverage is planned instead of improvised, and gaps can be seen.
See Schemes, Beats and Collections on One System
See how the ERPDrive Incense Edition applies group pricing and trade schemes on the order, checks a margin floor after discount, and posts beat collections against invoices.
Book a Free DemoProblem 5: Field Collections That Reach the Books Days Later
The Problem: Salesmen collect cash and cheques on the beat and write them on a slip. By the time the slip reaches accounts, days may have passed. Meanwhile the distributor's outstanding is wrong, reminder calls go to people who have already paid, and cash stays with the sales team longer than anyone intends.
How ERPDrive Solves It: Money collected in the field is deposited against the distributor's invoices and becomes a payment receipt in the ledger.
The Result: Outstanding is correct the same day the money is deposited, and follow-up goes only to distributors who still owe.
Problem 6: Outstanding Nobody Trusts
The Problem: When invoices, credit notes and receipts are spread across different registers, the outstanding figure for a distributor depends on who you ask. Credit decisions, such as whether to send the next order, are then made on an argument rather than a number.
How ERPDrive Solves It: GST invoices are raised from the sales order, credit notes and payment receipts post to the same double-entry ledger, and each distributor's account shows what is due. Our guide to accounts receivable management covers how to work the overdue list.
The Result: One outstanding figure per distributor that sales and accounts both accept.
Problem 7: Complaints and Returns Argued Without Data
The Problem: A distributor says a lot of cartons smells weak and asks for credit. Without a link from those cartons to their batch, you cannot tell whether the complaint is real, how many other cartons are affected, or which other distributors received the same batch.
How ERPDrive Solves It: Stock is picked and dispatched by lot, complaints are logged against the lot, and the lot can be traced back to its batch and perfume lot and forward to every dispatch. Credit notes are raised in the same system. See our guide to batch tracking and traceability.
The Result: Complaints are settled on evidence, and a real problem can be contained to the distributors who actually received the batch.
How to Set Up Schemes So They Can Be Measured
Whatever kind of scheme you run, the same few rules make it measurable:
- Write it down once, in one place. Name, products, the benefit (free goods or discount), start date and end date.
- Say who it applies to. All distributors, a customer group or a territory. A scheme that applies "to whoever the salesman thinks deserves it" cannot be measured.
- Apply it on the order, not afterwards. Schemes settled by claims months later are the hardest to control and the easiest to dispute.
- Protect the floor. Decide the lowest margin you will accept after all discounts, and check every order against it.
- Review the result. At the end of the scheme, compare the extra volume with what it cost in free goods and discounts.
Common scheme types in the agarbatti trade include quantity schemes (buy a number of cartons, get some free), percentage or flat discounts for a period, festival schemes ahead of peak buying seasons, and special prices for a customer group. Plan stock for festival schemes early; our guide to festive season production planning covers how.
Phone and Registers vs One System for Distribution
| Area | Phone, WhatsApp and Registers | ERPDrive Incense Edition |
|---|---|---|
| Pricing | Rates from old invoices and memory | Customer groups with their own pricing |
| Schemes | Announced on the phone, claimed later | Trade schemes applied on the sales order |
| Margin control | Discounts stack unnoticed | Margin floor checked after discount |
| Beats | Each salesman picks his own route | Territories and journey plans |
| Collections | Slips entered days later | Deposited against invoices as payment receipts |
| Outstanding | Different figure in each register | One ledger for invoices, credit notes and receipts |
| Complaints | Settled by argument | Logged against the lot, traced to batch and dispatches |
Distribution KPIs to Review Every Week
| KPI | How It Is Calculated | What It Tells You |
|---|---|---|
| Scheme cost as a share of sales | Free goods and discounts divided by sales, per scheme | Which schemes pay for themselves |
| Margin after scheme, by distributor | Net sales less cost of goods, per distributor | Which distributors really make money |
| Orders stopped at the margin floor | Count of orders caught below the floor | Whether price and scheme rules are being stretched |
| Collections vs amount due, by beat | Money collected divided by invoices due on the beat | Which routes and salesmen collect well |
| Days sales outstanding | Outstanding divided by average daily credit sales | How long the market holds your money |
| Overdue by age | Unpaid invoices grouped by days overdue | Where follow-up should go first |
| Visits made vs planned | Distributor visits completed against the journey plan | Coverage gaps in the market |
How the ERPDrive Incense Edition Runs Distribution
Step 1: Group Customers and Set Their Prices
Put distributors and retailers into customer groups, each with its own pricing, so the price on every order comes from a rule.
Step 2: Set Up Trade Schemes
Record each scheme once, with its products, benefit and dates, so it can be applied on sales orders and its cost added up.
Step 3: Set the Margin Floor
Decide the lowest margin you will accept after discounts. Orders are checked against it after group price and scheme are applied.
Step 4: Plan Territories and Beats
Set up territories and journey plans so each member of the sales team has a defined list of distributors to cover.
Step 5: Take Orders, Pick by Lot and Invoice
Sales orders carry the group price and scheme. Stock is picked by lot, dispatched and invoiced with a GST invoice raised from the order.
Step 6: Post Collections Against Invoices
Money collected on the beat is deposited against the distributor's invoices and becomes a payment receipt, so outstanding is correct the same day.
Step 7: Review Schemes, Margins and Outstanding Weekly
Go through scheme cost, margin by distributor, collections by beat and overdue by age with sales and accounts together.
Because distribution runs on the same system as production, stock and accounts, one place answers both "what can we make and dispatch" and "who owes us and why". See the Incense Edition page for everything that is included.
Frequently Asked Questions
How should an agarbatti brand manage distributor schemes?
Record each scheme once with its products, benefit, dates and who it applies to; apply it on the sales order rather than through later claims; check every order against a margin floor after discount; and review each scheme's cost against the extra volume it brought.
What is a margin floor?
It is the lowest margin you are willing to accept on an order after all prices, schemes and discounts are applied. In the ERPDrive Incense Edition the margin floor is checked after discount, so a combination of schemes cannot take an order below cost unnoticed.
Can ERPDrive manage beats for my sales team?
Yes. The Incense Edition has territories and journey plans that define which distributors each member of the sales team covers.
How do field collections reach the accounts?
Money collected in the field is deposited against the distributor's invoices and becomes a payment receipt in the ledger, so distributor outstanding is up to date the same day.
Can different distributors have different prices?
Yes. Customers sit in groups, each with its own pricing, so price differences are set deliberately and applied automatically on the order.
Conclusion: Put the Market on the Same Record as the Factory
An agarbatti brand can run a careful factory and still lose margin in the market, a few rupees at a time, through prices nobody set, schemes nobody counted and collections nobody posted. Record the price, the scheme and the payment on the order and the invoice, check every order against a floor, and plan the beats, and the market becomes as measurable as the factory.
The ERPDrive Incense Edition runs customer group pricing, trade schemes, the margin floor, territories, beats and field collections on the same system as production, stock and GST accounts. Book a free demo to see it with your own distributors, or message us on WhatsApp.