Here’s a recent paper that describes (among many other things) why combining product-specific EPDs and LCI data is inappropriate:
https://pubs.acs.org/doi/full/10.1021/acs.est.2c05697
Software products like OneClick allow LCA practitioners to combine LCI and EPD data. On many projects, of course, we need to make this compromise to demonstrate the difference we can make with environmentally preferable procurement decisions. But this opens up a number of very serious data quality and comparability concerns which no software platform or data product is wholly equipped to address—it’s moreso an issue of how EPDs are written.
So I’d consider OneClick better suited for more expert LCA practitioners because it doesn’t have the guardrails that TallyLCA has for ensuring harmonization of the background data.
If I implied that OneClick had data quality issues, that wasn’t quite my intent. OneClick puts in a lot of work to get things right. My point was more that it is very easy to be very wrong when combining LCI and EPD data, regardless of the software platform.