All insights

    When customers demand packaging data: how to respond fast, correctly and without the Excel hunt

    Author information unavailable in the original

    Published:

    Updated:

    Translation updated:

    Customer requirements rarely arrive as legal text. They arrive as an email with a deadline. How to build an answer you can reuse next time.

    Kartongförpackning och samlade dokument i en grön mapp

    The requirement comes from the customer, not the law

    For many companies, the first PPWR requirement is not a paragraph. It is an email from a customer, a brand owner, a retail chain or a tender: “Send your declaration of conformity and technical specification for item X, by Friday.”

    Three situations are especially common:

    • Private label and contract manufacturers delivering to brand customers who have to stand behind their own DoC.
    • Manufacturers selling to chains in several countries, where the chain has its own labelling and documentation requirements.
    • Suppliers that have won or are taking part in public tenders and must show evidence in the bid. See climate data in public procurement.

    In all three cases, someone else sets the pace.

    Why it gets stressful

    • The evidence sits with your suppliers, not with you.
    • The same question arrives from five customers in five formats.
    • Nobody knows which version of the document applies.
    • The answer is built from scratch every time.

    An answer you can reuse: four steps

    1. Sort the request. Which item, which role, which document is requested?
    2. Pull from one source. Evidence should be stored in structure per item, not scattered across inboxes.
    3. Check before you send. Is incoming evidence complete? Do the item numbers match?
    4. Save the answer. The next customer who asks gets the same evidence, updated where needed.

    What makes the difference in practice

    • A guardrail against incomplete answers. In CO2check's PPWR portal, an outgoing DoC is not generated if incoming documentation is missing.
    • Two outputs. DoC and technical specification, in standard or advanced format.
    • Suppliers do the work at the source. They upload their own documents per item.
    • Gap flagging. You see immediately which item numbers are not found.

    Christer Nöjd AB says this lets them “deliver correct documentation to our customers”. Read the customer case.

    Next step

    Take the latest customer request you received and measure: how long from email to answer, and how many people were involved? That is your baseline and your business case. See how the PPWR solution works.

    Frequently asked questions

    What do we do when a customer demands a DoC and technical specification at short notice?

    Sort the request by item and role, pull the evidence from a structured source, check that incoming documentation is complete and save the answer so it can be reused.

    Are we obliged to issue a DoC for our customers?

    It depends on your role in the value chain. Responsibility for the DoC lies with the manufacturer in the PPWR sense, but customers can demand evidence regardless. Determine your role per item.

    How do we avoid answering differently to different customers?

    By collecting evidence in structure per item and version-controlling it, so every answer is built on the same source.

    Related topics