Foundations of Retail Technology Systems

Introduction

Retail technology systems are the coordinated technologies, people, processes, data resources and governance arrangements through which a retailer creates, communicates, sells and fulfils value. They include familiar systems such as point-of-sale (POS) terminals and e-commerce websites, but also less visible capabilities: product-information management, inventory visibility, customer identity, payments, workforce scheduling, supply-chain planning, analytics, cybersecurity and integration platforms.

Retail technology is therefore not synonymous with hardware or software. A technically sophisticated platform can fail if store employees cannot use it, product data are inaccurate, processes conflict across channels, or managers do not trust the information produced. Conversely, a relatively simple system can create substantial value when it is aligned with the operating model and customer proposition.

The contemporary retailer operates in an environment characterised by multiple channels, rapid fulfilment expectations, mobile interaction, marketplace competition, privacy regulation and increasingly automated decision-making. The central managerial question is not simply, “Which technology should be purchased?” It is, “How should technology, organisation and information be designed together to support a distinctive retail strategy?”

Learning Objectives

After studying this chapter, you should be able to:

1. Define fundamental retail technology terminology and distinguish systems, platforms, applications, data and infrastructure.
2. Explain the evolution of retail technology from transaction automation to connected, data-enabled retail.
3. Analyse the relationships among people, processes, data and platforms across different retail formats.
4. Apply strategic and socio-technical frameworks to evaluate retail technology decisions.
5. Identify managerial, ethical, security and governance implications of retail systems.
6. Diagnose technology problems and propose a coherent improvement approach.

1. The Retail Technology System as a Socio-Technical System

A retail technology system is best understood as a socio-technical system: an arrangement in which technical components and human arrangements jointly produce outcomes. The technical elements may include devices, networks, databases, applications, application programming interfaces (APIs), cloud services and algorithms. The social elements include employees, customers, suppliers, managers, policies, incentives, skills and organisational routines.

A system has at least five analytically distinct layers:

These layers are interdependent. For example, an omnichannel “buy online, pick up in store” service requires an accurate inventory record, an order-management application, store processes for reservation and handover, network connectivity, employee training and customer communication. Removing any one of these elements weakens the service.

A useful distinction is between data, information and knowledge. Data are recorded observations or representations, such as a barcode, transaction value or timestamp. Information is data interpreted in context, such as “SKU 217 has 14 saleable units in Store A.” Knowledge is the capability to use information in a decision, such as recognising that apparent availability is unreliable because eight units are damaged or reserved.

Retail systems also involve different kinds of truth. A system of record is the authoritative source for a particular data domain. For example, a product-information management system may be authoritative for product descriptions, while a finance system is authoritative for posted accounting entries. A system of engagement supports interactions with customers or employees, such as an app or service desk. A system of insight analyses data to support decisions. Confusing these roles can create duplicate records, inconsistent prices and accountability gaps.

2. Core Terminology

Retail formats and channels

A retail format is the structural form through which retailing is conducted, such as a supermarket, department store, specialty shop, convenience store, discount store, warehouse club, marketplace or direct-to-consumer website. A channel is a route through which a customer discovers, orders, receives or returns merchandise. Channels may be physical, digital or assisted by employees.

Multichannel retailing means that a retailer operates more than one channel, but the channels may be managed separately. Omnichannel retailing seeks to provide a coordinated customer experience across channels, with shared information and connected processes. Omnichannel does not mean that every channel must be identical; it means that relevant capabilities, information and service commitments are coherently coordinated.

Operational systems

A point-of-sale system records sales, tenders, taxes, discounts, refunds and often customer identification. A barcode scanner is an input device; the POS application is the transaction-processing software; payment processing may be performed by an integrated payment service; and the sales record may be transferred to finance, inventory and analytics systems.

An enterprise resource planning (ERP) system integrates major internal processes such as purchasing, finance, inventory, human resources and sometimes manufacturing. A warehouse management system (WMS) controls or supports receiving, put-away, storage, picking, packing and dispatch. A transportation management system (TMS) supports transport planning, carrier selection, routing and shipment visibility.

A customer relationship management (CRM) system manages customer interactions and profiles. Customer data platforms (CDPs) generally seek to unify customer data from multiple sources for activation and analysis, although their capabilities and boundaries vary by vendor. A content management system (CMS) manages digital content, while a product-information management (PIM) system governs attributes, descriptions, media and classifications for products.

Architecture and integration

A platform is a reusable technological foundation on which multiple applications, services or interactions can operate. A commerce platform may provide catalogues, carts, promotions, checkout and order functions. A platform is not automatically superior to a standalone application: its value depends on fit, governance, extensibility, cost and operational reliability.

An API is a defined interface through which software components request or exchange functions and data. Event-driven integration communicates that something has happened—for example, “Order accepted” or “Inventory adjusted”—so that subscribed systems can respond. Batch integration transfers data at scheduled intervals. Real-time integration can reduce delay, but it may increase complexity, cost and failure-propagation risk.

Cloud computing provides on-demand access to shared computing resources, often with elastic capacity and usage-based pricing. Software as a service (SaaS) delivers an application managed by a provider. Edge computing processes some data near the location where it is generated, which can help when latency or connectivity is important, such as in stores or distribution centres.

Data and performance terms

A SKU (stock-keeping unit) identifies a specific sellable item, usually at a particular product, size, colour or configuration. A barcode is a machine-readable representation of an identifier; it is not necessarily the same as the SKU, although systems may associate them. Master data describe relatively stable business entities such as products, locations, suppliers and customers. Transactional data record events such as sales, receipts, transfers and returns.

Data quality includes accuracy, completeness, consistency, timeliness, validity and uniqueness. Data latency is the delay between an event occurring and its availability for use. Inventory visibility is the ability to know where inventory is, in what condition, and whether it is available for a particular promise. “On-hand” inventory is not always “available-to-promise” inventory because stock may be reserved, damaged, in transit or subject to safety rules.

3. Evolution of Retail Technology

Retail technology has evolved through overlapping stages rather than a simple linear sequence.

Stage 1: Mechanisation and transaction automation

Early retail systems mechanised pricing, cash handling and sales recording. The adoption of electronic cash registers and barcode scanning reduced manual entry and improved transaction speed. The immediate objective was operational efficiency and control: recording sales, reducing pricing errors and supporting end-of-day reconciliation.

Stage 2: Enterprise integration

Retailers then connected sales, purchasing, inventory, finance and distribution. The objective shifted from recording isolated transactions to coordinating the enterprise. Data warehouses and management information systems enabled reporting on sales, margins, stock turns and category performance. However, integration was often constrained by proprietary systems, duplicated databases and nightly batch processing.

Stage 3: Digital commerce and customer interaction

Websites, mobile devices, digital marketing and electronic payments created new customer touchpoints. The retailer had to manage digital catalogues, online search, delivery options, returns and digital service. The customer journey became less predictable: discovery might occur on social media, purchase on a mobile application and fulfilment from a store.

Stage 4: Omnichannel and real-time coordination

Retailers increasingly connected stores, websites, marketplaces, fulfilment centres and customer-service channels. Order-management systems became important because they allocate orders to locations while considering inventory, delivery promises, capacity and cost. Store inventory could become fulfilment inventory, but this also introduced operational tensions: picking online orders may disrupt store work, and inaccurate stock records can create failed promises.

Stage 5: Intelligent and autonomous assistance

Machine learning is now used for demand forecasting, recommendations, fraud detection, price analysis, image recognition and workforce planning. Internet-of-things devices, computer vision, electronic shelf labels, robotics and cashierless experiments extend the system into the physical environment. These technologies can improve responsiveness, but they do not eliminate the need for process design, human oversight, data governance or accountability.

The strategic lesson is that each stage adds capabilities while preserving older dependencies. A retailer cannot obtain reliable artificial-intelligence outputs from poorly governed product or transaction data. Nor can a mobile application compensate for an unreliable returns process.

4. A Framework for Analysing Retail Technology

A practical framework for postgraduate analysis is the four-part alignment model: people, processes, data and platforms. These elements should be considered together with strategy and governance.

People

People include customers, store associates, contact-centre agents, managers, IT specialists, suppliers and logistics partners. Their roles differ in authority, digital literacy, incentives and exposure to risk. A new handheld replenishment application may appear efficient to a head office but may fail if store associates lack time, connectivity or training. User experience is therefore an operational concern, not merely a design preference.

Important people-related questions include:

• Who performs each activity and who is accountable for its outcome?
• What skills, training and support are required?
• Does the system reduce or increase cognitive and administrative burden?
• Are incentives aligned with enterprise outcomes or only local targets?
• How are customers and employees affected by monitoring or automation?

Processes

A process is a sequence of activities that transforms inputs into an outcome. Retail processes commonly cross organisational boundaries. A return, for example, may involve a customer, store associate, POS, payment service, inventory record, fraud rule, finance ledger and reverse-logistics operation.

Process analysis should identify the “happy path” and exceptions. Retail systems often work well under normal conditions but fail when an item is damaged, a payment is reversed, a delivery is late, or stock differs from the record. Mature design treats exceptions as normal operational events rather than rare anomalies.

Data

Data should be analysed through its lifecycle: creation, validation, storage, use, sharing, retention and deletion. Data ownership should not be confused with data stewardship. A merchandising team may own the business definition of a product attribute, while a data-governance team establishes standards and an IT team operates the technical repository.

A simple conceptual expression helps explain the value of information:

This is not a numerical law; it is a managerial model. It states that information creates value only when it is relevant to the decision, sufficiently accurate, available at the required time, accessible to authorised users and understandable in context. A highly accurate report delivered after a replenishment decision may have less practical value than a slightly less precise report delivered on time.

Platforms

Platforms provide capabilities, standards and integration points. Their evaluation should include functional fit, reliability, scalability, interoperability, security, total cost of ownership, vendor dependence and ability to support future change. A platform architecture should distinguish stable core capabilities from rapidly changing customer experiences. This can reduce the risk that every innovation requires modification of the entire transaction backbone.

Strategy and governance

Technology must support the retailer’s value proposition. A discount retailer may prioritise low transaction cost, process standardisation and high availability. A luxury retailer may prioritise clienteling, rich product information and relationship continuity. A fast-fashion retailer may emphasise demand sensing, short replenishment cycles and supply-chain responsiveness. The same technology can therefore have different strategic value in different formats.

Governance defines decision rights, standards and controls. It answers questions such as who may change a price, approve an integration, access customer data, override an inventory quantity or deploy an algorithm. Without governance, decentralised innovation can produce duplication and inconsistent customer promises.

5. Retail Formats and Technology Priorities

These priorities are not deterministic. A supermarket may use advanced personalisation, and a specialty retailer may operate a large marketplace. The table identifies typical operating emphases rather than fixed technological identities.

6. Strategic Role of Retail Technology

The strategic role of technology can be examined through four questions.

Efficiency

Technology can reduce transaction time, manual reconciliation, picking effort and avoidable errors. Efficiency benefits should be measured across the whole process. Automating one step may merely transfer work to another department or to the customer.

Effectiveness and experience

Technology can improve product discovery, availability, personalisation, accessibility and service recovery. A recommendation engine is strategically useful only if recommendations are relevant, explainable enough for the context and connected to products that can actually be supplied.

Resilience and agility

Integrated systems can help retailers respond to disruptions, supplier delays, demand shocks and channel shifts. Yet tightly coupled systems may also create systemic vulnerability: an outage in identity, payments or integration can interrupt many channels simultaneously. Resilience therefore requires redundancy, fallback procedures, monitoring and tested recovery.

Innovation and differentiation

Data and platforms can support new services such as subscriptions, retail media, marketplace models, digital receipts, social commerce and dynamic fulfilment. Technology is a potential source of differentiation, but it is rarely defensible by itself because competitors can often purchase similar software. Advantage more often arises from distinctive data, process capability, organisational learning and trusted relationships.

A useful strategic test is whether an initiative is aligned with the retailer’s capabilities and proposition. The resource-based view suggests that sustained advantage is more likely when resources are valuable, rare, difficult to imitate and organisationally embedded. A generic cloud POS may be valuable but not rare; a retailer’s integrated knowledge of local demand, service routines and supplier relationships may be more difficult to imitate.

7. Applied Case: Northstar Home, an Illustrative Case

Background

Northstar Home is an illustrative mid-sized home-goods retailer with 38 stores and a growing website. It offers delivery, click-and-collect and store returns for online purchases. Its stores use a legacy POS system, while the website, warehouse and loyalty programme use separate applications.

Problem

Customers frequently receive inaccurate click-and-collect promises. The website shows stock that store employees cannot locate. Store associates maintain informal spreadsheets for reserved items, and the contact centre cannot see the latest order status. Managers respond by holding additional safety stock, which increases markdowns and working capital.

Analysis

The problem is not simply “old software.” Analysis using the four-part model identifies several interacting causes:

• People: store employees have no clearly assigned responsibility for reservation accuracy; incentives focus on sales rather than fulfilment reliability.
• Processes: receiving, cycle counting, reservation, picking and cancellation procedures differ by store.
• Data: on-hand quantities are updated after sales but not consistently after damage, display use, transfers or reservations.
• Platforms: the website receives periodic inventory updates; there is no integrated order-management layer to distinguish on-hand from available-to-promise stock.
• Governance: no owner is accountable for the definition and quality of “available stock.”

Approach and solution

Northstar first defines inventory states: on-hand, reserved, damaged, in-transit and available-to-promise. It assigns business ownership for these definitions and establishes standard store procedures. It then introduces an order-management capability that receives inventory events, applies reservation rules and communicates order status to the website and contact centre.

The technology rollout is deliberately staged. Six stores pilot the process, using handheld devices for receiving and cycle counting. Staff are trained in exception handling rather than only in the ideal workflow. The pilot measures failed collection promises, cancellation rates, time spent locating stock, inventory adjustments and customer complaints. Integration monitoring alerts the support team when events are delayed or rejected.

Outcome

After the pilot, Northstar expands the approach while retaining manual fallback procedures for network or system outages. The principal improvement does not come from the platform alone. It comes from aligning inventory definitions, employee responsibilities, standard processes and integration controls. The retailer also discovers that some products should not be offered for immediate collection because their display or damage risk makes availability unreliable.

Learning points

1. Omnichannel capability is an operating-model change, not merely a website feature.
2. Inventory accuracy is a socio-technical outcome.
3. A precise customer promise requires both data quality and fulfilment discipline.
4. Pilot measurement should include employee workload, exception rates and customer outcomes.
5. System boundaries and ownership must be explicit before integration is implemented.

8. Risks, Ethics and Governance

Privacy and consent

Retailers collect identity, location, purchase, browsing and inferred-preference data. Privacy governance should follow principles such as purpose limitation, data minimisation, transparency, access control, retention discipline and appropriate consent or other lawful basis. Personalisation should not become an excuse for indiscriminate surveillance.

Legal requirements vary by jurisdiction, but internationally relevant frameworks include data-protection laws, consumer-protection rules, payment-security requirements and accessibility obligations. Compliance is a minimum standard; ethical practice also asks whether a use is fair, expected and proportionate.

Cybersecurity and operational continuity

Retailers are attractive targets because they process payments, personal information and commercially sensitive data. Controls should include least-privilege access, strong authentication, secure configuration, network segmentation where appropriate, patching, logging, vendor assessment, incident response and tested backups. Availability is especially important during peak trading periods.

Algorithmic fairness and explainability

Algorithms may influence recommendations, credit decisions, fraud screening, prices, employee schedules or product visibility. Bias can enter through historical data, proxy variables, incomplete representation or objectives that reward conversion without considering fairness. Governance should define acceptable use, test performance across relevant groups, monitor drift and provide human review or appeal where decisions materially affect people.

Surveillance and labour

Computer vision, productivity dashboards and location tracking may improve safety or operations, but they can also intensify work, undermine dignity or create inaccurate performance judgments. Employers should define legitimate purposes, limit access, communicate practices and assess proportionality. Employee participation often improves both legitimacy and system quality.

Vendor and platform dependence

Outsourcing does not outsource accountability. Contracts should address security, service levels, data portability, audit rights, subcontractors, exit arrangements and incident notification. Retailers should avoid assuming that a popular platform automatically meets their process, regulatory or resilience requirements.

9. Contemporary Developments and Best Practices

Several developments are shaping retail technology systems:

• Composable commerce: retailers assemble modular capabilities rather than adopting one monolithic suite. This can increase flexibility but also raises integration and governance demands.
• Unified commerce: transaction, customer, inventory and order capabilities are coordinated across channels, ideally through shared services and consistent definitions.
• Generative AI: retailers use it for content drafting, service assistance, search, merchandising support and software development. Human review, source validation, intellectual-property controls and protection of confidential data remain essential.
• Computer vision and sensor systems: these can support shelf availability, loss prevention and automated checkout, but introduce privacy, accuracy and accessibility issues.
• Digital product information: richer attributes, sustainability data, provenance and repair information can improve both customer decision-making and regulatory reporting.
• Retail media: retailers use first-party customer and transaction data to sell advertising opportunities. This creates revenue potential but requires separation of commercial incentives from privacy and customer trust.

Best practice is less about adopting every new tool than about building disciplined capabilities:

1. Begin with a customer or operating problem and define measurable outcomes.
2. Map the end-to-end process, including exceptions and handoffs.
3. Establish data definitions, ownership, quality rules and retention requirements.
4. Design security and privacy into the system from the beginning.
5. Prefer open standards and documented interfaces where appropriate.
6. Pilot in representative settings and measure total process impact.
7. Train users, involve frontline employees and provide support during transition.
8. Monitor reliability, data quality, adoption, business outcomes and unintended effects.
9. Maintain fallback procedures and test continuity.
10. Review architecture periodically as strategy, regulation and customer behaviour change.

Limitations of Technology-Centred Thinking

Technology can reveal information and automate routines, but it cannot resolve ambiguous strategy, poor leadership or conflicting objectives by itself. A retailer may purchase advanced forecasting while buyers continue to override recommendations without recording reasons. It may implement a CRM while customers receive irrelevant communications because consent and identity resolution are weak. It may create a dashboard that measures activity rather than value.

There are also trade-offs. Real-time data can improve responsiveness but increase integration complexity. Personalisation can improve relevance but increase privacy risk. Automation can lower operating cost but reduce human discretion or create new exception work. Standardisation can improve control but suppress local knowledge. Good managerial analysis makes these trade-offs explicit rather than presenting technology as universally beneficial.

Chapter Summary

Retail technology systems are socio-technical arrangements composed of people, processes, data, applications, platforms, infrastructure and governance. Core concepts include POS, ERP, WMS, CRM, PIM, APIs, cloud services, master data, transactional data, inventory visibility and omnichannel retailing. Retail technology has evolved from transaction automation through enterprise integration and digital commerce toward real-time, intelligent and increasingly autonomous systems.

The four-part alignment model—people, processes, data and platforms—provides a practical way to analyse technology across retail formats. Strategic value may arise through efficiency, customer experience, resilience and innovation, but technology is valuable only when aligned with the retailer’s proposition and operating capabilities. The Northstar Home case demonstrates that an omnichannel problem involving stock promises cannot be solved by software alone; it requires clear data definitions, accountable people, consistent processes and integrated platforms.

Privacy, cybersecurity, algorithmic fairness, employee dignity, vendor dependence and continuity are central governance concerns. Effective practice begins with a business problem, designs the process and data model carefully, involves users, pilots changes, measures outcomes and maintains human and managerial accountability.

Key Terms

API: A defined interface enabling software components to request or exchange functions and data.

Available-to-promise: Inventory quantity that can legitimately be committed to a customer under specified rules.

Cloud computing: On-demand access to shared computing resources, often delivered through networks.

Customer relationship management (CRM): Systems and practices for managing customer interactions and information.

Data governance: Decision rights, standards, controls and responsibilities governing data.

Data latency: The delay between an event occurring and its data becoming available for use.

Enterprise resource planning (ERP): Integrated software supporting major organisational processes such as finance, purchasing and inventory.

Event-driven integration: Integration in which a system communicates that an event has occurred so other systems can respond.

Inventory visibility: The ability to know the location, condition and usable availability of inventory.

Master data: Data describing relatively stable business entities such as products, suppliers and locations.

Omnichannel retailing: Coordinated retailing across channels using connected information and processes.

Platform: A reusable technical foundation supporting multiple applications, services or interactions.

Point of sale (POS): A system that records retail transactions, tenders, discounts, refunds and related data.

Product-information management (PIM): Governance and management of product attributes, descriptions, classifications and media.

Retail format: The structural form of retail operation, such as supermarket, marketplace or specialty store.

Socio-technical system: A system in which technical and social elements jointly produce outcomes.

System of record: The authoritative source for a defined category of organisational data.

Transactional data: Data recording business events such as sales, receipts, transfers and returns.

Warehouse management system (WMS): Software supporting warehouse receiving, storage, picking, packing and dispatch.

Review Questions

Short Answer Questions

1. What is meant by a socio-technical retail technology system?
2. Distinguish data, information and knowledge using a retail example.
3. What is the difference between multichannel and omnichannel retailing?
4. Define master data and transactional data.
5. Why is available-to-promise inventory different from on-hand inventory?

Long Answer Questions

1. Explain the evolution of retail technology from transaction automation to intelligent retail, including the capabilities and risks associated with each stage.
2. Discuss the four-part alignment model of people, processes, data and platforms. Why must these elements be analysed together?
3. Compare the technology priorities of a supermarket, a specialty retailer and an online marketplace.
4. Evaluate the strategic role of retail technology using efficiency, experience, resilience and innovation as analytical dimensions.
5. Discuss the principal privacy, cybersecurity, algorithmic and labour-governance issues associated with contemporary retail systems.

Analytical / Application Questions

1. A retailer’s website shows stock as available, but stores frequently cannot locate items selected for collection. Diagnose the problem using the people–processes–data–platforms framework and recommend a staged intervention.
2. A luxury retailer is considering an AI recommendation engine that uses purchase history, browsing behaviour and location data. Assess the strategic benefits, data requirements, ethical risks and governance controls that should precede implementation.
3. A discount retailer must choose between a highly customisable modular architecture and a standardised integrated suite. Develop a decision framework that considers strategic fit, total cost, resilience, skills, vendor dependence and future change.

Multiple Choice Questions with Answers

Question 1

Which statement best describes a retail technology system?

A. A collection of hardware used only at checkout

B. A coordinated socio-technical arrangement of people, processes, data and technology

C. A database containing only customer records

D. A cloud subscription purchased by the IT department

Correct Answer: B. A coordinated socio-technical arrangement of people, processes, data and technology

Question 2

Which system is most directly associated with receiving, storing, picking and packing goods in a warehouse?

A. CRM

B. PIM

C. WMS

D. CMS

Correct Answer: C. WMS

Question 3

What distinguishes omnichannel retailing from merely multichannel retailing?

A. Omnichannel uses only physical stores

B. Omnichannel eliminates independent customer channels

C. Omnichannel coordinates relevant information and processes across channels

D. Omnichannel requires every channel to offer exactly the same service

Correct Answer: C. Omnichannel coordinates relevant information and processes across channels

Question 4

Which is an example of master data?

A. A single customer’s payment authorisation

B. A record of yesterday’s store sale

C. A product’s standard description and dimensions

D. A warehouse picking event

Correct Answer: C. A product’s standard description and dimensions

Question 5

Why may on-hand inventory exceed available-to-promise inventory?

A. Some on-hand units may be reserved, damaged or otherwise unavailable

B. Available-to-promise always includes goods in transit

C. On-hand inventory excludes physical stock

D. Available-to-promise is calculated only from customer reviews

Correct Answer: A. Some on-hand units may be reserved, damaged or otherwise unavailable

Question 6

What is the principal purpose of an API in retail architecture?

A. To replace all business processes

B. To define how software components exchange functions or data

C. To physically transport products between stores

D. To guarantee that data are accurate

Correct Answer: B. To define how software components exchange functions or data

Question 7

A retailer introduces a new fulfilment platform but does not change store procedures or employee responsibilities. Which analytical problem is most evident?

A. Failure to align technology with people and processes

B. Excessive product variety

C. Overuse of barcode standards

D. Insufficient warehouse floor space only

Correct Answer: A. Failure to align technology with people and processes

Question 8

Which principle is most consistent with responsible retail data governance?

A. Collect all possible data indefinitely

B. Allow every employee unrestricted access

C. Use data for defined purposes with appropriate access and retention controls

D. Treat vendor responsibility as a substitute for retailer accountability

Correct Answer: C. Use data for defined purposes with appropriate access and retention controls

Question 9

Which development most directly supports modular assembly of commerce capabilities?

A. Composable commerce

B. Manual cash reconciliation

C. A paper-based stock ledger

D. A single isolated cash register

Correct Answer: A. Composable commerce

Question 10

Why should a retailer pilot an AI or omnichannel system before broad deployment?

A. Pilots eliminate the need for governance

B. Pilots reveal process, data, adoption and unintended-effect issues in a controlled setting

C. Pilots guarantee a positive return on investment

D. Pilots make cybersecurity controls unnecessary

Correct Answer: B. Pilots reveal process, data, adoption and unintended-effect issues in a controlled setting