Skip to main content

Epicor iScala — ERP for International Subsidiaries

Epicor iScala at a glance
VendorEpicor Software Corporation
HeadquartersAustin, Texas, USA (product roots: Scala, Sweden)
OwnershipPrivately held; majority owner Clayton, Dubilier and Rice (since 2020)
DeploymentOn-premises or cloud-hosted (not multi-tenant SaaS)
Target marketInternational subsidiaries of midsize and large groups; buying decision often at a US headquarters
IndustriesDistribution, light manufacturing, sales and service organizations, hospitality
PricingNot published; quote-based via Epicor and partners
Websiteepicor.com/en/products/enterprise-resource-planning-erp/iscala

The short version

Epicor iScala is a multi-country ERP for the smaller foreign subsidiaries of midsize and large groups. It gets shortlisted for multi-language and multi-currency operation, country-specific statutory reporting, and consistent intercompany processes across a long list of localizations. A domestic US plant or warehouse almost never runs it; the typical American entry point is a headquarters standardizing its entities in Europe, the Middle East, Africa, or Asia on one system.

Vendor, history, ownership

The lineage traces to Scala Business Solutions, a vendor with Swedish roots that made its name in the 1980s and 1990s supplying localized business software to multinational subsidiaries across Europe, Eastern Europe, and Asia. Epicor merged with Scala in 2004 and has kept iScala as a separate line beside its flagship Kinetic ever since. Epicor is based in Austin, Texas, majority-owned since 2020 by the private equity firm Clayton, Dubilier and Rice, and the 3.x release line remains under active maintenance. Keep one distinction straight from the start: iScala is not Kinetic, and Kinetic is what Epicor leads with for domestic US manufacturing.

Modules and capabilities

Financials cover general ledger, payables, and receivables, joined by supply chain and procurement, warehouse and stock management, manufacturing, service and contract management, asset management, and mobile access. The real differentiator is the localization layer: local charts of accounts, country-specific tax and statutory reporting formats, and parallel reporting that satisfies group and local requirements simultaneously. That is what makes the system a standard building block in a two-tier ERP setup, with a corporate suite at headquarters, iScala in the subsidiaries, and intercompany transactions plus group reporting joining the tiers. A dedicated hospitality edition serves hotel and restaurant operations.

Best-fit companies

Subsidiary sites with roughly ten to a few hundred employees, in distribution, light manufacturing, sales and service organizations, and hospitality. The installed base concentrates in EMEA and Asia. The relevant US buyer is rarely a plant manager; it is the corporate center, CFOs and IT leaders responsible for foreign entities.

Licensing, hosting, cost

iScala runs on-premises or in a cloud-hosted environment operated by Epicor or a partner; it is not multi-tenant SaaS. Prices are unpublished, so budgets get assembled from quotes covering licenses or subscriptions, hosting, and implementation per country. Groups with many subsidiaries often centralize hosting in one region and connect local entities remotely. Our ERP cost guide breaks down the cost blocks of a multi-country rollout.

Editorial verdict

As a standard system for many small foreign entities, iScala is mature and credible, and few products match its localization catalog at this size. Purely domestic US operations should look at Kinetic or another home-market suite instead; that is not what this product is for. The open question is strategic, not functional: Epicor's visible investment flows to Kinetic. Have the vendor commit to the iScala roadmap, its cloud plans, and partner coverage in every country you actually need, in the contract.

What the Epicor iScala website looks like

Current view of the vendor homepage, captured by our editorial team.

Screenshot of the Epicor iScala vendor homepage

Comparable products

Related Topics

User reviews for Epicor iScala

No published reviews for Epicor iScala on usa.erp-software.org yet.

Write the first review →

Share your experience with Epicor iScala

Reviews are checked editorially for plausibility before publication (usually 1–3 business days). Your email address is never published and is stored only as a hash. Fields marked * are required.

Frequently asked questions

How is Epicor iScala different from Epicor Kinetic?

They answer different questions. Kinetic is what Epicor sells to North American mid-market manufacturers for their own plants. iScala exists for groups that need one system across foreign subsidiaries, so its strengths are localization, statutory reporting, and intercompany processing rather than deep manufacturing for a single US site.

Is Epicor iScala still actively developed and supported?

Yes. The 3.x line keeps receiving releases, support runs through Epicor and its partners, and no sunset has been announced. Because Kinetic clearly absorbs most of Epicor's visible investment, a prospective buyer should still ask for the iScala roadmap in writing during evaluation.

Who typically buys iScala in the United States?

Corporate centers, not plants. The classic buyer runs a tier-one ERP at headquarters and needs something lighter but locally compliant for smaller entities in Europe, the Middle East, Africa, or Asia. For purely domestic requirements Epicor steers prospects toward its other products.

What deployment options does iScala offer?

Two: on-premises in your own data center, or hosted by Epicor or a partner. Multi-tenant public SaaS is not on the menu. Groups with many entities commonly centralize hosting in one region and let subsidiaries connect remotely.

What makes iScala suitable for a two-tier ERP strategy?

The subsidiary can satisfy its own jurisdiction and its parent at the same time. Local charts of accounts and country-specific tax and statutory formats keep the entity compliant where it operates, parallel reporting feeds group requirements, and intercompany transactions plus group reporting connect the subsidiary tier to whatever suite runs headquarters. Most iScala installations sit exactly in that pattern.

What does Epicor iScala cost?

Only quotes exist; no list prices are published. The structural advice: model cost per entity, not as one group number, because localization, training, and implementation repeat in every country and often exceed the license share. Rollout number three is where underestimated budgets usually surface.