A stack of cost files and one buyer
It is the start of the quarter. Your buyer has cost updates from a dozen manufacturers. One sends a clean Excel file with your product codes. Another sends a PDF price list with their own codes and descriptions. A third expects you to log in to a portal and download a CSV with fifty columns. Some change a handful of lines; one changes everything.
Your buyer works through them, matching supplier codes to yours and typing new costs in. It takes days. A typing slip turns a case cost into a single unit cost. Nobody notices until margin reports look strange a month later.
Why this stays manual
Each supplier's file is different, and none of them use your codes reliably. The mapping between their codes and yours lives in the buyer's head or in an old spreadsheet. Pack sizes differ between how the supplier sells and how you stock. So the easiest thing is to read and type, even though it is slow and error-prone.
- Supplier codes are not stored against your products.
- Pack size conversions are done in the buyer's head.
- PDF price lists cannot be imported directly.
- Nothing checks for suspicious changes before costs are loaded.
- Effective dates are handled by loading early or late.
What the retyping costs
Errors in cost prices flow into margin reports, pricing decisions and sometimes sell prices. Costs loaded late mean selling at the old margin after the buy price rose. The buyer spends days on keying rather than negotiating or planning. And when the buyer is away, cost updates wait.
The buyer's time is the bigger loss. Quarterly cost changes are exactly when a buyer should be looking at which suppliers are pushing hardest, which lines are losing margin and where an alternative might be worth sourcing. Instead, those weeks go on typing, and the analysis that would pay for itself never gets done.
The cost file importer we build
- Each supplier's format is set up once: which columns hold the code, description, pack size and cost, or for PDFs, an AI extraction step that reads the table and proposes values.
- Supplier codes are mapped to your product codes and stored, so the mapping is reused every time.
- Pack size conversions are held per product, so a supplier's case cost becomes your stocking unit cost automatically.
- Every change is compared with the current cost. Unusual changes, new codes and missing lines are flagged for the buyer.
- The buyer approves the batch, and costs are loaded into your stock system on the effective date through its API or import.
- Alongside each update, the tool shows the effect on margin at current sell prices, so the buyer can see which lines need a price review.
| Retyping | Importer | |
|---|---|---|
| Supplier layout | Read by eye | Mapped once per supplier |
| Code matching | From memory | Stored mapping |
| Pack sizes | Converted by hand | Converted automatically |
| Errors | Found in margin reports later | Flagged before loading |
| Effective dates | Loaded when there is time | Loaded on the date |
The buyer's quarter afterwards
Cost files are dropped into the importer as they arrive. The buyer reviews a list of changes that look unusual, confirms new codes, and approves. The margin effect of each supplier's increase is visible straight away, which feeds the conversation about your own sell prices. Holidays no longer stall updates.
Does this sound like your buying desk?
- Manufacturers' cost files are keyed by hand.
- Supplier codes are matched to yours from memory.
- Case and unit costs get mixed up.
- Cost updates are loaded late.
- You find cost errors through odd margin reports.