Infor LX

Name: Infor LX
Brand: Infor

Infor LX is an enterprise resource planning (ERP) system for manufacturers that provides manufacturing operations, supply chain, and financial management functionality with extensibility via the Infor Development Framework and integration through Infor OS components.

Est 2002|Valuation $11B|Raised $1B|1 Ref Customers

LinkedIn 923K|Website|Web traffic 4.1M|FTEs 17,000|HQ Alpharetta, Georgia, US

MarketsERP

Platform CoversManagement Reporting Budgeting & Forecasting

Published Oct 14, 2026

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - Very small manufacturers (for example under ~50 employees) may find LX heavier than necessary compared with lightweight SMB ERPs. - Very large enterprises standardizing on a single global ERP platform (such as SAP S/4HANA or Oracle ERP Cloud) may prefer those global platform approaches. - Industries or use cases where competitors are more aligned - Professional-services-dominated businesses without manufacturing needs may be better served by services-oriented ERP systems. - Organizations prioritizing immediate, self-serve cloud analytics and a large marketplace of third-party integrations may find cloud-native alternatives more aligned. - Technical requirements that this product cannot meet - Organizations explicitly excluding IBM i deployments should consider alternatives. - Budget constraints that make alternatives more appropriate - Organizations that require predictable, low-cost SaaS with published list pricing and minimal implementation overhead may prefer cloud-first competitors with transparent pricing models. - Specific workflows or integrations where the product may be limited - Organizations whose analytics strategy requires unrestricted direct database access to cloud-hosted databases should validate the vendor's cloud data access model and contractual data access provisions. - Red flags in the buying process - No public free-trial model is evident for LX; procurement is typically conducted via enterprise contracting and negotiated terms. - Current limitations acknowledged by the vendor - Vendor materials do not present a consolidated public list of product limitations; modernization and enhancement communications are framed as product development activity. - Features on the roadmap (not yet available) - Vendor references to ongoing releases and modernization exist (for example release numbering was cited in documentation), but detailed roadmap timelines were not surfaced in the accessible materials. - Scale limitations - Vendor markets LX as scalable; no public, defensible scale breakpoint data was found for LX in the accessible materials. - Security or compliance gaps - Product-scoped SOC2/ISO certifications for LX are not clearly documented publicly; cloud-level attestations exist but procurement must validate scope and applicability. - Technical debt or architectural limitations mentioned in reviews - LX-specific public review excerpts were not accessible. Broader Infor ERP discussions indicate potential user experience and reporting friction in some installations. - API limitations or integration constraints - Integration patterns rely on Infor OS/ION constructs, which adds integration configuration and operational scope.

Deal disqualifiers: what makes a poor fit

Organizational mandates excluding IBM i; requirement for transparent, self-serve SaaS pricing and rapid trial-based evaluation; policies requiring direct SQL-level access to cloud-hosted databases for analytics without contractually defined data access provisions.

Reasons customers left for competitors (churn reasons)

Accessible sources did not provide robust LX-specific churn narratives. Based on adjacent ERP discussions, plausible drivers include user experience concerns, constraints in cloud data access models, and a preference for more modern analytics and integration approaches.

02Why they buy

- Documented competitive advantages and evidence - Public third-party validation specific to LX is limited. Vendor materials and the product's IBM i heritage are the primary sources for claims of platform continuity and manufacturing depth. - Unique features and capabilities - IBM i–native heritage and BPCS lineage are technical differentiators for organizations seeking continuity on that platform. - Areas where competitors have advantages - Broader partner and talent availability in SAP and Microsoft ecosystems; cloud-native suites may offer more modern UX and marketplace integrations.

03Field reports

Direct quotes from Gartner Peer Insights, Reddit, TrustRadius, G2, HackerNews

- Gartner Peer Insights: LX-specific content on Gartner appears limited; available public items reference Infor as a vendor or other Infor products rather than LX-specific reviews. - G2 (Infor LX): A G2 listing showed a modest aggregated rating based on a small number of reviews; conclusions from the aggregated rating should be cautious. - Capterra: The public listing for LX had insufficient review data at the time of access. - Reddit: Community posts referencing other Infor products describe reporting and usability frustrations in some cases. These posts are about other Infor ERP products but are directionally relevant to concerns around data accessibility and user interface expectations in legacy ERP environments. - HackerNews: No substantial LX-specific discussions were identified in the accessible results.

Balance: positive and negative reviews

Public review platforms show a mixture of positive and negative comments, but review volumes for LX are limited and thus not a reliable statistical sample.

Common criticisms and complaints (support issues, bugs, missing features)

Public, LX-specific complaint frequency is low due to limited LX-specific review volume. Adjacent Infor ERP discussions highlight recurring themes such as usability/search issues and data access/reporting friction; these should be investigated in reference checks for LX.

Reasons customers chose this product over alternatives

Vendor materials and contextual references indicate selection reasons may include platform fit with IBM i environments, depth of manufacturing functionality, and continuity with BPCS lineage in long-running installations.

Specific outcomes customers achieved (with metrics when available)

Vendor-hosted customer stories exist (e.g., Trinity Industries; Clover Dairy) but public summaries do not consistently include independently verified KPI metrics; treat vendor-published metrics as vendor-reported unless independently corroborated.

Customer pain points and frustrations mentioned in reviews

Most directly observed pain points were associated with other Infor ERP products: reporting/data pipeline effort, search/usability complaints, and cloud database access concerns.

Deal-breakers and reasons customers didn't purchase

Not well documented specifically for LX in accessible public reviews; likely procurement considerations include lack of transparent pricing, IBM i platform requirements, and integration/analytics expectations.

Case Studies

- Detailed customer success stories with metrics - Vendor-hosted case study content is available for customers such as Trinity Industries and Clover Dairy. The publicly available summaries do not consistently include quantified KPIs. - Specific results and quantified business impact - Not extractable from the available summaries; vendor-published results lack independent verification in the accessible excerpts. - Implementation details and time to value - Not provided in accessible summaries; additional information should be requested directly from the vendor or from customer references. - Challenges faced during adoption and how they were resolved - Not detailed in accessible summaries. - Note when metrics are vendor-published without independent verification - The vendor-hosted case studies should be treated as vendor-reported unless independent corroboration is provided. - Note methodology gaps - ROI and operational benefit claims in vendor case studies do not always include methodology or measurement details in the accessible extracts. - Include mixed results - projects that struggled or failed when available - No credible public write-ups of failed LX implementations were found in the accessible sources.

04Best fit

Company sizes: employee counts and revenue ranges

Typical fit (inferred): midmarket manufacturers with employee counts from lower hundreds up to a few thousand and revenues ranging from tens of millions up to around a billion.
Larger enterprises may use LX in specific divisions or where IBM i is entrenched.

Industries and verticals where adoption is strongest (with customer examples)

Process and discrete manufacturing.
Vendor-hosted examples include Trinity Industries and Clover (dairy/food manufacturing context).

Roles and personas: decision makers AND end users

Decision makers: CIO/IT Director (especially IBM i leadership), CFO/Controller, VP Operations / Plant leadership.
End users: production planners, schedulers, procurement and inventory teams, shop floor supervisors, finance/AP/AR staff.

Pain points and challenges the product addresses

Integrated manufacturing, supply chain, and finance workflows; suitability for multi-site operations; extensibility via IDF and Infor OS for reporting and workflow automation.

Qualification criteria: what makes a suitable fit

Existing IBM i investment and a requirement to continue that platform; manufacturing process complexity that benefits from mature ERP workflows; willingness to invest in integration and modernization via Infor OS components.

Real customer examples with company names when available

Trinity Industries (vendor-hosted customer story)
Clover Dairy / Clover Industries (vendor-hosted resource)

05The pitch

What the product does (core value proposition in objective terms)

- Infor LX is an enterprise resource planning (ERP) system for manufacturers, with modules covering manufacturing operations, supply chain, and financial management. - Vendor materials describe LX as applicable to both process and discrete manufacturing and note included tools for reporting, workflows, alerts, and dashboards when used with Infor’s broader technology platform (Infor OS). - Vendor documentation describes extensibility through the Infor Development Framework (IDF) and integration via Infor OS components (for example, ION-based integrations referenced in LX configuration documentation).

Target market and market positioning

Primary target: manufacturing companies operating on IBM i (AS/400 / iSeries) infrastructure that require ERP functionality for manufacturing processes and stable operational behavior.
Vendor materials indicate deployment in multiple countries; a specific, independently verifiable customer count for LX is not publicly available.

Get a comprehensive analysis of Infor LX including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →