How to automate stock replenishment across ERP and spreadsheets
Compare stock and sales across spreadsheet and ERP, with the team reviewing before the order.
Siglata team
Sep 16, 2026 · 6 min read
To automate stock replenishment across ERP and spreadsheet, map where stock and sales come from, set the rules with the people who buy, calculate the purchase suggestion with those figures in view, and let the team review before ordering. Siglata does this work with engineers alongside the company's team, in a 30-day pilot quoted per process.
Many ERPs already offer a purchase suggestion. The problem shows up when part of the history lives in Excel, when there is more than one system, or when the real operating rule does not fit the ERP's default parameter.
What usually breaks
A weekly spreadsheet that compares stock and sales carries exceptions the ERP does not see: a promotion, supplier lead time, a recent stockout, a SKU with no movement. The buyer checks by hand because they do not trust a number that arrives alone.
How to build the routine
Map the sources
List the ERP, the spreadsheets, and the files that feed purchasing.
Compare stock and sales
Set the period and the level, SKU, store, or warehouse, with the team.
Write the rules
Minimum, maximum, days of cover, and exceptions stay explicit.
Produce the purchase suggestion
The result shows quantity and the data used in the calculation.
Review and order
The team authorizes. The order follows the flow the company already uses.
Illustrative stock and sales cross-check
Example SKUs, not a customer file. Coverage is the reason a suggestion appears.
| SKU | Stock | 30-day sales | Suggested qty |
|---|---|---|---|
| CAM-104 | 12 | 28 | 16 |
| CAM-210 | 4 | 19 | 15 |
| CAM-318 | 40 | 9 | 0 |
Example weekly buyer spreadsheet
Illustrative grid. Switch Before and After to see a note the buyer used to keep by hand.
| A | B | C | D | |
|---|---|---|---|---|
| SKU | Stock | 30-day sales | Note | |
| 1 |
| A | B | C | D | |
|---|---|---|---|---|
| SKU | Stock | 30-day sales | Note | |
| 1 |
Example purchase suggestion review
Illustrative chrome. It does not authenticate or open a live file.
Buyer spreadsheet
Example
Source
Weekly export
| SKU | Qty |
|---|---|
| CAM-104 | 8 |
Purchase suggestion
Example
Review
Pending
| SKU | Qty | Reason |
|---|---|---|
| CAM-104 | 16 | Low cover |
Why the native ERP suggestion often fails
The native suggestion works when the history and the rule live in one system. It fails when purchasing still exports to Excel, when two systems disagree, or when last month's promotion still sits in the average. Siglata connects those sources and keeps the ERP in place. The replenishment page at /reposicao describes the same comparison.
What the 30-day pilot covers
- One process with a closed scope.
- Engineers connect the systems and adapt the routine.
- The team uses the result, says what to change, and decides what to expand.
- No ERP replacement just to get a replenishment spreadsheet.
If replenishment in your company still depends on comparing a spreadsheet and the ERP every week, we want to understand how that routine works there. Write to angelica@siglata.com or WhatsApp from the replenishment page.
See how we work
