Infor SyteLine (CloudSuite Industrial): a reference guide

Versions and release history

What SyteLine is and who uses it

SyteLine is a manufacturing ERP that covers order entry, planning, production, purchasing, inventory, service and financials in one SQL Server database. It was created by Symix for discrete manufacturers and grew to support engineer-to-order, make-to-order and mixed-mode production under the Frontstep and MAPICS names before Infor acquired it in 2005.

Infor positions CloudSuite Industrial for small and midsize industrial manufacturers, with micro-verticals such as machinery and equipment, electrical and electronics, metal fabrication, plastics, medical devices, furniture and fixtures, and windows and doors. Searches for Siteline, Sytline or Sightline ERP refer to this same product.

Do not confuse it with Infor CloudSuite Industrial Enterprise, a separate product for large multi-site, multi-company manufacturers that comes from the Infor LN code line, not SyteLine.

Go deeper: Netray SyteLine services, Glossary: CloudSuite Industrial, Infor LN vs SyteLine selector

SyteLine modules

Infor groups SyteLine functions by area rather than selling a long list of separately named modules. The list below follows the functional areas used in Infor's own SyteLine release documentation; some, such as Service and APS, are licensed as options.

• Customer service and order management: quotes (estimates), customer orders, pricing and promotions, shipping and invoicing
• Manufacturing: items, bills of material, routings, jobs, production schedules, shop floor reporting and costing
• Material planning: MRP and the Advanced Planning and Scheduling (APS) engine for finite and infinite planning
• Procurement and inventory control: purchase orders, receiving, lot and serial tracking, cycle counting
• Financials: general ledger, accounts payable, accounts receivable, fixed assets, multi-currency
• Project management for contract and engineer-to-order work
• SyteLine Service (formerly Infor Field Service-Plus): service orders, contracts and units
• Product configuration (Infor PCM, and Infor CPQ in newer releases)
• Data collection, portals, Microsoft Outlook and Excel add-ins, mobile access
• Multi-site: several sites per database, with replication between sites and intranets

Go deeper: SyteLine configurator best practices, Glossary: SyteLine APS, Glossary: SyteLine multi-site, SyteLine MRP vs APS assessment

Architecture: Mongoose, IDOs, forms and servers

SyteLine is built on Infor Mongoose, a .NET framework in which the application is defined largely by metadata stored in SQL Server. Forms (the user interface), IDOs (Intelligent Data Objects, the mid-tier business objects) and Application Event System handlers (business processes) are all metadata, which is why customer changes can be kept apart from the base product and carried forward with tools such as FormSync.

A typical on-premises CSI 10 install has a SQL Server database server, one or more utility (application) servers running the IDO Runtime Service under IIS, and optional servers for reporting, APS planning, Infor OS and Factory Track. The utility server renders the IDO layer and also runs background tasks, scheduling and alerting; Infor recommends a separate utility server in the DMZ for internet-facing access.

Users work in a browser client that renders every form, including customized ones, as an HTML5 page. The older Windows smart client still exists but Infor states it is being phased out in favour of the browser.

Go deeper: Glossary: Mongoose, Glossary: IDO, Glossary: Application Event System, SyteLine SQL Server performance tuning

On-premises SyteLine vs CloudSuite Industrial in the cloud

The application code is the same; what changes is who runs the servers and how far you can reach into them. In Infor's multi-tenant cloud on AWS, changes must be made with the Mongoose tool set, direct access to the databases and servers is not permitted, and each customer's personalizations are stored in a separate database.

On-premises and customer-hosted sites can still write SQL Server stored procedures, triggers, custom tables and direct database integrations. Those are the items that need the most rework when moving to the cloud, because they have to be rebuilt as IDO extensions, event handlers or ION flows.

Upgrades also differ. Cloud tenants receive updates on Infor's schedule, while on-premises customers decide when to upgrade and must reach version 10 before they can apply current feature releases. Infor runs a fixed-scope program (Infor Leap) for moving on-premises customers to its cloud.

Go deeper: SyteLine to CloudSuite migration, SyteLine to CloudSuite upgrade cost estimator, CloudSuite Industrial AI, on-prem options

Integration: ION, BODs, ION API, EDI, e-commerce and CRM

Infor ION is the standard integration layer. Mongoose maps SyteLine IDOs to ION BODs (Business Object Documents), so documents such as sales orders, items and shipments can be published to or received from other Infor and third-party applications, and the Event System handles received BODs.

For synchronous calls, external programs can use IDO web services (SOAP and REST) or .NET classes. In current releases a REST API Wizard generates a REST endpoint with Swagger documentation for a chosen IDO, which can then be exposed through the ION API gateway with OAuth 2.0.

EDI, e-commerce storefronts and external CRM systems are normally connected through ION, IDO web services or an EDI translator rather than direct table writes. SyteLine also has its own customer contact and CRM functions, which were expanded in 8.01.

Go deeper: How to set up SyteLine ION integration, SyteLine ION API integration guide, SyteLine EDI integration guide, SyteLine e-commerce integration guide

Implementation, upgrades and support

Infor does not publish SyteLine list prices. License or subscription cost depends on deployment model, named or concurrent users, and which optional products (APS, Service, CPQ, Factory Track, Infor OS) are included; implementation cost depends on the partner's rates and the scope of the project.

Timeline and cost are driven mostly by the number of sites and companies, data conversion quality, the number of integrations, the volume of custom reports, and how many customizations must be carried forward or rebuilt. Upgrades from 8.x or 9.x to version 10 add report migration (custom SSRS reports to Mongoose Reporting), form and IDO revalidation, and regression testing.

Infor's partner Guide Technologies states that version 10 is the only SyteLine version Infor still maintains. Customers on 8.x or 9.x should check their support status with Infor and plan an uplift to 10 or a move to the cloud.

Go deeper: SyteLine implementation cost guide, SyteLine 8 to 10 upgrade guide, SyteLine 9 to 10 upgrade checklist, SyteLine version EOL risk assessment

Customizing and developing on SyteLine

Most changes need no code: form personalization, design mode edits to forms, user-defined fields, new IDO properties and relationships, and Application Event System rules that run on inserts, updates or user actions to update data, start a process, request approval or send a notification.

When code is needed, developers write IDO extension classes in .NET (typically C#) that run inside IDO processing, plus form scripts, and can create their own tables, IDOs and forms. Keeping these in Mongoose metadata (rather than modifying base objects) is what lets them survive upgrades and run in the multi-tenant cloud.

On-premises sites can additionally use SQL Server objects and SSRS reports, but those do not carry into the cloud. Changes should move from test to production through Mongoose export and import or FormSync rather than being edited directly in production.

Go deeper: IDO extension class for custom business logic, Debug a Mongoose extension class in Visual Studio, Promote form customizations from test to production, Mongoose customization deployment checklist

Getting help: user groups, community and consultants

The main independent user organization is the SyteLine User Network (SUN), which runs an annual conference for SyteLine and CSI users (its 36th was held in Atlanta in March 2026) plus regional meetings. There are also regional groups, such as a UK SyteLine/CSI user group and a SyteLine Japan group on Infor Community.

Infor's own channels are the Infor Support Portal (cases and knowledge base), Infor Documentation Central at docs.infor.com, the Infor Community forums, and Infor's Inforum customer conference. Many customers also work with an Infor partner or an independent SyteLine consultant for day-to-day support and development.

Go deeper: SyteLine user group events 2026, SyteLine training curriculum guide, SyteLine consultant hiring guide

AI on SyteLine

Infor's GenAI Embedded Experiences add text generation inside CloudSuite Industrial; the 2025.10 release covered material review report and corrective action request text and dunning letter generation. These features are delivered through Infor's cloud platform.

On-premises customers who want AI usually connect a model to SyteLine through IDO REST calls or the ION API, with permissions enforced by SyteLine security, and some keep the model on their own hardware for data control.

Go deeper: Infor SyteLine AI integration, On-prem, air-gapped LLM for SyteLine, SyteLine MCP server

Frequently asked questions