The world of supply chains is transforming, driven by the rapid adoption of IoT devices – projected to hit 24 billion by 2030. But here’s the challenge: without unified standards, these devices can’t communicate effectively, leading to inefficiencies, security risks, and data silos. The solution? IoT standards that enable seamless communication, scalability, and security across global networks.
Key Takeaways:
- IoT Standards Matter: They ensure devices from different manufacturers work together, prevent data silos, and improve security.
- Top Protocols: MQTT, CoAP, LoRaWAN, and HTTP each serve specific use cases, from real-time telemetry to long-range tracking.
- Business Benefits: Standardized IoT systems reduce costs, speed up processes, and help [leaders] (https://ceohangout.com/an-effective-leader/leaders/) improve decision-making with reliable data.
- Compliance Is Key: Regulations like ETSI EN 303 645 ensure security and market access, while frameworks like EPCIS 2.0 enhance tracking for sensitive goods.
Quick Comparison of IoT Protocols:
| Protocol | Best Use Case | Power Usage | Range | Security |
|---|---|---|---|---|
| MQTT | Real-time telemetry | Low | Network-dependent | TLS |
| CoAP | Constrained devices | Very Low | Network-dependent | DTLS |
| LoRaWAN | Remote tracking | Extremely Low | 2–15 km | AES-128 |
| HTTP | Cloud APIs/FOTA | Medium-High | Network-dependent | TLS |
IoT standards aren’t just technical frameworks – they’re the backbone of modern supply chains, enabling efficiency, security, and global interoperability. Dive into the article for detailed insights on protocols, compliance, and real-world applications.
Living up to the hype: Lessons from IoT supply chain wins
sbb-itb-2fdc177
Key IoT Standards and Protocols
IoT Protocol Comparison Guide for Supply Chain Applications
Picking the right protocol is a game-changer when addressing interoperability challenges in global supply chains.
Overview of MQTT, CoAP, LoRaWAN, and HTTP
When it comes to supply chain IoT deployments, four protocols stand out, each designed for specific operational needs:
- MQTT (Message Queuing Telemetry Transport): This protocol relies on a publish–subscribe model, which separates producers from consumers. It’s incredibly scalable – HiveMQ demonstrated it could manage 200 million concurrent connections on AWS. As of 2024, it’s been adopted by 56% of developers.
- CoAP (Constrained Application Protocol): CoAP is built for resource-constrained devices with limited RAM and CPU. It follows a REST-like request–response model over UDP, which reduces connection overhead and cuts transmission power by 67% compared to MQTT. Its support for UDP multicast also allows simultaneous commands to multiple devices.
- LoRaWAN (Long Range Wide Area Network): This protocol is perfect for long-range, low-power communication over unlicensed frequencies, with a range of 2–15 km. For instance, in Gold Coast, Australia, a city-wide deployment using LoRaWAN identified leaks for 10% of commercial customers, saving over AU$1 million annually. It’s ideal for battery-operated sensors that need to last for years without a recharge.
- HTTP/HTTPS: The go-to protocol for cloud API integrations and firmware-over-the-air (FOTA) updates. While HTTP/HTTPS is widely used and familiar to developers, it has significant overhead – its headers range from 700 to over 1,000 bytes compared to MQTT’s 2 bytes. It also consumes 40% more power, making it better suited for cloud APIs rather than battery-powered sensors.
Here’s a quick comparison of these protocols to help you decide which one fits your needs best.
Protocol Comparison Table
| Criterion | MQTT 5.0 | CoAP (RFC 7252) | HTTP/1.1-2 | LoRaWAN |
|---|---|---|---|---|
| Architecture | Publish-Subscribe | Request-Response | Request-Response | Star-of-Stars |
| Transport | TCP | UDP | TCP | RF (Unlicensed) |
| Min. Header | 2 bytes | 4 bytes | ~700 bytes | Variable (Low) |
| Power Usage | Low (0.989 mWh) | Very Low (0.929 mWh) | Medium-High (1.384 mWh) | Extremely Low |
| Range | Network-dependent | Network-dependent | Network-dependent | Long (2–15 km) |
| Security | TLS (Port 8883) | DTLS (Port 5684) | TLS (Port 443) | AES-128 |
| Scalability | Very High (Millions) | High (Subnets) | High (Horizontal) | High (Regional) |
| Best Use Case | Real-time telemetry | Constrained devices | Cloud APIs/FOTA | Remote asset tracking |
When to Use Each Protocol
- MQTT: Ideal for real-time event streaming from thousands of devices to multiple consumers, especially in environments with firewalls or NAT.
- CoAP: Best for devices with severe constraints, such as those with limited RAM (around 10 KB) or where every milliwatt counts.
- HTTP: Perfect for cloud-to-cloud integrations or scenarios where developer speed takes priority over protocol efficiency.
- LoRaWAN: A great choice for outdoor sensors tracking assets over large areas, especially when devices need to run for years on a single battery.
Interoperability Challenges and Solutions
The Problem of Fragmented Standards
In supply chain IoT, the real hurdle often isn’t the technology itself but ensuring devices can communicate effectively. A variety of protocols – such as Wi‑Fi, Zigbee, Z‑Wave, Bluetooth, LoRaWAN, and NB‑IoT – makes integration tricky because each device speaks its own "language". For example, a warehouse sensor using Zigbee might not easily communicate with a fleet tracker running on LoRaWAN, forcing businesses to invest in complex and expensive solutions to bridge these gaps.
The numbers paint a daunting picture: 80% of IoT initiatives fail due to interoperability issues. About 64% of organizations face major integration challenges, and 30% of projects ultimately fail because devices just don’t work together. Many manufacturers design their products to function exclusively within their ecosystems, creating vendor lock-in that can inflate costs by as much as 40%. On top of that, inconsistent data formats – like JSON versus XML – require custom translations, delaying deployment timelines.
Security concerns add another layer of complexity. Devices running on different firmware and protocols often come with varying security standards, leaving systems vulnerable. In fact, 70% of IoT devices have known security weaknesses, and more than half of companies (52%) report cyberattacks through their IoT or operational technology systems. Even when devices are connected, semantic differences – like one system recording "77°F" while another logs "25°C" – can cause misinterpretations that throw off automated processes.
These issues highlight the need for a comprehensive approach to achieve true interoperability.
How to Achieve Interoperability
Overcoming these challenges requires a mix of strategies aimed at improving device communication. One key solution is deploying IoT gateways paired with middleware platforms – such as Spring Cloud Gateway, Apache Kafka, or Eclipse IoT. These tools help translate data between protocols, reducing security risks by up to 40% and simplifying integration.
Adopting an API-first approach with open standards like MQTT, CoAP, and HTTP can also address vendor lock-in, potentially cutting costs by up to 35% compared to proprietary systems. Additionally, emerging protocols like Matter – supported by major players like Apple, Google, and Amazon – are gaining traction as universal standards that enable cross-brand compatibility.
To ensure a smooth transition, many organizations (75% of leaders) recommend a phased rollout. This involves pilot testing in real-world scenarios to identify and resolve protocol issues early. Modular architectures also play a crucial role, allowing businesses to easily add or replace devices as technology evolves. Lastly, it’s vital to align chosen standards with regional regulations like GDPR and industry-specific requirements such as ISO/IEC 30141.
Global Regulatory Frameworks for IoT Standards
ETSI EN 303 645
ETSI EN 303 645 has become a key benchmark for consumer IoT security worldwide. It outlines 13 high-level security provisions along with data protection requirements, offering manufacturers flexibility in implementation while ensuring specific outcomes are achieved. This results-driven approach accommodates a wide range of devices, from simple sensors to complex IoT gateways.
The standard isn’t limited to physical devices – it also covers related services like mobile apps and cloud back-end systems that support IoT products. Meeting ETSI EN 303 645 requirements provides a "presumption of conformity" with major regulations such as the EU Radio Equipment Directive (RED) and the UK Product Security and Telecommunications Infrastructure (PSTI) regime.
This framework has been adopted in several regions, including the United Kingdom, Singapore, Finland, and Australia. As of August 1, 2025, the EU made cybersecurity requirements under the RED Delegated Act mandatory. Additionally, ETSI adopted the current version (V3.1.3) on September 11, 2024. Manufacturers can confirm compliance using ETSI TS 103 701, a document that specifies the test cases needed to verify each security provision.
"ETSI EN 303 645 acts as the global security passport for your consumer IoT devices." – CCLAB
For global supply chains, ensuring regulatory compliance is essential to maintaining market access and securing consumer trust.
Meeting Compliance Requirements in Global Markets
Regulatory compliance is one of the biggest challenges in IoT deployment. For global supply chains, meeting these standards is critical for legal market entry. Falling short can lead to certification delays lasting 6–12 months, driving up costs and pushing back market launches.
The growing focus on secure-by-design principles means manufacturers must build security into products from the start, rather than addressing it later. Steps like assigning unique credentials to devices (instead of using universal default passwords), establishing a public vulnerability disclosure policy, and clearly defining end-of-life dates for security updates are now essential.
Another critical tool for compliance is maintaining a Software Bill of Materials (SBOM). This document tracks all hardware and software components – such as firmware, chipsets, and sensors – enabling manufacturers to meet regulatory demands and monitor components across intricate supply chains. The consequences of non-compliance can be severe: devices may be banned from sale, GDPR violations could result in hefty fines, and retailers might cancel orders if security issues arise.
"Compliance is not a barrier. It is a competitive advantage that signals quality and reliability to your buyers." – CCLAB
Case Studies: IoT Standards in Action
Amazon’s Supply Chain Transformation
Amazon has revolutionized its supply chain operations with IoT technology, relying on MQTT to ensure seamless communication. Using AWS IoT Core, the company connects millions of devices within its fulfillment network, enabling secure and low-latency data transfer between sensors and the cloud.
In 2021, Amazon introduced Amazon Monitron, deploying 104,000 sensors across 192 sites in Europe. These sensors monitor over 34,000 pieces of equipment, such as motors, pumps, and conveyor belts, by collecting vibration and temperature data through MQTT. This data is used to identify anomalies, allowing for predictive maintenance. The results? A 69% reduction in unplanned downtime and an estimated savings of $37.83 million in operational costs. This demonstrates how unified IoT standards can drive efficiency and cost savings.
"Cloud computing has been transformative in the logistics industry, and together with AI, machine learning, and the smart sensors found in the internet of things (IoT), has been nothing short of revolutionary in the way the fulfillment sector operates." – Alessandra Antonelli, Country Manager, Amazon Web Services, Italy
Amazon also uses IoT for real-time inventory tracking. At the AWS Executive Briefing Center in Seattle, a system called "Illuminate" tracks beverage inventory across 16 meeting rooms. It employs IO-Link industrial smart sensors and MQTT protocols, saving hospitality staff four hours of labor per day by eliminating manual checks.
These examples show how IoT standards can significantly enhance operational efficiency, a trend mirrored in other industries.
Cold Chain Tracking for Temperature-Sensitive Products
Maintaining proper conditions for temperature-sensitive goods is critical, and EPCIS 2.0 (Electronic Product Code Information Services) has emerged as the global standard for real-time sensor data sharing. Ratified in June 2022 and adopted as ISO/IEC 19987:2024, it provides a framework for tracking and managing sensitive products across supply chains.
Walmart has integrated Wiliot’s battery-free "IoT Pixels", which use Bluetooth Low Energy (BLE) standards, into its U.S. supply chain. As of early 2026, this system operates in 500 locations, monitoring tens of millions of pallets. These sensors track temperature and movement, sending automatic alerts when perishable goods are left unrefrigerated or misrouted. Walmart plans to scale this system to all 4,600 U.S. stores and 40+ distribution centers, improving food safety compliance and reducing waste. This is especially crucial given that 30% of food produced for human consumption is wasted, much of it due to temperature issues during transit.
"We’re bringing intelligence to the things themselves, so the supply chain can think and act in real time." – Nick Matthews, Vice President of Solutions and Architecture, Wiliot
The pharmaceutical industry faces even tighter constraints, often requiring temperatures to remain within ±0.9°F (±0.5°C). EPCIS 2.0’s sensorReport feature embeds data on temperature, humidity, and light exposure directly into supply chain events, creating a machine-readable record. This ensures compliance with regulatory audits and enables proactive measures to protect product integrity.
These examples underline how IoT standards are reshaping diverse supply chains, from food to pharmaceuticals, by improving safety, efficiency, and accountability.
Future Trends in IoT Standards for Supply Chains
2026 and Beyond: Evolving Standards
The SGP.32 standard is transforming how supply chain managers handle global connectivity. Unlike its predecessor, which relied on SMS-based communication, SGP.32 adopts an IP-native architecture compatible with NB-IoT and LTE-M networks. This upgrade allows enterprises to switch connectivity providers post-deployment without the need for hardware changes, offering unprecedented flexibility.
According to Kaleido Intelligence, around 50 million SGP.32-compliant eSIMs will be managed globally by 2027, with commercial adoption expected to surge in the second half of 2026. Central to this standard are two key components:
- eIM (eSIM IoT Remote Manager): A platform for managing profile lifecycles across entire device fleets.
- IPA (IoT Profile Assistant): A tool enabling seamless communication between the eIM and the SIM on each device.
"Connectivity strategy is no longer operational detail. It is a board-level decision." – IoT Now Magazine
To stay ahead, businesses should prioritize procuring IoT devices with eUICC hardware that supports SGP.32, moving away from older SGP.02 standards. This shift enables global single-SKU manufacturing, where devices are shipped with a bootstrap profile and receive their operational profiles upon reaching their destination. As 2G and 3G networks phase out, SGP.32 ensures seamless profile updates for existing devices, eliminating the need for expensive hardware replacements.
These advancements not only enhance connectivity but also pave the way for integrating real-time, edge-based analytics into supply chain operations. As standards evolve, the ability to leverage analytics at the network edge will redefine efficiency and responsiveness.
The Role of Edge AI in IoT
Enhanced connectivity is laying the groundwork for edge AI, which is now a cornerstone of supply chain innovation. The global edge AI market, projected to grow from $25 billion in 2025 to nearly $120 billion by 2033, is driven by the demand for real-time decision-making without relying on cloud processing. Modern IoT sensors can detect temperature deviations as small as 0.5°C per hour, predict threshold breaches up to four hours in advance, and recommend maintenance actions – saving over $50,000 per shipment of high-value goods.
"Knowing where something was yesterday is irrelevant in today’s volatile economy. What matters now is knowing exactly where it is today… and where it will be tomorrow." – KC Jagadeep, CEO, Ceymox
The new operational benchmark for 2026 is predictive visibility. Instead of focusing on historical data, AI-powered IoT systems now deliver real-time updates and future trend predictions. This shift from descriptive to prescriptive analytics allows for automatic rerouting and proactive loss prevention. To make the most of these systems, robust over-the-air (OTA) update capabilities are essential for managing evolving AI models and addressing security updates throughout the device lifecycle. Start by implementing these systems on high-risk routes or those with compliance challenges, where the potential financial benefits outweigh the investment.
Conclusion
IoT standards have transitioned from being optional to becoming the backbone of competitive supply chain operations. With global IoT investments nearing $1 trillion in 2023 and the number of devices expected to reach 24 billion by 2030, the focus has shifted. The question isn’t whether to embrace these standards but how quickly they can be put into action.
To align with these trends, companies must enhance internal connectivity to support seamless global integration. Strong local networks are the foundation for success on a larger scale. Unified protocols like MQTT and CoAP eliminate data silos, turning disconnected devices into an interconnected system. This enables real-time tracking of shipments across continents while monitoring factors like temperature, location, and condition.
Beyond improving operational efficiency, standards-based IoT solutions offer tangible business benefits. They help cut development and deployment costs, speed up time-to-market, and provide regulatory perks, such as expedited customs clearance. Financial institutions are also rewarding companies with standardized, transparent supply chain data by offering better rates, as this data improves risk assessment accuracy. With IoT evolving alongside technologies like 5G, IPv6, and edge AI, the industry is growing at an estimated 18% CAGR through 2025.
Companies that embrace IoT standards now – choosing protocols tailored to their needs and implementing layered security measures like TPM chips and encryption – are setting themselves up for scalable growth. These decisions, often made at the board level, are crucial for securing a competitive edge in the future. Connectivity is no longer just an operational choice; it’s a strategic advantage. For more insights and opportunities to connect, visit CEO Hangout.
FAQs
How do I choose the right IoT protocol for my supply chain?
The right IoT protocol for your supply chain hinges on specific needs like power efficiency, range, security, and data transfer capabilities. Protocols such as MQTT, CoAP, and LPWAN each bring distinct advantages to logistics operations.
When making your choice, think about factors like:
- Scalability: Can the protocol handle your operation’s growth?
- Compatibility: Will it work seamlessly with your current systems?
- Security: Does it offer robust protection for your data?
Carefully assessing these aspects can help you establish a reliable and forward-looking connectivity solution tailored to your supply chain requirements.
What’s the fastest way to fix IoT interoperability across vendors?
The fastest way to tackle IoT interoperability is to use standardized protocols such as MQTT or CoAP. These protocols improve connectivity and make integration less of a headache. Prioritize open standards, ensure devices are compatible with current infrastructure, and implement strong security measures like HTTPS or DTLS to protect data. Moreover, adopting common data formats and widely accepted industry standards – particularly in supply chains – can simplify communication and make it easier to integrate devices from different vendors.
Which IoT standards and regulations do I need to comply with?
To meet the demands of IoT standards in supply chains, organizations need to focus on three key areas: cybersecurity, interoperability, and product safety. These standards include a mix of mandatory rules and advisory guidelines, which are constantly changing to keep pace with technological advancements.
To stay compliant, it’s important to align internal policies with IoT-related activities, secure commitment from leadership, and carefully manage risks associated with third-party vendors. Ignoring these standards can result in serious consequences like product recalls, financial penalties, and security breaches. Staying informed and proactive is critical for protecting both operational efficiency and overall security.