01 / Context
Compare like with like.
Products, locations, units of measure and time periods need to match before the files are combined.
Replenishment · Stock × sales
Restock based on what sells.
Compare inventory with sales and prepare a purchase proposal your team can check.
Built around the systems you already use. Implemented with your team.
Illustrative example
The next purchase starts with a clear list.
Product, stock coverage and the reason to restock.
Stock × sales
What needs attention before the next purchase.
The same stock can last three days or three weeks. The sales rate changes the decision.
Replenishment review
Illustrative example · Last 7 days
| Product | Stock | Sales / 7 days | Coverage | Next step |
|---|---|---|---|---|
| Coffee 500 g | 18 units | 42 units | 3 days | Review replenishment |
| Olive oil 500 ml | 36 units | 28 units | 9 days | Review replenishment |
| Rice 5 kg | 70 units | 35 units | 14 days | Monitor |
| Sugar 1 kg | 40 units | 14 units | 20 days | Monitor |
Coffee 500 g
Coverage: 3 daysStock: 18 units · Sales / 7 days: 42 units
Review replenishment
Olive oil 500 ml
Coverage: 9 daysStock: 36 units · Sales / 7 days: 28 units
Review replenishment
Rice 5 kg
Coverage: 14 daysStock: 70 units · Sales / 7 days: 35 units
Monitor
Sugar 1 kg
Coverage: 20 daysStock: 40 units · Sales / 7 days: 14 units
Monitor
Coverage = available stock ÷ average daily sales.
In this example, items with fewer than 10 days of coverage go to review. Your team defines the actual rule.
The list explains the signal. Your team decides what to buy.
Coverage is an estimate based on the observed period. Supplier lead times, open orders and seasonality are reviewed before quantities are set.
Your operation defines the rules
The calculation is only part of replenishment.
We define the criteria with the people who buy, sell and track inventory every day.
02 / Purchasing
Account for what is already on its way.
Supplier lead times, minimum order sizes and open orders help determine when and how much to buy.
03 / Exceptions
Flag what needs checking.
Mismatched records, outdated stock balances and unusual sales remain visible for review.
04 / Decision
Keep purchasing decisions with your team.
The proposal brings together the data and the reason for each item. The people who know the operation approve the next step.
The technology at work
From files to the next step.
An inventory workflow: compare what is in stock with what is selling, then prepare the next purchase.
Keep the systems you already use.
Siglata brings together ERP inventory, sales and product records to help you follow the operation.
Source files3 files collected
| File | Source | Records |
|---|---|---|
| Estoque.xlsx | ERP | 4 |
| Vendas.csv | Sales | 4 |
| Produtos.xlsx | Product records | 4 |
Your systems remain the source of your data.
Technology that works with the AI agents you already use.
Codex
Hermes Agent'%20fill='%23000000'%20/%3e%3c/svg%3e)
Grok Bot
Before you begin.
Do I need to replace my ERP?
We start with the systems and files you already use. In the first conversation, we assess how to obtain the data and keep the routine up to date.
Does Siglata place purchase orders automatically?
This workflow produces a proposal for review. Any additional automated step must be agreed with your team as part of the scope.
What if my product records do not match?
Implementation includes checking identifiers, units and time periods. Differences must be resolved or flagged before they inform a purchase.
How does the pilot work?
We choose one process and a defined part of the operation for a 30-day pilot. Scope, evaluation criteria and pricing are agreed before work begins.
Let's start with one process.
A 30-day pilot in your operation.
We implement a workflow and evaluate the results with your team. Each project is quoted according to the workflow and the scope of the pilot.
Message on WhatsApp