Starting point
Reuse should compare whole equipment, repair, component harvesting and material recovery as distinct alternatives. The decision requires authorisation, testing appropriate to the use, traceability and a market. Harvesting means removing components for reuse; removing an intact part does not demonstrate that it is fit for supply.
Compare routes without counting the same revenue twice
Equipment may have value as a functioning unit, a source of components or material. The choice requires comparing mutually compatible outcomes. If memory and storage are sold separately, the remainder should no longer be valued as the same complete equipment in the original quote. Removal may reduce one route's value to make another viable.
First define the constraints: ownership, contracts, data, locks, brand use and buyer requirements. Then examine condition and demand. A functional component without an identifiable application or customer may sit idle and consume space. The assessment should consider time to sale and potential market changes, alongside the advertised price.
Distinguish preliminary assessment from functionality testing
Switching on equipment, observing its appearance or checking its configuration helps assess reuse potential. These activities do not necessarily demonstrate all relevant functions. SERI makes this distinction explicit in its R2v3 guidance: assessment of potential and functionality testing are stages with different scopes. The reference comes from the R2 programme and does not mean that Circuvia or any operator is certified. [1]
The buyer needs to know what was checked and under which conditions. A memory module may require a different plan from a power supply or logic board. Define functions, acceptance criteria, instruments and records with the competent team. The commercial description should match the level actually demonstrated, avoiding treating “removed from equipment” as synonymous with “tested and approved”.
Choose components based on the market and testability
Identify the part number, revision, compatibility and application. Similar-looking parts may not be interchangeable, and compatibility must be confirmed before promising supply. Check whether proportionate means exist to test, handle and package the component without introducing damage. A lack of testing capability may require a specialist partner or another route.
The project also needs limits on which items will be removed. Dismantling everything indiscriminately may raise costs and create slow-moving stock. Prioritise families with demand, known specifications and a demonstrable preparation process. Record the reasons for selection so the team can repeat the decision when a batch with a different composition arrives.
Structure approval by item or defined batch
Identification should link the component to its origin and relevant results. Where each item is tested, retain this link through dispatch. Where a characteristic can be assessed by sampling, the plan must justify its use and limitations; an accepted sample does not justify indiscriminate generalisation to every function of every part.
Decisions for preparing reusable components
Workstream
- Identity
- Approval question
Which part, revision and application are being supplied?
- Supporting evidence
Part number, origin and configuration
- Functionality
- Approval question
Which functions were checked?
- Supporting evidence
Procedure and results
- Data
- Approval question
Is there storage or information requiring treatment?
- Supporting evidence
Relevant treatment and acceptance
- Condition
- Approval question
Is there damage or are there limitations that must be disclosed?
- Supporting evidence
Inspection and defined grading
- Delivery
- Approval question
How will condition be preserved until the buyer receives it?
- Supporting evidence
Packaging, identification and receipt
Preparation of electrically sensitive items or items with specific risks must follow the corresponding technical procedures.
Calculate cost per accepted component
Hypothetical example: removing and sorting 100 components costs R$ 1,000, and testing costs R$ 500. If 60 are accepted, this R$ 1,500 represents R$ 25 per accepted component, before packaging, transport, taxes, returns and other expenses. Dividing only by 100 would yield R$ 15 and hide the effect of rejection.
If acceptance falls to 40 items at the same total cost, this portion rises to R$ 37.50 per accepted item. The example shows why process yield affects the decision. Include the donor equipment's opportunity cost and management of rejected items. Potential revenue from remaining fractions should be estimated separately and confirmed when a deal is made.
Preserve data security and configuration
Media and devices with storage must follow the applicable sanitisation programme before release. Removing a component changes its location but does not complete data treatment. Link the item's identification to the procedure, outcome and approval. Equipment with management or account locks also requires an authorised resolution before sale.
After a repair, record the final configuration and replaced parts. A test performed before the intervention may not represent the delivered product. The article on ITAD, sanitisation and chain of custody explores this workstream. Controls must allow functional approval, data treatment and commercial authorisation to be distinguished, because each answers a different question.
Include returns in programme feasibility
SERI's guidance on reuse plans includes defining tests and managing returns. This reference reinforces that the commercial cycle continues after the sale. The agreement should state condition, limitations, acceptance criteria and the dispute procedure, while respecting applicable obligations. [2]
Record the reason for every return: incompatibility, reproduced failure, transport damage or description discrepancy. A return does not automatically prove a component defect, but should not be dismissed without analysis. Compare behaviour across batches and procedures. If a pattern emerges, identify the potentially affected group and review release with the responsible technical professionals.
Use the pilot to decide on scale
Before promising recurring volumes, measure the supply of donor equipment, the proportion of eligible components, acceptance, productivity and actual demand. An exceptionally homogeneous batch may give an exaggerated impression of continuity. Define how the operation will respond to changes in model, condition and availability of the items underpinning the project.
The trade-in and ITAD service can connect inventory, assessment and the structuring of reuse and recovery routes. Expansion makes sense when quality, supply and the market can keep pace with scale. A component that is approved, identified and accepted by the buyer provides a more useful basis for assessment than the simple number of parts removed.
Sources and references
References accessed on 30 September 2026. The numbering in the text indicates the concepts supported by each source.
Circuvia corporate content to support project discussions. Methods, acceptance criteria and applicable requirements are defined within the scope of each operation.
