The item master is the most-read table in any ERP. Every purchase order line, sales order line, bill of materials, stock movement and journal for inventory points at an item. If the item is set up badly (two codes for the same bolt, the wrong unit, no cost), every document built on it inherits the mistake.
In a spreadsheet, an item is usually just a name in a column, spelled slightly differently on each sheet: "Baut M8x20", "BAUT M8 X 20", "bolt m8-20". An ERP needs one code per thing you stock, buy or sell, and it needs to know a few facts about that thing before anyone can transact with it.
What makes a good item code
The SKU (stock keeping unit) is the item's permanent key. A few rules that consultants apply everywhere:
- One code per physically different thing. If two products are interchangeable on the shelf, they are one item. If a customer or an inspector would care about the difference (size, grade, colour), they are two.
- Do not encode too much meaning. A code like
RM-STL-PLT-3MMis readable, but long "intelligent" codes break when the classification changes. Keep the code short and stable; put the details in the name and fields. - Never reuse a code. When an item is discontinued, mark it inactive. Its history (receipts, sales, costs) must still point to the same code.
- Name it the way people search. Noun first, then attributes: "Bolt hex M8 x 20 zinc", not "Zinc-plated hex bolt for frame".
Item types
Item type tells the system how an item is used. Voltrus has three:
| Type | Used for | Typical flow |
|---|---|---|
raw | Raw materials and bought-in components | Bought on a PO, consumed by work orders |
finished | Products you make (or buy) and sell | Produced by work orders or bought, shipped on sales orders |
consumable | Supplies used up in operations | Bought and issued, not built into products |
Other ERPs also have service, phantom (a sub-assembly that is never stocked) and kit types. Voltrus does not. Services you sell or buy are best invoiced as standalone invoice lines rather than as stocked items, and a sub-assembly is modelled as a finished item with its own bill of materials.
Units of measure and conversions
Every item has one base unit (uom): the unit stock is counted and valued in. Choose the smallest unit you ever count, because stock can only be as precise as its base unit.
Suppliers and customers often trade in other units. Cable is stocked in metres but bought by the 100 m roll; screws are stocked as pieces but sold by the box of 200. In Voltrus each extra unit is an item unit conversion: one row says 1 of this unit = factor × base unit.
| Item | Base unit | Alternate unit | Factor |
|---|---|---|---|
| CABLE-NYM-3x2.5 | m | ROLL | 100 |
| SCREW-M4x10 | pcs | BOX | 200 |
| PAINT-WHITE | l | PAIL | 20 |
Purchase order, sales order and BOM lines can then be written in the alternate unit. A PO for 5 ROLL of cable receives 500 m into stock, because stock always moves in the base unit. Prices on the line follow the line's unit.
Cost
The item's unit_cost is the value the system uses for inventory under moving average and standard costing, and the starting point for cost roll-ups. On import it is your best current cost; afterwards it is maintained by the system (moving average re-prices it on each receipt) or by a released standard cost estimate. How each method works is explained in Inventory valuation.
Planning fields
These fields decide how the system suggests replenishment. They can be filled later, but an item with none of them will never trigger a purchase suggestion.
| Field | Meaning |
|---|---|
planning_method | mrp (default): plan from demand. reorder_point: min/max. none: never suggest. |
reorder_point | The "min" for reorder-point items. |
max_qty | The order-up-to level for reorder-point items. |
safety_stock | A buffer MRP tries to keep on hand. |
lead_time_days | Days from ordering to receiving (if no supplier lead time). |
min_order_qty, order_multiple | Suggested quantities are rounded up to the minimum, then to the multiple. |
Per-warehouse overrides live in item warehouses, and the supplier's own lead time and part number in item suppliers. Reorder points, safety stock and lead times explains how to set the numbers.
Tracking
The tracking field is none, lot or serial. Lot tracking records a batch number (and optionally an expiry date) on every movement; serial tracking records each unit individually. Decide this at setup: it changes what the warehouse must record on every receipt and shipment. See Lots, serials and quality inspection.
In Voltrus
Checklist
- Clean duplicates out of your item list before importing.
- Pick a short, stable code scheme and write it down.
- Choose each item's base unit as the smallest unit you count.
- Add unit conversions for every unit a supplier or customer uses.
- Decide lot or serial tracking per item before the first receipt.
- Fill planning fields for at least your top 20% of items by value.