Skip to main content
Back to work

BOM & Recipes

When one raw material goes up in price, how many hours does repricing the whole catalogue take?

3

automatic pricing tiers

Private project - the system sits behind a login

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

  1. Import from the existing Excel filesA condition, not a feature - the system starts from what exists
  2. A raw material price changes
  3. Automatic cascade through the BOMIncluding products built from other products
  4. Three price tiers derived at onceCost, retail and wholesale - from margins the client sets

Technologies

FieldAutomation
TechnologiesReact · Vercel · Neon · Supabase · openpyxl