What Is Product Code?
Also known as: product codes, item group, GL product code
Definition
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.
Product Code Explained
Product code is deceptively important. It looks like a classification field, but it is actually the bridge between the manufacturing system and the general ledger. When an item is received, issued, scrapped, shipped, or invoiced, SyteLine looks to the product code to determine the inventory, cost of sales, revenue, and variance accounts for that posting. Change an item's product code and you change where its money lands in the chart of accounts.
Because it is required on every item, the product code also becomes the default reporting dimension for product-line analysis: gross margin by product code, inventory value by product code, scrap by product code. Most SyteLine sites end up managing their business through this lens, which means the structure you design during implementation determines what management can see for years afterwards. Too few codes and everything is one blur; too many and reporting fragments and account maintenance becomes a burden.
Design should follow the way the business is actually managed rather than the way engineering classifies parts. If leadership reviews performance by market segment, the product code structure should let them. If profitability is managed by manufacturing process, structure accordingly. A frequent mistake is to mirror an existing part-numbering scheme, which usually reflects historical engineering logic and rarely aligns with how anyone reads a P&L.
Changing product codes after go-live is possible but consequential. Historical transactions retain their original account postings while new transactions follow the new mapping, so year-over-year comparisons break unless the change is timed to a fiscal boundary and documented for finance. Plan the structure carefully during implementation, and if a change becomes necessary, treat it as a controlled finance project rather than a data cleanup task.
Why It Matters
- Product codes drive general ledger account determination, making item setup a control point that finance must own jointly with operations.
- They are the default dimension for margin and inventory reporting, so the structure defines what management can analyze.
- Changing codes after go-live breaks period-over-period comparability unless carefully timed and documented.
- A poorly designed structure forces finance into spreadsheet reallocation every month, a permanent and avoidable cost.
In Practice
Design product codes by starting from the management reporting pack, not the item master. Ask finance to show the profitability views they actually present to leadership, then confirm every one of those views can be produced by grouping product codes. If any view requires a manual reallocation, the structure is wrong and it will stay wrong for years.
Frequently Asked Questions
Why does every SyteLine item need a product code?
Because the product code determines which general ledger accounts the item's transactions post to - inventory, cost of sales, revenue, and variance accounts. Without it, SyteLine cannot resolve account determination for a receipt, issue, or shipment. It doubles as the primary reporting dimension for product-line margin and inventory analysis, which is why finance should approve the structure.
Can I change an item's product code after go-live?
Technically yes, but historical transactions keep their original account postings while new ones follow the new mapping, which breaks period-over-period comparability. If a change is genuinely needed, time it to a fiscal year boundary, document the mapping for finance and audit, and consider whether reclassifying historical balances is required for meaningful trend reporting.
Related Terms
Item Master
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.
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.
Multi-Site (SyteLine)
Multi-site in SyteLine is the architecture that lets one installation run several plants, warehouses, or legal entities as distinct sites - each with its own inventory, planning, and transactions - while sharing master data and consolidating financially.
Go Deeper
SyteLine Implementation Cost Calculator
Estimate the full first-year cost of an Infor SyteLine implementation, including licensing, services, data migration, and internal effort.
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 9 to 10 Upgrade: Step-by-Step Guide
Plan your SyteLine 9 to 10 upgrade with this step-by-step guide: Mongoose framework changes, FormSync customization merges, timelines, costs, and testing.
Working with Product Code in a live environment? Our engineers do this every day - and our AI agents automate most of it.
Try it here, free
Contribution Margin by Product Worksheet
Compare products by contribution margin per unit, per product line and as a percentage of revenue, then export the table to Excel.
New to Infor SyteLine? Start with the Infor SyteLine guide and toolkit, or plan with Training Path Builder, ERP Certification Study Planner, Upgrade Path Planner.
Keep exploring
Free tools
- Contribution Margin by Product WorksheetCompare products by contribution margin per unit, per product line and as a percentage of revenue, then export the table to Excel.
- Product Compliance Test Plan and Budget WorksheetPlan every test needed to sell a product in each market, with cost, lead time and a running total you can export to Excel.
- Inventory Subledger to GL Reconciliation SQL GeneratorGenerates a SQL query that compares inventory subledger value with the GL inventory accounts and shows the difference by account and period.
ERP fixes and how-tos
- How to Change an Item's Standard Cost in SyteLineUpdate a SyteLine item's standard cost by hand or through Cost Rollup, then run Recost Inventory to revalue on-hand stock and post the GL variance correctly.
- How to Run a Cost Rollup in SyteLineRun a SyteLine standard cost rollup: use Simulate mode first, fix variance exceptions from missing routings or zero-cost items, then post new standard costs.
- Fixing SyteLine's 'transaction out of balance' GL posting errorSyteLine's GL posting error for an out-of-balance transaction usually points to a rounding issue, a missing account mapping, or a partially-costed transaction. Here is how to trace it to the source module.
Guides
- How to Configure General Ledger Posting in SyteLineGuide to configuring general ledger posting in Infor SyteLine. Set up chart of accounts, posting rules, transaction types, and GL distribution for manufacturing transactions.
- How to Set Up Item Master Defaults in Infor SyteLineStep-by-step guide to setting up item master defaults in Infor SyteLine. Configure default planning, costing, and inventory settings for new items.
- SyteLine Chart of Accounts Design Best PracticesDesign an effective chart of accounts in Infor SyteLine with best practices for account structure, segmentation, and financial reporting configuration.