Infor SyteLineGlossary

What Is Multi-Site (SyteLine)?

Also known as: multi site, multisite, site and entity structure

Definition

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.

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.

Why It Matters

The site and entity structure sets planning boundaries and inventory visibility, which shapes daily operations at every plant.
Legal entity mapping determines statutory reporting and intercompany accounting, making it a finance and compliance decision.
Restructuring sites after go-live is extremely expensive because historical transactions carry the original assignment.
Segregated facilities for ITAR or export-controlled work depend on correct site design to enforce data boundaries.

In Practice

A test worth running during design: pick your three most common cross-plant scenarios - a transfer, a customer order sourced from another plant, and an intercompany sale - and walk each end to end through the proposed site and entity structure. If any requires a manual journal or a spreadsheet, the structure needs rework before you build it.

Frequently Asked Questions

What is the difference between a site and an entity in SyteLine?

A site is the operational boundary that owns inventory, jobs, orders, and planning - roughly a plant or warehouse. An entity is the financial and legal reporting boundary that aggregates one or more sites for statutory accounts. A single legal entity can contain several sites, and intercompany accounting handles transactions that cross entity boundaries.

Should each plant be a separate SyteLine site?

Usually yes, if the plant holds its own inventory, plans its own production, and needs its own operational reporting. Separate sites give clean planning boundaries and inventory ownership. Use a single site with multiple warehouses only when locations share planning and inventory pools completely - for instance a satellite storage building serving one manufacturing operation.

Related Terms

SyteLine Replication

SyteLine replication is the built-in mechanism that copies data between sites and databases in a multi-site installation. Replication categories define what moves, replication rules define where it goes, and the framework queues and delivers changes between site databases.

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.

CloudSuite Industrial

CloudSuite Industrial (CSI) is the cloud-delivered edition of Infor SyteLine, hosted by Infor on AWS alongside the Infor OS platform. It uses the same Mongoose application but adds managed updates and restricts customization and direct database access.