Material and lot control

The certificate is per heat. Your system records the order

A service center can fill one line of your order from three heats without doing anything wrong. If your identifier is the purchase order, you merge heats on the rack and never see it, until a customer asks which bar a part came from. We build the identifier that is created once at receipt and survives being cut in half.

Free lot label generator Talk about your material flow

The problem

The certificate is issued per heat. Your system records material per order

That one mismatch is where most cert trails are lost, and it is invisible until a customer asks.

A mill test certificate belongs to a heat of steel, not to your purchase order. A service center can fill a single line item from two or three heats without doing anything wrong, and without that being obvious on the packing slip.

So if the unique identifier in your system is the PO, the order line, or the delivery, you can merge heats on the rack and never see it happen. Months later a customer asks for the cert covering a particular part, and you have two certificates, one job, and no way to say which bar the part came out of.

At that point you are reconstructing from memory and dates. Sometimes that works. Sometimes you reship, or you eat the parts.

Where it breaks

Five specific places, not five general worries

Receiving records the order, not the heatEverything downstream inherits this. If heat is not captured at goods in, no amount of discipline on the floor can put it back, because the information was in the paperwork and the paperwork has been filed.

The drop goes back on the rack bareYou cut from the labelled end, the remnant returns to the rack with nothing on it, and the next job that uses it is untraceable. This is the single most common gap, and the fix is as dumb as deciding which end the label goes on.

The scan gets skipped on a busy dayAny step that depends on someone remembering will be skipped the week you most need it. If the only two options at the saw are scan the right bar or stop working, people will scan the nearest bar that looks right, which is worse than no data.

The certificate is a PDF in a folderNamed after the supplier and the month, found by opening five of them. It exists, it is correct, and it is not attached to anything, so producing it on request is a person's afternoon rather than a lookup.

Nothing stops an untraceable part shippingTraceability that is a good habit is traceability you do not have. Until the system refuses to produce the packing slip, you will find the gaps at audit rather than at the loading dock.

What correct looks like

One identifier, created once, carried all the way

Five steps. The shape matters more than the software.

Step	What happens
Goods in	Each bar, plate or coil becomes its own lot, tied to its heat number. The certificate is scanned once and attached to the heat, not filed by supplier.
On the rack	The lot is labelled so it survives coolant and handling, on the end that stays on the rack. No allocation to a job yet.
At the saw	The cut creates the link: this lot, this job. Two scans, before the blade drops. Remnant returns as the same lot, still labelled.
Through the job	The lot travels with the routing, so inspection reads it off the job rather than asking the operator what he remembers.
At shipping	No lot attached means no packing slip and no invoice. The certificate prints from the job in one click because it was attached at step one.

Note what is deliberately not in that sequence: the office deciding in advance which bar the floor will use. Let the floor pick the material and have the cut record the choice. Allocating specific bars to specific jobs at receipt looks tidier on a screen and falls apart the first time somebody takes the convenient bar.

What we build

Usually an addition to what you already run

Heat and lot capture at receiptA field, a scan of the certificate, and a label that prints. Done by whoever already handles the paperwork, in about the same time it takes now.

Lot to job linking where the cut happensOn whatever is already by the saw. A tablet, a wedge scanner into an existing screen, a phone. The constraint is tap count, not features.

Split and remnant handlingA lot that is cut keeps its parentage, so a remnant used eight months later still resolves to the same certificate. This is the part people usually have to bolt on afterwards.

A blocking rule at shippingConfigurable, because not everything you make needs it, and absolute for the part numbers that do.

The gap reportLots on hand with no heat recorded, and jobs shipped this week with no lot attached. Five minutes a week, read while the bar and the memory are still in the building.

One click certificate packJob number in, the certificates covering every lot consumed out, as one PDF. This is the thing customers judge you on and it should not involve a folder.

Typically three to eight weeks, and your ERP keeps doing everything it does today. We are adding one attribute, making it survive being cut in half, and refusing to let parts leave without it.

Being straight with you

What this is and is not

We are not auditors and we do not write your quality manual. ISO 9001 clause 8.5.2 requires you to identify outputs and control that identification where traceability is a requirement, and AS9100 tightens it. What the clause does not do is tell you where in your shop the trail actually breaks. That is an operational question, and it is the one we answer.

Paper works, at a size. One job, one bar, one traveler and a legible handwritten heat number is a perfectly good system and plenty of shops should keep it. The point this stops being true is when the same fact has to exist in two places at once: on the rack, on the traveler, in the office and on the certificate pack. That is the threshold, not headcount.

If you get heat level traceability right, country of melt comes almost free. It arrives on the same certificate, per heat, and it is becoming its own problem on the customs side. Worth building the one identifier with both uses in mind rather than doing this twice.

FAQ

Common questions

Our ERP already has a lot number field. Is that not enough?

It depends what the lot is keyed to. If one lot can span several heats, the field records the delivery rather than the material, and the certificate trail is already broken. The test is simple: pick a shipped job from six months ago and try to produce the certificate for the specific bar it came from. If that takes more than a minute, the field is not doing the job.

How do we handle remnants and drops?

The remnant stays the same lot it always was, with its parentage recorded, so a piece used eight months later still resolves to the original certificate. Two practical details matter more than the software: put the label on the end that stays on the rack, and use a paint pen rather than a sticker on anything that lives in coolant.

What stops operators skipping the scan when they are busy?

Making it a condition of getting paid rather than a condition of being conscientious. No lot attached, no packing slip, no invoice. Alongside that, always give them a way to record that the label was unreadable, which flags the job for someone in the office. If the only options are scan correctly or stop work, you will get wrong scans instead of missing ones.

Is this the same thing as country of melt reporting?

They share the same source document and the same identifier, but they are different jobs. Traceability answers which bar this part came from. Country of melt and pour answers where that bar's steel was melted, which is what Section 232 entry reporting now wants per line. Getting heat level traceability in place first makes the second one mostly a matter of recording one more field from the same certificate.

Which ERPs can this be added to?

We have built this kind of lot attribute and roll up alongside Epicor, Infor CloudSuite and SyteLine, Business Central, NetSuite, Sage and QuickBooks based setups, and alongside systems shops have written themselves. The pattern barely changes. What changes is how the system lets you extend the lot record and get data back out.

Keep exploring

Lot label generatorFree, prints in your browser
Country of melt reportingThe same certificate, the customs side
ERP integrationGetting the attribute in and the data out

Next step

Pick a job you shipped six months ago.

Try to produce the certificate for the specific bar it came from. If that takes more than a minute, there is a gap worth half an hour of our time on a call.

Email usmail@voliom.com