Coil-to-dispatch control for a roofing sheet manufacturer
How a roofing ERP is typically structured when coil balances, dealer rates and same-day dispatch all have to hold together.
Business challenge
A roofing manufacturer running several profiling lines cannot confirm coil balances without physical counting, quotes rates from a list circulated on WhatsApp, and discovers credit overruns only during monthly recovery.
Existing process
- Enquiries noted by salespeople in personal diaries
- Rate list shared as an image in a WhatsApp group
- Coil consumption written on the shop-floor register and entered weekly
- Cutting instructions passed on handwritten slips
- Dispatch sequence decided each morning by the supervisor
- Outstanding tracked in a separate spreadsheet by accounts
Solution implemented
A single system where the approved rate list drives quotations, every profiling order consumes against a specific coil, and dispatch is planned against confirmed production and validated credit.
Implementation approach
- 1Discovery across sales, stores, production, dispatch and accounts
- 2First phase covering enquiry, rates, orders and coil inventory
- 3Second phase adding production, dispatch and credit control
- 4Salesperson mobile application released with the second phase
- 5Tally synchronisation and dashboards in the final phase
Modules developed
- Lead and enquiry management
- Dealer master with category-wise rates
- Coil inventory with balance tracking
- Cutting and profiling orders
- Quotation and sales order management
- Dispatch planning with vehicle allocation
- Outstanding and credit control
- Management dashboard
Integrations
- Tally
- WhatsApp notifications
- Meta and Google lead capture
Business outcomes
- Coil balance verifiable at any point without a physical count
- One approved rate applied consistently across the sales team
- Credit position checked before dispatch rather than after
- Scrap and wastage measured against each production run
- Dispatch planned against vehicle capacity and delivery sequence
Expected outcomes for a build of this shape. Not a record of results at a named client.