Material traceability for contractors

Material traceability means being able to answer, from records rather than memory, where any material came from and where it went: which supplier, on which purchase order, received on which goods receipt, as which batch, with what QC decision, issued to which zone, on what date, by whom. For a contractor who fabricates and installs, that chain has seven hops, and it breaks at whichever hop nobody wrote down. The practice is simple to state and hard to keep: one identity for the material from request to receipt, one record per hop, and no movement without a record. Below is what to record at each hop, why the store and the site so often disagree, and a checklist to audit your own store against.

The chain, hop by hop

1 · Supplier → purchase order

The supplier is a record, not a name typed on the order. Each order line refers to a catalogue item by its ID. If the line is a free-typed description, the trail has already forked: the receipt will have to guess which item it belongs to.

2 · Purchase order → goods receipt

Receive against the order line, never against a fresh description. Record ordered, previously received and receiving now, so the balance is arithmetic rather than memory. Refuse over-receipt. Keep the supplier's delivery note number on the receipt.

3 · Goods receipt → batch

One receipt line becomes one batch with its own identity — your receipt reference — plus the supplier's batch or heat number for the material. A batch with no supplier identity cannot be matched to a supplier problem later.

4 · Batch → QC decision

Record the inspector, the decision and the quantities: approved, quarantined, returned. A split must add up to the batch. A return to the supplier carries the return note number and the reason. Nothing leaves quarantine without a second recorded decision.

5 · Batch → project → zone

Reservation and issue happen by zone: which batch, how many, for which request, by whom, on which date. Material moved between projects is a recorded act with an approver, not a forklift trip.

6 · Issue → production

The issue is what allows fabrication to begin. Record it as an event that unblocks the zone; do not assume the floor has what the store thinks it sent.

7 · Production → installation

The honest hop. Most contractors — and most software — stop tracing at the zone. Linking a specific batch to a specific installed panel needs unit-level identity through fabrication, which few workshops keep. Know where your chain ends and say so.

"Site says it never arrived. Store says it was issued."

Both are telling the truth. An issue is a store act; an arrival is a site act; between them is a truck and nobody's record. The material was issued to the zone on paper, loaded (or not), delivered (or partly), and received by a foreman who signed a note that stayed in the cab. The fix is a delivery record with the receiver's name from the signed note, and a site-receipt step that can only be recorded against a delivery that was actually dispatched. When both exist, the question answers itself in one screen.

Self-audit checklist

Pick one batch received last month. Can you name its supplier, order line, receipt, QC decision and the zones it was issued to without asking anyone?
Does every order line carry a catalogue item ID, or a description someone typed?
Can your store receive 300 of an ordered 500 and show the balance without a spreadsheet?
Can a QC reject be split — part approved, part quarantined — and does the quarantine physically stop an issue?
Is material moved between projects recorded with an approver and a date, or remembered?
Does the site receipt name the person who signed, and refuse a receipt for a delivery never dispatched?
Where does your chain end — at the zone, or at the installed unit? Is that written down anywhere?

How Muthari OS handles this. Suppliers are a register and each purchase order links to one. The catalogue item ID travels from the purchase order to the goods receipt, so the receipt does not re-derive what was ordered. Receipts hold ordered / previously received / receiving now per line, refuse over-receipt, and mint one stock batch per line, with the supplier's batch or heat number recorded on the line. QC is a real gate: only approved batches can be issued; a batch can be split into approved and quarantined quantities that must add up; a return to the supplier needs a return note and an NCR reference, and it reopens the order balance. Every movement — receipt, QC, reservation, issue, borrow, return — is a row in an append-only ledger with one writer and the actor's name. Issues record the zone, the request and the source batches with cost, and unblock fabrication for that zone. Material borrowed between projects is approved and ledgered; ownership and cost stay with the lending project. Dispatch is by delivery note with a QR on the zone; site receipt refuses anything not dispatched and records the receiver's name from the signed note. The honest limit: Muthari links a batch to the zone it was issued to, not to the installed panel, and the tracing view walks outward from a zone rather than forward from a batch.

Book a free demo See the whole system →