Summary: These days, decision-makers are really feeling the pressure to prove the origins of their products, stay on top of traceability regulations, and shift to digital formats for trade documents. Hey there! In this post, we're diving into the world of blockchain supply chain management and how it's evolving in 2026. Let's unpack what’s going on and see how this technology is making waves! We’re going to dive into the data you'll need to provide and the specific standards you should pay attention to. We'll also chat about the latest trends in the food, pharma, and shipping industries. Plus, I’ll share some tips on how to start a program that genuinely brings in real returns on investment.

Blockchain in Supply Chain Management: How Blockchain Supply Chain Management Really Works

---

What’s changed since 2024: the reality check you need

• EPCIS 2. So, guess what? The 0 model has officially taken the spotlight as the go-to data model for tracking events at an individual level. It's all about JSON and JSON-LD, plus you've got REST APIs and sensor telemetry in the mix. Pretty cool, right? These days, it’s not just a nice perk anymore. If your setup doesn’t match up with EPCIS 2, you're really missing out! 0 and CBV 2. Just a heads-up--you're probably going to run into some pretty frustrating interoperability issues later on. Feel free to dive into more info at gs1.org. There's a lot to explore!

If you're keeping tabs on what's happening in the U.S. Hey there! So, you know how we’ve been talking about food traceability thanks to FSMA 204? Well, here’s a little silver lining! The deadline for compliance has been pushed back by a whole 30 months. Instead of the original January 20, 2026, you've now got until July 20, 2028. That’s definitely a bit of breathing room for everyone involved! This is a great opportunity for you to take a step back and solidify your data foundations. So, back in March 2025, the FDA announced something big, and then in August of the same year, they rolled out a proposed rule. Keep in mind to schedule for that extended date, but don’t let your momentum slow down! If you want more details, just check out fda.gov.

• When it comes to the U.S. landscape... Hey there! Just a heads-up: starting November 2024, the DSCSA package-level electronic tracing in the pharma world is moving past the “stabilization” phase. It's officially kicking into gear! They're aiming for some exemptions until 2025-2026 to make sure everything runs smoothly. This means we’re getting ready for some live electronic data exchanges that’ll work seamlessly together! But don’t worry too much if you’re one of the smaller dispensers--you’ve got a bit more time to prepare. For all the latest information, check out fda.gov. You’ll find everything you need to know there!

If you’ve been keeping an eye on the EU's Ecodesign for Sustainable Products Regulation (ESPR), you’ll be interested to know that it officially got the green light in May 2024! So, guess what? Digital Product Passports (DPP) are now a must-have, thanks to some new product-specific regulations. Get ready to see binding DPP specs for every category rolling out about 24 months after it gets started. If you’re looking for more details, check out consilium.europa.eu. They’ve got all the info you need!

Paperless trade is making the leap from testing to full-scale rollout! DCSA member carriers have committed to transitioning at least half of their transactions to electronic bill of lading (eBL) format by 2027. They're really pushing to go all-in with 100% eBL by 2030. Great news--interoperable eBL transactions are finally here! If you're curious to learn more about it, check out dcsa.org for all the details.

Key point: Blockchain has really stepped into the spotlight and isn't just a side hustle anymore. The actual goal of our project is to make traceability easier and move towards a paperless approach in trade. Blockchain is just one of the tools in our toolbox to help us achieve that.

---

The operating model that works in 2026

A robust blockchain supply chain setup typically consists of four key layers. Imagine each layer as its own mini product, complete with Service Level Agreements (SLAs) and data management, rather than just seeing it as a “pilot.” It’s like treating each part with the importance it deserves, ensuring everything runs smoothly and effectively! ”.

1. Identity and Identifiers
   When you’re dealing with physical and digital IDs, think of GTINs, GLNs, SSCCs, and EPCs as your trusty keys. They really are the essentials you need! Hey there! Just a quick tip: be sure to use GS1 Digital Link URIs. This way, you can easily resolve those IDs online and scan them all with just one 2D code. It makes things so much simpler! Take a look at this link: (gs1.org). You'll find some interesting info there! Hey, if you're thinking about organizational or actor identity, it might be a good idea to check out X. You can use 509 or DID/VCs to manage your counterparties and any human roles involved. Oh, and just so you know, VCs, too. So, back in May 2025, we hit a big milestone when 0 got the W3C Recommendation status. This really sets you up with a reliable, standards-driven way to share signed attestations--think organic certifications or factory audits--while still keeping things private with selective disclosure. If you're looking for more details, you can check this out: (w3.org).

2) Event Data Model (Off-Chain by Default)

• Use EPCIS 2 to track the physical flow. Here are some events that you might find interesting: Object, Aggregation, Transformation, and Transaction. Hey, just a quick reminder to make sure you add those sensor streams! They’re super important for tracking stuff like cold chain monitoring and doing quality checks depending on the conditions. Don't let that slip your mind! To keep things private and improve performance, make sure to keep all the data off the main chain. If you're curious to learn more, just click here for all the details!

3) Trust & Notarization (On-Chain Minimalism)

Hey, have you thought about using a permissioned ledger? Options like Hyperledger Fabric, Besu, or Quorum could be great choices. You might also want to check out a consortium chain for your needs.

• anchoring the hashes for your EPCIS event batches.
• Notarizing documents like eBL title transfers, for example.
• managing workflows that include several different people or teams.
• Keep it straightforward: just hold onto what you really need to show integrity and keep everything in order. Everything else can chill in your EPCIS repository or warehouse.

4) Process and Documents

Let's bring the "last mile" of trust into the digital age! We can do this by transforming important documents like bills of lading, certificates, and quality or inspection reports into secure, signed data. Hey there, if you're in the maritime industry, it’s a good idea to stick with the DCSA eBL APIs. Following the FIT Alliance guidelines can really help you avoid those pesky platform lock-in problems. It’s just a smart move! Take a look at this: dcsa.org. It's worth checking out!

---

Where blockchain actually delivers value (with real examples)

• Keeping track of food sources and quick recalls. Walmart's leafy greens initiative has really upped its game lately! They've managed to reduce the lot-level traceback time from around 7 days down to just a few seconds, thanks to the IBM Food Trust and GS1 standards. How cool is that? Not only does it help cut down on waste, but it also speeds up recalls and makes them way more accurate. Honestly, why bother trying to come up with something completely new when you can just take a page from their book? Just look at what Walmart did--after that romaine lettuce E. coli scare, they decided to use blockchain tech to keep tabs on their leafy greens. It’s a smart move, and it shows how following what works can save a lot of headaches! Check it out here: (corporate.walmart.com). So, over in the MENA region, Carrefour is getting involved with the whole Food Trust thing to keep tabs on fresh chicken and even their in-store microgreens. It’s pretty cool to see how they’re stepping up their game! They’ve even rolled out this cool QR code feature for consumers. Just scan it, and you’ll get the scoop on important stuff like whether it's halal, the hygiene ratings, and even temperature info. This is such a cool way to keep shoppers in the loop! You can check it out here: IBM Newsroom.
• Pharma DSCSA: Verification and Contracts.

So, let’s talk about the Drug Supply Chain Security Act (DSCSA) in the pharmaceutical world. It's all about keeping track of medications and ensuring that everything is above board. Verification is a big piece of the puzzle here--it helps us confirm that the drugs we’re handling are legit and safe. Plus, contracts play a crucial role in outlining responsibilities and ensuring that everyone’s on the same page. It’s all about making sure the supply chain runs smoothly and safely! MediLedger, thanks to Chronicled, has really shifted the landscape. Instead of getting caught up in constant squabbles over data, we’re finally in a spot where everyone understands the pricing and chargebacks clearly. It’s a breath of fresh air! So, what’s the scoop? They’re experiencing an impressive 70% drop in contract errors, which is pretty amazing! Plus, there’s a solid 50% reduction in manual work for the whole team. That’s where the real short-term ROI is hanging out! If you want to dive deeper into this, check out the details on chronicled.com. Oh, and don't forget about that pilot program the network ran for the FDA under the DSCSA! It involved 25 big names--think top manufacturers and wholesalers. It really showed how efficiently blockchain can manage those confidential change-of-ownership records. Pretty impressive, right? (mediledger.com).

• Going paperless with trade and finance. The DCSA members are really pushing for 100% electronic Bills of Lading (eBL) by 2030. It's an ambitious goal, but they believe it's totally achievable! This change is expected to save about $6. We're looking at direct costs hitting around $5 billion, which could really ramp up trade growth by about $30 to $40 billion every year. That's some serious potential! And hey, with interoperable eBL transactions set to kick off in 2025, we can finally wave goodbye to that frustrating problem of “everyone has to be on the same platform.” It’s about time we get some flexibility! Want to know more about this cool new development? Just click here for all the details! It's definitely worth a look! By the way, GSBN’s consortium infrastructure is making some serious progress! They've already handled hundreds of thousands of electronic Bill of Lading (eBLs) and are now fully equipped to roll out the DCSA eBL API v3. It’s exciting to see how far they’ve come!

0. Hey, guess what? Carriers like Hapag-Lloyd and ONE are totally in on this, and it's not just a test--they're fully up and running! If you're curious and want to learn more, check it out here.

• The story behind luxury goods and how they make customers feel. So, there's this group called the Aura Blockchain Consortium, and it's got some really well-known names in it, like LVMH, Prada, and Richemont. They came together to create a special permissioned network using Quorum. This network is pretty versatile! It supports both ERC-721 and ERC-1155 tokens, runs smoothly on Azure, and also comes with consumer wallets. So, here's the deal: it's really focused on notarization and digital product passports. It's not about swapping out ERP systems or those track-and-trace features we often hear about.
  If you want to dive deeper, just head over to auraluxuryblockchain.com for more info!

Here’s what didn’t go as planned (and why it’s important to know): TradeLens was officially shut down in 2022. The reason? It just didn’t catch on in the industry like everyone hoped it would, and it ended up not being viable from a business standpoint. Just a quick reminder: your approach to governance and multi-homing really needs to be stronger than the tech you're using. (maersk.com).

---

The data you need to capture (and where it lives)

• Key master data (off-chain):
• Items: We're talking about GTIN, product names and their details, info on sustainability (like how much of it is made from recycled materials), and any allergens.
• Locations: We're talking about GLN and street addresses, plus geo coordinates if we need them.
• Parties Involved: GLN/DUNS, info about legal entities, and what roles everyone plays.
• We've got event data available thanks to EPCIS 2. 0 (off-chain, hash-anchored on-chain):.
• ObjectEvent: Just picture things like commissioning, shipping, receiving, or keeping an eye on stuff at the case or unit level.
• AggregationEvent: This one focuses on the connections between cases and pallets, as well as between pallets and containers.
• TransformationEvent: This one’s all about the nitty-gritty of things like mixing different lots, co-packing, and all the different steps in the manufacturing process.
• TransactionEvent: This links up events with purchase orders (POs), advanced shipping notices (ASNs), and invoices. Take a look at this link: gs1.org. It's worth checking out!

So, when it comes to sensor and condition telemetry, you've got a whole bunch of stuff being covered right out of the box with EPCIS 2. We're talking about temperature, humidity, shock, CO2 levels, and even time-out-of-refrigeration (OOTR). It's all pretty seamless! 0. Take a look at this link: (gs1.org). It's worth checking out!

So, the document talks about this thing called an on-chain pointer and its connection to off-chain content. So, we keep things like eBL, eCOO, phytosanitary, and quality certificates stored as verifiable credentials or signed JSON files. It's a pretty secure way to manage all that important info! Think of the blockchain as a super secure envelope that shows if anyone's tried to mess with it, all while keeping a detailed record of every transfer.

• Consumer-facing links:
  Imagine having a single 2D barcode that takes you directly to GS1 Digital Links. This little code can connect you to product pages, certifications, and even recall APIs. It’s pretty neat because it simplifies things for point of sale, keeps track of everything for traceability, and really enhances the customer experience all in one go! (gs1.org).

---

How to design your network so it actually inter‑operates

• Make sure to follow the standards!
• So, you should go ahead and use GS1 EPCIS/CBV version 2. You've got a few key tools to keep in mind: 0 for tracking events, GS1 Digital Link for creating scannable identities, DCSA eBL APIs for all your shipping needs, and don’t forget about W3C VCs 2. Each of these plays a unique role in making things work smoothly! You won't find much on things like certifications, inspections, or ESG claims--it's pretty much a blank slate. Feel free to take a closer look at it over at gs1.org. It’s worth checking out!
• Data architecture pattern:
• Store EPCIS in a scalable repository, like Postgres, Elastic, or a Cloud Data Warehouse. Alright, so the first step is to gather and sign your events into groups. After that, you'll want to create a Merkle root or a hash for each of those batches and store it on the blockchain. Simple as that! You can go for Kafka or Event Hubs to stream your data. It's perfect for getting near-real-time updates on recalls, estimated times of arrival, and claims.
• Privacy and Governance:
  Let’s kick things off by using off-chain payloads as our go-to choice. We should really keep any on-chain stuff to a minimum, sticking to just IDs and proofs. When you want to share information, but only what’s necessary, go ahead and issue those W3C Verifiable Credentials (VCs). You can include Data Integrity or JOSE/COSE proofs and just focus on the essential details that each person really needs to see. It’s all about keeping it simple and secure! (w3.org).
• Make sure to lay out data rights in the network bylaws. This should cover who’s allowed to request what kind of info, how long we keep that information, the process for handling erasure requests, and what areas we’ll be checking during audits. Just a friendly reminder to make sure you've got your antitrust lawyer in the loop.
• Multi‑homing and exit:
• Make sure to use public APIs, like the EPCIS capture/query OpenAPI and the DCSA eBL. They’re really important! This means that members can easily switch providers without having to mess with all their wiring again. Think of TradeLens shutting down as a bit of a wake-up call. (ref.gs1.org).

---

Regulatory alignment by vertical

• Food (U.S.) So, when we talk about FSMA 204 data capture, it's really focused on two main things: Key Data Elements (KDEs) and Critical Tracking Events (CTEs). These are all part of what's known as the Food Traceability List. The FDA is considering pushing back the compliance deadline to July 20, 2028. Looks like you've got a little time to dive into your EPCIS 2! You’re set up to streamline and automate the collection of that lot-level data. If you want to dive deeper into this topic, you can find more details right here: IBM Newsroom. Enjoy exploring!
• Pharma (U.S.)
  The DSCSA is pushing for electronic tracking that's not just compatible with other systems but also works at the individual package level. We're looking at a stabilization phase that’s happening from 2023 to 2024, with a few specific exemptions that will carry on into 2025 and 2026. It’s definitely a smart move to start getting your data formats and verification processes lined up now, rather than just crossing your fingers and waiting for more delays. Take a look at the info on the FDA website. It’s got all the deets you need!
• EU Product Passports
  So, the Digital Product Passport (DPP) from the ESPR needs to have product sustainability info that can be easily read by machines. Imagine GS1 IDs, VCs, and EPCIS as the essential building blocks for your Digital Product Passport (DPP). They're like the foundation you need to create something solid and functional! Just a heads up! There will be delegated acts rolling out for every product category, so make sure you're prepared for a lead time of roughly 18 months. (consilium.europa.eu).
• Maritime Trade
  Make sure to keep track of DCSA's plans for reaching that goal of 100% electronic Bill of Lading (eBL) by 2030. It's definitely something to watch! Big names like MSC and Hapag-Lloyd are already on board with this timeline, and they've got some important interoperability goals lined up for 2025. If your bank or insurance company isn't up to speed yet, it's a good idea to get them involved sooner rather than later. (msc.com).

---

Implementation blueprint: 90 days to “first value,” 9 months to scale

Phase 0: Business Case and Compliance Mapping (2-3 Weeks)

• Pick a specific SKU family or document that really makes a difference, like eBL for a particular lane or maybe lot-level produce. Make sure to measure a few key performance indicators (KPIs) before and after the changes. You’ll want to keep an eye on things like time spent, the rate of disputes, dock-to-stock times, days sales outstanding (DSO), and how much claims leakage there is.

Phase 1: Data Foundation (6-8 weeks)

First things first, go ahead and grab those GS1 identifiers--like the GTIN, GLN, and SSCC.

• Get the EPCIS 2 up and running. Make sure to check out the 0 repository and don’t forget to publish those capture and query endpoints! Don’t forget to connect your ERP, WMS, and PLC events to Object, Aggregation, and Transformation events. It’s a crucial step! (ref.gs1.org). Make sure to include those key temperature and humidity sensors! And don't forget to get them all set up to work with EPCIS.

Phase 2: Trust Layer (4-6 weeks in parallel)

Alright, so you’ve got a couple of options here. You can choose a consortium or platform like Fabric, Besu, or Quorum. Or, if it feels more in alignment with what you're thinking, you might lean towards something like GSBN or Aura. Just go with what vibes best with your plans!

• Kick things off by anchoring your event batch hashes. Then, go ahead and roll out your first verifiable credential, like an Organic certificate. Don't forget to check that it's verified across different organizations too! For more details, swing by w3.org. You’ll find a bunch of useful info there!

Phase 3: Process Digitization (4-8 Weeks)

• Shipping: Grab the DCSA eBL v3! Make sure you've got at least one carrier and a trade finance bank in the mix. Don't forget to give that interoperable eBL transfer a good test! (dcsa.org).
• Food: Let’s launch an easy-to-use GS1 Digital Link QR code that helps folks trace where their food comes from. Plus, we should get some automated recall systems in place to keep things safe. (gs1.org).
• Pharma: Let's speed things up by making product identifier checks ultra-fast and getting our contracts and chargebacks in sync, just like they do with the MediLedger model. (chronicled.com).

Phase 4: Scale and Automate (Months 4-9)

Let's get more suppliers involved by using those standardized EPCIS mappings and those useful “data quality” bots we have. How about we dive into some cool analytics? We can start looking at things like cold-chain excursion risk, which helps us keep track of temperature-sensitive products. Then there's the first-expired-first-out (FEFO) compliance to make sure we're using up our stock efficiently and not letting anything go to waste. Oh, and we should definitely add chargeback anomaly detection to the mix--it's a great way to spot any oddities in our billing that could save us some headaches later on. Let’s kick governance into high gear! We need to nail down those onboarding SLAs, keep an eye on query rights, and get our audit and rotation processes up and running.

---

KPIs our clients actually hit (and you should demand)

• Traceback speed: You can now track down a lot or farm in just seconds instead of it taking days like it used to. This is all part of Walmart’s commitment to efficiency! (corporate.walmart.com).
• eBL cycle time: We're really speeding things up! We're reducing that process from days to just a few hours. This not only cuts down on courier costs but also makes it super easy to handle same-day title transfers, which means getting financing done faster than ever. (dcsa.org).
• Contract/chargeback disputes: You can anticipate a pretty significant decrease of 50-70% in disputes within just a couple of quarters! This isn't just a guess--it's actually supported by some solid life sciences data from MediLedger. (chronicled.com).
• Data quality: More than 95% of events have valid GLN/GTIN numbers and correctly follow the business steps. Plus, we’re keeping mistakes to a minimum--less than 0. Looks like about 5% of the aggregations are ending up orphaned.
• Getting ready for compliance: We’re all set with EPCIS 2! We've got 0 coverage for all KDEs and CTEs on your FSMA 204 FTL items. Plus, we’ve made it super easy to connect our DSCSA "suspect/illegitimate" workflows with the FDA’s NextGen portal formats, whether you’re using JSON or XML. It’s all about making things smoother for you! (fda.gov).

---

Architecture deep‑dive: what goes on‑chain vs. off‑chain

On-chain (permissioned, low volume):

• So, when you're working with those EPCIS event sets, make sure to use block headers that have batch hashes--basically, the Merkle roots.
• Staying on top of document state machines, such as eBL ownership and managing a revocation registry for cert VCs.
• It's best to keep personal information to a minimum--actually, avoiding it altogether is even smarter. If you need to handle any sensitive identifiers, just remember to hash and salt them! It’s a smart way to keep things secure.

Off‑chain (scalable, queryable):

• EPCIS repositories that help you capture and query APIs, along with master data catalogs and sensor time series.
• We keep signed documents--whether they're VCs, JSON files, or PDFs--saved in object storage, and they’re organized using content-addressable URIs.
• Resolver services, like the GS1 Digital Link, help bridge the gap between barcodes and online content. (gs1.org).

So, why bother making this split? Well, it really boils down to three key things: performance, privacy, and portability. With this method, you can switch up your ledgers or operators without worrying about losing any of your data history. Also, it helps you stay on top of all the new standards that keep coming up, like VCs 2. 0 and DCSA APIs. Take a look at this link: w3.org. It’s worth checking out!

---

Governance: the make‑or‑break

• Consortium Charter: This part dives into the different membership levels, what voting rights you have, how we manage any changes, plus details on fees and liability.
• Data Policy: This section covers your rights regarding data depending on your role, how long we keep your information, the legal reasons we have for processing it, and what steps we take if there's a problem or you need to address an issue.
• Exit Guarantees: This means you can easily export your EPCIS data and VC registries whenever you want. We use SHA-256 anchoring, so moving your data around is super simple!
• Antitrust Guidelines: We've put together some playbooks that our legal team has checked out to help us avoid any problems with sharing information.

So, TradeLens is closing up shop, and it's a clear reminder that having the right technology alone doesn't cut it. At the end of the day, you've got to consider the incentives that drive people and businesses. Starting off on the right foot is super important, so it’s a good idea to have a solid governance model in place and to embrace multi-homing right from the get-go. (maersk.com).

---

Emerging best practices we recommend in 2026

Make sure you’ve got your DPP readiness in check for the EU, even if you're only selling in the U.S. You never know when you'll need it! Setting up a product passport with IDs, EPCIS, VCs, and open resolvers really boosts consumer confidence and makes it a lot easier for retailers to get on board. It's like giving everyone a little extra assurance while streamlining the whole process. If you want to dive deeper into the topic, just click here. There's some great info waiting for you! Think of eBL as more like email instead of a completely different platform. By getting on board with the DCSA eBL standards, you'll be able to collaborate with just about anyone, no matter what tools they're using. It really opens up the possibilities! The interoperability is definitely already showing us its benefits. If you want to dive deeper into the topic, just check it out here!

• Take advantage of VCs for the certifications you’d like to use again, like organic, halal, conflict-free, and audit results. They’re super flexible, can be revoked if needed, and you can choose who you want to share them with. If you're looking for more info, check out this link. It’s got all the details you need! Hey, if you're in the food industry, don't wait around for that extended FSMA 204 deadline! Dive into using EPCIS right away. It’s a great way to spot any data quality issues with your suppliers and packing houses before they become a bigger problem. Trust me, you'll be glad you did! The FDA keeps stressing that it’s all about being ready, so don’t wait around! If you want to dive deeper into the details, check out their website here.

---

Budgeting and timeline guidance

• Phase 1 pilot (just one product family or lane): You'll want to budget about $150k to $500k for setting up your EPCIS repository, getting your integrations in place, and starting that first notarization flow.
• Year-1 scale (multiple sites, bringing on suppliers, eBL + finance): Expect to budget around $750k to $2 million for this. It could be around 5 million, but it really all depends on how complicated those integrations and change management processes turn out to be. Alright, so when it comes to operational expenses, you should budget anywhere from $8,000 to $20,000 each month. This covers things like hosting services, key management and hardware security modules (HSM), monitoring tools, and those consortium fees. Just something to keep in mind as you plan!

Just a heads up, one of your biggest costs might end up being all that tangled data and getting everyone on the same page. So, definitely keep that in mind when you’re putting your budget together!

---

7Block Labs’ playbook (how we de‑risk your investment)

• Standards-first design: We start off on the right foot by laying down a strong foundation with EPCIS 2. You're all set with GS1 Digital Link, DCSA eBL, and W3C VCs right from the start. With this approach, you can forget about the hassle of switching platforms just to improve compatibility. (gs1.org).
• “Hash-first” blockchain: We make sure to secure proofs and document states directly on the blockchain. Meanwhile, your payloads are safely tucked away in repositories that you manage yourself.
• See real results in just 90 days:
• Produce: Work on getting the recall speed for one category to match Walmart's impressive standards. Take a look at how they’re handling things! You can find all the details right here: Walmart's move with blockchain. It's pretty interesting stuff!
• Pharma: Want to reduce those annoying chargeback disputes? Check out how they’re using a shared truth system over at MediLedger. It’s a game changer! (chronicled.com).
• Trade: Kick things off with your first standards-based eBL by teaming up with a partner carrier and lender. (dcsa.org).

---

Quick FAQ for decision‑makers

So, do I actually need to use blockchain to meet the requirements of FSMA 204 or DSCSA? Not at all! But I gotta say, having a ledger along with VCs really simplifies cross-organization verification and auditing, especially as you grow. It just makes everything smoother, you know? On top of that, it’s a great way to future-proof your DPP and get you closer to trading without paper.

• Public or permissioned?
  If you’re working with B2B traceability and want to keep your trade documents private, it’s a good idea to go for permissioned networks or join a consortium like GSBN. Public networks can be super useful for anchoring and doing open verifications, as long as your policy allows it. (gsbn.trade).

So, what's the scoop on platform risk? When you're thinking about your design, aim for ones that stick to open standards like EPCIS, DCSA eBL, and VCs. It's really the way to go! This way, if a platform ever decides to shut down (like TradeLens did), you can rest easy knowing your data and workflows will still be secure. If you want to dive deeper into this topic, just click here for all the details!

---

Final thought

By 2026, to really make "blockchain in supply chain" effective, we need to focus on establishing solid standards and ensuring top-notch data quality. At the same time, we should keep trust within the chain as a light, easy-to-manage layer. So, you’re going to want to get on board with EPCIS 2. By jumping on board with the DCSA eBL and using the GS1 Digital Link, along with issuing Verifiable Credentials (VCs) for your attestations, you’re setting yourself up to ship faster and manage recalls in a smarter way. Plus, you’ll be able to secure financing quicker. This means you’ll be ready to tackle any challenges that regulators and customers might throw at you! Take a look at this: (gs1.org). You might find it pretty interesting!

---