What Is Item Master?

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.