A spreadsheet says an ECM was purchased for a loader. Six months later, another buyer treats that row as proof of the controller currently fitted. The conclusion may be wrong: the item could still be in stock, have been returned or have gone to another approved job.
Give each event its own status
Quoted, ordered, received and installed describe different events. Keep them separate in the component record. A purchase date should not become an installation date simply because the latter has not been entered.
Link the order to the intended machine, then record the actual destination when it is known. If stock is reassigned, preserve the original request and the later assignment. Do not overwrite the first machine name and leave the transaction history unexplained.
The same distinction applies to displays and sensors. A delivered carton is evidence of receipt, not evidence of application approval or completed installation. Use the relevant receiving and equipment records to establish those later events.
Keep the requested reference and delivered reference visible
Record what was ordered and what arrived as separate fields. If a supported substitute was accepted, retain the confirmation and its conditions. A difference should have an explanation, not disappear because someone replaced the original number in the spreadsheet.
Where the component has an individual serial number, keep it separate from the part number. The part reference describes the item type; the serial helps trace the particular unit. Do not invent a serial value for an item that has no readable one.
Attach receipt photographs to the receipt event. Photos supplied during quotation may depict a sample rather than the delivered unit. Clear file labels make it possible to tell those evidence sets apart long after the conversation with the supplier has ended.
Installation needs its own confirmation
Use the record from the responsible installation process to associate the unit with the machine. Identify the event date and the source of confirmation. A planned workshop booking is not the same as a completed installation.
Keep any application preparation or configuration record distinct from the hardware delivery. An invoice for a module does not establish what later work was performed. Record the responsible source without claiming checks that were not actually documented.
If the component was never installed, leave that state visible. There is no benefit in making a history appear complete when the evidence stops at receipt. The unresolved state helps the stock team locate the item and prevents a later buyer from treating it as an installed reference.
Removal is not automatically a failure finding
A removed unit may be awaiting assessment, returned under an agreed process or retained for another documented reason. Record that reason as reported. Do not label every removed electronic component defective merely because it is no longer on the machine.
Keep a removed unit's identity connected to its previous installation event. If it is placed in storage, note that location separately. This preserves the distinction between a loose item with a known history and one whose origin has not been established.
Make corrections without erasing the trail
If a number was transcribed incorrectly, save the correction with its source. Retain the original observation or document where appropriate. Silent edits make it difficult to tell whether the item changed or only the record changed.
For repeat orders, start from the latest confirmed application requirement, not simply the last invoice line. Check for a documented change or an unresolved return. A previous purchase can be a useful lead without being current approval to buy the same item again.
The guide to equipment logs deals with operating observations, while used-machine handover records covers incoming history. Transaction states answer another question: where did this particular part go, and which event actually confirms it?
A small record with clear states is easier to trust than a long list of unexplained part numbers. Keep the machine, component and event linked, and leave unknown information marked as unknown until it can be supported.
