Blockchain in Supply Chain: Case Study on Cold Chain and Temperature-Sensitive Goods

---

Why cold chain traceability is different (and hard)

Handling temperature-sensitive items can be a bit of a challenge, can’t it? Imagine this: a pallet gets toasty at temperatures ranging from 2 to 8°C for just thirty minutes. At first, everything seems perfect when it shows up at your door. But then, a few weeks later, you might find yourself dealing with recalls, products losing their effectiveness, or worse, having to toss stuff out. If you're one of the folks in charge of making those tough decisions, it’s no longer just about “track-and-trace.” Today, it’s all about having reliable, standards-based evidence that shows:

• The product stayed within the set limits from beginning to end, all the way to the very last mile.
• We can easily keep tabs on who interacted with the product and what it is at every stage of the process. You can definitely rely on the sensor data and calibration. It really comes down to knowing the device's identity, rather than just focusing on the data alone.
• When it comes to sharing info, we do it with care: auditors have access to everything they need, but partners only see what’s essential.

Awesome news! With 2024-2025 around the corner, we've finally got all the key elements we've been looking for--EPCIS 2! You've got zero sensor events, but there's been a big push in DSCSA and FSMA. Plus, let's not forget about those verifiable credentials (VC 2). You’ve got it! So there's also the whole deal with IoT attestation, which is part of the IETF RATS/EAT framework. You can really combine these into a pretty solid production-grade stack now! Hey, why not take a look at it on gs1.org? You might find it really interesting!

---

Regulatory backdrop you must design for (U.S. focus)

• Pharma (DSCSA): Just a heads up, the FDA has rolled out a stabilization period, and it's set to end on November 27, 2024. So, after that, they started rolling out some gradual exemptions for the bigger trading partners. What this means is that the actual enforcement will really get going in 2025. Alright, here’s the scoop: manufacturers need to wrap things up by May 27, wholesalers have a little more time until August 27, and for the bigger dispensers, they're in the clear until November 27. So, if you’re running a small dispensary, you’ve got a little extra breathing room--your exemption actually goes all the way until November 27, 2026. Hey, quick heads up! I wouldn’t call this a delay, but just keep in mind that your systems still need to work together smoothly and stay digital. If you want to dive deeper into the details, just click here. It’ll take you to the full scoop!

Hey there! So, here's the scoop on food regulations (FSMA 204): The FDA is planning to extend the compliance deadline by an extra 30 months. That means they're now aiming for July 20, 2028, thanks to a new rulemaking set for 2025. Just thought you should know! Also, just a heads up--both the FDA and a bunch of trade organizations have pointed out that they’re planning to start regular inspections in 2027. It’s not totally official yet, but that’s the aim! They're also working on getting standardized electronic records in place and ensuring that everyone has 24/7 access to data. Take a look at this: (govinfo.gov). You might find it interesting!

• USP 1079 series: The newest chapters have just dropped, and they’re all about getting temperature mapping spot-on for storage areas (take a look at <1079). Starting May 1, 2024, they'll roll out some new updates. Plus, they've got some really useful tips for keeping an eye on your devices!

1. Let’s jump into mean kinetic temperature and tackle those annoying excursions (anything below 1079). 2). Looks like we're about to see some new qualifications for transport lanes rolling out soon! Auditors are definitely paying more attention to these updates lately! You can check it out for yourself here.

• Cell & Gene Transport: So, ISO 21973:2020 gives us the important guidelines we need when it comes to shipping cells that are meant for therapy. This covers a whole range of things like keeping track of documents, checking things for accuracy, staying on top of monitoring, and making sure communication flows smoothly. Feel free to take a look at it here.
• Calibration: NIST really stresses the importance of having a solid “unbroken chain” when it comes to calibrations, and they want each step to be accompanied by clear uncertainties. Also, ISO/IEC 17025 lays out the standards that labs need to follow when they're handing out those calibration certificates. You can think of calibration proofs as some really high-quality data. (nist.gov).

---

Case studies with fresh, concrete lessons

1) NHS last-mile vaccine monitoring with immutable event logs

Everyware is joining forces with NHS facilities in the UK to monitor temperature changes for those sensitive vaccines. They're making sure these vaccines stay in that ideal range of 2-8°C during storage and while handling those super-cold shipments. It’s a crucial step to ensure everything stays safe and effective! They're using the Hedera Consensus Service to add timestamps to events in a way that makes them tamper-proof. This not only keeps things secure but also helps them respond quickly to any incidents that might pop up. This method shows how to anchor high-frequency IoT streams in a smart way that won't break the bank, and you won't have to stash all that raw data on the blockchain either! If you're curious to dive deeper into this topic, check it out here.

Key takeaways to remember:

When you use unchangeable order and timestamps on a public ledger, it really builds trust among everyone involved in those multi-party cold chains--like the journey from a third-party logistics provider to a hospital and then to a pharmacy.

• Keeping your raw logs off-chain is a pretty savvy move. How about we send batched hashes, like Merkle roots, to the chain every 5 to 15 minutes? That way, we can keep things running smoothly and efficiently!
• Make sure to give each device (or logger batch) its own special key material. This way, you can securely link the data to that specific piece of hardware.

2) APAC vaccine traceability at scale (eZTracker, Zuellig Pharma)

Zuellig and GSK have joined forces to create a hub in Singapore, and it’s pretty exciting since it’s going to be serving 13 different markets! They're using eZTracker to verify that vaccines are real and legit exactly when they’re needed. On top of that, they're also trying to switch to lower-carbon sea transport whenever they can. Since 2020, this system has been operating in Hong Kong, Thailand, and the Philippines. It's just had a nice upgrade and is now officially called eZVax. What really makes this unique is how it brings together cold chain management with verification for both consumers and clinicians. It’s not just about having blockchain technology by itself; it’s this powerful combo that really stands out. Hey, if you want to dive deeper into the details, just click here!

What to copy:

• Use your phone to quickly scan items and packages to make sure they’re the real deal, and stay on top of any recalls that come up. To really win over the executives, try blending your sustainability initiatives--like moving more of your shipping to the sea--with solid traceability measures. This combo not only shows you're committed to the environment but also ensures that everything is tracked and transparent, which makes a strong case for getting their support.

3) IBM Food Trust + iFoodDS for FSMA 204 programs

Hey there! So, guess what? IBM and iFoodDS have joined forces to build a pretty impressive traceability network called IBM Food Trust. They’re actually bringing together the FSMA 204 capture and validation workflows using something they call Trace Exchange. It’s a big step forward in making our food systems safer and more transparent! For big food companies, this is a total game-changer! It really streamlines the whole process of bringing on new suppliers and makes sure all the data is in order before inspections get underway. Want the full details? Just head over here: newsroom.ibm.com. It's worth checking out!

---

The stack that works in 2025

When you're putting together your cold chain setup, keep these standards and interfaces in your back pocket:

1. Getting to know “things” and events with GS1 EPCIS 2. 0:.

• EPCIS 2. With 0, you’ve got access to JSON/JSON-LD and REST APIs right out of the box, plus some handy SensorElements that provide info on things like temperature, humidity, and even shock. It's pretty neat how it all comes together to keep you updated on the conditions you care about! It's really all about hitting those data-sharing targets laid out by DSCSA and FSMA 204. Feel free to take a closer look at it over at gs1.org. There’s a lot of great info there!

1. Show that your device is secure by using IoT attestation (you know, the IETF RATS/EAT stuff):

Make sure your loggers or gateways are set up to create EAT tokens (either JWT or CBOR). These tokens should include important hardware-backed info, such as details about the secure element, the firmware version, and the boot state. This way, you can connect the readings straight to an actual state of the device. Hey, take a look at this: rfc-editor.org. You might find it interesting!

3) Package people/organization proofs with W3C Verifiable Credentials 2.0:

• Let’s kick off the process of issuing verification certificates for stuff like sensor calibration certificates (you know, like ISO/IEC 17025) and lane qualifications--especially when it comes to USP 1079. You’re all set with the green light for 5, plus you've got the Authorized Trading Partner (ATP) status for DSCSA with OCI.
  The VC 2. Great news! As of May 2025, we’ve officially hit a major milestone with the W3C Recommendation. This means we're starting to see some solid multi-vendor interoperability! You can get all the details here: (w3.org). Check it out!

1. Let’s talk about sharing access using GS1 Digital Link and digital signatures.

• Go ahead and use just one 2D barcode, such as a DataMatrix or QR code, that includes a Digital Link. This will help steer regulators and partners right to the data they need. And hey, with GS1 Digital Signatures, you can rest easy knowing that the info on your packaging is safe and reliable! (gs1.org).

1. Tie your evidence to a public or consortium ledger: Hey, instead of just grabbing those raw logs, why not give batch-and-anchor EPCIS event digests and time-series temperature hashes a shot? It could really simplify things! This way, you get the benefits of tamper-evidence and the ability to audit everything, all without spending a fortune. It’s a win-win!
2. Make sure to keep track of your storage logs that you can count on. To make sure you're hitting those retrieval SLAs and keeping everything on the up and up, why not combine IPFS CIDs for integrity with Filecoin storage? And don’t forget to check out the new Proof of Data Possession feature for hot and warm datasets! It’s a great way to keep things both secure and accessible. (docs.ipfs.tech).

7) Interoperate with DSCSA’s VRS and OCI:

Hey, if you’re in the pharmaceutical business, don’t forget to connect your EPCIS+ledger setup with the VRS (that’s the Verification Router Service) and your OCI ATP credentials. It’s a crucial step! We've checked out some performance test suites that show these credentials can handle roundtrips in under a second, which is pretty awesome. That quick response time is crucial for managing returns on sales and dealing with any questionable products. If you're interested, you can find more info about it here. Take a look!

---

Reference architecture (practical and deployable)

• Edge layer So, we're dealing with these super precise data loggers that use BLE, LoRaWAN, and NB-IoT technology. They send out a little update every 5 minutes. Pretty neat, right? Every device's got this cool secure element, like the ATECC608A or the NXP SE050, that really keeps everything locked down. It’s responsible for storing the device's keys and handling the payload signatures, making sure everything stays safe and sound. Oh, and by the way, there's this optional gateway that can toss in some EAT attestation claims if you're interested. Take a look at this: microchip.com. You won't want to miss it!
• Ingestion and normalization You can set up your ingestion service to receive data using either MQTT or HTTPS. It's pretty straightforward! Hey, make sure to check those device signatures and convert the readings into EPCIS 2. Here's an ObjectEvent/TransformationEvent using the SensorElement.
• Evidence machine
• For each shipment, make sure to put together the readings into hourly Merkle roots. Let's save all the logs in object storage and also on IPFS/Filecoin. We can link those hourly roots straight to a ledger for easy tracking. After that, make sure to upload the attestation receipts back to EPCIS so they’re stored as permanent “evidence URIs.” If you want to explore more, check this out: (docs.ipfs.tech). Happy digging!
• Identity & credentials Make sure to keep a credential wallet close by for those ISO/IEC 17025 calibration VCs, DSCSA ATP credentials (OCI), and lane/shipping system qualifications (USP 1079). It’ll help you stay organized and on top of things! 4/. Don't forget to grab any auditor permits you might need! For more details, just check out this link: iso.org.
• Access control
• Transform a GS1 Digital Link QR or DataMatrix into a customized view of verifiable credentials, signed PDFs, EPCIS queries, and cryptographic proofs, all while keeping everything under policy control. For more information, check out the details over at gs1.org. You'll find everything you need there!
• Pharma extras We've got your back with VRS APIs for checking product verification, and we also do OCI checks to keep tabs on ATP status. On top of that, we're getting in sync with the GS1 US DSCSA Implementation Suite (Release 1. The third season is set to launch in 2026! Check this out: (gs1us.org).

---

What “good” looks like in production

• Evidentiary temperature integrity Hey there! Just a quick reminder: for each unit, case, or pallet, don’t forget to whip up a signed summary that includes the min, max, and mean values. You’ll also need to create the EPCIS SensorElements. And if there are any excursions for MKT--basically anything that falls below 1079--make sure to put together an excursion report as well. Thanks!

1. There's a calibration VC chain that links up with NIST traceability, plus a ledger receipt that provides proof against tampering. (uspnf.com).

• Multilevel sharing
• We’ll hook up dispensers and retailers with a convenient, compact dossier. And for the regulators, they’ll get access to complete logs and proof in under 24 hours--just like the FSMA/DSCSA requires.
• Provable device trust
• Connect each reading to the device's identity by using the secure element serial number and attestation (EAT). If there are any updates to the firmware, you'll definitely see that reflected in the claims.
• Recall efficiency EPCIS+Digital Link really simplifies the process of recalling products. Instead of having to pull everything from whole categories, you can just focus on the specific lots or traceability codes that are affected. It’s way more efficient! (gs1.org).

---

Cold chain-specific patterns (with numbers)

• Sampling and costs Alright, so when it comes to those usual pharma or food shipments, they typically keep track of data every 5 minutes for a good 3 days straight. So, if you break it down, that comes out to roughly 864 readings each day. When you multiply that by the number of days in a shipment, you're looking at about 2,592 readings total for just one shipment. Pretty wild, right? So, if you're handling around 1,000 shipments each month, you're probably looking at about 2. 6 million readings!. So, here’s the deal: we gather up 60 readings, which is about five hours' worth of data, and then we mash them together to create a single Merkle leaf. So, we usually crank out about 5 to 6 leaf roots every hour, which adds up to roughly 72 anchors for each shipment we handle. But here’s the interesting part: in reality, we can actually simplify that to just one anchor for each lane every hour. By doing it this way, we can cut down on on-chain operations by more than 90%, all while making sure everything stays auditable. Pretty neat, right?
• MKT-based excursion adjudication
• Let's establish a few business rules: we can totally overlook those temporary "door-open" spikes as long as the shipment MKT stays within the given range (as per the labeled storage). But hey, if the MKT exceeds the threshold or if we see any single-point violations that cross the hard limits, we need to flag it right away. (uspnf.com).
• Cryogenic/ultra-cold lanes Hey there! Just a quick tip when dealing with CAR-T and other cell therapies: don’t forget to add in the cryogenic shipper telemetry details--things like location, orientation, any shock or tilt, and pressure. And make sure to include the ISO 21973 documentation in the dossier too. It’s super important! Hey, just a quick reminder to keep that “chain of identity” going strong! Make sure you have the VCs all set and ready to go at those handoff checkpoints. It really helps keep everything smooth! (iso.org).
• Confirmed interactions with partner companies in the pharmaceutical industry. If the ATP credentials for a counterparty aren't working, make sure to stop the data exchange. Also, VRS calls should ideally finish up in less than a second when those credentials are included. The OCI test harness is currently showing results around 1-1. 5 seconds for roundtrips. (oc-i.org).

---

Emerging best practices we recommend in 2025

1. Consider calibration as a piece of who you are. Hey, for each logger, make sure to attach a VC that includes the ISO/IEC 17025 lab details, the certificate number, the uncertainty, and when it's due. Thanks! Hey, just a quick reminder to make sure you include a NIST-traceability statement. It’s an important piece! If your calibration has expired, that basically means you’ll be moved down to a lower assurance tier. (iso.org).

2) Hardware Roots of Trust at the Edge

Hey, have you thought about using some secure elements like the ATECC608A or SE05x? They’re great for keeping your keys safe and can handle ECDSA signing directly on the device. It’s a smart way to make sure everything stays secure! Make sure to pair these with EAT claims so you can confidently verify that your boot and firmware states are legit. Take a look at this: (microchip.com). It's pretty interesting!

VC 2.0 Everywhere

• I think we should go with VC 2. You've got zero for ATP credentials, auditor access, calibration, and training attestations, like the whole “qualified shipper loading” thing.
  This method really helps minimize the need for custom integrations, which in turn makes audits a lot easier. If you want to dive deeper into it, just head over to this link: w3.org. You’ll find all the details there!

1. EPCIS 2. Think of 0 as the language we all share.

• Keep the business side of things off the blockchain. Use the EPCIS event stream as your main source of truth for everything you’re doing. To keep everything above board, it’s a good idea to connect digests to the blockchain. If you want to dive deeper into it, head over to gs1.org for more info!

1. Try to limit on-chain writes as much as possible, but at the same time, make sure to enhance verifiability. Hey there! Have you thought about using hourly anchors? It could be a good idea to save your logs in IPFS or Filecoin too! Just a suggestion! Thanks to the new PDP-enabled warm storage, you can look forward to quicker retrieval proofs! Take a look at this: filecoin.io. You won't want to miss it!
2. DSCSA: It's time to get your OCI and VRS sorted out! Don't wait too long to set them up.

• Don't just sit there twiddling your thumbs waiting for the final enforcement to kick in. Feel free to get your organization all set up with the right credentials. Don’t forget to run some tests with at least two different VRS providers, and make sure your EPCIS 2 is good to go! All the mappings are spot on! GS1 US recommends that you stay with Release 1 for now. We're kicking things off in phases starting in 2026. If you’re interested in diving deeper, you can find more information here. It’s worth a look!

7) FSMA 204: Build Once for 2027-2028

• So, even if there's talk about extending things, it's really important to get standardized KDE/CTE capture in place, make sure we can retrieve data 24/7, and rely on EPCIS-based evidence. If you're looking to streamline supplier data on a larger scale, you might want to check out IBM/iFoodDS or something along those lines. It's a solid option to consider! If you want to dive deeper into the topic, you can find all the details here.

---

Tooling snapshot you can adopt today

• EPCIS 2. 0 APIs: Make sure to grab those ObjectEvent/TransformationEvent and SensorElement by using JSON or JSON-LD. Check it out here.
• OCI ATP credentials and wallet: Let’s connect those ledger-backed credential flows, especially focusing on the DSCSA. For all the info you need, just check it out here. It’s all laid out for you!
• VRS: Just double-check that your provider has successfully completed those independent tests for conformance and performance. Ideally, you want to see verification times for your credentials hovering around the 1-second mark. If you’re looking for more details, you can check it out here. It's got everything you need!
• Digital IDs on Labels: Make the most out of GS1 Digital Links and GS1 Digital Signatures to effortlessly bridge the gap between your physical products and the digital realm. Learn more here.
• Verifiable storage: Make sure your logs are secure by using IPFS CIDs. You can store them on Filecoin for extra safety, and remember to hang onto those on-chain receipts! If you want to dive deeper into this topic, check it out here.

---

Procurement-ready specs for cold-chain sensors (what to insist on)

• How accurate and far you can shoot, depending on the lane:
• It works great in a temperature range of 2 to 8°C, and it’s got a nice level of accuracy at ±0. It can handle temperatures around 3°C, and it manages dry ice temps from -60 to -80°C like a champ. Plus, it can even dip down to a chilly -150°C for those cryogenic telemetry needs!
• Identity and attestation:
• Features a cool hardware-backed keypair that's using ECDSA P-256. It also has the option for EAT claims and can handle signed payloads.
• Calibration:
• They've got an ISO/IEC 17025 certificate as a VC, which is pretty impressive. This certification goes over things like uncertainty, methods, and due dates. Plus, it even comes with a note about NIST traceability, which is a big deal! You can take a look at it over at iso.org.
• Data model:
• It comes with built-in support for EPCIS 2. You've got 0 fields in the SensorElement, which means there’s no time info, unit of measurement (uom), range details, or sampling rate available.
• Security and records:
• Keeps audit trails and signature controls in line with 21 CFR Part 11, which is super important when you’re working in regulated settings. If you’re looking for more info, check out the FDA’s website at fda.gov. They’ve got all the details you need!

---

90‑day pilot plan (repeatable)

• Weeks 1-2: Getting the Lay of the Land and Setting Up the Rules.
• Pick out two lanes: one for domestic transport and another for cross-border shipping. Hey! Just a quick note: pick a temperature range between 2 and 8°C, and team up with two partners, like a third-party logistics provider or a dispensing site. Sounds good?
• Get your success metrics sorted: keep tabs on how quickly you can spot excursions, make sure that your dossier is complete (don't forget about EPCIS, VC, and receipts), and monitor how long verification takes, especially if you're using VRS/OCI for pharma.
• Weeks 3-6: Time to Get Everything Set Up and Make Some Connections! Alright, let’s get those calibrated loggers set up with hardware signing. Once that’s done, we can start the data ingestion process. And don’t forget, we need to make sure everything lines up smoothly with EPCIS 2. Alright, here’s the game plan: first, set up your hourly anchoring. Next, make sure you’ve got your IPFS/Filecoin storage sorted out. You’ll also need to handle provisioning for ATP and grab any other credentials you might need through OCI. And hey, don’t forget to add that GS1 Digital Link to your labels--it’s super important! (gs1.org).
• Weeks 7-10: It's time to kick off those runs and dry drills! Let’s make sure we’re getting into a good groove. Okay, so here’s the plan: we’re looking to get between 25 to 50 shipments rolling. Let’s also throw in a few trial runs to see how things go. And don’t forget to dive into the marketing analysis based on the guidelines in <1079. 2>; and let’s finish things off with a quick recall drill, just to make sure that the 24-hour dossier gets delivered. (uspnf.com).
• Weeks 11-12: Time to Validate and Make Decisions! Hey, just a heads up--be sure to check out the QA evidence using ISO 21973 and USP 1079. Alright, so we need to tackle four checklists, take a look at the VRS/OCI latency, and put the finishing touches on the rollout plan. Don’t forget to also nail down the partner onboarding strategy while we're at it! (iso.org).

---

Brief in-depth details: specialty therapy (cryogenic) pattern

• Requirements: We’ve got to chill things down to a serious level--think around -150°C or even colder--and maintain that for a solid week to ten days.
  We're looking to include some orientation and shock sensing, plus we want to make sure we have solid chain-of-identity controls in place too. Also, make sure to keep that ISO 21973 transport plan and verification in mind! And let’s not overlook the importance of round-the-clock monitoring--it’s crucial. We should definitely have some intervention options available too, like what you’d find with Smartpak II and its platform. (iso.org).
• Architecture deltas: Hey team! Just a heads up, we’re rolling out two-factor custody handoffs. This means that from now on, you’ll need to have your badge handy along with a VC scan to keep everything secure. Thanks for your cooperation! At the clinical sites, we’ll create customized views based on the roles of those involved. On top of that, we’ll be tracking the telemetry from cryo-shippers, treating them as EPCIS SensorElements. We're excited to roll out hourly anchors and alert-driven on-demand anchors for those moments when things don't go as planned.
• Business rule: Alright, so if we have any tilt event that goes beyond what we can handle right at the transfer point, we’ll have to do a visual inspection. Plus, we’ll document that with a notarized event (VC) and add it to the dossier. Just a quick heads-up: the payer will only release the funds if everything in the dossier looks good.

---

Risk, ROI, and what to say to your CFO

• Risk reduction: No more relying on those sketchy “trust me spreadsheets.” Instead, we're moving towards cryptographic receipts and standardized dossiers that regulators can actually understand (think EPCIS plus VC and ledger proof). Much clearer, don’t you think?
• Cost control: When you anchor digests every hour, it helps keep those ledger costs steady and predictable. Also, storing your data using verifiable storage like Filecoin or IPFS is way more budget-friendly than putting all those raw logs directly on the blockchain. And hey, make sure to check out those awesome retrieval proofs! They’re super useful! You can find more about them here.
• Revenue protection: You’ll be set up to manage recalls more quickly and accurately, which means you'll deal with way fewer write-offs from those annoying unprovable excursions. Plus, with reliable partner performance, you can totally go ahead and claim your SLA credits!

---

Final checklist before you greenlight

• Great news! We’ve got the EPCIS 2. We've got the capture and query APIs up and running, and they’ve been put through their paces with SensorElements. Everything's looking good! Take a look at this link: gs1.org. You might find it interesting! Hey there! Just wanted to let you know that we’ve issued the OCI ATP credentials to you and your key partners. We also put the VRS connectivity to the test, and everything looks good! More info here: (oc-i.org).
• The VC 2. The issuer is all set up now, so we’re good to go with calibration certificates and auditor access! Learn more at: (w3.org).
• We’ve set up a cool hourly anchoring pipeline that uses public receipts, and we’re also storing our logs on IPFS/Filecoin. Dive deeper here: (docs.ipfs.tech).
• We’ve finished up the USP 1079! You’ve got a storage mapping plan along with the lane qualification strategy, right? This is all part of the documentation process. Just a note, make sure everything is updated as of October 2023! We've got number 5 in the pipeline! We're definitely keeping an eye on ISO 21973 for cell and gene lanes. Feel free to dive into the details here: lachmanconsultants.com. You'll find some great information waiting for you! Your quality system now has audit trails and e-signatures that are fully aligned with 21 CFR Part 11. If you want to dig deeper, check this out: fda.gov. It's got all the info you need!

---

One more thing: don’t forget the label

Just stick a single GS1 Digital Link 2D code on the unit or case. This code should direct folks to a policy-controlled view that includes:

Here’s a rundown of EPCIS events that covers the essentials: who was involved, what happened, when it took place, where it occurred, and a bit about the SensorElement as well.

• Details about calibration VCs and ISO/IEC 17025 standards.
• Ledger receipts and IPFS CIDs.
• DSCSA verification (if it’s related to pharmaceuticals).
• If it’s food-related, make sure to check out the FSMA 204 KDE/CTE package.

If you want to dive deeper into this, feel free to head over to gs1.org for more info!

That’s how you turn every physical item into a digital twin that you can verify, making audits a breeze and building trust-- all without bogging down your partners with a ton of integrations.

---

At 7Block Labs, we’re all about building and delivering these awesome stacks. Hey there! If you're looking for a tailored 90-day pilot plan that fits your unique lanes and regulatory requirements, I'd love to set up a working session. It would be great to bring in your quality and security teams to hash out all the details together. Let me know when you’re free!