Unity for SaaS · Epicor · Epicor Kinetic

Epicor Kinetic integration for SaaS companies

Manufacturers run on Epicor Kinetic, Epicor 10 and Epicor 9. Unity connects your product to all three, syncing customers, parts, sales orders, invoices and payments through Epicor's own business logic, under your brand, managed by our team.

How do SaaS products integrate with Epicor Kinetic?

Epicor Kinetic is built on business objects that enforce its rules, so an integration should create records through them, never straight in the database. On Kinetic and recent Epicor 10 releases, Unity uses Epicor's REST API. On older releases, including Epicor 9, which predate that API, Unity calls the same business objects through a lightweight agent inside the customer's network. Either way, every order and payment follows the rules and BPMs your customer has set up. Our team builds the integration, delivers it under your brand and keeps it running through Epicor upgrades.

What syncs

Epicor records Unity maps for SaaS products

Each map uses Epicor's own business objects, so records land with the company, site, terms and pricing your customer's team expects.

Epicor recordTypical directionWhat it's used for
Customers, ship-tos and contactsBoth waysThe accounts your app serves, with their ship-to addresses and buyer contacts
Parts and inventory by warehouseFrom EpicorPart numbers, revisions, units of measure and on-hand quantities by site and warehouse
Price listsFrom EpicorCustomer and group price lists, so your app quotes what Epicor will invoice
Quotes and sales ordersBoth waysQuotes and orders captured in your app, created in Epicor with the right ship-to, site and terms
Shipments and trackingBoth waysPack slips, carriers and tracking numbers that keep customers and invoices current
AR invoices and open balancesFrom EpicorOpen invoices, credit memos and balances for payments, collections and customer portals
Cash receiptsTo EpicorPayments collected in your app, applied to the right invoices in a cash receipt group
Suppliers, purchase orders and AP invoicesBoth waysVendors, POs and bills for procurement, AP automation and supplier portals
Jobs and production statusFrom EpicorJob progress and due dates for scheduling, MES and customer order-status tools
How Unity connects

Epicor's business logic, on every version

Epicor customers run everything from Kinetic in Epicor's cloud to Epicor 9 on their own servers. Unity works with all of them.

REST API on Kinetic and Epicor 10

On releases with Epicor's REST API, Unity reads and writes through it, including BAQs your customer has already built to expose the data they care about.

Business objects on older releases

For Epicor 9.05.607A and other releases without the REST API, a lightweight Intelligrate agent inside the customer's network calls Epicor's business objects. It connects out, so no inbound firewall ports are opened.

Every company and site

Manufacturers often run several companies and sites in one Epicor system. Unity sets the right company and site on each call and keeps each company's data separate.

Custom BPMs respected

Because records are created through Epicor's business objects, the BPMs, user-defined fields and validations your customer relies on still fire, with nothing bypassed.

Field notes

Epicor problems we've already solved

These are the issues that stall do-it-yourself Epicor integrations, and how Unity handles each one.

Groups

Cash receipts and AP invoices stuck in unposted groups

Epicor batches cash receipts and AP invoices into groups that must be posted. Unity creates the group, adds each transaction and posts it automatically or leaves it for review, depending on each customer's preference.

BPM exceptions

A customer's BPM blocks the record

Custom BPMs can stop an update with their own message. Unity raises a case with that exact message, so the right person can fix the data or the rule.

Upgrades

An integration breaks after an Epicor upgrade

Moving from Epicor 9 to 10 or to Kinetic changes how integrations connect. Unity manages the move as part of the service, so your product keeps working.

Customer IDs

Orders fail on the wrong customer reference

Epicor uses both a customer ID and an internal customer number. Unity maps your app's accounts to both, so orders, invoices and payments always point at the right customer.

Use cases

Which SaaS products connect to Epicor Kinetic?

Payments and accounts receivable

Pull open AR invoices into your platform, collect payment, and create cash receipts in Epicor applied to the right invoices.

Transportation management (TMS)

Send orders from Epicor to your TMS for load planning, then return carriers, tracking numbers and actual freight costs.

CRM, CPQ and quoting

Give reps customer balances, prices and order status, and turn quotes into Epicor sales orders.

B2B ecommerce and customer portals

Show customers their own pricing, stock and order history, and create Epicor orders the moment they check out.

Procurement, AP automation and supplier portals

Sync suppliers and purchase orders, push approved AP invoices, and return payment status to your app.

Why Unity

Unity is a managed integration service for SaaS companies, built on the Intelligrate iPaaS. We build your Epicor integration, put your brand on it, monitor it, fix errors and handle upgrades. Integration updates can even flow into your own help desk. See how Unity works for SaaS.

200+Epicor companies connected
8–12 wkstypical time to go live
350M+records processed on the platform
75+other systems you can add next
FAQ

Epicor Kinetic integration questions

Which Epicor versions does Unity support?

Epicor Kinetic, Epicor 10 and Epicor 9 back to version 9.05.607A, whether Epicor runs in Epicor's cloud or on the customer's own servers.

Can Unity connect to Epicor 9, which has no REST API?

Yes. For Epicor 9 and other releases without the REST API, a lightweight Intelligrate agent inside the customer's network works through Epicor's business objects. It connects out, so no inbound firewall ports are opened.

Does Unity work with Epicor Kinetic in Epicor's cloud?

Yes. In Epicor's cloud, Unity connects through Epicor's REST API, so there's nothing to install on your customer's side.

Will our customer's custom BPMs and user-defined fields still work?

Yes. Unity creates records through Epicor's business objects, so BPMs and validations fire as usual, and user-defined fields can be mapped like any other field.

What happens when a customer upgrades from Epicor 9 or 10 to Kinetic?

Unity manages the upgrade as part of the service. We move the integration to the new connection method and keep your maps in place, so your product keeps working through the change.

How long does an Epicor integration take?

A first Epicor integration typically goes live in eight to twelve weeks. Each new customer after that is mostly configuration, since the maps are already built.

Connect, scale, sell more

Selling to Epicor manufacturers?

Tell us what your product needs from Epicor. We'll show you how Unity connects it, under your brand.