The Epicor Master Customer Agreement (MCA) is Epicor’s standard contract for its software, SaaS and data services, hardware, Support and Consulting Services. The version dated 2026-07-30 provides that the MCA, the Orders that incorporate it, and any Product Supplement named in an Order make up “the Agreement”.[1] Its licence and compliance terms sit mainly in section 2, with related provisions on assignment (section 17), termination (section 14) and notices (section 18). This article covers those terms. Support and cloud services are in Epicor Support, SaaS and hosting terms.
The MCA governs which version applies over time. Orders renew automatically, and “The MCA in effect at the time of renewal will govern the Deliverables for the duration of the Renewal Term”.[1] A customer who signed under an older version may therefore be bound by the current text after its next renewal. Catalog proof: Orders renew automatically under the then-current MCA.
Editions
The MCA does not distinguish editions. It distinguishes Perpetual Products, Subscription Products and SaaS Services, and separates Epicor’s own Products from Third-Party Applications, which are marked with ”*” on an Order.[1] “Deliverables” covers Products, Documentation, Customizations, services and other work under an Order or Statement of Work. It excludes hardware and Third-Party Applications.[1]
Metrics
Grant. “Epicor grants Customer a non-exclusive, non-sublicensable, non-transferable right to use the Deliverables for Customer’s internal business purposes during the License Term.”[1] The grant is subject to compliance with the Agreement. Catalog proof: Licence is for internal business purposes during the License Term.
Who counts. A User is one of the “Employees or contractors authorized by Customer and licensed to use Deliverables subject to the terms of the Agreement and any identification or authentication requirements”. Customers may not “make the Deliverables available to anyone other than its Users”.[1] The definition does not mention Affiliates. Group companies, outsourcers and customers’ own clients should be checked against it. Catalog proof: Users are employees or contractors of the customer.
Two bases. The Order states whether a Product is licensed on a named user basis or a concurrent User basis.[1]
| Basis | Rule in MCA s.2.1 | Catalog row |
|---|---|---|
| Named user | Logins “are for designated individual Users only”; no sharing; “an individual User login may be redeployed to another individual upon notice” | Named User |
| Concurrent user | “Customer will not allow more Users to access the Products than allowed under the Order” | Concurrent User |
Counting / floors
Named users. One login per individual. Generic, shared or department logins are excluded by the words “may not allow a User login to be shared or used by more than one individual User”. Redeployment, for example when an employee leaves, is allowed “upon notice”.[1] Under section 18.5, notices about Users, User counts and adjustments go to Epicor’s sales address.[1] Catalog proof: Named user logins cannot be shared but can be redeployed on notice; User count changes are notified to Epicor sales.
Concurrent users. The cap is the number of Users accessing at the same time. The MCA does not define how a session is measured. Any technical counting rule would come from the product documentation or a Product Supplement.[1] Catalog proof: Concurrent access may not exceed the Order quantity.
Self-monitoring. “Customer must monitor Products usage, including accurate assignment to named users, and must notify Epicor of any unauthorized use or usage exceeding the granted license.”[1] The duty to report sits with the customer, not with an audit. Catalog proof: Customer must monitor usage and report excess use.
Excess use. “If Customer’s usage exceeds the number of Users (Named or Concurrent) stated in the Order, Customer must pay Epicor the additional Fees applicable to excess use within 10 days of the invoice date.”[1] The MCA does not say which price applies to excess use or from what date it is charged, so the Order matters here. Additional Perpetual Products bought during a Support term are added to Support with prorated fees.[1] Catalog proof: Excess Named or Concurrent Users are paid within 10 days of invoice; Additional perpetual products join the existing Support subscription.
Verification and audit
Section 2.5, “Verification and Audit”, gives Epicor two tools instead of an on-site audit clause.[1]
- Remote monitoring. “Epicor may remotely monitor Customer’s compliance with usage and the terms of this Agreement.” Section 7.9 also lets Epicor compile non-personal statistical information on how the Products are used.
- Certification. “On Epicor’s written request, no more frequently than annually, Customer will provide Epicor, within 10 business days, a signed certification along with supporting documentation, verifying that the Products have been used in complete compliance with the terms of this Agreement.”
Section 2.5 survives termination of the Agreement.[1] Ten business days is a short time to produce supporting documentation. A customer would need a current list of named users and their assignments, and peak concurrent counts, already to hand. Catalog proof: Epicor may monitor usage remotely; Annual compliance certification within 10 business days.
Usage restrictions and suspension
Under section 2.3, the customer and its Users may not, or let any third party, copy, modify or create derivative works of the Deliverables. They may not rent, lease, lend, sell, sublicense, assign or distribute them, or reverse engineer them. Nor may they “use or access the Deliverables to build, support, market, provide, or use any products or services without Epicor’s written consent”.[1] That last restriction is broad. Read literally, it covers third-party consultants and service providers who use the software to support the customer. If the restrictions are breached, Epicor “may take remedial action … including suspending Customer’s right to use the Deliverables”. It must give prompt notice and limit the suspension in time and scope.[1] Under section 11.2, the customer indemnifies Epicor against claims arising from unauthorized Product use or breach of section 2.3. Catalog proof: No copying, modifying or using Deliverables to build products or services; Epicor may suspend use for breach of the usage restrictions.
Virtualization & partitioning
There is no hardware metric. Perpetual Software is defined as installed “on hardware owned or leased and controlled by Customer at Customer’s premises, or … within a third-party server co-location facility”.[1] The test is control of the hardware. Virtual machines on customer-controlled hosts fit the definition, while third-party managed infrastructure needs checking. In Epicor’s own single-tenant hosting, the 2019 BisTrack specification says Epicor creates user IDs in “the Epicor Active Directory” and that customers have no administrative access to Active Directory, the Windows servers or SQL Server.[2] Catalog proof: On-premises Software runs on customer-controlled hardware or co-location.
Cloud / BYOL
The MCA does not provide for moving perpetual licences to a customer-chosen public cloud. Hosting by Epicor is covered in Epicor Support, SaaS and hosting terms.
Programs
Termination. “All license rights granted to Customer under this Agreement or an Order immediately terminate upon termination of the Agreement or such Order.”[1] Either party may terminate for a material breach not cured within 30 days. A customer that terminates for Epicor’s breach must do so within 60 days of the failure to cure. Breach of confidentiality or of the assignment clause allows immediate termination. If an Order covers several Product types, termination can be limited to the affected Product.[1] Catalog proof: Licence rights end when the Agreement or Order terminates.
Assignment and corporate change. “Customer may not assign or transfer any rights or obligations under this Agreement without Epicor’s prior written consent, and Epicor may charge a reasonable license transfer fee.” The next sentence treats “Any sale or transfer of Customer’s assets, stock, or interests in, or any merger, consolidation, restructuring, or other business reorganization (including bankruptcy assignments or assumptions)” as a transfer. Epicor may assign on written notice.[1] Divestments and acquisitions therefore need Epicor’s consent before licences move. Catalog proof: Assignment and corporate transactions need Epicor consent and may incur a transfer fee.
Purchase orders and roadmaps. A customer purchase order has “no force or effect on the Agreement”. Purchases are not contingent on future functionality or roadmap statements.[1] Catalog proof: Purchase orders and roadmap statements do not change the Agreement.
Disputes. Under section 16, disputes go first to negotiation and then to arbitration before a single arbitrator. Actions to collect amounts due, or to enforce confidentiality or intellectual property rights, are excluded and may go to court. Customers domiciled in North, Central or South America arbitrate in New York under the American Arbitration Association’s commercial rules. Other customers arbitrate under the LCIA Rules, seated in London, under the law of England and Wales.[1]
Out of scope
This page does not cover data protection, confidentiality, liability caps and indemnities, except where they bear on licence use. It also does not cover the Australian, New Zealand and Canadian provisions in section 19, or the Product Supplements, which could not be retrieved.