Verified use case
What happened?
Walmart Canada adopted DL Freight to give the retailer and its carriers a shared basis for calculating freight invoices. Walmart's September 2020 announcement reported about 500,000 loads annually, around 2% discrepancies and a 97% reduction from previous dispute levels. The documented use case is coordination of shipment and billing records; the published figures do not establish current savings, current transaction volume or payment in cryptocurrency.
Context before technology
Background
Freight invoices combine agreed rates with events that happen during a journey. Waiting time, fuel adjustments and delivery changes can create different totals when a shipper and a carrier maintain separate records. The resulting dispute delays approval and forces both sides to reconstruct what happened.
Walmart Canada's September 2020 release described DL Freight as its national standard for freight invoicing and payment management across carriers. That announcement is direct evidence of the retailer's reported implementation and outcomes at that time. It is not a current operating dashboard.
The implementation account published by LF Decentralized Trust describes a Hyperledger Fabric system built with DLT Labs. It connects legacy carrier systems and supports confidential data sharing. Its distinctive design decision was to agree the invoice from a shared record, rather than compare separately generated bills after delivery.
This case differs from food provenance: the unit being reconciled is a shipment and its payable charges. A successful implementation needs reliable commercial inputs and agreed correction procedures even when the underlying ledger preserves the history.
Roles and records
How does the operating model work?
1. Agree the commercial inputs
The implementation account describes shared calculations and contractual governance. For a comparable project, FluidRWA recommends versioning rate cards, fuel formulas, effective dates and exception rules. An accurately executed calculation can still produce a disputed bill when the parties disagree about its inputs.
2. Connect shipment evidence
Shipment records from existing systems feed the common process. Define which party is authoritative for departure, delivery, waiting time and changes, and retain both the original event and any correction. These are proposed implementation controls; the public case does not disclose every field or interface in Walmart's production environment.
3. Calculate under controlled visibility
The published technical account describes permissioned Hyperledger Fabric channels protecting relationships between each carrier and Walmart. Procurement should test access using actual participant roles: a carrier, subcontractor, finance analyst and administrator should each see only the information their role requires.
4. Approve, pay and reconcile
The public account connects invoice calculation to payment authorization. The bank payment and accounting close still need identifiers that link back to the approved obligation. Test a duplicate event, corrected rate, rejected payment and partial credit before declaring an invoice-to-cash workflow complete.
Core infrastructure
- Shipment and rate data
- DL Freight application
- Hyperledger Fabric permissioned ledger
- Carrier-system integration
- Shared invoice calculation
- Payment authorization and accounting
Confirmed milestones
How did the use case develop?
- 01
2019 implementation period
Development and pilot described
The technical case study documents configuration, integration and a pilot before national deployment. This page does not assign an exact launch day from inconsistent retrospective descriptions.
- 02
September 2020
National implementation publicly described
Walmart Canada reported adoption across carriers and published annual-load and discrepancy figures.
- 03
Published implementation account
Architecture and operating results documented
LF Decentralized Trust's case study describes shared calculation, permissioned data access and historical invoice processing. Its metrics belong to that deployment period.
- 04
October 19, 2026
Public-record review
FluidRWA checked the available retailer announcement and implementation account. No newer audited client-level operating result was established in these reviewed records.
Evidence of adoption
What outcomes are publicly confirmed?
Loads annually in the 2020 disclosure
Walmart Canada's dated statement; not a current throughput figure.
Discrepancies reported in 2020
The retailer also reported a 97% reduction from previous dispute levels. The underlying denominator and audit workpapers are not published here.
Cash ROI
The implementation case study treats the financial return as confidential. FluidRWA has not calculated or invented a savings percentage.
Metrics are attributed to their reporting organization and date. They are not forecasts, endorsements or guarantees of equivalent results.
Current position
What are the latest confirmed updates?
- The reviewed public record supports a historical production case, with both the retailer's announcement and a detailed implementation account available for inspection.
- The case study's approximately 1.5% discrepancy figure and Walmart's approximately 2% figure are separate published descriptions. They are not combined into a new benchmark or presented as contradictory current measurements.
- Present-day carrier coverage, software version, operating cost and service levels remain unverified in the reviewed material. A prospective buyer should request a recent reference call and current evidence.
What buyers can learn
Why did this use case progress?
- FluidRWA interpretation: the business problem was narrow enough to measure with disputed invoices and approval time, instead of a general claim of digital transformation.
- A shared calculation can remove disagreements caused by duplicate records when all parties accept the governing inputs and rules.
- Integration with existing carrier systems makes participation possible without requiring every firm to replace its transport software.
- A useful next implementation would baseline dispute count, disputed value, exception age and support hours together, so a lower dispute rate cannot hide slower handling of difficult cases.
Limits of the evidence
- The public results come from participants and an ecosystem implementation account; FluidRWA did not audit the deployment.
- The evidence does not isolate blockchain's contribution from better data, integration and process redesign.
- Historical discrepancy rates do not establish a current SLA or a result another customer will achieve.
- Keeping a record of a shipment event does not prove that a sensor, driver entry or commercial charge was correct.
Questions to take into procurement
- Which contract version and rate inputs produced this invoice?
- Who can correct a late or disputed shipment event?
- Which information can each carrier see?
- Does approval trigger a bank instruction, an accounting entry or both?
- How will we measure disputes without excluding difficult loads?
Relevant FluidRWA directories
Common questions
Did Walmart Canada pay freight carriers with cryptocurrency?
The reviewed records describe blockchain-based invoice coordination and payment authorization. They do not establish payment using cryptocurrency. A shared invoice ledger and the asset used to pay an invoice are separate design choices.
What results did Walmart publicly report?
Its September 2020 announcement described about 500,000 loads annually, around 2% discrepancies and a 97% reduction from prior dispute levels. These are participant-reported historical figures, not independently measured current results.
Was DL Freight a public blockchain?
The implementation case study describes Hyperledger Fabric, permissioned participants and confidential relationships between Walmart and individual carriers.
Could a conventional shared database achieve similar results?
The public records do not provide a controlled comparison that isolates the effect of blockchain. Teams should compare governance, data access, integration effort and cost against an appropriately designed conventional alternative.
Research record
FluidRWA reviewed the following public records. Company names are presented as plain text and are not outbound promotional links.
- Walmart Canada: Walmart Canada et DLT Labs recompensees pour l'innovation dans la chaine d'approvisionnement, September 2020; French-language corporate release. https://www.walmartcanada.ca/content/walmart-canada/fr_ca/news/2020/09/01/walmart-canada-and-dlt-labs-recognized-for-supply-chain-innovation.html
- LF Decentralized Trust: DLT Labs & Walmart Canada Transform Freight Invoice Management with Hyperledger Fabric; historical implementation case study, accessed October 19, 2026. https://www.lfdecentralizedtrust.org/case-studies/dltlabs-case-study
Independent research summary, not legal, investment or regulatory advice. Public statements may be updated after the research cut-off.
Last updated
Questions about your project? contact@fluidrwa.com