Vendor Price Increases for ECI Spruce
The increase letter or spreadsheet read once, each line matched to the item record in Spruce by vendor part number, and the new cost laid beside your sell price and margin with the effective date. The buyer decides, and the cost and price changes go into Spruce by a person.
Purchasing & inventoryUpdated Oct 202620 ERPs
See it work on Spruce.
Click through the steps. Fictional data, in Spruce’s terms; the real thing runs on Spruce.
From the Summit rep, Oct 14 · Effective Nov 1, 2026 · 38 lines, 2 pages · Read twice
Effective November 1, 2026, the items below move to the new cost shown. All other items increase 4.5%.
SF-16D50 · 16d sinkers, 50 lb · 38.40 to 40.70
SF-DS158 · 1-5/8 drywall screws, 5 lb · 21.90 to 23.15
SF-JH210 · joist hanger, 2x10 · 1.84 to 1.96
SF-LS70 · 7/16 lag screw, 100 ct · 0.92 to 0.96
A PDF from the rep, forwarded to one address. A model reads it twice: vendor, effective date, every line.
The problem, as it happens in Spruce.
A price increase arrives as a PDF letter from the rep, a spreadsheet from the mill, or a line in an email: four and a half percent on fasteners, effective the first. Somebody prints it, finds each item in the item record by a part number that doesn’t quite match, and keys the new cost in Spruce one screen at a time. The sell price gets looked at later, if at all.
The lines that got missed are the ones nobody tracks. Spruce carries the old cost until the next receipt, the sell price stays where it was, and the margin on that item quietly drops for a quarter until someone reads the gross margin report. Or the sell goes up first, and the counter finds out from the customer.
How it works.
- 1
The increase is read
A letter, a spreadsheet or the rep’s email, forwarded to one address or dropped in a folder. A model reads it twice: the vendor, the effective date, and every line with its part number, old cost, and new cost or percent.
- 2
Each line is matched to the item record
By vendor part number first, then by description and pack where the number has drifted. A line that matches nothing, or matches two things, is shown as a question, not a guess.
- 3
Cost, sell and margin side by side
For every matched item: the cost Spruce has now, the new cost, the effective date, the current sell at each price level, and the margin before and after. A sell price that holds your margin is proposed, rounded to your price points.
- 4
The buyer decides, a person updates Spruce
Accept the cost, take the proposed sell or set your own, or leave the sell alone and give up the margin on purpose. The approved changes go into Spruce as a Spruce import where one exists, or keyed by your team from what Lunica prepared, dated to take effect on the first.
How it connects to Spruce.
Lunica reads the item record, vendor part numbers and cross-references, current cost, the price levels and their sell prices, and recent receipts and sales by item through a read-only login to the Spruce SQL Server database. The letter or file is read by a model only for the lines in it; the item file is looked up for those lines and nothing else.
Nothing is changed in Spruce on its own. Every cost and sell change is a line the buyer accepted, edited or declined, and the accepted ones go back as a Spruce import where one exists, or keyed by your team from what Lunica prepared, with the effective date. The letter is kept with the decision beside it, so the next time the rep asks, the answer is on record.
What a week looks like.
- Every line of the letter matched, or shown as a question.
- The margin impact known before the cost changes, not after.
- A sell price proposed per line, rounded to your price points.
- The letter, the decision and the effective date on record, by vendor.
Questions
Does it change costs or prices in Spruce?
No. The buyer accepts or declines each line, and the accepted changes go into Spruce as a Spruce import where one exists, or keyed by your team from what Lunica prepared. Nothing is updated on its own.
What if the letter is just a percentage?
Then every item for that vendor, or for the category the letter names, is listed with the percent applied to the cost Spruce has. The buyer sees the whole list before anything is accepted.
What if the part numbers don’t match?
The line is matched by description and pack where the number has drifted, and shown as a question if it is still not sure. A matched line always shows what it matched, so the buyer can catch a wrong one.
Can it propose the new sell price?
Yes. Per price level, holding the margin you had or the floor you set, rounded to your price points. The buyer can take it, change it, or leave the sell where it is.
Does it handle the effective date?
Yes. The change is prepared with the date from the letter, so the cost moves on the first and not the day the letter arrived. Receipts after that date are checked against the new cost.
What about open quotes and contract prices?
Open quotes and contract prices on the affected items are listed with the change, so the buyer knows which customers are quoted at the old cost before the sell moves.
How does the letter get to Lunica?
Forward it to an address you set up, or drop it in a folder on the share. Nothing is installed on the Spruce server; Lunica runs on one Windows server inside your network, or beside ECI’s hosted Spruce.
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.
The same workflow, on another ERP.
Vendor Price Increases is written for every system on the list. You’re reading the Spruce version.
See it on your Spruce data.
Thirty minutes. We walk the workflow on Spruce data, then map it to yours.