Overview
Price levels are Luminous's B2B pricing feature — they let you offer different effective prices to different customers without changing each product's published list price. This article covers how to create price levels, how to assign them to customers, and how units of measure (UOM) affect the price that appears on a line item.
For a full explanation of how Luminous resolves which price auto-fills when you open a sales order (priority order, quantity tiers, invoice carry-over), see How do price levels work in Luminous?
Step 1 — Create a price level
- In the main navigation, go to Sales → Pricing.
- Click the Level tab.
- Click Create Level (top-right).
- Fill in the dialog that opens:
- Name — a descriptive label you and your team will recognise (e.g. "Wholesale 10%").
- Type — the calculation method for this level:
- Price-Based — a percentage discount is subtracted from the product's list (wholesale) price.
- Cost-Based — a percentage markup is added on top of the product's weighted average cost.
- Manual — an exact dollar price override is entered per SKU (and optionally per quantity tier).
- Percent Discount — the percentage figure that drives the price-based or cost-based calculation. For Manual levels this field is not used for calculation; prices come from the per-SKU overrides you set separately.
- Click Submit. The new level appears in the Level list.
Step 2 — Assign a price level to a customer
Price levels take effect through the customer (company) record, not the product record.
Set a customer's default price level
- Open the customer's record (Sales → CRM, then select the company on the Companies tab).
- Click Pricing Structure.
- Open the Apply Client Price Level tab.
- Choose the price level from the dropdown and click Save.
This level becomes the default that auto-fills the Price Level field whenever you create a sales order for that customer.
Set category-level price groups
If a customer should get different pricing for different product categories:
- In the same Pricing Structure area, open the Pricing Groups tab.
- Add a pricing group linking a product category (and optionally a subcategory) to a specific price level.
A category-level price group takes priority over the customer's default price level for matching products.
Set per-SKU customer price overrides
For one-off prices that bypass price levels entirely:
- Open the SKU Price Overrides tab in Pricing Structure.
- Enter or import an exact dollar price for the specific SKU.
A customer-specific SKU price overrides everything else — no price level calculation applies to that line.
Step 3 — Add per-SKU price overrides for Manual levels
If you have Manual-type price levels, you need to enter the exact override price for each SKU.
- From a product record: open the product, go to the Pricing tab, attach a quantity pricing schedule, then enter override prices per tier and per price level in the pricing grid.
- Bulk import: go to Tools → Imports, find the Price Overrides import in the Pricing section, and upload a CSV with columns for SKU, Price Schedule, Tier Minimum Quantity, Price Level, and Override Price. You can also access this import from the customer record's Pricing Structure → SKU Price Overrides tab.
How units of measure affect price level calculations
When a sales order line item is entered using a non-base unit of measure (for example, ordering in Cases when the product's base UOM is Each), Luminous automatically adjusts the price using the SKU's configured conversion factor.
What happens at pricing time
- Quantity conversion — Luminous looks up the conversion rule between the ordered UOM and the SKU's base UOM. It multiplies the entered quantity by the conversion factor to get the equivalent base-UOM quantity. This converted quantity is what drives quantity-tier selection in a price schedule.
- Price level applied to the base price — The price-based discount (or cost-based markup) is calculated against the product's per-base-unit price.
- Price scaled back to the ordered UOM — The resulting per-base-unit price is multiplied by the same conversion factor to produce the price displayed per ordered unit.
Example
| Detail | Value |
|---|---|
| Base UOM | Each |
| Ordered UOM | Case |
| Conversion factor | 1 Case = 12 Each |
| Wholesale price (per Each) | $1.00 |
| Price level | Price-Based, 10% discount |
Calculation:
- Discounted per-Each price: $1.00 − 10% = $0.90
- Price per Case: $0.90 × 12 = $10.80
The line item shows a Unit Price of $12.00 (list per case) with a line discount bringing the net to $10.80.
Key points
- The conversion factor used is the SKU-level conversion rule configured under Inventory Admin → Units of Measure → Conversion Rules. If no SKU-specific rule exists, Luminous falls back to the system-level rule for that unit class.
- For kit products, UOM conversion is not applied to pricing — the kit's price is used as-is.
- If no conversion rule exists for the selected UOM, the conversion factor defaults to 1, and the price is returned at the product's base-UOM price regardless of the UOM selected.
- The quantity used for tier matching is the converted (base-UOM) quantity, so ordering 2 Cases (= 24 Each) will match a tier set at a minimum of 20 Each.
Quick reference — where to find each setting
| Task | Where |
|---|---|
| Create / edit price levels | Sales → Pricing → Level tab |
| Assign default level to a customer | Customer record → Pricing Structure → Apply Client Price Level |
| Set category-level price groups | Customer record → Pricing Structure → Pricing Groups |
| Set per-SKU customer overrides | Customer record → Pricing Structure → SKU Price Overrides |
| Set per-SKU manual price overrides (by tier & level) | Product record → Pricing tab; or Tools → Imports → Price Overrides |
| Configure UOM conversion factors | Inventory Admin → Units of Measure → Conversion Rules |