What Is Multi-Site (SyteLine)?

Multi-Site (SyteLine) Explained

A site in SyteLine is the operational boundary: it owns inventory, jobs, orders, and shop transactions, and planning runs per site. Above sites sit entities, which represent the legal and financial reporting structure. Sites can share a database or live in separate databases on separate servers, grouped into site groups that define which sites can see and transact with each other. This flexibility is why SyteLine suits manufacturers who grew by acquisition and now run plants with genuinely different processes.

Inter-site transactions are the operational payoff. A transfer order moves inventory from one site to another with in-transit visibility and proper accounting on both ends. Centralized order entry lets one customer service group take orders and source them from whichever plant can supply. Multi-site planning can consider supply at sister sites before creating new supply. Each of these depends on replication being configured correctly so both sites recognise the same items and customers.

Financially, entities aggregate site results for statutory reporting, with intercompany accounting handling transactions that cross legal boundaries. For a defense contractor with a segregated ITAR facility, or a group with separate legal entities per country, this structure is not optional - it is the requirement that drives the whole design. Getting the site and entity mapping right at implementation is far cheaper than restructuring later, when years of transactions carry the original assignment.

The recurring failure is treating multi-site as a technical setting rather than an operating model decision. Sites determine where planning boundaries fall, where inventory is visible, how transfers are costed, and which numbers roll up to which legal entity. Those are executive decisions about how the business runs. When they are made by an implementation team in a configuration workshop, the result is usually a structure that fights the business for a decade.