In a spreadsheet company the "price list" is usually a file on someone's laptop, last updated two years ago, with exceptions remembered by the sales team. Two salespeople quote the same customer different prices, the invoice uses a third, and the customer disputes the bill. Pricing in an ERP is about one thing: the price on the invoice should come from a rule you set on purpose, and you should be able to see which rule it came from.
Price lists
A price list is a table of prices with a scope. The usual design:
- One default selling list that applies to everyone without a special arrangement.
- Customer-specific lists for key accounts or channels (distributor, retail, export).
- Quantity breaks: a lower unit price from a minimum quantity, for example Rp 52,000 from 1 unit and Rp 48,000 from 100.
- Validity dates, so next year's prices can be loaded in December and take effect on 1 January without anyone remembering to switch.
- Per currency and unit of measure, so an export customer has USD prices and a carton price is not confused with a piece price.
Buying prices follow the same structure: a supplier's prices are a buying list.
The order prices are found in
When a line is entered without a typed price, a good ERP looks for a price in a fixed order and records where it came from. Voltrus uses:
- The customer's own price list.
- The default price list.
- The last price this item was sold at.
The line keeps a price source (manual, quotation, customer price list, default price list or last price), so anyone reviewing an order can see whether a price was typed by hand.
Worked example
Price lists: the default list has item BRK-10 at Rp 52,000 from 1 unit. PT Maju's list has Rp 50,000 from 1 unit and Rp 47,000 from 100.
| Customer | Quantity | Price found | Source |
|---|---|---|---|
| PT Maju | 40 | 50,000 | Customer price list |
| PT Maju | 150 | 47,000 | Customer price list (break at 100) |
| CV Baru (no list) | 40 | 52,000 | Default price list |
| CV Baru, item not on any list | 40 | last sold price | Last price |
Voltrus re-prices a draft line automatically when its quantity, unit, item or customer changes, as long as the price came from the system. A price that was typed, or copied from a quotation, never changes on its own.
Discounts
Discounts are better kept separate from the price, so you can see what you gave away. Indonesian trade often uses stacked discounts written as "10+5": 10% off, then 5% off what remains, which is 14.5% in total, not 15%.
| Amount | |
|---|---|
| List price | 100,000 |
| Less 10% | −10,000 |
| Subtotal | 90,000 |
| Less 5% of 90,000 | −4,500 |
| Net price | 85,500 |
Voltrus order lines carry two stacked discounts and calculate them this way.
Quotations
A quotation is a formal offer: these items, at these prices, valid until this date. It does not post anything to the ledger and does not reserve stock. Its value is in the record: what was offered, to whom, and whether it was won.
A quotation moves through clear statuses:
| Status | Meaning |
|---|---|
| Draft | Being prepared. |
| Sent | Given to the customer. |
| Accepted | The customer agreed. |
| Rejected | The customer declined. Record why: it is your best pricing feedback. |
| Expired | The validity date passed without an answer. |
| Converted | Turned into a sales order. |
Converting a sent or accepted quotation creates a draft sales order with the same lines, prices and discounts, and the order line's price source becomes quotation. That link is what makes quoting worth the effort: no retyping, and no dispute about the agreed price.
In Voltrus
From a quotation, Next steps offers the status moves and Convert, which opens the new draft sales order. Customer items print the customer's part number and description on delivery orders and invoices.
Print on a quotation opens a printable offer with your letterhead, the lines, discounts, the validity date, PPN estimated at the company rate when the customer is taxable, and a signature box for the customer's acceptance; print it to PDF and send it. Quotations have no document number of their own, so quote the customer's reference or the date when you follow up. Purchasing has a quotation comparison by item in the API, but no screen for it yet.
Checklist
- Create one default selling price list before the first order, with validity dates.
- Give key accounts their own list instead of manual prices.
- Load quantity breaks where you actually offer them.
- Quote from the system and convert, never retype.
- Record the reason on every rejected quotation.
- Review manual-price order lines weekly.