Skip to main content

ERP Software in the US — Independent Directory, Guides & Glossary

erp-software.org is an editorial resource on ERP, CRM and inventory-management software. This US edition covers selection, implementation and cost questions for American companies of every size — from a first system at twenty employees to a multi-entity rollout — written plainly, with no sales pitch and no paid placement.

Start here

What the US market actually looks like

Buyers arriving from a search engine tend to meet the same six or seven vendor names. The market is considerably wider than that, and more fragmented. Building this directory produced a few numbers worth knowing before you start shortlisting.

Almost nobody publishes a price. Of the 302 products profiled here, ten publish enough pricing detail to budget from. The rest quote through partners. Any five-year figure you find in a blog post is an estimate — which is why our TCO calculator asks for your own inputs instead of handing you a number.

Industry specialists outnumber the generalists. Six products sit in the enterprise category, eighteen in mid-market, eleven in small business. The other 267 are segment or industry systems: 35 for discrete manufacturing and job shops, 29 for distribution, 23 for construction, 15 for the public sector, 11 for apparel, on down a long tail that reaches seed-to-sale cannabis tracking and grain accounting. If your operation has an unusual process, somebody has probably built a system for exactly it.

On-premises is not dead. Only 131 of the 302 are cloud-only. Another 163 sell cloud and on-premises both, and eight are Windows or IBM i products with no true SaaS option — several of them with large, actively supported installed bases. Anyone telling you the deployment decision has already been made for you is selling something.

Most vendors are American, not all. 256 of the 302 are headquartered in the United States; 46 are foreign vendors selling into the US, mostly European enterprise suites plus a handful of open-source projects. Support hours, partner availability and localization depth follow from that.

Where to go next

Buying a first real system. Read what an ERP system is, then ERP for small business, and work through the requirements document guide before talking to a single vendor. A written requirements list is what stops a demo from selling you a system you did not need.

Replacing something that has aged out. Start with ERP migration and the legacy systems category, which covers the products most US replacement projects are moving off: Dynamics GP, NAV and SL, Infor XA and LX, Oracle E-Business Suite, Sage 100 and 500. Data migration is where these projects run over budget.

Already implementing. The implementation guide, the first-90-days checklist and change management cover the phase where technical readiness and organizational readiness stop being the same thing.

Answering to a board. Role-specific views for CEOs, CFOs and IT leaders.

Also here: industry pages covering how requirements shift by sector, and use cases organized by business model rather than industry — project business, subscription, seasonal, branch networks.

How this site is written

Every product profile was researched individually against the vendor's own documentation and public records, then checked for current naming — the US ERP market consolidates constantly, and yesterday's brand is often today's module inside somebody else's suite. Products we could not verify as actively sold were left out rather than padded in. Figures we could not confirm are absent rather than estimated. Listings are descriptive, not endorsements, and the directory publishes no rankings: entries run alphabetically inside each category, which is the one ordering nobody can buy.

Other editions

For the German market visit erp-software.org (Deutsch) or the French edition (Français).