What Is Item Master?
Also known as: item record, SyteLine Items form, item file
Definition
The item master in SyteLine is the central record that defines every part the business buys, makes, stocks, or sells - carrying identity, units of measure, planning parameters, costing method, product code, and quality attributes that drive nearly every downstream transaction.
Item Master Explained
Every material transaction in SyteLine resolves back to an item record. The master carries identity fields such as item number, description, and revision; classification fields including product code, item type, and commodity code; unit of measure with conversion factors; and the flags that determine how the item behaves - stocked or non-stocked, lot tracked, serial tracked, phantom, purchased or manufactured. Those flags are set once and then influence planning, costing, inventory, and quality for the life of the part.
Planning attributes are where item master quality most directly hits the P&L. Order policy determines whether MRP or APS creates lot-for-lot, fixed quantity, or period-based supply. Lead time, safety stock, order minimum, multiple, and yield or scrap factors shape every planned order. A single item with a stale six-week lead time that is actually two weeks will inflate inventory continuously and invisibly, and there are usually hundreds of such items in a system nobody has audited.
Costing is the other high-consequence area. The item's cost method - standard, actual, average, LIFO, or FIFO depending on configuration - governs how inventory value and variances post. Combined with the product code, which maps the item to inventory, cost of sales, and revenue accounts, the item master effectively drives the manufacturing side of the general ledger. Finance rarely realises how much of their close depends on choices a planner made on a part setup screen.
In multi-site SyteLine the item exists at both a shared and a site-specific level, so an item can be replicated across sites while carrying different planning parameters at each. That is powerful and also the source of persistent confusion, because a change made at one site may or may not propagate depending on replication rule configuration. Understanding which fields are site-specific is a prerequisite for any multi-site data governance policy.
Why It Matters
- Item master data quality sets the ceiling on MRP and APS accuracy - no planning engine can outperform its inputs.
- Stale lead times and safety stocks silently inflate working capital across thousands of parts at once.
- Product code and cost method choices on the item drive general ledger postings, making item setup a finance control point.
- Item governance is a recurring audit finding in AS9100 and ITAR-regulated shops where part identity and revision control are inspected.
In Practice
Run a periodic exception report comparing item lead time against actual purchase order receipt lead time over the last twelve months. Items where the parameter exceeds actual by more than fifty percent are directly generating excess inventory. On most installs this one report identifies several hundred thousand dollars of correctable stock.
Frequently Asked Questions
What are the most important fields on a SyteLine item record?
Item type and stocked flag determine how the part behaves everywhere. Product code drives general ledger account assignment. Order policy, lead time, safety stock, and order quantity rules drive every planned order MRP or APS creates. Cost method governs inventory valuation and variance posting. Lot and serial flags are effectively irreversible once transactions exist, so decide them before go-live.
Can item planning parameters differ between sites in SyteLine?
Yes. In a multi-site configuration, some item attributes are shared across sites while planning parameters such as lead time, safety stock, and order policy are maintained per site. That is intentional, since the same part may be purchased locally at one plant and transferred from another. It also means a change at one site does not automatically apply elsewhere unless replication rules say so.
Related Terms
Product Code
A product code in SyteLine is a required grouping assigned to every item that determines which general ledger accounts inventory, cost of sales, and revenue transactions post to, and serves as the primary dimension for product-line reporting.
Phantom BOM
A phantom BOM is a subassembly that exists in the bill of material for engineering clarity but is never stocked or built as its own order. Planning blows straight through it, passing demand directly to its components on the parent job.
Job Order
A job order in SyteLine is the production work order that authorises manufacturing a quantity of an item. It carries its own copy of the bill of material and routing, collects material, labor, and overhead costs, and moves through a defined status life cycle.
Go Deeper
SyteLine MRP Health Check
Diagnose why your SyteLine MRP output is noisy or ignored, scoring data accuracy, parameters, and planner behavior across ten dimensions.
SyteLine Implementation Cost: 2026 Pricing Guide
SyteLine implementation cost ranges from $150K to $1.5M+. See 2026 pricing by company size, phase-by-phase budgets, and the hidden costs to plan for.
SyteLine APS: Advanced Planning & Scheduling Explained
How SyteLine APS advanced planning and scheduling works: CTP order promising, resource groups, APS vs MRP mode, and tuning tips for discrete manufacturers.
Working with Item Master in a live environment? Our engineers do this every day - and our AI agents automate most of it.