customer asks about policy on reducing packaging material

Packaging policy is not a separate data point in VSME

VSME has no separate packaging figure in the core module. What can be asked instead comes via waste indicators and via free-text disclosure of environmental policies and actions. A customer asking about "packaging reduction policy" typically translates that into one of two things: (1) does the company have a concrete policy document or target, or (2) is there data on packaging waste that substantiates the answer. Without one of the two, the most honest answer is "no" or "no policy in place", not a completed "yes" that you cannot support.

If there is indeed a reduction target for packaging, the alignment with the documented reduction target is logical: packaging is then often one of the sub-measures under a broader waste target, not a standalone VSME metric. If a specific packaging plan is absent, the answer usually traces back to general waste figures: if packaging waste is a substantial part of total waste production, you can mention that without suggesting that a formal reduction plan exists. That distinction — figures versus policy — is precisely where customers often lack clarity in their questions, and where you need to be precise in your answer.

Where this comes from: VSME waste module and scope 3

The core module of VSME asks about waste production and separation at enterprise level, but contains no separate packaging criterion; packaging reduction is typically a voluntary disclosure that an enterprise adds itself if it has policy on this. For enterprises that also report packaging as part of their chain emissions, the emissions from packaging material according to the GHG Protocol fall under scope 3 — comparable to the classification that also applies to emissions in the value chain. If the enterprise has no separate packaging policy but does have general scope 3 figures, that is a different answer than "yes, there is a packaging plan" — and that distinction is precisely where this data point often goes wrong.