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