BOM & Recipes
When one raw material goes up in price, how many hours does repricing the whole catalogue take?
3
automatic pricing tiers
What was stuck
Bills of materials and recipes managed in Excel. Every change to a single raw material’s price forces a manual recalculation of every product containing it - and when a product is made of other products, the calculation branches in all directions. In practice that means pricing is updated rarely, margins erode unnoticed, and every update is an opportunity for an error that reaches the customer’s price.
What we built
A bill-of-materials system with nested recipes, where a price change to one raw material cascades automatically to every product containing it - including products built from other products. Three pricing tiers are derived at once: cost, retail and wholesale, from margins the client sets. And instead of retyping everything, direct import from the existing Excel files. That was a condition, not a feature: a system demanding data entry from scratch starts against resistance, while one that reads what already exists starts on day one.
The process, end to end
- Import from the existing Excel files
- A raw material price changes
- Automatic cascade through the BOM
- Three price tiers derived at once
Technologies
| Field | Automation |
|---|---|
| Technologies | React · Vercel · Neon · Supabase · openpyxl |
Facing something similar?
Tell us what's stuck and we'll tell you honestly whether - and how - we can help.
Let's talk