Skip to content

Slow-Moving Inventory for Epicor LumberTrack

Every item in LumberTrack with no sales in months, its last receipt, cost and value by branch and vendor, sorted into what goes back, what gets marked down and what moves to the other branch. The return request is drafted, and a person decides.

Purchasing & inventoryUpdated Oct 202620 ERPs

See it work on LumberTrack.

Click through the steps. Fictional data, in LumberTrack’s terms; the real thing runs on LumberTrack.

Slow movers · Oct 20 · both branches
Illustrative
No sales in 6+ months412 itemsSeasonal items judged on last year
Value at cost$148,620On the books
Returnable$41,300Inside a vendor’s window today
Transfer$9,84038 items the other branch sells
VendorItemsValue at costReturnableWindow closes
Cascade Millwork26$22,410$12,410Dec 15
Lakeside Roofing Supply41$12,960$8,200Nov 30
Summit Fasteners63$5,930$5,930Rolling, 12 months
Blue Ridge Truss4$3,180$0No returns
Built from LumberTrack’s sales, receipts and on-hand. Return rules are yours, per vendor.

Every item with no sales in six months, by branch and vendor, with the value at cost and the vendor’s return window.

1 / 4

The problem, as it happens in LumberTrack.

Dead stock at a dealer is a report in LumberTrack nobody runs, because it comes back with four thousand lines and no way to act on them. The product master says ninety-six of something are on hand at Route 9; it does not say the last one sold in February, that Main St sells a dozen a month, or that the vendor takes returns within a year of receipt.

So it sits. The door that could have gone back to the vendor in March is past its return window in September, the pallet of ice melt gets counted again in January, and the carrying cost never shows up anywhere because the inventory is still on the books at cost. The write-down lands at year end, all at once, when the accountant asks.

How it works.

  1. 1

    What stopped selling is found

    Every stock item with no sales in the months you set, by branch: on hand, cost, extended value, last receipt, last sale, and the vendor it came from. Seasonal items are judged against the same months last year, so snow shovels in July are not dead stock.

  2. 2

    Sorted into return, markdown or transfer

    Returnable if the vendor takes it and the receipt is inside their window. Transfer if the other branch sells it. Markdown if neither. Each item carries the reason and the value at stake.

  3. 3

    A person decides

    The buyer opens on the vendor with the most returnable value first. Return, mark down, transfer, keep, or leave it for next quarter. Every decision is kept with the item, so the list gets shorter.

  4. 4

    The return request is drafted

    One request per vendor, with the items, quantities, receipt dates and PO numbers from LumberTrack. The buyer sends it. The markdown and transfer lists are laid out for LumberTrack and keyed or imported by a person.

How it connects to LumberTrack.

Lunica reads the product master, on-hand by branch, cost, sales history, receipts with their PO and date, and the vendor on each item through a read-only login to the LumberTrack SQL Server database. Vendor return windows and restocking fees are a rule you set per vendor, not something read from LumberTrack.

Nothing is sent to a vendor and nothing is changed in LumberTrack on its own. The return request is a draft the buyer sends; the markdown and transfer lists go back as an import where LumberTrack takes one, or keyed by your team from what Lunica prepared. A return the vendor accepts becomes a credit only when a person posts it.

What a week looks like.

  • Every item with no sales in months, with its value, by branch and vendor.
  • Returns requested inside the vendor’s window, not after it.
  • Transfers between branches before a markdown, and markdowns before a write-off.
  • The write-down known quarter by quarter, not discovered at year end.

Questions

Does it change costs, prices or quantities in LumberTrack?

No. The markdown and transfer lists go into LumberTrack as an import where LumberTrack takes one, or keyed by your team from what Lunica prepared, and the return is posted by a person when the vendor’s credit arrives.

How does it know what the vendor will take back?

From a rule you set per vendor: the return window, the restocking fee, whether special orders count. Lunica reads the receipt date and PO from LumberTrack and checks each item against the rule.

What about seasonal items?

An item is judged against the same months last year. Something that sells every winter and not in July is not on the list in July.

Can it tell a special order from stock?

Yes, where LumberTrack marks it. A special order that was never picked up is its own list, with the customer and the order on it, because the call to make is different.

Does it send the return request?

No. It drafts one per vendor with the items, quantities, receipt dates and PO numbers. The buyer reads it and sends it.

What does the controller see?

The value by branch, by vendor and by age, and what was decided. The write-down that is coming is visible each quarter instead of at year end.

How much data does the model see?

The rows behind a decision: the items for one vendor, their receipts and sales. The list itself is built from LumberTrack’s numbers, not by a model.

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.

The same workflow, on another ERP.

Slow-Moving Inventory is written for every system on the list. You’re reading the LumberTrack version.

See it on your LumberTrack data.

Thirty minutes. We walk the workflow on LumberTrack data, then map it to yours.