After your upload or manually fill out your product data, you have to map it to Pickler's impact values (LCI database Idemat) to get the impact results.
1. In short: how mapping works
You upload/fill out your available product data to Pickler to get started
You use the product form for manual input, CSV for bulk product import, or API for a sync with your ERP system (the last two are part of the data management subscription).
Pickler places worst-case values for product data that is not yet collected. This is done, so you can’t accidentally make false claims.
You map your product data to Pickler’s LCI database, to enable impact calculations.
You work on collecting more specific product data. This helps you lower your environmental impact, since you move away from worst-case data.
2. Why do we apply mapping in Pickler?
There are many benefits to mapping your input data:
You don't need to adapt your product management to the data of Pickler, which makes for much easier data onboarding.
There are few restrictions on your data input format, which enables an easy start to getting your data in Pickler.
It enables easy navigation in the app for all your company users; as it's familiar product data for them.
Not having to adapt to the naming conventions in Pickler, makes working with the data easier and less prone to error.
Less time-consuming. You map once, and can always use the same mapped data.
There's a clear distinction between your reference data and our LCI database values. Which is in line with anti-greenwashing regulations. .