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