Digital Technologies and Traceable Circular Flows

Introduction

Reverse logistics has traditionally depended on fragmented records, manual inspection, telephone communication and limited visibility after a product leaves the customer. These conditions make it difficult to answer basic operational questions: Where is the returned item? Who owns it? What condition is it in? Is it safe to resell, repair, remanufacture, recycle or dispose of? Has recovered material been incorporated into another product? Digital technologies address these questions by creating connected, time-stamped and increasingly verifiable information flows.

In a circular economy, the physical movement of products and materials must be coordinated with an information flow that records identity, condition, location, ownership, processing history and environmental attributes. Digitalisation does not itself create circularity. A poorly designed digital system can simply make an inefficient linear process faster. The managerial challenge is therefore to select technologies according to the decisions they improve, the evidence they create and the partners they connect.

This chapter examines enterprise resource planning (ERP) systems, returns-management platforms, the Internet of Things (IoT), radio-frequency identification (RFID), digital product passports, blockchain, cloud platforms, robotics and digital twins. It evaluates their contribution to visibility, condition monitoring, automation, traceability and cross-partner coordination, while also addressing data quality, interoperability, cybersecurity, privacy, governance and economic feasibility.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Explain how digital technologies support traceable circular flows.
2. Distinguish the roles of ERP, returns platforms, IoT, RFID, cloud systems and distributed ledgers.
3. Design an information architecture for product return, recovery and recycling processes.
4. Evaluate digital product passports and digital twins for circular-economy applications.
5. Assess the business, ethical, regulatory and cybersecurity risks of digitalisation.
6. Select appropriate technologies using operational, economic and governance criteria.

1. The Information Foundation of Circular Flows

A circular flow includes the reverse movement of used products, components, packaging and materials and their reintegration into productive use. Its information requirements differ from those of a conventional forward sale. Forward logistics usually begins with known products moving toward a known customer. Reverse logistics begins with uncertain quantity, timing, location, ownership and condition.

A useful conceptual distinction is between four information layers:

Traceability is the capability to reconstruct the history and present status of an item, component or material. Visibility is broader: it is the ability to observe relevant flows and exceptions in time to support decisions. A system can provide visibility without complete traceability—for example, showing that a pallet is at a facility without recording its component history. Conversely, a highly traceable system may provide historical records but poor real-time visibility.

Circular traceability should be designed around material and product loops. At minimum, it should connect the following events:

1. Manufacture and initial identification.
2. Distribution and ownership transfer.
3. Use and maintenance.
4. Return initiation and transport.
5. Receipt and inspection.
6. Grading and disposition decision.
7. Recovery operation.
8. Secondary sale or reintegration.
9. End-of-life processing and material recovery.

A central design principle is data minimisation: collect information that supports a defined operational, legal, safety or sustainability decision. Excessive data collection increases cost, privacy exposure and cybersecurity risk without necessarily improving circularity.

2. Enterprise Systems and Returns Platforms

ERP systems

An ERP system integrates core business processes such as purchasing, inventory, finance, sales, manufacturing and human resources. In reverse logistics, the ERP can create return authorisations, update inventory, record credit notes, allocate recovered goods and connect recovery decisions to financial accounting.

However, a conventional ERP is usually transaction-centred rather than condition-centred. It may record that an item was received, but not whether its casing is cracked, its battery has degraded or its firmware is obsolete. ERP systems therefore provide the system of record for commercial and financial events, while specialised systems often capture operational inspection and condition data.

Returns-management platforms

A returns-management or returns-management-authorisation platform coordinates customer initiation, eligibility rules, routing, transportation, inspection, disposition and refund. It may use decision rules such as product category, warranty status, defect code, distance, resale value and facility capacity.

The key performance concept is disposition accuracy: the proportion of returned items assigned to an economically and environmentally appropriate recovery route. A simple measure is:

The measure is dimensionless and assumes that an independently established assessment of the best available disposition exists. It should not be confused with recovery rate, because a correct decision may still result in disposal when no safe recovery option exists.

Integration requirements

ERP and returns platforms should exchange, at minimum:

• product and serial-number master data;
• customer, supplier and ownership information;
• return authorisation and reason codes;
• transport and receiving events;
• inspection and grading results;
• inventory status and financial settlement;
• final disposition and environmental records.

Application programming interfaces (APIs), event-driven integration and common data standards are preferable to repeated manual re-entry. Integration should also preserve data lineage: organisations must be able to determine who created, changed or approved a record.

3. IoT and Condition Monitoring

The Internet of Things connects physical objects, sensors, communication networks, edge devices and software applications. In reverse logistics, IoT is valuable when product condition changes during use, storage or transport and when that condition affects recovery value or safety.

Typical sensors measure temperature, humidity, shock, tilt, pressure, location, energy use, vibration, battery state and opening events. A sensor may transmit continuously, periodically or only when a threshold is exceeded. Edge computing can process data near the item, reducing communication costs and allowing immediate alerts.

A threshold rule can be represented as:

Here, x_t is the measured value at time t, and x_min and x_max are approved lower and upper limits, expressed in the same units as x_t. The rule assumes that the threshold is valid for the product and that sensor calibration and time synchronisation are adequate. A threshold alert is not by itself proof of damage; it is a trigger for investigation.

IoT improves condition-based routing. For example, a returned refrigeration unit with a documented temperature excursion may require safety inspection before resale. A battery pack with a known number of deep-discharge events may be directed to remanufacturing rather than resale. The value of IoT depends on the relationship between the measured variable and the recovery decision. Collecting data that cannot change a decision creates cost without operational value.

Important limitations include sensor failure, calibration drift, battery depletion, connectivity gaps, false alarms and data ownership disputes. Sensor data also creates privacy concerns when products reveal users’ locations, habits or consumption patterns.

4. RFID and Automatic Identification

RFID uses radio waves to identify tagged objects. A reader communicates with a tag, which may be passive, semi-passive or active. Passive tags draw energy from the reader and are generally inexpensive; active tags contain a battery and can support longer range or sensor functions.

RFID differs from barcode identification because it does not always require direct line of sight and can identify multiple tagged items. This can accelerate receiving, sorting, cycle counting and return aggregation. RFID is particularly useful for reusable transport items, garments, appliances, tools, containers and high-value components.

RFID does not automatically provide complete traceability. The system must associate each read with a location, timestamp, reader identity and business event. A tag may also be removed, damaged, duplicated or attached to the wrong item. Therefore, RFID should be treated as an automatic data-capture mechanism, not as a substitute for process control.

A practical RFID design specifies read points such as dispatch, customer return, consolidation, inspection, repair and resale. Read performance should be tested under actual conditions, including metal surfaces, liquids, stacked goods and varying tag orientations.

5. Digital Product Passports

A digital product passport (DPP) is a structured digital record associated with a product, component or material. It can provide information about composition, origin, repair, maintenance, durability, recycled content, hazardous substances, ownership events and end-of-life handling. DPPs are increasingly important because circular-economy regulation and procurement requirements are moving toward product-level evidence.

A DPP should distinguish between:

• immutable or legally controlled attributes, such as serial identity;
• changeable operational attributes, such as repair history;
• role-based information, where different users see different data;
• evidence documents, such as test certificates;
• derived indicators, such as estimated remaining useful life.

The passport should use persistent identifiers and interoperable formats. A QR code, NFC tag or RFID tag may provide physical access to the passport, but the identifier is not the passport itself. The passport may be stored across several systems, provided that its records remain linked and governable.

A DPP supports circular decisions by reducing information asymmetry. A refurbisher can identify material composition and disassembly instructions; a buyer can verify repair history; a recycler can identify hazardous substances; and a regulator can audit claims. Nevertheless, the passport is only as reliable as the data submitted by manufacturers, users, repairers and recyclers. Governance must define who may write data, who verifies it and how corrections are recorded.

6. Blockchain and Distributed Traceability

Blockchain is a form of distributed ledger in which transactions are recorded across a network according to agreed validation rules. It can support a shared history among organisations that do not fully trust one another, especially where a central operator is politically or commercially unacceptable.

Potential applications include chain-of-custody records for recycled materials, proof of repair, ownership transfers, deposit refunds and sustainability claims. A blockchain can make later alteration more difficult, but it does not guarantee that the original data was truthful. This is the “garbage in, immutable garbage out” problem.

Blockchain is appropriate only when several conditions hold:

1. Multiple independent parties need a common record.
2. Participants require tamper-evident history.
3. No trusted central database operator is acceptable or practical.
4. Governance and validation rules can be agreed.
5. The benefits exceed integration, energy, transaction and legal costs.

A permissioned ledger is often more suitable for industrial supply chains than an open, permissionless network because participants and access rights are known. Sensitive information should generally remain off-chain, with the ledger storing hashes, permissions or references. Blockchain should not be selected merely because traceability is required; conventional databases may be faster, cheaper and easier to correct.

7. Cloud Platforms, Data Spaces and Interoperability

Cloud platforms provide scalable computing, storage, analytics and integration services. They allow manufacturers, logistics providers, repairers and recyclers to access shared applications without maintaining all infrastructure independently. Cloud systems also support dashboards, machine-learning services and remote software updates.

However, “cloud” does not automatically mean collaborative. A platform controlled by one organisation may create dependency, unequal bargaining power and data lock-in. Cross-partner coordination requires agreed data models, identity management, access rights, service levels and exit arrangements.

Interoperability has at least three dimensions:

• Technical interoperability: systems can exchange data.
• Semantic interoperability: exchanged data has the same meaning.
• Organisational interoperability: partners agree on responsibilities and processes.

For example, one partner’s “returned” status may mean that a customer has requested a return, while another partner’s status may mean that the item has physically arrived. A shared vocabulary and event definitions are therefore essential.

Data quality can be assessed using dimensions such as accuracy, completeness, timeliness, consistency, uniqueness and validity. A simple completeness measure is:

The numerator and denominator must refer to the same dataset and field definition. A high completeness score does not prove accuracy; a field can be populated with an incorrect value.

8. Robotics, Automation and Artificial Intelligence

Robotics can automate repetitive, hazardous or high-volume activities such as sorting, unloading, disassembly, picking and pallet movement. Collaborative robots may work near people, while autonomous mobile robots transport items between workstations. Vision systems can identify product models, damage, labels and surface defects.

Automation is most successful when product variation is controlled and process data is standardised. Reverse logistics is difficult to automate because returned products differ in age, condition, configuration and packaging. A hybrid model is therefore common: machines perform identification, movement and standardised tests, while trained employees handle ambiguous inspection and safety decisions.

Artificial intelligence can support:

• image-based damage classification;
• demand forecasting for refurbished products;
• estimated remaining useful life;
• anomaly detection in sensor streams;
• routing and disposition recommendation;
• natural-language extraction from service records.

AI recommendations should be treated as decision support unless validated for autonomous use. Models may reproduce historical bias, fail on rare damage types or become inaccurate when products, customers or operating conditions change. Human review is essential for safety-critical decisions, warranty disputes, worker evaluation and customer credit decisions.

9. Digital Twins for Reverse and Circular Operations

A digital twin is a continuously updated digital representation of a physical object, process or system, linked through data and capable of supporting analysis or action. It is more than a static model or dashboard. A meaningful twin has an identified physical referent, a data connection, a defined purpose and a method for updating state.

A product twin may contain serial identity, operating history, sensor readings, repair events, software version, component replacements and predicted remaining life. A facility twin may represent stocks, queues, equipment capacity and material flows. A network twin can simulate alternative return locations, inspection capacities and recovery routes.

Digital twins support scenario analysis. Managers can compare the effect of adding an inspection cell, changing consolidation points or prioritising high-value returns. Yet a twin is only as useful as its assumptions and data. If returned items are missing from the system or condition information is systematically biased, the twin may create false confidence.

10. A Reference Architecture for Traceable Circular Flows

A robust architecture can be organised into five layers:

1. Physical layer: products, components, packaging, sensors, tags and equipment.
2. Capture layer: RFID readers, mobile applications, inspection tools and gateways.
3. Transaction layer: ERP, warehouse management, transport management and returns systems.
4. Trust and data layer: master data, event logs, DPP repositories, permissions and audit trails.
5. Decision layer: dashboards, optimisation, AI, digital twins and management reporting.

The architecture should support a closed event loop. A return event generates an identity record; inspection adds condition data; the disposition decision creates a work order; recovery changes inventory and product status; the final outcome updates the passport and sustainability records.

A useful technology-selection matrix is shown below.

11. Metrics and Economic Evaluation

Technology investment should be assessed through operational and circular outcomes rather than adoption alone. Relevant measures include:

• return-cycle time;
• percentage of returns with complete identity and condition records;
• first-pass inspection accuracy;
• recovery yield;
• resale or reuse rate;
• avoided disposal quantity;
• inventory accuracy;
• unauthorised or lost-item rate;
• partner data latency;
• energy and emissions per recovered unit;
• cost per successfully recovered unit.

Recovery yield can be defined as:

The numerator and denominator must use the same unit, such as kilograms, units or monetary value. If different output categories are combined, the aggregation rule must be stated. A mass-based yield may hide the difference between high-value component recovery and low-value material recovery.

A basic technology business case can use net present value (NPV):

Here, I₀ is the initial investment, B_t is benefit in period t, C_t is operating cost in period t, r is the discount rate per period, and n is the evaluation horizon. Benefits and costs must be measured in the same currency and period. The analysis assumes that cash flows and the discount rate are estimated consistently. It should be supplemented by sensitivity analysis because adoption, recovery volumes and data-quality improvements are uncertain.

A positive NPV does not prove that a project is strategically desirable. Managers must also consider resilience, regulatory compliance, worker safety, supplier dependence, equity and environmental impacts.

12. Illustrative Case: Circular Electronics Recovery Network

Background

The following is an illustrative case. A consumer-electronics manufacturer sells refurbished devices through an extended network of retailers, authorised repairers and recyclers. Returns arrive with incomplete customer descriptions, mixed accessories and uncertain battery condition.

Problem

The manufacturer experienced long inspection queues, incorrect warranty decisions and limited knowledge of which components could be recovered. Retailers used spreadsheets, repairers used separate service systems and the recycler received little information about materials. Management could not reliably distinguish a device awaiting customer authorisation from one physically received at a recovery centre.

Analysis

The organisation mapped the information flow and identified three root causes: inconsistent product identifiers, incompatible event definitions and missing condition data. It also found that a blockchain pilot would not solve the main problem because the immediate need was standardised capture and workflow integration, not a decentralised ledger.

Approach

The company implemented a staged architecture:

1. A returns platform generated a unique return authorisation linked to the device serial number.
2. RFID was used for container-level movement, while serial numbers were scanned at inspection.
3. A mobile inspection application recorded battery health, screen damage, data-erasure confirmation and accessory status.
4. The ERP received approved inventory and credit events through APIs.
5. A product-history service exposed verified repair and component information to authorised repairers and recyclers.
6. A rules-based engine recommended resale, repair, parts harvesting or recycling; employees approved exceptions.
7. A dashboard displayed queue age, missing data and recovery outcomes by partner.

Outcome

The system improved event consistency and reduced manual re-entry. More importantly, it allowed managers to separate process delay from transport delay and to identify partners with persistent data-quality problems. The company postponed a blockchain deployment until a specific cross-party chain-of-custody requirement emerged.

Learning points

The case demonstrates that digital transformation should begin with process and data governance. Identification, event definitions and accountability created more value than adding the most fashionable technology. It also shows that automation should be proportionate: machine-supported recommendations were useful, but safety and ambiguous damage decisions remained subject to human approval.

13. Governance, Ethics and Regulation

Digital circular flows raise several governance issues. Ownership of data must be distinguished from the right to access or use it. A manufacturer may own product-design information, while a repairer creates service data and a customer may have rights over personal data generated during use.

Privacy controls should include purpose limitation, consent or another lawful basis where required, access control, retention limits, encryption and secure deletion. Product data can become personal data when it is linked to an identifiable user, household or location.

Cybersecurity risks include compromised sensors, counterfeit identities, ransomware, unauthorised firmware updates, manipulated recycling claims and denial-of-service attacks. Controls should include strong authentication, least-privilege access, network segmentation, patch management, incident response, backups and supplier security assessments.

Regulatory requirements increasingly concern product durability, repairability, recycled content, hazardous substances, producer responsibility and substantiation of environmental claims. Organisations should maintain auditable evidence and avoid presenting estimated or self-declared data as independently verified fact.

Ethical practice requires attention to workers and smaller partners. Automated grading may disadvantage workers who handle difficult product categories; platform rules may impose costly data requirements on small repairers; and algorithmic scoring may unfairly deny warranty support. Governance should include appeal routes, human oversight, transparent decision rules and consultation with affected stakeholders.

14. Implementation Road Map and Best Practices

A practical implementation sequence is:

1. Define circular objectives and decisions before selecting technology.
2. Map physical, information and financial flows.
3. Establish product, location, partner and event master data.
4. Select a limited pilot with measurable operational value.
5. Integrate systems through documented interfaces.
6. Test data quality, cybersecurity and exception handling.
7. Train workers and partners and define accountability.
8. Measure recovery, service, cost and environmental outcomes.
9. Scale only after process stability is demonstrated.
10. Review the architecture periodically as regulation and technology change.

Best practice is to design for interoperability, reversibility and auditability. Use open or widely supported data formats where feasible, maintain clear ownership of identifiers, separate operational records from analytical copies, and document model assumptions. Digital tools should make the correct circular action easier, not merely create more data.

Contemporary Developments

Current developments include product passports linked to regulatory reporting, edge AI for local condition assessment, computer vision for automated grading, low-power wide-area sensing, robotic disassembly, synthetic data for model testing and carbon-accounting platforms linked to product events. Generative AI may assist employees in searching service histories or drafting inspection summaries, but generated content must be grounded in authorised records and checked before it affects safety, finance or compliance.

The strategic direction is toward interoperable product and material data spaces in which participants retain control over their data while sharing verified attributes for defined purposes. The central challenge is institutional as much as technical: circularity requires commercial incentives, common standards, trustworthy governance and recovery capacity alongside digital infrastructure.

Chapter Summary

Digital technologies make circular flows more visible, measurable and coordinated, but technology alone does not produce circular outcomes. ERP systems provide commercial and financial control; returns platforms coordinate authorisation, routing and disposition; IoT supplies condition information; RFID automates identification; digital product passports preserve product and material history; cloud platforms enable scalable collaboration; blockchain can provide tamper-evident shared records in appropriate multi-party settings; robotics and AI automate selected activities; and digital twins support simulation and decision analysis.

Effective architecture links identity, events, state and decisions across the product life cycle. Its success depends on data quality, interoperability, governance, cybersecurity and human judgement. Organisations should select technologies according to the decisions they improve and evaluate them using recovery, service, financial, environmental and social measures. A staged implementation that begins with process clarity and shared data definitions is generally more reliable than a technology-first approach.

Key Terms

Digital product passport: A structured digital record containing information about a product, component or material across its life cycle.

Digital twin: A data-connected digital representation of a physical object, process or system.

Disposition: The decision regarding reuse, repair, refurbishment, remanufacture, recycling or disposal.

ERP system: Integrated software supporting enterprise transactions such as inventory, finance, purchasing and sales.

Event traceability: The ability to reconstruct significant events affecting an item or material.

IoT: A network of connected physical objects, sensors, communications and software.

Interoperability: The ability of systems and organisations to exchange and correctly interpret information.

Master data: Stable reference data such as product, location, partner and identifier records.

Permissioned blockchain: A distributed ledger in which participation and access are controlled.

RFID: Radio-frequency identification using radio communication between tags and readers.

Reverse logistics: The planning and control of flows from consumption toward recovery, reuse or disposal.

Recovery yield: The proportion of returned input converted into saleable, reusable or otherwise recovered output.

Returns-management platform: Software coordinating return initiation, authorisation, routing, inspection and disposition.

Sensor calibration: The process of comparing and adjusting a sensor against a recognised reference.

Traceability: The capability to follow an item’s identity, history, location and status.

Visibility: The ability to observe relevant flows and exceptions for decision-making.

Data lineage: A record of the origin, transformation and use of data.

Condition monitoring: Systematic observation of variables that indicate product or asset state.

Review Questions

Short Answer Questions

1. Distinguish visibility from traceability in reverse logistics.
2. What are the principal roles of ERP and returns-management platforms?
3. Why does RFID not automatically create complete traceability?
4. Identify two advantages and two limitations of IoT condition monitoring.
5. What is the purpose of a digital product passport?

Long Answer Questions

1. Explain how a reference architecture can connect physical products, capture technologies, enterprise systems and decision tools.
2. Critically evaluate blockchain for cross-partner circular supply-chain traceability.
3. Discuss how digital twins can support capacity planning and recovery-network design.
4. Analyse the governance, privacy and cybersecurity requirements of connected circular flows.
5. Develop a staged implementation plan for a retailer seeking to digitalise its returns process.

Analytical / Application Questions

1. A company records 840 complete and valid inspection records out of 1,000 required records. Calculate completeness using the formula in the chapter and explain what the result does not prove.
2. A manufacturer must choose between RFID, IoT sensors and a digital product passport for a high-value battery-return programme. Recommend a combination and justify it according to identity, condition, traceability and cost requirements.
3. A proposed blockchain project has several partners but a trusted industry association already operates a low-cost shared database. Analyse whether blockchain is justified and identify the evidence required before investment.

Multiple Choice Questions with Answers

Question 1

Which system is primarily designed to coordinate return authorisation, routing, inspection and disposition?

A. Returns-management platform

B. Payroll system

C. Computer-aided design system

D. Customer advertising platform

Correct Answer: A. Returns-management platform

Question 2

What is the main distinction between visibility and traceability?

A. Visibility concerns only finance, while traceability concerns only transport.

B. Visibility supports observation for decisions, while traceability reconstructs history and status.

C. Visibility requires blockchain, while traceability requires RFID.

D. Visibility applies only to forward logistics.

Correct Answer: B. Visibility supports observation for decisions, while traceability reconstructs history and status.

Question 3

An IoT threshold alert should generally be interpreted as:

A. Conclusive proof that a product is damaged

B. A trigger for investigation or action

C. A replacement for sensor calibration

D. A legally verified warranty decision

Correct Answer: B. A trigger for investigation or action

Question 4

Which statement about RFID is correct?

A. It always requires direct line of sight.

B. It automatically proves that every recorded event is correct.

C. It can automate identification but requires process and event controls for traceability.

D. It can operate only on disposable products.

Correct Answer: C. It can automate identification but requires process and event controls for traceability.

Question 5

Which condition most strongly supports the use of a permissioned blockchain?

A. A single organisation wants a private spreadsheet.

B. Multiple known parties need a tamper-evident shared history.

C. No participants need access controls.

D. The data has no ownership or governance concerns.

Correct Answer: B. Multiple known parties need a tamper-evident shared history.

Question 6

Completeness is calculated as 840 valid required fields divided by 1,000 required fields, multiplied by 100. What is the result?

A. 8.4%

B. 40%

C. 84%

D. 184%

Correct Answer: C. 84%

Question 7

Which layer includes ERP, warehouse management and returns systems in the reference architecture?

A. Physical layer

B. Capture layer

C. Transaction layer

D. Decision layer

Correct Answer: C. Transaction layer

Question 8

Why is human oversight important in AI-supported reverse logistics?

A. AI cannot process any operational data.

B. Models may fail on rare conditions or create unsafe or biased decisions.

C. Human oversight eliminates the need for data quality.

D. AI systems are legally prohibited in all logistics activities.

Correct Answer: B. Models may fail on rare conditions or create unsafe or biased decisions.

Question 9

What is a digital twin?

A. A static product brochure

B. A data-connected representation of a physical object, process or system

C. A duplicate warehouse worker identity

D. A barcode printed twice

Correct Answer: B. A data-connected representation of a physical object, process or system

Question 10

Which is an example of semantic interoperability?

A. Two systems use different cables.

B. Two systems exchange data but assign different meanings to “returned.”

C. Two organisations use the same definition for a return event.

D. A sensor operates without a battery.

Correct Answer: C. Two organisations use the same definition for a return event.