Genuine, Used, Refurbished or Compatible Industrial Parts
Updated · Written by HAM
Both offers say “genuine”. One is unused old stock; the other is a repaired used unit. They are not like-for-like offers. Manufacturer identity, present condition and suitability for your machine need separate evidence before the prices can be compared.
Condition words are proposals, not common test standards
One seller may use refurbished for cleaning and a power-on check; another may replace wear components, repair boards, load-test functions, record measurements, and issue its own warranty. New can mean current authorised stock, old unopened surplus, or merely unused according to the seller. Compatible may describe physical fit, electrical similarity, functional equivalence, or only a catalogue cross-reference. The buyer cannot compare these offers until each word becomes observable evidence and responsibility.
Begin with the consequence of failure. Is this a shelf spare for a noncritical station, a component required to restart a bottleneck, or part of a safety-related function? What downtime, quality, personnel, environmental, cyber, or regulatory exposure follows a wrong or early failure? Higher consequence raises the evidence, approval, validation, and contingency threshold.
Three questions that “genuine” does not settle
| What to examine | Example information | What to establish next |
|---|---|---|
| Maker | Claimed original manufacturer | Traceable origin tied to the offered unit |
| Condition | Unused stock or repaired used item | Storage, repair, test and warranty evidence |
| Suitability | Same complete order code | Revision, settings and surrounding equipment |
An authentic or unused item has not necessarily passed the checks your application needs. Tie test records to the serial number of the unit that will actually be shipped.
Traceability answers different questions from authenticity
Traceability connects the offered unit to a source, identity, records, and transaction. It may support an authenticity assessment, but a serial photograph alone does not prove genuine manufacture, authorised channel, condition, or ownership. Ask who supplied the item, what records can be shared, whether packaging and labels belong to the offered unit, and whether identifiers may be checked through an appropriate manufacturer or channel process.
Keep claims attributed: seller-stated, document-supported, manufacturer-confirmed, buyer-inspected, or independently tested. Do not collapse them into verified genuine unless the evidence and verifier support that conclusion. If the necessary assurance cannot be reached for the application, the state is unresolved—not genuine by appearance or counterfeit by suspicion.
OMRON’s E3JM lineup includes a transmitter/receiver table following a through-beam design change. It is a concrete example of old and redesigned combinations having different operating outcomes within a family. Use the relevant product’s combination data; do not apply this table to other sensors or servos.
Check which functions were tested and under what conditions
A power-on light does not test I/O, communication, analogue accuracy, encoder feedback, load behaviour, intermittent faults, thermal stability, memory retention, protective functions, or safety performance. Ask what functions were exercised, under what conditions, for how long, with which equipment and pass criteria. Define untested functions as open risk rather than assuming a broad working statement covers them.
For a repaired or refurbished part, request incoming fault, work performed, parts replaced, configuration or firmware handling, final test, and whether calibration or manufacturer procedures apply. For used parts, record known history and removal reason, but do not invent remaining life from age. For compatible parts, the test plan must cover system interfaces and behaviour changed by substitution.
Condition-evidence matrix
Ask every seller to define its category. Evidence matters more than the heading used in a listing.
| Offer category | Evidence to request | Residual questions |
|---|---|---|
| Genuine new through traceable channel | Exact code, packaging and identifiers, channel record, storage and warranty basis | Is the sales channel authorised for this destination, and does the warranty cover the intended use there? |
| New old stock or surplus | Item images, sealed or opened state, date or lot, source, storage, inspection and warranty | How may age, storage, battery, seals, capacitors, firmware or support affect use? |
| Used | Source, operating history if known, removal reason, inspection, serial evidence and functional test | What life remains and which failure modes were not tested? |
| Refurbished or repaired | Incoming condition, work scope, replaced parts, facility, test method, results, warranty and return | Did the process address likely failure modes and configuration? |
| Compatible or third-party | Maker, exact cross-reference, specifications, interfaces, approvals, test evidence and limits | Who accepts system change, validation and future-support risk? |
Make the test report belong to the offered item
A report is useful only when its scope, method, result, and item linkage can be understood.
- Item linkageRequired
- Full code, serial, photographs, date and tester.
- Connects the report to the unit being sold.
- Incoming conditionRequired
- Damage, contamination, seals, missing parts, errors and repair signs.
- Shows what the work started with.
- Work performedRequired
- Cleaning, repair, replacement, firmware handling, calibration or none.
- Defines refurbished or repaired.
- Test method and limitsRequired
- Functions, load, duration, equipment and pass criteria.
- Reveals what tested does and does not cover.
- Results and exceptionsRequired
- Measured results, failed checks, untested functions and deviations.
- A pass statement without limits hides risk.
- Generic certificateAvoid
- Fully tested with no serial, method, criteria or result.
- Does not establish this unit’s condition.
Warranty matters only when the claim path works
Read who gives the warranty, its duration and start event, covered failure, exclusions, remedy, return authorisation, freight allocation, test burden, and response if no fault is found. A replacement-only warranty may not cover downtime, engineering labour, customs, or absence of another unit. Check whether the seller can respond across borders and accept evidence the buyer can practically collect.
Agree incoming inspection before shipment. Photograph packaging and identifiers, check seals and damage, reconcile code and accessories, retain documents, and quarantine the item until required checks are complete. If installation is needed for acceptance, define who authorises it, the safe test environment, deadline, and rollback. Do not discover after failure that applying power voided the remedy.
Lower evidence is a different decision, not a cheaper equivalent
A traceable new unit, tested used unit, and third-party compatible unit should not be ranked in one price column as though only condition differs. Used adds history and test-scope uncertainty. Compatible adds manufacturer, interface, validation, documentation, and future-support questions. Either may be chosen for a bounded use, but approval, contingency, and total cost must reflect its residual risk.
Tell HAM the part code and the condition you will consider: new, used, refurbished or compatible. We can ask Japanese sellers for traceability, test and warranty evidence for the offered unit. Check that evidence and the unit’s suitability for the application before buying.
Frequently asked questions
- Does unopened packaging prove a part is new and genuine?
- No. Packaging is one piece of evidence. Source, identifiers, storage, age, channel, item linkage, and an appropriate verification path still matter.
- What should a refurbished-part test report contain?
- It should identify the unit, incoming condition, work, replaced components, test method and limits, results, exceptions, date, tester, and warranty basis.
- When can a compatible part be acceptable?
- When its maker and specifications are known, system differences are reviewed, limits and approvals are understood, validation and rollback are planned, and the responsible engineer accepts the risk.