How to Manage Customer Specifications That Change by Order

A single product code rarely means a single set of limits. One buyer accepts a water content ceiling that another rejects, and a paint maker wants a tighter Gardner colour value than a trader does. Same grade, different promise.

The order desk usually carries these differences in memory and in old emails, which works while one person handles every account. It fails the week that person is on leave and a repeat order ships against the plant’s default sheet.

The cost arrives late. A rejected tanker, a return with a debit note, a finding at the customer’s supplier audit. Each one traces back to a requirement that existed somewhere but was not in front of the person releasing the order.

Start with the fields the order desk actually argues about. Test parameters need a minimum, a maximum and a test method such as Karl Fischer titration. Then add drum type, fill weight, pallet pattern, label language and the shelf life left on arrival. Keep it to one screen.

Add the document pack. Some customers want a certificate of analysis per batch and others per delivery. Some want the safety data sheet in a named language, with their own product code printed on it.

Link the record to the product, never to a single order. Version it with a start date and record who agreed the change, so older orders keep pointing at the version that applied to them.

The check should run at two moments. When the order is keyed, the screen shows the customer’s packaging and document rules to the person entering it. When a batch is allocated, the system compares the lab result with each limit on the record.

A pass releases the order. A fail does not. The system names the parameter, the limit and the result. The desk can then pick another batch, ask quality for a concession or phone the buyer before the truck is booked.

Allocation is where this pays off. Two batches of one grade can pass for a gasket maker and fail for a pharma buyer, and a plant-wide quality sheet shows neither.

Customers revise specifications by email, often without saying so. Make a revision a task with an owner: someone receives the new sheet, updates the record, sets the start date and signs it off. Nobody edits a live record in place.

Deviations need the same discipline. A concession for one tanker is not a new limit. Record who asked, who approved, which order it covers and why, so it lapses when that order closes.

Review the deviation log every month, because a concession granted five times is really a specification that should be renegotiated with the buyer.

Do not load every account at once. Pick the five that reject most often or audit most closely, then copy their requirements from the last signed agreement and the last three complaint letters.

Run the new check beside the old routine for a month and note every order it holds that the desk would have released. Those are your findings, and they argue for the next ten accounts better than any demo.

This week, pull the most recent rejection note, find the clause that was missed and enter that clause first.