Skip to main content

Receive a data request

What Is a Data Request?​

A data request is a structured ask from a customer — a battery manufacturer or product company using Traceable — for specific supply chain data that they need to complete a Digital Product Passport (DPP) for a product you supply into.

Customers are required under EU Battery Regulation 2023/1542 to include verified supply chain data in their DPPs, covering areas such as material composition, carbon footprint, country of origin, recycled content, and hazardous substance declarations. They cannot always gather this data themselves — they need it from suppliers like you.

A data request is not a generic email asking for documents. It is a structured form within Traceable specifying exact DPP fields and the information required for each one.

How You Are Notified​

When a customer creates a data request for you, Traceable notifies you in two ways simultaneously:

  1. Email notification — sent to your registered email address. The email includes the customer's name, the product the request relates to, the number of fields requested, and the due date. It contains a direct link to open the request in Traceable.

  2. Dashboard notification — the Open Data Requests counter on your Supplier Dashboard increments, and the request appears at the top of the list (sorted by due date). The urgency indicator will be green, amber, or red depending on the time until the due date.

If you manage multiple customer relationships, both channels clearly identify which customer sent the request, so you can prioritise accordingly.

What a Data Request Contains​

Open a request by clicking it on the dashboard or navigating to Data Requests in the sidebar. Every data request contains the following sections:

Customer and Product Information​

  • Customer name and logo — so you know who is asking
  • Product name — the specific battery product or component the DPP relates to
  • Product category — the EU Battery Regulation category (EV battery, LMT battery, Industrial battery, SLI battery, or Portable battery)
  • Product identifier — the customer's internal model or part number

Request Details​

  • Requested fields — a list of specific DPP data fields the customer needs you to provide. Each field is named exactly as it appears in the DPP form, accompanied by a description of what is being asked and the expected format (e.g., "Carbon footprint — lifecycle carbon footprint in kg CO₂e per kWh, based on LCA methodology compliant with EU Battery Regulation Annex II")
  • Message from customer — a free-text note from the customer providing context, flagging specific concerns, or explaining why certain fields are being requested
  • Due date — the deadline by which the customer needs your response

Documentation Requirements​

Some requests include a Documents section listing specific certificates or evidence files the customer needs alongside the data values. Review this section carefully — submitting values without the requested supporting documents may result in the customer returning the request to you.

Reading the Request Carefully​

Before starting your response, read the entire request. In particular:

Understand each field being requested. Field names like "Carbon footprint — cradle to gate" or "Recycled content — cobalt" have precise regulatory definitions. If a field is unfamiliar, refer to the Glossary for definitions. Submitting an incorrect value type (for example, submitting total lifecycle carbon footprint instead of the cradle-to-gate value) will result in the response being returned by the customer.

Check the due date against your capacity. If the due date is unrealistic — for example, three days from now for a request that requires you to commission a laboratory analysis — contact the customer via the request's message thread immediately to discuss an extension. Do not wait until the deadline passes.

Note any specific document requirements. If the customer has listed required certificates or reports, confirm you have them before beginning the response.

If You Do Not Have the Requested Data​

Customers sometimes request data that you do not have readily available, or that requires third-party analysis or verification to obtain. The correct action is always to communicate — not to leave the request unanswered.

Options available to you:

  • Respond with a comment — use the message thread within the request to explain which fields you cannot provide and why. The customer can then decide whether to adjust the request, source the data elsewhere, or grant additional time.
  • Submit a partial response — you can submit data for the fields you have and add a comment noting which fields are outstanding and when you expect to have them. See Respond to a Data Request for details on partial submissions.
  • Request clarification — if you are unsure exactly what is being asked, use the message thread to ask. Customers generally prefer a brief clarification exchange over receiving an incorrect or misunderstood response.

Do not leave a request unanswered without communicating. Unanswered requests delay DPP completion, which in turn delays the customer's product to market. Your supplier relationship with the customer depends on responsive and transparent communication.