Lunica for Epicor Kinetic
Lunica runs beside Kinetic the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.
Epicor’s manufacturing ERP, for the manufacturers who sell into the building trade.
How Lunica connects to Kinetic.
Lunica reads Epicor Kinetic through Kinetic’s REST services or a read-only database login: the customer master and open items for aging and statements, open purchase orders and receipts for AP matching, the part master for counts and pricing, quotes and order history for the sales desk. Terms are read as Kinetic has them, so an account on Net 30 ages on that, not on a flat net-30.
Nothing is written to Kinetic by Lunica. Work that belongs in Kinetic goes back as a Kinetic REST call or DMT import where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from Epicor ECM, which keeps working exactly as before. Lunica runs on one server inside your network, whether Kinetic is in Epicor’s cloud or on your own server.
51 workflows for Epicor Kinetic.
Every workflow in the directory, written in Kinetic’s terms, with a demo in its formats.
Questions
Does it need a server?
Lunica runs on one server inside your network, whether Kinetic is in Epicor’s cloud or on your own server, set up and maintained by Lunica. It reads Epicor Kinetic through Kinetic’s REST services or a read-only database login. There is no inbound connection from outside your network.
What does Lunica read in Kinetic?
The customer master, open items and terms, purchase orders and receipts, the part master, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Kinetic?
Nothing lands in Kinetic without a person. What belongs in Kinetic goes back as a Kinetic REST call or DMT import where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Epicor ECM. Lunica reads them when a workflow needs one and never writes to them.
See it on your Kinetic data.
Thirty minutes. We walk a workflow on Kinetic data, then map it to yours.