Roofing Sheet ERP Software in Surat & Gujarat: ERP, CRM, Accounting and AI Automation
Yukti AI, a software company in Varachha, Surat, builds roofing sheet ERP software for manufacturers and traders in Surat and across Gujarat: ERP, CRM and accounting in one system, with WhatsApp and AI automation that can be built on the same data. A multi-module ERP starts from ₹30,000, with the final quote after a free 30-minute workflow audit. This page also shows the working version we built for a roofing sheet manufacturer and trader in Ankleshwar, Gujarat — one system for inquiry and CRM, quotation with rate approval, sales order with a credit check, stock reservation, purchase, roll-forming production with wastage and scrap, quality, dispatch challan, GST invoice, payment, accounting and profit by order.
The client makes and sells roofing sheets from Ankleshwar in Bharuch district, South Gujarat. It roll-forms trapezoidal, corrugated, decking and ridge-flashing sheets to order from colour-coated, galvalume and GP coil, and it also trades polycarbonate sheets, UPVC sheets, base plates, accessories and bolts. Its stock sits in several godowns, quotes depend on rate and margin, customers buy on credit, and every order is either made, bought or served from stock. Yukti AI built one connected ERP, CRM and accounting system that follows an order from the first inquiry to the profit it earned, using the client’s own godown stock list as the product master. It is a working version shown to the client as a demo: it runs on sample customers and rates, and its WhatsApp, GST filing and bank links are not connected yet.
Roofing sheet ERP software in Surat and Gujarat — enquire
- ERP, CRM and accounting in one system for roofing sheet manufacturers and traders: quotations with rate approval, coil and sheet stock, production, challan-controlled dispatch, GST invoices and profit by order.
- Built around your products and rules, not an average company: your coil items, units, dealer rates, credit limits and godowns.
- WhatsApp and AI automation that can be built on the same data: quotation sharing, dispatch updates, payment reminders and an owner briefing (AI features can be built; see the labels below).
- Tally can stay for your accountant while operations run in the ERP.
- Hindi, Gujarati and English conversations with a Surat team you can meet.
A full multi-module ERP starts from ₹30,000; the final quote is given after a free 30-minute workflow audit. It is a one-time build including data setup, training and 12 months of support, then a small annual maintenance fee.
Office: 220, Leonard Square, Yogichowk, Varachha, Surat – 395006, Gujarat, India
Contents
- Quick answer and quick facts, including what this build is and is not
- The business and who this roofing ERP fits
- The challenge, before vs after and task by task
- Solution architecture: inquiry to profit
- Module-by-module walkthrough: CRM and leads, quotations and rate approval, orders and credit, stock and reservations, purchase, production and coil, dispatch, GST billing and payments, accounting, profit by order, HR and payroll, approvals, alerts and reports
- ERP vs CRM for a roofing business
- AI for roofing sheet makers and traders and WhatsApp and workflow automation
- Custom roofing ERP vs generic ERP, Tally and Excel
- Every feature and its purpose, roles and the business rules
- How it was built, what was delivered, technology, the next stage and cost and timeline
- Roofing sheet ERP in Surat and Gujarat: ERP vs CRM vs accounting vs AI, module checklist, coil stock and wastage, dealer CRM and WhatsApp, AI use cases, implementation and cost, buying checklist, ready-made vs custom, Tally and support in Surat
- FAQ
What is the best ERP software for a roofing sheet manufacturer and trader?
The best ERP for a roofing sheet business follows the whole chain instead of stopping at accounts: inquiry and CRM, a quotation checked against minimum rate, margin and discount rules, owner approval for exceptions, a sales order with a customer credit check, stock reservation, a purchase request when coil or trading items are short, roll-forming production with a coil requirement formula, wastage and scrap, quality, a dispatch challan with a loading checklist, a GST invoice for what was actually dispatched, payment allocation, double-entry accounts and profit by order. Yukti AI, a software company in Surat, built exactly this ERP, CRM and accounting system as a working version for a roofing sheet manufacturer and trader in Ankleshwar, Gujarat, and describes it here module by module.
Quick facts
| Item | Detail |
|---|---|
| Client | A roofing sheet manufacturer and trader in Ankleshwar, Bharuch district, Gujarat (client name not published) |
| Industry | Roofing sheet manufacturing and trading — profile sheets roll-formed to order from coil; trading of polycarbonate, UPVC, accessories and bolts |
| Business type | Manufacturer and trader selling to contractors, builders, industrial units, farmers and agri users, dealers and retail buyers, mostly on credit |
| What was built | ERP + CRM + accounting in one system: lead pipeline, quotations, orders, production, inventory, purchase, dispatch, transport, GST invoicing, receivables, double-entry accounts, HR and payroll, tasks and approvals, 42 reports, documents, audit log, WhatsApp workspace |
| Workflow modelled | Inquiry → CRM → quotation → rate approval → sales order → stock reservation / purchase / production → quality → dispatch → challan → invoice → payment → accounting → profitability |
| Product master | About 96 items from the client’s own godown stock list dated 19 October 2026 (coil and sheet brands, GP decking, polycarbonate, base plates and accessories, UPVC, bolts) plus made-to-order roofing sheet products |
| Product families in the system | Trapezoidal, corrugated and decking sheets, ridge flashing, 7 Nali profile, polycarbonate rolls, UPVC sheets and ridges, cement profile sheets, base plates, air ventilators, GI gutters, bolts, scrap |
| Warehouses | Five: coils and GP sheets godown, finished goods godown, polycarbonate / UPVC / accessories godown, scrap yard, WIP floor, each with bins |
| Roles | Ten roles and 41 permissions, enforced in the menu, the screens and the business logic |
| Tax | GST invoices with CGST + SGST or IGST by customer state, rates 0, 5, 12, 18 and 28 percent; financial year from April |
| Data | Customers, vendors, staff and company details are sample data; inventory opens with the client’s real stock list; rates are illustrative |
| Technology | React, TypeScript, Vite, Tailwind CSS, a typed service layer and automated tests; browser storage in this version |
| Status | Working version shown to the client as a demo. Not described as delivered, signed or in daily use. |
What this build is, and what it is not
This is a working version built for a roofing sheet manufacturer and trader in Gujarat and shown to the client as a demo. It does run end to end: you can take an inquiry through to a posted invoice, a payment and a profit figure. But it has no server — the data lives in one browser — and its customers, vendors, employees, company address, GSTIN and bank values are sample data. The product list and opening stock come from the client’s real godown stock sheet; purchase and sales rates are illustrative placeholders.
Not connected: WhatsApp (messages are logged as “Simulated Sent”), GPS tracking, GST return filing, e-invoice, e-way bill and bank feeds. They are built as seams that connect at go-live. No savings, revenue, user numbers or client quotes are claimed anywhere on this page.
A roofing order is a coil, a quote, a reservation, a challan and a margin
The business sells two kinds of goods. The first is made-to-order roofing sheet: colour-coated, galvalume or GP coil is slit and roll-formed into trapezoidal, corrugated or decking sheets, or bent into ridge flashing, in the length the customer asks for, usually quoted per sheet or per running foot. The second is trading goods bought and sold as they are: polycarbonate sheets in rolls, UPVC sheets and ridges, cement profile sheets, base plates, air ventilators, GI gutters, screws and bolts.
The stock side is broad. The client’s printed godown list runs to about 96 lines across coil brands such as JSW Coloron Plus, JSW Indradhanush, TATA, Manaksia and AM/NS, GP decking sheet, Skylite polycarbonate, base plates and accessories, UPVC and Prium bolts. Coil and sheet are counted in kilograms, accessories in numbers, so the system needs real unit conversions between sheets, running feet, millimetres, kilograms, rolls and metric tonnes.
The buyers are different too: contractors and builders who want a firm quote and a delivery date, industrial units and PEB fabricators who buy in volume on credit terms, farmers and poultry sheds, and dealers who resell. Each wants a rate that is fair to them and still earns a margin, and each carries a credit limit.
Roofing ERP software has to protect the margin and the stock at the same time: no quote below the minimum rate without the owner, no promise of coil that is already reserved, no dispatch of quantity that is not ready, no invoice for goods that did not leave the gate.
Who is this roofing sheet ERP, CRM and accounting system for?
It was designed around a business that both makes and trades in building materials and quotes against a margin. If you run a roofing sheet, profile sheet, PEB accessory, colour-coated coil, galvalume or GP sheet business in Ankleshwar, Bharuch, Surat, Vadodara or anywhere in Gujarat and India, this is the shape of manufacturing ERP software that fits you.
It is a good fit if most of these are true:
- Quotations are written in Word, Excel or on WhatsApp, and nobody checks the rate against cost before they go out.
- Discounts are decided on the phone, and the owner finds out about a thin-margin order after the material has left.
- Coil and sheet stock is counted in kilograms, sold in sheets or running feet, and nobody can say quickly what is free after promises already made.
- Short material is chased by phone with several vendors and the cheapest rate is not recorded anywhere.
- Dispatch quantities, invoices and the books are updated separately, so billed and dispatched do not match.
- Credit customers overshoot their limits and overdue follow-up depends on memory.
- Nobody knows the true profit of one order, only the total at year end.
The same design suits fabrication units, steel and metal traders, polycarbonate and UPVC sheet suppliers, fastener and hardware traders (see our fastener trading ERP) and other building-material dealers. For the wider view see software for manufacturing businesses and software for construction and building materials.
Quotes, stock, dispatch and books kept apart
These points describe the gaps the system was designed to close for a roofing manufacturer and trader. They are our description, not quotes from the owners, and none of the client’s business figures are shown here.
- Rates without a floor. A salesperson can quote any rate. Without a minimum approved rate per product and customer, margin is found out later.
- Stock that can be promised twice. Coil is counted in kilograms, sheets in pieces and accessories in numbers, and nothing separates stock on hand from stock already allocated to an order.
- Purchase by phone. Rates from several vendors are not compared on record, and the approval to buy is informal.
- Production without a coil formula. How much coil a 500-sheet order really consumes, including wastage, is estimated by experience, so shortages appear at the machine.
- Dispatch, invoice and ledger out of step. Challans, GST invoices and accounts entries are made separately, so what left the gate and what was billed drift apart.
- Credit by trust. Outstanding is checked after the order, not before, and ageing is built by hand.
- No order-level profit. Total profit is known at the end of the year; the profit of one order, with freight and scrap, is not.
If your business runs on spreadsheets and a billing package like this, see how we replace Excel and Tally with one system.
How an order is tracked in the roofing ERP
Before
- Quotes in Word, Excel or WhatsApp with no rate check
- Discounts agreed on the phone, margin found later
- Stock counted but not separated from promises
- Vendor rates compared by phone calls
- Coil needed for an order estimated by feel
- Challan, invoice and ledger entered separately
- Credit and ageing checked by hand
After (in the ERP)
- Inquiry → quotation → order → challan → invoice → payment as one linked record
- Minimum rate, margin and role discount limits checked before a quote is shared; exceptions go to the owner
- Available stock = on hand minus reservations, by warehouse and bin
- Purchase request, multi-vendor quotes, owner-approved vendor, PO, GRN and bill
- Coil requirement from unit weight and a wastage formula
- Invoice only for dispatched quantity, journalled automatically
- Credit limit checked at order time; ageing in five buckets
How does a day in a roofing sheet business change, task by task?
The table walks through real jobs and what each looks like in the ERP. The “before” column is a general description of working across spreadsheets and a billing package, not a measurement, and no time savings are claimed.
| Task | Before (sheets and a billing package) | After (in the system) |
|---|---|---|
| Inquiry arrives | Noted on paper or WhatsApp | Lead created with source, salesperson, requirement, quantity, expected value, next follow-up and priority; duplicates blocked |
| Quoting | Word or Excel file | Quotation with rate, discount, GST and freight; flags if below minimum rate or over the discount limit |
| Rate approval | Phone call to the owner | Approval request to the owner with the reason; order conversion blocked until approved |
| Confirming the order | Verbal or WhatsApp | Order created from the approved quotation with a credit check; owner approval if the customer is over the limit |
| Checking stock | Look at the godown, ask the store | Material plan shows available stock after reservations; shortage creates a draft purchase request |
| Buying short material | Phone around for rates | Rate inquiry to several vendors, quotes recorded, best vendor selected, owner approves, PO raised |
| Making the sheets | Instruction to the machine operator | Production job with coil requirement, machine, operator, stages, scrap and quality counts |
| Dispatching | Challan written by hand | Challan limited to ready quantity, approval, 9-point loading checklist, vehicle and driver, stock reduced on completion |
| Billing | Invoice typed separately | GST invoice only for dispatched and uninvoiced quantity, posted to the ledger |
| Collecting | Reminder calls from memory | Receipts allocated to invoices, advances kept as advances, ageing and reminders from live outstanding |
| Knowing the profit | At year end | Estimated and actual profit per order, with freight and scrap |
Want a system like this for your roofing or steel business?Tell us how your inquiries, quotes, stock and dispatch run today and we’ll show you what one system would replace. Free workflow audit, reply the same day.
Get a free workflow auditOne thread, inquiry to profit
All business logic sits in one service layer. A material issue reduces coil stock and sets the job’s material cost; a finished-goods receipt adds sheets to stock, reserves them for the order and posts a journal; a completed dispatch moves stock and updates the order; a posted invoice credits sales and GST, debits receivables and books the cost of goods sold. The dashboard, alerts, reports and statements are read from those same records, so a number is typed once.
Roofing ERP modules, walked through in business order
Sixteen menu groups covering CRM, customers, sales, orders, production, inventory, purchase, dispatch, accounting, HR, tasks, reports, documents and administration — the scope of a full AI-powered business management system, shaped around a roofing sheet maker and trader. Here they are in the order an order moves through the business.
Dashboard and action centre
The owner lands on an executive dashboard with KPI tiles, small charts and an action centre: a list of what needs attention, built by rules from live records and sorted by severity. Each item links to the record it is about. Other roles land on their own home screen: salespeople on the field-sales workspace, the accountant on accounting, purchase on purchase requests, production on planning, inventory on the stock dashboard, dispatch on dispatch overview, and factory workers and drivers on a mobile My Work page.
1. CRM: leads, follow-ups, visits and customers
Every inquiry becomes a lead with party, contact person, phone and WhatsApp number, source, salesperson, requirement, specification, estimated quantity and unit, expected value and close date, priority, next follow-up and next action. The five sources are WhatsApp, Phone Call, Website, Referral and Market Visit. The system blocks a duplicate lead for the same party and phone on the same day.
Leads move on a Kanban board through ten stages: New Inquiry, Contact Pending, Contacted, Requirement Collected, Quotation Preparation, Quotation Sent, Negotiation, Awaiting Customer Confirmation, Won / Order Confirmed, and Lost / On Hold. Moving a lead to Lost needs one of nine reasons, such as price too high, competitor offered a lower price, project postponed, went with a local supplier, credit terms not agreed or delivery time too long, which feeds a lost-lead report. Every call, meeting, WhatsApp note and stage change is written to the lead’s log, and sharing a quotation moves the lead to Quotation Sent on its own.
The follow-ups screen lists what is due and overdue. The field-sales workspace is built for a phone: a salesperson plans a visit to a customer or lead, checks in with a location note, checks out, records an outcome, or marks the visit missed; a second visit cannot start before the current one is closed. A customer 360 page shows a customer’s orders, invoices, outstanding, advances, credit headroom, contacts and complaints, and a team performance view compares each salesperson’s invoiced sales with a monthly target. Salespeople see only their own customers, leads, quotations and orders. For the CRM side on its own see custom CRM software and AI CRM.
2. Quotations, pricing and rate approval
A quotation is built from the product master: description, specification (profile, thickness, width, length and colour), quantity, unit, rate, discount percent, GST rate and HSN, plus packing and transport, a payment term, validity and expected delivery. Behind the rate sits a price master with quantity price tiers, customer-specific rates and customer-specific minimum rates. As a salesperson types, the screen shows the standard rate, the customer’s own rate, the cost, the minimum approved rate, the last rate offered to this customer and the last rate actually invoiced.
The checks are rules the owner can see and change:
- Minimum approved rate = cost ÷ (1 − minimum margin %). Example: cost 100 with an 8 percent minimum margin gives a minimum rate of 108.70, which gives a margin of exactly 8 percent. A customer-specific minimum overrides it.
- Discount limit by role. In the demo configuration a salesperson may give up to 3 percent, an accountant or purchase user 0, and the owner any amount. These are example settings, not the client’s policy.
- Margin check. Net rate after discount is compared with cost; a margin below the product’s minimum is flagged even if the rate looks acceptable.
On submit, a clean quotation is approved by the rules, and an owner submitting is approved at once. A flagged quotation from anyone else becomes Pending Approval, raises a Special Pricing or Discount Exception request to the owner with the exact reasons, and cannot be converted to an order until approved. When the owner approves, any negotiated rate below the standard is saved to that customer’s rate master and written to the audit log. A rejected quotation stays rejected; a revision creates a new numbered quotation and marks the old one Superseded, with the whole revision chain visible. Approved and sent quotations expire after their validity date. Quotations print or save as PDF.
Statuses: Draft, Pending Approval, Approved, Sent, Accepted, Rejected, Expired, Converted and Superseded. A quotation conversion report shows how many reach an order, and a discount analysis shows who gives how much.
3. Sales orders, order types and the credit check
An order is created from an approved quotation (or directly) and takes one of three types: Manufacturing (roll-formed in-house from coil), Trading (bought and sold as is) or Stock (served from finished goods already in the godown). The system suggests the type from the products on the quotation. The order carries delivery address, required delivery date, priority, transport instructions, payment term and an optional direct delivery flag for goods that a supplier ships straight to the customer.
At creation the system works out the customer’s outstanding, less any unallocated advance, plus this order’s value, and compares it with the credit limit. If the limit is exceeded and the user is not the owner, the order is held as Awaiting Approval and an owner request is raised, with the exact numbers in the reason. Orders move through 15 statuses — Draft, Awaiting Approval, Confirmed, Material Planning, Material Shortage, In Production, Quality Check, Ready for Dispatch, Partially Dispatched, Fully Dispatched, Invoicing Pending, Partially Invoiced, Completed, On Hold and Cancelled — and the later ones are derived from dispatched and invoiced quantities, so nobody sets “Completed” by hand.
Every order line tracks six quantities: ordered, allocated, produced, ready, dispatched and invoiced. A colour-coded deadline indicator turns amber when the required date is within the warning window (3 days by default) and red once it is missed. An order with dispatched quantity cannot be cancelled, and cancelling releases its reservations. The order page keeps a timeline of every step with who did it.
4. Inventory, reservations and stock audit
Stock is a movement ledger. Every receipt, issue, dispatch, transfer, return, scrap entry and adjustment is a movement with a type, a reference and a user, and balances are derived from the movements. The 12 movement types are Opening Stock, Purchase Receipt, Production Issue, Production Receipt, Dispatch, Customer Return, Supplier Return, Transfer In, Transfer Out, Adjustment, Scrap Receipt and Scrap Disposal. A movement that would take a warehouse below zero is refused unless negative stock is switched on in settings.
Reservations are kept apart from the balance, so the screen shows on hand, reserved and available for every product, plus stock in transit on dispatched challans and WIP in open production jobs. The product master carries explicit unit conversions — Sheet to Running Foot, to millimetres and to kilograms, Roll to kilograms, and MT to kilograms — so coil can be bought in tonnes, issued in kilograms and sold in sheets. Stock is valued at weighted-average cost by replaying movements in order.
Five warehouses with bins hold the coils and GP sheets, finished goods, polycarbonate / UPVC / accessories, scrap and the production floor, and stock can be transferred between them with a recorded reason. Manual movements are limited to customer returns, supplier returns and scrap disposal and always need a reason. A physical stock audit records the counted quantity against the book quantity; if there is a difference it goes to the owner for approval, and only then does it post an adjustment movement and a journal. Low-stock items against a minimum level and slow-moving items with no dispatch or issue for a chosen number of days are reported separately.
5. Purchase: request, vendor rates, order, receipt and bill
A shortage found while planning an order creates a draft purchase request linked to the order, or a user raises one by hand. Requests above owner level need approval; the owner’s own requests are approved at once. An approved request becomes a vendor rate inquiry sent to one or more vendors — the message text is generated, and in this build it is shown rather than sent on WhatsApp. Each vendor’s reply is recorded with rate, quantity available, delivery days and terms, or marked declined. The purchase manager selects one, and the vendor selection goes to the owner for approval.
Only then can a purchase order be raised from the inquiry, and a second PO for the same inquiry is blocked. Goods are received through a GRN with partial receipts allowed and receipt above the outstanding quantity refused. Where the supplier delivers straight to the customer, the receipt demands delivery evidence such as a customer-signed receipt reference. The supplier bill is booked against the PO with the supplier’s invoice number, and the same number cannot be booked twice for the same vendor. Vendor payment is allocated to bills, a possible duplicate payment is refused, and payables ageing shows what is due. Vendors carry a rating and an on-time percentage.
6. Production: coil requirement, jobs, scrap and cost
Each finished roofing product is linked to the raw coil it is cut from. From a validated weight per sheet and a wastage percentage the system works out the coil needed. The weight comes from the strip dimensions × thickness × steel density (7.85 grams per cubic centimetre), and the product master stores it so planning never guesses: a product without a weight cannot be planned.
A 0.50 mm sheet, 10 ft (3,048 mm) long, cut from a 1,220 mm strip weighs 1,220 × 3,048 × 0.50 × 0.00000785 = 14.60 kg. An order of 500 sheets is 7,300 kg of finished sheet. At an example wastage of 4 percent, coil required = 7,300 ÷ (1 − 0.04) = about 7,604 kg, of which about 304 kg is expected wastage. The wastage percentage is a configurable formula; the values in this build are illustrative until the factory supplies its own standards.
Planning an order reserves the available coil (in kilograms) for each line and, if coil is short, raises a purchase request for the shortage in kilograms. A production job is then scheduled for a quantity that cannot exceed what is left on the order line, with a machine, an operator, planned start and end and the formula to use. The six stages are Material Allocation, Material Issue, Cutting / Slitting, Roll Forming / Profiling, Quality Inspection and Finished Goods Receipt. Two formulas ship with the build: a standard profile sheet and a fabricated flashing with higher wastage for bending and cutting.
Material is issued from a warehouse at average cost, which sets the job’s material cost and consumes the reservation. The operator or manager records output and scrap in kilograms — output more than 5 percent over plan is refused — and the screen shows actual wastage next to planned. Quality is recorded as passed, rejected and rework, and the total cannot exceed the recorded output. On finished-goods receipt (blocked a second time for the same job) the system adds labour and conversion cost, charged per kilogram of coil issued, subtracts the scrap recovery value, divides by the passed quantity, adds the sheets to finished stock at that unit cost, reserves them for the order and posts a balanced journal. Scrap goes to the scrap yard and a later scrap sale posts to the books. Planned-versus-actual, material utilisation, job delays and quality rejection reports sit on top.
7. Dispatch: challan, loading checklist, transport and delivery
A challan can carry only quantity that is ready (authorised for dispatch), not yet dispatched and not already on another open challan, so a partial dispatch is a normal case and over-dispatch is impossible. Depending on a setting, a challan goes to approval before loading. In loading, each line is ticked as loaded and a nine-point checklist is completed: all lines accounted for, quantities verified against the challan, stock allocation confirmed, material loaded, vehicle and driver assigned, challan approved, invoice status checked, delivery instructions reviewed, and loading photos or supporting documents attached.
Dispatch cannot be completed with a line unloaded, a checklist item open, or a vehicle number or driver missing (and, if the setting is on, without a tax invoice). Completing it reduces stock from the reserved warehouse, updates the dispatched quantity, moves the order to Partially or Fully Dispatched, starts a trip with the transporter, freight and advance, and tells the accountant that an invoice is pending. The trip is closed when the delivery is acknowledged with a proof-of-delivery note and a delay reason where relevant. A dispatched challan cannot be cancelled; a customer return and credit note are raised instead.
Transport requests go to several transporters for a quote; replies record freight, vehicle type and capacity, pickup time and ETA, and the system checks that the vehicle capacity fits the load before one is selected. GPS check-ins are a consent-gated, simulated field in this build, and live tracking is not claimed. An order reconciliation view lines up ordered, dispatched and invoiced quantities per line so a gap shows at once. Vehicle-side tools for a larger fleet are covered in fleet management software.
8. GST invoicing, receipts and receivables
An invoice is drafted only for quantity that was dispatched and not yet invoiced (or, if the workflow setting says invoice-before-dispatch, quantity on approved challans). Tax splits into CGST plus SGST when the customer’s state equals the company’s state and IGST otherwise; packing and transport are added on the first invoice for an order at 18 percent; the total is rounded to the nearest whole amount with the round-off shown; the due date follows the payment term (immediate, 50 percent advance, net 7, 15, 30, 45 or a custom 60 days). A draft can be discarded; a posted invoice can never be deleted — a credit note is issued instead.
Posting writes one journal: receivables debited; manufactured and trading sales credited separately; freight income, output CGST, SGST or IGST and round-off credited; and cost of goods sold debited against the right inventory account at average cost. GST is never counted as revenue.
Receipts are recorded by cash, bank transfer, UPI or cheque with a reference and allocated to specific invoices, or auto-allocated to the oldest due first. The system refuses over-allocation, a future-dated receipt and a possible duplicate with the same customer, amount, date, mode and reference. Money not allocated stays as a customer advance and can be applied later. Receivables and ageing bucket outstanding into Not Due, 1 to 30, 31 to 60, 61 to 90 and 90 plus days by invoice and by customer, and a payment reminder message is generated from the live outstanding and due date and logged. Credit notes need owner approval, cannot exceed the invoice outstanding, and reduce it only after approval.
9. Accounting: double entry, statements and bank reconciliation
The accounting module is a real double-entry ledger, not a report layered on top. The chart of accounts has about 40 accounts in assets (cash, bank, receivables, raw, finished, trading and scrap inventory, input GST, advances, plant), liabilities (payables, output GST, customer advances, salary payable, loan), equity, income (manufactured sales, trading sales, freight recovered, scrap sales, round-off) and expenses (cost of goods sold, freight outward, salaries, rent, electricity, repairs, admin, fuel, incentive, labour absorbed, stock adjustment, bad debt).
- A journal must balance and may not have a line with both a debit and a credit; an unbalanced journal is rejected.
- Drafts never post. A posted journal is never edited; it is reversed with a new journal that references the original and a reason.
- Invoices, receipts, vendor bills and payments, production receipts, scrap sales, stock adjustments, credit notes, expenses and payroll post their own journals; manual receipt, payment, contra and journal vouchers are also available.
- Reports: trial balance, profit and loss, balance sheet, cash flow, GST summary, ledgers and party statements, and a statement comparing the stock sub-ledger with the general ledger.
- Bank reconciliation matches bank-statement lines to book entries; bank feeds are not connected, so statement lines are entered by hand.
- Expenses are claimed, approved and posted by category.
The financial year starts in April and numbers such as QT-2026-0001 or INV-2026-0001 follow it. The tax and valuation treatments (weighted-average cost, COGS posting) are simplified and flagged for review by the company’s accountant; the books can also stay in Tally — see Tally integration with a custom ERP.
10. Order profitability: estimated vs actual
For every order the system shows goods revenue (before GST), estimated material cost, freight, and estimated profit and margin. As real cost arrives it replaces the estimate: for a manufacturing order, coil issued plus labour and conversion less scrap recovery plus freight and other direct cost; for a trading order, purchase order cost plus freight and other direct cost; for a stock order, the average stock cost of what was dispatched plus freight. The screen says plainly when a number is still an estimate. Gross profit is never confused with cash collected, which is tracked separately in receivables.
11. HR, attendance and payroll
The factory and office team are in the same system. Attendance can be self-checked-in from a phone with a simulated location (a consent flag controls any GPS use), with late-after, half-day and full-day hours and overtime after a set number of hours in settings. Staff can ask for a correction, which HR approves. Leave has a balance by type and overlapping requests are refused. Salary advances record a monthly deduction that cannot exceed the advance. A payroll run uses attendance, overtime, incentives, allowances and deductions for monthly and daily-wage workers, cannot produce a negative net salary, goes to the owner for approval and is then paid with a salary slip for each person.
12. Approvals, tasks, alerts, reports, documents and audit
One Approval Centre handles every request that needs the owner: special pricing, discount exceptions, credit-limit exceptions, purchase requests, purchase orders, vendor selection, stock adjustments, challans, credit and debit notes, expense claims, payroll finalisation and leave. Rejecting needs a reason; a duplicate request for the same record is not created twice. Tasks carry assignee, deadline, priority and evidence. Notifications are de-duplicated, reach the right roles, and overdue payments escalate after 30 days.
The owner’s action list is generated from rules: payments overdue, delivery deadlines missed or approaching, material shortages, ready orders with no challan, dispatched quantity not invoiced, quotations awaiting rate approval, purchase approvals, customers over credit limit, stock-audit discrepancies, supplier bills due, attendance exceptions, transport quotes to choose, delayed deliveries and overdue follow-ups.
Reports number 42 in six groups, each exportable to CSV or printable:
| Group | Reports |
|---|---|
| Sales (8) | Sales by month, customer, product and salesperson; quotation conversion; lost-lead analysis; discount analysis; gross margin by order |
| Inventory (8) | Current stock, valuation, movement, low stock, slow-moving, material consumption, scrap and wastage, physical stock discrepancies |
| Production (6) | Output, work in progress, job delays, planned vs actual, material utilisation, quality rejection |
| Dispatch (5) | Pending dispatch, partial dispatch, delayed deliveries, transport cost, delivery performance |
| Finance (9) | Customer outstanding, receivable ageing, supplier outstanding, payable ageing, collections, cash flow, expenses, profit and loss, trial balance |
| HR (6) | Attendance, overtime, leave, payroll, salary advances, employee activity |
A document register keeps files against records, and an audit log records who did what and when for pricing changes, approvals, stock adjustments, reversals and status changes. In this browser-only version the log is not tamper-proof; an immutable log arrives with the server database.
Still quoting, dispatching and billing from separate files?Show us one real order from inquiry to payment and we’ll map what would change. Free workflow audit, reply the same day.
Get a free workflow auditERP vs CRM for a roofing sheet business: which one do you need?
An ERP runs the inside of the business: stock, purchase, production, dispatch, invoices and accounts. A CRM runs the relationship with buyers: inquiries, follow-ups, quotations, visits, complaints and outstanding. Readymade software usually sells them separately, so a roofing supplier ends up with a CRM that does not know the real stock and an ERP that does not know who is waiting for a quote.
| Question | Answered by the ERP | Answered by the CRM |
|---|---|---|
| How much 0.50 mm white coil is free after current orders? | Yes — on hand minus reservations | Only if it reads the ERP |
| Which inquiries need a call today? | — | Yes — follow-ups and stages |
| Is this quote above the minimum rate? | Yes — cost, margin and rules | Only if it reads the ERP |
| Can this customer take another order on credit? | Yes — limit vs outstanding | Yes, if connected |
| Which salesperson is behind target? | Yes — invoiced sales | Yes — pipeline and visits |
| Where is the dispatched load? | Yes — challan and trip | — |
For a manufacturer-trader that sells on quotes, the right answer is usually one system where the CRM side reads the same stock, rates and invoices as the production side. That is how Yukti AI builds — this system is ERP, CRM and accounting on one record. See custom CRM software and Yukti AI CRM for the CRM side on its own, and CRM automation for connecting an existing CRM.
What AI can realistically do for a roofing sheet maker and trader
Most writing about AI in metal roofing is about estimating from satellite images or machine vision on the line. For an Indian sheet maker and trader the more practical first step is AI on top of good business data: once inquiries, quotes, stock, orders, dispatch and payments sit in one system, a model can read them. Without that data there is nothing for AI to work on. The labels below say exactly what exists.
Built in this system today (rule-based, no external AI model)
- Rate and discount checks — minimum rate, margin and role discount limits applied to every quotation line.
- Owner action list — overdue payments, missed deadlines, shortages, credit breaches and pending approvals found by rules.
- Price context — last offered rate and last invoiced rate shown beside the rate being typed.
- Shortage logic — a plan that turns a coil shortage into a purchase request in kilograms.
- Reminder and message drafts — payment reminder and vendor rate inquiry text generated from live records.
Buildable on the same data — not built yet
- A plain-language owner briefing each morning: quotes waiting, orders at risk, coil running low, cash due.
- Quotation drafting from a WhatsApp inquiry: read the sizes, colour and quantity, suggest the customer’s last rate and a rate that keeps the minimum margin. The approval rule still decides.
- Reorder suggestions for coil by thickness and colour from consumption and open orders.
- Lost-lead and discount pattern analysis across salespeople and customer types.
- Plain-language questions such as “which orders are short of white 0.45 mm this week?”, answered from live records by an ERP-connected AI agent.
- A voice agent for overdue payment calls (see voice AI payment reminder calls).
Needs sensors or hardware — not in scope
- Weighbridge or scale integration for gross, tare and net weight at the godown, camera-based surface defect checks, and coil-line or roll-former machine counters.
See how we approach this on AI ERP and AI automation in Surat.
Automation for roofing sheet suppliers: WhatsApp, reminders and reports
Automation here means removing re-typing and chasing. Much of that comes from one record: an approved quotation becomes an order without retyping, a completed dispatch reduces stock and prompts the invoice, a posted invoice journals itself, a receipt ages the receivables, and the dashboard and reports update on their own.
The next layer is messages and schedules. The system already contains a WhatsApp workspace with eight templates — quotation share, customer follow-up, order confirmation, dispatch update, invoice share, payment reminder, vendor rate inquiry and transport inquiry — each filled from the live record, behind an adapter that a real WhatsApp Business Platform connection can replace. Built with WhatsApp automation and workflow automation, the live version can:
- Send the quotation and order confirmation to the customer on WhatsApp, and start a lead from an incoming message
- Send dispatch details — vehicle number, driver and expected arrival — when a challan is completed
- Send payment reminders from live outstanding and overdue days, escalating by ageing bucket
- Send a rate inquiry to several vendors at once and collect the replies
- Send the owner a daily summary of approvals pending, shortages and dues at a fixed time
Honest status: in this build every WhatsApp message is logged as “Simulated Sent” and nothing reaches a phone. Connecting the WhatsApp Business Platform needs a verified business number and message templates, and message charges are paid to Meta; see WhatsApp Business API pricing in India.
Custom roofing ERP vs generic ERP, Tally and Excel
A general comparison of the options a roofing sheet maker or steel trader usually weighs. It describes typical behaviour, not any specific vendor.
| Need | Excel / WhatsApp | Tally | Generic readymade ERP | Custom roofing ERP |
|---|---|---|---|---|
| Quotation rate and margin check | Manual | No | Sometimes, add-on | Built in: minimum rate, margin, role discount limits |
| Owner approval of exceptions | Phone call | No | Generic workflow | Built in; conversion blocked until approved |
| Stock reservation for orders | No | No | Often | Built in: available = on hand − reserved |
| Coil kg to sheets, wastage formula | Separate sheet | No | Rare | Built in: unit weight and wastage formula |
| Multi-vendor rate comparison | Phone and notes | No | Sometimes | Built in with owner-approved vendor |
| Challan-controlled dispatch | Paper | Delivery notes | Often | Built in: ready quantity, checklist, vehicle, driver |
| Credit limit check at order | Manual | Report only | Often | Built in: owner approval if exceeded |
| CRM: leads, visits, follow-ups | Notebook | No | Separate product | Built in on the same data |
| GST accounting | No | Strong | Yes | GST invoices and double-entry books; accountant can keep Tally |
| Profit by order | Year end | No | Rarely | Built in: estimated vs actual |
| Fits your process | Loosely | No | You adapt to it | Built around it |
Many manufacturers keep Tally for the accountant and run operations in the ERP; see Tally integration with a custom ERP and our guide to moving from Excel and Tally to one system.
Every feature of the roofing ERP, and what it is for
Everything in this table is built into the working version. The right-hand column is the purpose of the feature, not a measured result.
| Feature | What it does | Purpose for the business |
|---|---|---|
| Lead pipeline | 10 stages, 5 sources, 9 lost reasons, duplicate block | No inquiry lost, reasons for losing visible |
| Follow-ups and field visits | Due list, planned visits, check-in, outcomes | Sales time spent on the right customers |
| Price master and tiers | Standard rate, quantity tiers, customer rates and minimums | One source of truth for rates |
| Minimum rate and margin check | Cost ÷ (1 − margin) with customer overrides | No sale below the floor without the owner |
| Discount limit by role | Limit per role flags excess | Discounts controlled where they are given |
| Quotation revisions | Numbered revisions, superseded chain, validity | The customer always has one current offer |
| Rate approval | Owner request with reasons; blocks order conversion | Exceptions are decisions, not accidents |
| Customer rate memory | Approved special rates saved with audit | Next quote starts from the agreed rate |
| Credit check | Outstanding − advances + order vs limit | Credit risk checked before material moves |
| Order types | Manufacturing, trading, stock, direct delivery | Each order follows the right path |
| Order quantity tracking | Ordered, allocated, produced, ready, dispatched, invoiced | One look shows where an order stands |
| Deadline indicator | Green, amber, red from required date | Late orders seen before they are late |
| Stock movement ledger | 12 movement types, derived balances | Every kilogram and sheet accounted for |
| Reservations | Per order line and warehouse | Stock cannot be promised twice |
| Unit conversions | Sheet, running foot, mm, kg, roll, MT | Buy in tonnes, sell in sheets |
| Physical stock audit | Count vs book, owner approval, journal | Adjustments are authorised and visible |
| Low and slow stock | Minimum levels and no-movement days | Reorder in time, spot dead stock |
| Purchase request and approval | Linked to order shortage | Buying is authorised and traceable |
| Multi-vendor rate inquiry | Quotes recorded, vendor selected, owner approves | Best rate on record |
| PO, GRN and vendor bill | Partial receipts, duplicate bill block | Pay only for what was received |
| Coil requirement formula | Unit weight and wastage give kg needed | Shortage found before the machine stops |
| Production jobs | Machine, operator, 6 stages, 5 percent tolerance | Output planned and recorded per job |
| Scrap tracking | Scrap kg, scrap yard, scrap sale | Wastage visible and recoverable |
| Quality counts | Passed, rejected, rework | Only passed sheets reach stock |
| Finished-goods costing | Material + labour + conversion − scrap | A real cost per sheet |
| Challan control | Ready quantity, approval, 9-point checklist | Dispatch only what is ready and verified |
| Transport quotes and trips | Quotes, capacity check, trip, POD | Freight compared and delivery proven |
| GST invoice by state | CGST + SGST or IGST, freight, round-off | Correct tax on every invoice |
| Receipts and advances | Allocation, auto-allocate, duplicate block | Cash applied to the right invoice |
| Receivables ageing | Five buckets by invoice and customer | Collections focused where overdue |
| Credit notes | Owner approval, cannot exceed outstanding | Corrections without deleting invoices |
| Double-entry accounts | Balanced journals, reversal only | Books that always balance |
| Financial statements | TB, P&L, balance sheet, cash flow, GST summary | Management and tax view from the same data |
| Bank reconciliation | Statement lines matched to books | Bank and books agree |
| Order profitability | Estimated vs actual per order | Know which orders earn money |
| HR and payroll | Attendance, leave, advances, payroll, slips | Wages from recorded attendance |
| Approval Centre and tasks | 13 approval types, task deadlines | Nothing waits in a chat thread |
| Action list and notifications | Rule-based, de-duplicated, escalating | Owner sees what matters first |
| Reports | 42 reports, CSV and print | Answers without building a sheet |
| WhatsApp workspace | 8 templates; simulated send in this build | Ready for a real connection |
| Audit log and roles | 10 roles, 41 permissions, who-did-what log | Control over who can change what |
Who works in it
Ten roles are set up: Owner, Salesperson, Accountant, Purchase Manager, Production Manager, Inventory Manager, Dispatch Manager, HR Manager, Factory Worker and Driver. Each has a home screen suited to the job — a salesperson’s is a phone-first field workspace, a worker’s and driver’s is a My Work page with attendance and assigned tasks. Permissions are checked in the menu, in route guards, on screen actions and in the service layer, so hiding a button is not the only protection. Salespeople see only their own customers, leads, quotations and orders; only the owner can change sales rates, margins and price tiers, and only the owner or purchase manager can set cost rates. In the demo the sign-in is a user picker with no passwords; real logins arrive with the database stage.
The business rules the system enforces
These are the checks that make the numbers trustworthy. Each is enforced in the logic, not just in the screen.
| Area | Rule |
|---|---|
| Quotation | Net rate below minimum approved rate, discount over role limit, or margin below minimum raises a flag; flagged quotations from non-owners need owner approval |
| Order | Only an approved quotation converts, once; credit limit breach holds the order; cancelled orders cannot change; orders with dispatched quantity cannot be cancelled |
| Stock | Negative stock refused (configurable); reservations cannot exceed available stock or the ordered quantity; adjustments only through an approved audit |
| Production | No planning without a measured unit weight; job quantity cannot exceed the open order line; output over 5 percent above plan refused; quality counts cannot exceed output; one finished receipt per job |
| Purchase | PO only after owner-approved vendor selection; one PO per inquiry; no receipt above the outstanding PO quantity; direct delivery needs evidence; duplicate supplier invoice and duplicate payment refused |
| Dispatch | Challan quantity limited to ready and unshipped quantity; loading checklist, vehicle and driver required; dispatched challans cannot be cancelled |
| Billing | Invoice only dispatched and uninvoiced quantity; posted invoices cannot be deleted; credit notes need approval and cannot exceed outstanding |
| Receipts | No future-dated receipts, no over-allocation, no duplicates; unallocated money held as advance |
| Accounts | Journals must balance; posted journals are reversed, never edited; GST is not revenue |
| Money | Every amount rounded to paise at each step; quantities to three decimals |
See your own roofing business in a working system firstWe build on your real product list and process, so you judge something working, not a slide deck. Free workflow audit, reply the same day.
Get a free workflow auditHow it was built
Start from the real stock list
The client’s printed godown stock sheet, dated 19 October 2026, became the product master and the opening stock: about 96 lines of coil, sheet, polycarbonate, UPVC, accessories and bolts.
Model the chain
Inquiry → CRM → quotation → rate approval → order → stock, purchase or production → quality → dispatch → invoice → payment → accounts → profit, as one typed data model.
Put the rules in one place
Pricing, approvals, stock, production, dispatch, billing and accounting rules live in a service layer that every screen calls, and permissions are checked there too.
Run the real services to seed the data
The sample dataset is created by running the same services, so sample ledgers, stock and receivables agree with each other from the first screen.
Simplify for the shop floor
Client feedback was that screens had too much text and too many options. Each page was redesigned around a headline, a few status tiles, a pipeline filter and a short table, for non-technical staff and phones.
Test the invariants
Automated tests cover money rounding, the real-stock opening balances, the seed data and end-to-end workflows: partial payments, over-allocation, duplicate receipts, dispatch and invoice limits, quotation approval, negative stock, unbalanced journals and credit notes.
What was delivered
Stated factually — what the system does, not a claim about savings or revenue.
No client quote, time saving, revenue, margin improvement or user figure is published, and the system is not described as delivered or in daily use. The client’s stock quantities, rates and business numbers stay private; the customers, vendors and staff in the demo are sample data.
Technology
- React 18, TypeScript (strict), Vite and Tailwind CSS — the application, with Lucide icons and Recharts for charts.
- Zustand store, React Router — one typed data object, with every write run as one action on a copy so a failed action changes nothing and shows an error message.
- A service layer — sales, production, inventory, purchase, dispatch, billing, receivables, accounting, HR, approvals, alerts and a WhatsApp adapter as plain functions that check permissions and write the audit log.
- Vitest tests — money, opening stock, seed data and end-to-end workflow rules.
- Browser storage — this version keeps data in the browser; export and import is a manual JSON backup. A server database replaces it in the next stage.
The next stage
| Step | What happens |
|---|---|
| Real standards | Factory supplies measured sheet weights, wastage, labour and conversion rates and scrap values; real rates and the real customer, vendor and team lists replace the samples |
| Server database | PostgreSQL with multi-user logins, row-level permissions, an immutable audit trail and file storage for photos, PODs and attachments |
| WhatsApp Business Platform replaces the simulated adapter; incoming inquiries create leads; delivery status is tracked | |
| GST and banking | E-invoice (IRN) and e-way bill through a GST suvidha provider, GST return exports, and bank-statement import for reconciliation |
| Field and weighbridge | Phone geolocation with consent and a retention policy; vehicle telematics; weighbridge or scale integration |
| Accountant review | Tax, valuation and COGS treatments reviewed by the company’s accountant; optional Tally sync |
| AI layer | Owner briefing, quotation drafting from WhatsApp, reorder suggestions and plain-language questions on the same data |
What decides the cost of roofing sheet ERP software, and how long does it take?
The cost of a custom roofing ERP depends on the modules you need, the number of users and godowns, and the integrations (WhatsApp, GST e-invoice, Tally, bank). It is quoted after a free scoping call, once we have seen how your inquiries, quotes, stock, dispatch and collections actually run. Large vendor ERP projects take months to implement; a focused custom build is meant to be much faster. WhatsApp message charges are paid to Meta and any AI usage to the AI provider.
Focused builds — a single-module system, one automation, a Shopify store — typically take about 7–10 days. A multi-module ERP or CRM usually takes a few weeks depending on scope. For a roofing business like this one, the working version comes first on your own product list, so the owners can judge something that runs before committing to the rollout. Data setup, team training and support are part of how Yukti AI works, and the scope is written into the quotation.
More detail in our custom ERP cost guide, on custom ERP software and on AI automation cost in India.
If you quote by rate, reserve stock and dispatch by challan, this is buildable for you
The pattern — lead and quotation with rate approval, credit-checked orders, reserved stock, multi-vendor purchase, production from coil or raw material, challan-controlled dispatch, GST invoicing and profit by order — fits:
- Roofing sheet, profile sheet, decking and PEB accessory manufacturers
- Steel, GP / GI / PPGL / PPGI coil and sheet traders and processors
- Polycarbonate, UPVC, FRP and insulation sheet suppliers
- Fabricators, purlin and structural suppliers, fastener and hardware traders
Start with a free workflow audit. See Manufacturing ERP Software, Fabrication ERP Software or Custom ERP Software in Surat. Related builds: a corrugated box ERP with costing and quotations, a fastener trading ERP, a solar mounting structure ERP and a garment manufacturing ERP.
Who needs roofing sheet ERP software in Surat and Gujarat?
Roofing sheet ERP software suits any Surat or Gujarat business that roll-forms profile sheets from coil, trades colour-coated, galvalume or GP sheets, or sells polycarbonate, UPVC sheets and accessories, and that quotes on rate and margin, sells on credit and ships by challan. If quotes, coil stock, dispatch and accounts sit in separate files, one connected system removes the most re-typing first.
South Gujarat has a large industrial and building-material base. Around Surat, the industrial areas at Sachin, Pandesara, Udhna and Katargam are roughly an hour or so from the Ankleshwar and Bharuch estates, with Vapi and Sarigam to the south, Dahej to the north near Bharuch, and Vadodara, Ahmedabad and Rajkot beyond and Vadodara, Ahmedabad and Rajkot beyond. Sheds, warehouses, cold storages, farm structures and factory extensions keep demand for profile sheet steady across all of it, and the businesses that serve that demand tend to look alike: a roll-forming line or two, a coil godown, a trading counter, a few salespeople on the road and an owner who approves every difficult rate.
The working version on this page was built for a manufacturer and trader in Ankleshwar, Bharuch district. Yukti AI is a Surat software company with its office in Varachha, so the same design can be set up for a Surat unit on its own product list and rate rules. These are the business types it fits best.
| Type of business | What usually hurts most | Module to switch on first |
|---|---|---|
| Roll-forming manufacturer (trapezoidal, corrugated, decking, ridge) | Coil needed per order is guessed; scrap is not tracked; margin is known only at year end | Production with a coil requirement formula, then profit by order |
| Manufacturer-trader (sheets plus polycarbonate, UPVC, accessories) | Two kinds of orders in one godown; stock promised twice | Inventory with reservations and order types |
| Colour-coated, galvalume or GP coil and sheet trader | Rates change often; quotes go out without a floor | Quotations with minimum rate and owner approval |
| Coil processor (slitting, cutting to length) | Offcuts, remnants and kilogram-to-sheet conversions | Unit conversions and the stock ledger |
| Dealer or distributor of roofing material | Credit exposure and slow collections across many small customers | Credit limit at order and receivables ageing |
| Shed and PEB contractor who also stocks sheets | Site orders, quotations and stock mixed in one notebook | CRM, quotations and dispatch by challan |
If your trade is close but not identical, the pattern still carries over. See custom ERP software in Surat for the wider service, software for manufacturing businesses for the sector view and software for construction and building materials for the supply side.
ERP vs CRM vs accounting vs AI automation: what each does for a sheet manufacturer-trader
The ERP runs stock, purchase, production, dispatch and billing. The CRM runs inquiries, follow-ups, quotations and visits. Accounting keeps the double-entry books, GST and receivables. AI automation sits on top of all three, reading their data to draft quotes, brief the owner and chase dues. For a roofing sheet business they work best as one record, not four tools.
Buyers often search for these as four separate products and end up with four separate subscriptions that do not talk to each other. The salesperson quotes from the CRM without seeing free coil, the store issues material from the ERP without seeing who is waiting for a quote, and the accountant re-enters invoices in a separate package. The table shows what each layer is responsible for and the question it should answer in a few seconds.
| Layer | Its job | A question it should answer | In the working version on this page |
|---|---|---|---|
| ERP | Stock, purchase, production, dispatch, invoicing | How much of this coil is free after current orders? | Built and working |
| CRM | Leads, follow-ups, quotations, visits, complaints | Which inquiries need a call today? | Built and working |
| Accounting | Journals, ledgers, GST summary, receivables, bank reconciliation | Who owes us money and for how many days? | Built and working |
| WhatsApp automation | Sends quotes, dispatch updates and reminders from live records | Has the customer received the dispatch details? | Templates built; sending is simulated, not connected |
| AI automation | Reads records, drafts, summarises, flags | Which three orders need my attention this morning? | Rule-based alerts built; AI model features can be built |
A sensible order for a new project is the operational core first (stock, quotations, orders, dispatch, invoices), then the CRM pipeline on the same data, then WhatsApp, and AI last, because AI needs a few weeks of clean records to be useful. Our guide on ERP vs CRM: what a growing business needs first goes through that choice in more detail, and the AI business management system page shows how the layers are joined. If you only need the sales side, read about custom CRM software; if you want an AI layer on an ERP, see AI ERP.
Roofing sheet ERP module checklist: coil, forming, job cards, dispatch, dealers, GST
A complete roofing sheet ERP covers eight areas, plus the integrations around them: coil and sheet stock, slitting and roll-forming, production job cards, dispatch with challans, dealer and customer management, quotations with rate control, GST invoicing, and collections. Use the table below as a checklist when you compare any software, ours or anyone else’s, and ask to see each row working on your own products.
| Area | What it should control | Test question for a demo | Working version on this page |
|---|---|---|---|
| Coil and sheet stock | Kilograms, sheets and running feet; warehouse and bin; reserved vs free | Show free stock of one colour and thickness after two open orders | Built: movement ledger, reservations, conversions |
| Slitting and roll-forming | Coil issued, sheets produced, wastage and scrap | Enter 500 sheets and show the coil needed | Built: six production stages, scrap yard |
| Job cards | Machine, operator, dates, material issue, quality result | Open one job and show cost per kilogram | Built: jobs with output tolerance and quality status |
| Dispatch | Challan limited to ready quantity, loading checklist, vehicle and driver | Try to dispatch more than is ready | Built: blocked by the system |
| Dealers and contractors | Customer-specific rates, credit limits, visit history | Quote the same sheet to a dealer and a retail buyer | Built: customer rate master and customer 360 |
| Quotations | Minimum rate, margin, discount limit, approval, revisions, validity | Quote below the floor as a salesperson | Built: flagged and sent to the owner |
| GST invoicing | CGST and SGST or IGST by state, freight, round-off, posted invoices locked | Invoice a partly dispatched order | Built: only dispatched quantity is billable |
| Collections | Receipts, advances, ageing, credit status, reminders | Show overdue customers by 30, 60 and 90 days | Built: ageing buckets and reminder templates |
| Integrations | WhatsApp, e-invoice, e-way bill, bank, Tally | Show a real message or e-way bill generated | Not connected in the working version; scoped per project |
Each row above is described module by module in the walkthrough earlier on this page. For a broader factory view that also includes bills of material and planning, see manufacturing ERP software; if your trade is closer to cutting, bending and fitting, see fabrication ERP software and our fabrication ERP case study.
How roofing ERP handles coil stock, sheet weight and wastage
Coil is bought and stocked in kilograms, but customers order sheets of a given length, so the ERP must convert between kilograms, sheets, running feet and millimetres. It stores a unit weight per sheet, applies a wastage percentage to find the raw coil an order needs, and keeps stock on hand separate from stock reserved for open orders, so the same coil is never promised twice.
A formula example shows the logic. A sheet cut from a strip 1220 mm wide, 3048 mm (10 feet) long and 0.50 mm thick, in steel of density 7.85 g per cubic centimetre, weighs about 14.60 kg. An order of 500 such sheets is 7,300 kg of finished weight. If the wastage allowance were 4 percent, the raw coil to allocate would be about 7,604 kg, of which roughly 304 kg is wastage. The 4 percent is only an illustration for the arithmetic; every factory sets its own standard after measuring offcuts, setup losses and rejects, and the ERP stores that standard as a setting, not as a fixed number.
Three practical points decide whether the numbers hold up in the godown:
- Thickness has two meanings. Coated coil may be quoted by total coated thickness or by base metal thickness. The item master should say which one the coil record uses, otherwise the unit weight and the purchase rate quietly disagree.
- Offcuts are stock. Remnants and short lengths either go to scrap, to a scrap sale, or back into stock for small orders. The ERP needs a separate scrap yard and a reason code for each movement, or the wastage figure becomes a guess.
- Reservations beat memory. When an order is confirmed, the quantity is reserved against the coil or finished sheets. Available stock is on hand minus reserved, and a negative balance can be blocked by a setting.
The working version on this page does all three, using the client’s own godown list as the product master; the wastage and weight values in it are illustrative placeholders until a factory supplies its standards. The same stock logic is described for another trade in our fastener trading ERP case study, where goods are also counted in kilograms and pieces at once, and in the corrugated box ERP case study, where paper reels play the role of coil.
Dealer and contractor CRM with WhatsApp follow-up for sheet suppliers
A roofing sheet CRM records every inquiry from WhatsApp, calls, the website, referrals and market visits, moves it through stages to won or lost, and schedules the next follow-up. Because it shares one record with stock and rates, the salesperson quotes against real availability and approved prices, and WhatsApp messages are filled from the live quotation or order.
Many roofing inquiries arrive as a photo or a few lines on WhatsApp: a size, a colour, a quantity and a question about when it can be delivered. A fast, clear reply often matters in winning the deal. A CRM that is separate from stock cannot give that number, so the salesperson calls the store and the reply is delayed.
A useful dealer and contractor CRM does these things in one place:
- Captures each inquiry with its source, and blocks duplicate leads from the same phone number.
- Moves the lead through stages such as New Inquiry, Requirement Collected, Quotation Sent, Negotiation and Won or Lost, with a reason recorded for every lost deal.
- Shows a customer page with past orders, last rate offered, last rate invoiced, outstanding and complaints.
- Keeps separate rates and credit limits for dealers, contractors, industrial buyers and retail customers.
- Plans field visits, records check-in and outcome, and compares each salesperson with the monthly target.
WhatsApp is the follow-up channel. In the working version there are eight message templates for quotation sharing, follow-up, order confirmation, dispatch update, invoice sharing, payment reminder, vendor rate inquiry and transport inquiry. They are filled from live records but sending is simulated, so nothing reaches a phone yet. To make them live, the business needs a verified WhatsApp Business number; message charges are paid to Meta, as explained in WhatsApp Business API pricing in India. For how we build the sending side, see WhatsApp automation and the WhatsApp automation guide for India.
If you want a ready CRM for the sales team first, without a full ERP, Yukti AI CRM is the product version and CRM automation connects an existing CRM to your other tools.
AI and automation for roofing sheet makers: what is built and what can be built
In the working version on this page, the automation is rule-based: rate and discount checks, an owner action list, shortage logic and message drafts. No AI model is inside it. Features such as a morning owner briefing, quotation drafting from a WhatsApp inquiry and reorder suggestions can be built on the same data; they are labelled below as can be built, not as delivered.
AI is only as good as the records it reads. Once inquiries, quotes, stock, dispatches and payments are in one place, a model can summarise and draft; before that, it can only guess. The table separates what exists from what is possible, so you can judge the ideas without mistaking them for features.
| Use case | What it would do | Status |
|---|---|---|
| Rate and discount checks | Flags quote lines below minimum rate, margin or role discount limit | Built in the working version (rule-based) |
| Owner action list | Lists overdue payments, late deliveries, shortages, credit breaches and pending approvals | Built in the working version (rule-based) |
| Shortage to purchase request | Turns a coil shortage into a purchase request in kilograms | Built in the working version (rule-based) |
| Morning owner briefing | A short plain-language summary on WhatsApp: quotes waiting, orders at risk, coil running low, cash due | Can be built |
| Quotation drafting from a WhatsApp inquiry | Reads size, colour and quantity, suggests the customer’s last rate and a rate that keeps the minimum margin; approval rules still decide | Can be built |
| Coil reorder suggestions | Proposes purchase quantity by thickness and colour from consumption and open orders | Can be built |
| Vendor invoice and test certificate reading | Extracts quantities and rates from a PDF or photo into a goods receipt for checking | Can be built |
| Overdue payment calls | A Hindi or Gujarati voice agent that calls customers with the amount due | Can be built |
| Ask-the-ERP agent | Answers questions such as which orders are short of a colour this week, from live records | Can be built |
| Weighbridge, camera or machine-counter links | Reads weights, surface defects or sheet counts from hardware | Needs sensors; not in scope |
Two cautions keep this honest. First, AI drafts and the approval rule decides; a suggested rate never bypasses the minimum-rate check. Second, running costs are separate: WhatsApp message charges go to Meta and AI usage to the AI provider. For how we scope this kind of work, see AI automation in Surat, AI agents for business, voice AI payment reminder calls and workflow automation, and for prices AI automation cost in India.
Roofing ERP implementation, data migration and cost factors
A multi-module ERP and CRM from Yukti AI starts from ₹30,000, with the final quote after a free 30-minute workflow audit. Focused builds take about 7 to 10 days and a multi-module system a few weeks. The price is a one-time build that includes data setup, training and 12 months of support, followed by a small annual maintenance fee.
The ₹30,000 is a starting point, not a fixed price for every roofing business. What moves the quote up or down is scope, and it is easiest to see scope as a list.
- Modules. Stock and billing alone is smaller than stock, production, purchase, CRM, dispatch and accounting together.
- Users and roles. A five-person office with an owner and a store is simpler than ten roles with different permissions.
- Godowns and bins. More locations mean more transfers, counts and audit rules.
- Product master. A short, clean list loads quickly; a long list of colours, thicknesses, brands and lengths needs more clean-up first.
- Integrations. WhatsApp, GST e-invoice, e-way bill, Tally and bank links each add work and some carry outside charges.
- Reports and print formats. Your own quotation, challan and invoice layouts take extra time to match.
- AI features. A morning briefing or quotation assistant is added after the core is stable, and AI usage is billed by the AI provider.
The path is short. We start with the free 30-minute workflow audit, in which you walk us through one real order from inquiry to payment. We then agree the module list and the quote, load your product list, customers, vendors, opening stock and outstanding balances, show you a working version on your own data so you can judge it before the full rollout, train the team, and go live with support in the first year. Data you already keep in Excel or Tally is the usual starting point; see how to move from Excel and Tally to one system and replace Excel and Tally.
For the general cost picture across industries, read the custom ERP cost guide for India, and for how this works for a Surat business see custom ERP software in Surat.
Roofing sheet ERP buying checklist: 12 questions to ask before you sign
Before buying any roofing sheet ERP, ask the vendor to show twelve things on your own product list: kilogram and sheet conversion, free stock after reservations, minimum-rate approval, wastage-based coil requirement, challan-limited dispatch, GST invoice from dispatched quantity, credit limit at order, receivables ageing, Tally handling, data ownership, support language and a written scope. A vendor who cannot demonstrate them is selling a general package.
- Units. Can one coil item be stocked in kilograms and quoted in sheets or running feet, with the conversion stored once?
- Free stock. Does it show on-hand, reserved and available separately?
- Rate floor. Is there a minimum rate per product and customer, and does a lower quote stop for approval?
- Coil requirement. Can it work out raw coil for an order using unit weight and wastage?
- Dispatch control. Is the challan limited to ready quantity, with vehicle and driver recorded?
- Invoice from dispatch. Can it bill only what actually left the gate?
- Credit. Is the credit limit checked when the order is created, not after?
- Ageing. Does it show dues by 1–30, 31–60, 61–90 and over 90 days?
- Tally. Can your accountant keep Tally while operations run in the new system?
- Ownership. Who owns the data and the source, and how is it exported if you leave?
- Support. Is support available in Hindi, Gujarati and English, and for how long is it included?
- Scope in writing. Is the module list, user count, integration list and training plan in the quotation?
Red flags: a demo that uses someone else’s products only, a price that does not say what is excluded, integrations promised as “available” without a working example, and any claim of savings with no figures behind it. The same list works whether you are comparing readymade packages, an in-house tool or a custom build. Our page on custom ERP vs off-the-shelf ERP gives the longer comparison.
Ready-made ERP or custom roofing ERP: how to choose
Choose a ready-made ERP if your process is standard, your product list is small and you are happy to adapt your way of working to the software. Choose a custom roofing ERP if you quote on rate and margin, convert coil to sheets, reserve stock and ship by challan, and your team keeps falling back to Excel because the package does not fit.
| Point | Ready-made ERP | Custom roofing ERP |
|---|---|---|
| Fit to coil and sheet logic | Some packages are generic on stock and billing; conversions and wastage may need workarounds | Built around kilogram-to-sheet conversion and the coil formula |
| Rate approval | Some are limited to a price list | Minimum rate, margin and role discount limits as rules |
| Time to start | Fast if the process matches; slower if it needs configuration | Focused builds in about 7 to 10 days, multi-module in a few weeks |
| Cost pattern | Some are priced per user or per month, on a continuing basis | One-time build from ₹30,000 with 12 months of support, then small annual maintenance |
| Changes later | Depends on the vendor and the package | You can ask for new screens and rules |
| Risk | Staff may not adopt it if it does not match the shop floor | You must describe your process clearly at the start |
Neither option is always right. A hybrid also works: keep a package for accounting and build the operations side around it, which leads to the next section. Read the longer comparison and the custom ERP software overview, or look at other trading and distribution builds such as the hardware shop ERP in Gujarat.
Using Tally alongside a roofing sheet ERP in Gujarat
Many Gujarat roofing businesses already use Tally, and their CA often files GST from it. A custom ERP does not have to replace it. The ERP runs quotes, stock, production and dispatch, and a Tally connection can be built to pass sales and purchase vouchers and party ledgers across, so each entry is made once and the accountant keeps the tool they trust.
The drift between systems is the real problem. When an invoice is typed once in a billing tool and again in Tally, the figures can drift apart, and the month-end hunt for the difference takes time. With a connected set-up, the operational entry happens in the ERP and the accounting entry follows from it. How the connection works, and which data moves in which direction, is explained in our guide to Tally integration with a custom ERP.
Two things to keep straight on this page. The working version contains its own double-entry accounts, GST summary and bank reconciliation, so it can run alone. Tally sync, e-invoice and e-way bill are not connected in it; they are scoped in a real project once your GST set-up and accountant’s needs are known. GST treatment in any build is checked by your accountant before use. Some businesses later move accounting fully into the ERP in phases; others never do, and that is fine.
If you are still on spreadsheets, the step before this one is moving from Excel and Tally to one system.
Roofing ERP support from a Surat software company
Yukti AI is a software company at 220, Leonard Square, Yogichowk, Varachha, Surat 395006. For Surat and South Gujarat roofing businesses, the free 30-minute workflow audit can be done at our office, by phone or on WhatsApp. The team works in Hindi, Gujarati and English, which matters when salespeople, store staff and accountants all use the system.
Distance is rarely the obstacle for this kind of software, because an ERP is used in a browser and set up from your product list, rate rules and stock sheet. Being in the same city or state helps with the human parts: a quick meeting to walk through the godown flow, a call in Gujarati with the store supervisor, and support after go-live on WhatsApp.
A good first conversation covers five things: what you make and what you trade, how an inquiry becomes a quote, how coil is bought and issued, how dispatch and billing are done, and how collections are chased. You do not need to prepare anything formal; one real order from the last month is enough. If you run in Surat, Ankleshwar, Bharuch, Vapi, Vadodara or elsewhere in Gujarat, message us on WhatsApp at +91 95862 55455 or use the contact page.
To see more of what we have built before you decide, browse all case studies, read about Yukti AI, or open the AI automation agency in Surat page for the automation side. Each case study states plainly what is live, what is a working version and what is not connected, and this one follows the same rule.
Roofing sheet ERP software: questions manufacturers and traders ask
Explore more
Case study: glass & aluminium ERP
Measurement to quotation for glass, and every aluminium bar and remnant tracked with a cutting planner.
Manufacturing ERP Software
Production, stock, costing, dispatch and billing for factories.
Custom ERP Software in Surat
ERP built around how your South Gujarat business actually runs.
AI ERP
An ERP with an AI layer that reads your data and briefs the owner.
Custom CRM Software
Lead, quotation and follow-up management built around your sales process.
Fabrication ERP Software
Quotes, job cards, material and dispatch for fabrication units.
Case study: fastener trading ERP
Stock, rates, orders and receivables for a fastener trader.
Case study: corrugated box ERP
Box costing, quotations with locked revisions, job cards and GST billing.
Case study: solar structure ERP
A solar mounting structure manufacturer on one system.
Case study: garment ERP
Another manufacturer on one record, from fabric to dealer order.
All case studies
Every Yukti AI build — manufacturing, trading, jewellery and services.
Replace Excel & Tally
Move from sheets and a billing package to one system.
Tally integration with a custom ERP
Keep Tally for the accountant, run operations in the ERP.
AI Agents for Business
Answer stock, quote and dues questions on WhatsApp from live ERP data.
WhatsApp Automation
Quotation sharing, dispatch updates and payment reminders on WhatsApp.
Workflow Automation in Surat
Reminders, alerts and daily reports that run around the ERP.
Voice AI Payment Reminder Calls
Hindi calls that chase overdue customer payments.
Custom ERP Cost Guide
What a custom ERP costs in India and what drives the price.
Summary
Yukti AI, a software company in Surat, built a working ERP, CRM and accounting system for a roofing sheet manufacturer and trader in Ankleshwar, Bharuch district, Gujarat, and showed it to the client as a demo. It follows an order from inquiry to profit: a 10-stage lead pipeline with follow-ups and field visits; quotations checked against a minimum approved rate (cost divided by one minus the margin), margin and role discount limits, with owner approval for exceptions and conversion blocked until approved; orders of type manufacturing, trading or stock with a customer credit-limit check; a stock movement ledger with reservations, five warehouses and unit conversions between sheets, running feet, kilograms, rolls and tonnes; purchase with multi-vendor rate comparison, owner-approved vendor selection, PO, GRN and supplier bill; production jobs with a coil requirement formula from unit weight and wastage, scrap tracking, quality counts and finished-goods costing; challan-controlled dispatch with a nine-point loading checklist; GST invoices with CGST and SGST or IGST for dispatched quantity only; receipts, advances and ageing; double-entry accounts with reversal-only corrections; order-level estimated and actual profit; HR and payroll; 42 reports; and a WhatsApp workspace. The product master and opening stock come from the client’s own godown stock list; customers, vendors, staff, rates and company details are sample data; WhatsApp, GPS, GST filing, e-invoice, e-way bill and bank feeds are not connected, and no savings, results or daily use are claimed. Cost is quoted after a free scoping call. Message Yukti AI on WhatsApp at +91 95862 55455 to start.