Lunica for DMSi Agility
Lunica runs beside Agility the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.
DMSi’s ERP for lumber, millwork and building-products distributors and pro dealers, with tally and special-order depth.
How Lunica connects to Agility.
Lunica reads DMSi Agility through a read-only login to the Agility database: the customer master and open items for aging and statements, open purchase orders and receipts for AP matching, the item master for counts and pricing, quotes and order history for the sales desk. Terms are read as Agility has them, so an account on Net 30 EOM ages on that, not on a flat net-30.
Nothing is written to Agility by Lunica. Work that belongs in Agility goes back as an Agility import or API call where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from Agility’s document attachments, which keeps working exactly as before. Lunica runs on one Windows server inside your network, or beside DMSi’s hosted Agility.
51 workflows for DMSi Agility.
Every workflow in the directory, written in Agility’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 DMSi’s hosted Agility, set up and maintained by Lunica. It reads DMSi Agility through a read-only login to the Agility database. There is no inbound connection from outside your network.
What does Lunica read in Agility?
The customer master, open items and terms, purchase orders and receipts, the item master, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Agility?
Nothing lands in Agility without a person. What belongs in Agility goes back as an Agility import or API call where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Agility’s document attachments. Lunica reads them when a workflow needs one and never writes to them.
See it on your Agility data.
Thirty minutes. We walk a workflow on Agility data, then map it to yours.