Notes for owners · Sales management
Why foundries lose repeat business: a register for rejections, delays and replies
Why a foundry's regular buyers quietly cut its schedule after a rejection or a late lot, and how a one-page register of every problem and reply becomes a tool for winning the next order.
The GullySales team · Updated 17 Oct 2026 · 6 min read
On this page
- What the buyer remembers when the next schedule is split
- Why the foundry forgets what the buyer remembers
- The register: one row per problem
- Reading the register before the buyer does
- For example: a Sangli foundry and a shrinking schedule
- A sheet or a CRM, and what neither can fix
- Fill the first rows from your debit notes
The pump maker that has taken your casings for years releases its next schedule, and your share is smaller. Nobody calls to say why. Look for the reason in the last few problems. A lot of casings showed blowholes after machining. A dispatch slipped while the furnace was relined. A rejection email waited three weeks for a reply. Repeat casting orders depend on how the last problem was handled. Keep one register of every rejection, delay and complaint, with the date you replied and what you changed, and take it to the buyer before the next schedule is decided.
What the buyer remembers when the next schedule is split
The defects that hurt most are found in the buyer's machine shop, not at the gate. The boring bar opens up a blowhole or a sand inclusion. A hard spot breaks an insert. By then the machine hours are spent, and some buyers debit you for those hours as well as the casting.
His quality engineer remembers two things about it: how many came back, and how long you took to answer. If the buyer keeps a vendor rating, both go into it.
A delay you warned the buyer about is an inconvenience. One discovered when the truck did not arrive is a planning failure in the buyer's own plant.
Why the foundry forgets what the buyer remembers
Each problem reaches a foundry through a different door. The debit note goes to accounts, the WhatsApp photo of the blowhole to the supervisor, the call about the late lot to the owner. The rejected castings come back weeks later on a challan and sit in a corner of the fettling shop.
Nobody joins these up. So the foundry cannot answer the question the buyer is silently asking: is this supplier getting better or worse?
The register: one row per problem
Keep it as a shared sheet. The example column is one illustrative row.
| Column | What to write | Example |
|---|---|---|
| Raised on | The date the buyer first told you, by any route | Day 1 |
| Customer and part | Buyer, part number and pattern number | Pump maker, casing, pattern 112 |
| Problem | Rejection, short supply, late dispatch or wrong papers | Rejection |
| Found where | Incoming inspection, after machining, at assembly or in the field | After machining |
| Quantity | Pieces affected, out of the lot | 18 of 300 |
| Cause | The defect and its root, in shop words | Shrinkage at the flange boss, riser too small |
| First reply | When, and who answered the buyer | Day 2, quality head, by phone |
| Written answer | When the cause and action note went, and to whom | Day 6, to the quality engineer, purchase copied |
| Change made | What is different on the floor now | Riser enlarged, first casting of each lot cut and checked |
| Debit | Value of the debit note, and whether you accepted it | Accepted after seeing the pieces |
| Closed | When the buyer confirmed it, or "open" | After the next lot came through clean |
| Next schedule | Did the next release grow, hold or shrink? | Held |
The last column turns a quality log into a sales tool. Enough rows show which problems, answered which way, cost you volume.
Reading the register before the buyer does
Sort it by pattern, not by customer. When one pattern appears in three rows, the pattern or its method is the problem. Fix it before you quote that buyer anything new.
Give every row a written answer within a week of the complaint. A row still waiting after seven days goes to the owner's desk, whoever was handling it.
Before any review meeting or visit, print that customer's rows, closed ones included, and take them in. Go through them yourself before the buyer raises them: what happened, why, and what changed. A supplier that brings its own failures to the table turns the meeting from blame into evidence.
Close a buyer's open rows before you show the buyer the register, and do not use it to contest every debit.
For example: a Sangli foundry and a shrinking schedule
Imagine a grey iron foundry in Kupwad MIDC, Sangli, pouring pump casings for a pump maker in Pune. The details are illustrative.
Over two releases, the schedule for the main casing fell to about half. The owner assumed a rival had undercut the foundry and cut the rate by about 4 per cent. The buyer accepted it, and the quantity stayed where it was.
Then the owner built the register from that customer's debit notes and returned-casting challans. There were four rejections in a year. Three were on the same casing pattern, all shrinkage at the same boss, and each had been answered by sending replacement castings and nothing else. When the owner asked to see the buyer's notes, two read "repeat defect, no corrective action".
The foundry enlarged the riser on that pattern and began cutting the first casting of every lot. The owner sent the four rows, the cause and the change to the quality engineer and purchase, and asked for a review. There the owner walked through the rows before anyone raised them. Over the next releases the casing quantity climbed back to roughly three quarters of its old level, not all of it. The rate cut stayed, which was the price of guessing instead of looking.
A sheet or a CRM, and what neither can fix
A shared spreadsheet is enough if one person handles every complaint. A CRM, set up through CRM implementation and customisation, earns its place when several people raise complaints or the register should sit beside each customer's quotations.
The register will not save an account lost to a foundry with machining in-house, or a buyer cutting the supplier list for reasons of its own. And if the rows show your rejection rate is the real problem, the cure is method and metallurgy, not a better reply.
If the register shows that most rows came in the first lot of a new buyer, start with getting the first repeat order. Agreeing who answers what is the job of complaint and escalation management. See also casting and foundry.
Fill the first rows from your debit notes
Ask accounts for every debit note from your three largest buyers. Ask stores for every returned-casting challan. Enter each as a row and fill in what you can remember; the blank columns are the habits to fix first. If you want the register set up and the reply routine agreed with your team, tell us what you need.
