aceModerate evidence
Published recordBusinessGood Space
More
A cross-contextual meta-analysis of agentic AI in retail and supply chain operations: efficacy and implementation insights
- Truvace record
- TRV-2026-2715raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Systematic review or meta-analysis
- Sources
- 1 sourcePeer-reviewed
- sha256
- 5ca05f3513d0…check it
Abstract Agentic artificial intelligence (AI) systems are increasingly deployed in retail and supply chain operations, yet the empirical evidence for their efficacy has never been systematically quantified. This meta-analysis synthesizes 19 studies (total $$N = 5{,}292$$ ) to quantify the impact of agentic AI on operational performance and examine how contextual factors shape outcomes. Using a random-effects model with restricted maximum likelihood (REML) estimation and the Hartung-Knapp (HK) adjustment for conf…
The gain
A meta-analysis of 19 studies (N = 5,292) found agentic AI in retail and supply chain operations improved operational performance on average, with a pooled Hedges' g of 1.58 (95% CI 0.26 to 2.89).
What this doesn’t fix
The studies were extremely heterogeneous (I² = 99.5%) and showed meaningful selective reporting, and the e-commerce estimate rests on only three studies, so the pooled effect should not be read as a general expectation.
Sources
1 on file- Industrial Artificial Intelligencedoi:10.1007/s44244-026-00039-3
Cite this record
v1Truvace Impact Record TRV-2026-2715, v1: “A cross-contextual meta-analysis of agentic AI in retail and supply chain operations: efficacy and implementation insights.” Truvace, 2026-11-12. /record/TRV-2026-2715 (accessed on the day you copy it). sha256 5ca05f3513d0efaf…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2715 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.