Skip to content

Lunica for ECI Spruce

Lunica runs beside Spruce the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.

ECI’s ERP for lumber and building-material dealers: point of sale, inventory, deliveries, manufacturing and accounting.

How Lunica connects to Spruce.

Lunica reads ECI Spruce through a read-only login to the Spruce SQL Server database: the customer account and open items for aging and statements, open purchase orders and receipts for AP matching, the item record for counts and pricing, quotes and order history for the sales desk. Terms are read as Spruce has them, so an account on Net 30 EOM ages on that, not on a flat net-30.

Nothing is written to Spruce by Lunica. Work that belongs in Spruce goes back as a Spruce import where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from Spruce document imaging, which keeps working exactly as before. Lunica runs on one Windows server inside your network, or beside ECI’s hosted Spruce.

51 workflows for ECI Spruce.

Every workflow in the directory, written in Spruce’s terms, with a demo in its formats.

Questions

Does it need a server?

Lunica runs on one Windows server inside your network, or beside ECI’s hosted Spruce, set up and maintained by Lunica. It reads ECI Spruce through a read-only login to the Spruce SQL Server database. There is no inbound connection from outside your network.

What does Lunica read in Spruce?

The customer account, open items and terms, purchase orders and receipts, the item record, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.

Can it post to Spruce?

Nothing lands in Spruce without a person. What belongs in Spruce goes back as a Spruce import where one exists, or keyed by your team from what Lunica prepared.

What about our documents?

Invoice copies and scans keep living in Spruce document imaging. Lunica reads them when a workflow needs one and never writes to them.

See it on your Spruce data.

Thirty minutes. We walk a workflow on Spruce data, then map it to yours.