How Alba builds a proposal
The reorder engine in plain language — when and why it fires.
Every evaluation cycle (you can run on-demand or schedule daily), the engine does this:
1. Read your catalog — only active beverages with par > 0. 2. Project forward — how many bottles will be left when the next delivery actually arrives, given your recent sales velocity? 3. Find criticals — anything where projected stock ≤ reorder point. These are the wines that must be in the proposal. 4. Group by distributor — one proposal per supplier with critical wines. 5. Build three options: - A = critical only - B = critical + priority-1 top-ups (other wines below par) - C = critical + priority-1 + priority-2 top-ups (the wider net) 6. Check minimum — for each option, does it reach the distributor's minimum order? If not, auto-pad with extra bottles from the same distributor's catalog so the proposal is always actionable. 7. Send it — via your preferred channel.
The engine does not duplicate within the same delivery cycle. If you skip or postpone a proposal, you won't get a fresh one for the same supplier until the cutoff has passed.