SyteLine, CloudSuite Industrial, SX.e, CloudSuite Distribution: Infor's ERP Names Explained

A plant controller says the company runs SyteLine. The IT lead says CloudSuite Industrial. The partner's proposal says CSI. The finance director, reading all three documents, reasonably assumes the business is evaluating three systems. It is running one.

Infor's product names have changed enough times that the same ERP now shows up under two or three labels in a single meeting, and the distribution side has the same problem: SX.e and CloudSuite Distribution are one product, described differently depending on who is talking and when they learned it. Before anyone can scope an integration, a migration, or a storefront, everyone in the room has to agree which system is actually running.

Quick answer: SyteLine and Infor CloudSuite Industrial (often shortened to CSI) are the same manufacturing ERP; SyteLine is the long-standing name, CloudSuite Industrial is the cloud-era branding, and Infor's own 2026 product page uses both. Infor Distribution SX.e and Infor CloudSuite Distribution are the same wholesale distribution ERP; CloudSuite Distribution is the cloud edition, and Infor's documentation library for CloudSuite Distribution describes the product as Distribution SX.e. "CloudSuite" is a delivery and packaging brand rather than a product of its own, so the useful question is always which engine sits underneath. M3, LN, and VISUAL are separate Infor ERPs, not other names for these two.

The name map

SyteLine, CloudSuite Industrial, CSI. One ERP for discrete and process manufacturers: job orders, estimates, shop floor scheduling, MRP, and the costing behind them. Infor currently markets it as Infor SyteLine, describes it as multi-tenant and cloud-native on AWS, and positions it for industrial machinery, electronics, fabrication, food and beverage, automotive, and aerospace manufacturers.

Distribution SX.e, SX.e, CloudSuite Distribution. One ERP for wholesale distributors: branches, a counter, matrix pricing, and the account hierarchies that decide what each buyer can see and buy. It is the default system across much of electrical, industrial, plumbing, and janitorial distribution.

M3. A different ERP, strong in food and beverage, fashion, chemicals, and process manufacturing, with a cloud edition referred to as M3 CE. It is not a renamed SyteLine or SX.e.

LN. A different ERP again, built for multi-company, multi-currency enterprise manufacturing, common among automotive and aerospace suppliers.

VISUAL. Infor's order-centric ERP for make-to-order and job-shop manufacturers, separate from SyteLine despite serving similar shops.

The pattern that clears up most confusion: an Infor name with "CloudSuite" in it describes how a product is packaged and delivered, while SyteLine, SX.e, M3, and LN describe the engine doing the work.

Why the names keep shifting

Infor built its product line through acquisitions and then, over the last decade, wrapped those products in industry-branded cloud suites. The engines kept running under their original names inside customer companies, where people had used them for years, while the marketing moved to CloudSuite. The result is two vocabularies living side by side: the practitioner's name, which is what the product was called when the team was trained on it, and the vendor's current name, which is what appears on the renewal.

Infor itself does not pick one. Its current SyteLine product page is titled "Infor SyteLine," describes the product as multi-tenant cloud-native on AWS, and carries an FAQ asking what the difference is between Infor SyteLine and Infor CloudSuite Industrial, which is about as clear a signal as a vendor can give that its own customers are confused. On the distribution side, Infor's documentation sits in the CloudSuite Distribution Library while naming the product Infor Distribution SX.e, and its text moves between "CloudSuite Distribution" and "Distribution SX.e" within the same page.

What actually differs is deployment

If the names are interchangeable, the thing that is not interchangeable is where the system runs. The same ERP can be multi-tenant cloud, hosted by Infor and updated on Infor's schedule, or an on-premises or single-tenant installation run by the customer. Infor's own migration program, Infor Leap, exists specifically to move on-premises and single-tenant customers onto the multi-tenant CloudSuites.

For any project that touches the ERP, that deployment question matters far more than the product name. It changes who configures integration endpoints, which authentication design applies, how much can be customized, and how upgrades land. On SX.e, for example, a CloudSuite tenant normally has its integration endpoint configured by Infor Cloud Service, while an on-premises install is configured by the customer's own team, and on SyteLine the choice between the native IDO REST path and the ION API gateway depends on the same distinction. Two companies that both say "we run CloudSuite Industrial" can be scoping very different projects.

How to tell which one you run

Four questions settle it in one conversation, without anyone arguing about names.

What does the business do all day? Job orders, estimates, bills of material, and a shop floor point to SyteLine. Branches, a counter, and matrix pricing point to SX.e. Lot traceability, catch weight, or a style and color matrix usually point to M3.

Who hosts it? If Infor hosts it and updates arrive on Infor's calendar, you are on a multi-tenant CloudSuite. If your team or a partner applies upgrades to servers you control, you are on-premises or single-tenant, whatever the contract calls it.

What does the version string say? SX.e documentation is published by release, such as 2026.x, and your system's about screen or your partner can tell you exactly which release is live. That string, not the brand, is what an integrator scopes against.

What does the support portal call it? Infor's own community forums file SyteLine discussions under CloudSuite Industrial and SX.e topics under CloudSuite Distribution, which is a quick way to confirm the pairing for your own system.

What each name means for a Shopify project

Once the engine is identified, the integration questions become specific, and they differ sharply by product. The fuller breakdown by product lives on Uncap's Infor to Shopify integration overview; the short version follows.

On SyteLine, the deciding issue is availability: Infor documents that availability is on hand minus allocations, and SyteLine's built-in available-to-promise and capable-to-promise logic can give buyers a date for made-to-order items, which is covered in depth on the Infor SyteLine integration page. On SX.e, the deciding issue is pricing: matrix pricing is documented by numbered price types, Infor publishes a Service Interface REST API with named pricing endpoints, and the details are on the Infor SX.e integration page.

M3 is the one Infor product with an official Shopify connector, and Infor's own guide describes it as a basic integration for a business-to-consumer model, which is why wholesale M3 users usually need more than it provides; the Infor M3 integration page walks through exactly what the connector does and does not cover. SyteLine and SX.e have no official Shopify connector at all, so the connection is built against the documented API surface, which is where knowing the deployment model pays off on day one.

Across all of them, the architecture is the same one Uncap Connect is built on: the Infor system stays the source of truth for pricing, inventory, and accounts, and Shopify renders what the ERP resolves. Uncap has been a Shopify Platinum Partner since 2013, with 380+ storefronts launched on Shopify, including for manufacturers, distributors, and wholesalers. Talk to Our Experts and bring three facts, the product name your team uses, who hosts it, and the release string, and the first scoping conversation can start from the real system instead of the brochure.