How to request EPR data without exposing supplier trade secrets

“Please send the specification” is not a sufficient EPR data request. The term can mean anything from a finished component weight to a complete drawing, formulation, tolerance stack, quote, or manufacturing method. That ambiguity creates risk for both parties.

The requesting company may not know which fields the reporting process actually needs. The supplier may not know whether the request is limited to regulatory reporting, whether the data will reach procurement or competitors, or whether declining one field will threaten the relationship.

Start with the actual reporting purpose

Official program requirements can be narrower than a complete engineering specification. California’s current source-reduction guidance, for example, describes reporting total weight of plastic covered material and the number of plastic components. Oregon requires obligated producers to report supply data to its approved producer responsibility organization. Those requirements do not make every possible supplier specification field necessary for every request.

Always confirm the current program, producer, material, market, reporting period, and methodology before deciding which supplier fields are required.

Why ordinary data can become sensitive

A field is not sensitive only because of its name. Sensitivity can arise from granularity and combination. A material family may be routine; the exact grade, layer construction, supplier, SKU, annual volume, and price together may expose sourcing strategy, economics, or manufacturing knowledge.

• Technical sensitivity: formulation, grade, tolerances, drawings, process parameters, or performance methods.
• Commercial sensitivity: quotes, unit cost, volume, capacity, terms, customer allocation, or supplier relationships.
• Competitive inference: ordinary fields that reveal more when linked across products, suppliers, customers, dates, or volumes.
• Regulatory context: information whose submission, aggregation, disclosure, or confidentiality treatment depends on a specific program.

A better six-step request

1. Name the obligation or decision. State the program, market, period, reporting purpose, and responsible requester.
2. Translate it into fields. Define the value, unit, applicability, evidence, source, and acceptance rule for each field.
3. Classify the request. Mark each field required, supporting, optional, or unnecessary for the purpose.
4. Provide safe response states. Allow provided, unknown, not applicable, clarification requested, and potentially sensitive—not only a blank field or forced value.
5. Define visibility and use. Explain who reviews the value or evidence, what may move downstream, how long it is retained, and when it may be reused.
6. Review before promotion. Keep contributed information distinguishable from accepted business records until the accountable party completes validation.

When full supporting detail is unnecessary

A process can sometimes accept a narrower value, redacted evidence, an attestation, aggregated information, or restricted reviewer access rather than exposing an entire source document. Whether that is sufficient depends on the applicable program, contract, validation method, and legal advice.

Use an escrow-like review boundary

In an escrow-like operating model, the supplier contributes information and supporting evidence into a governed review path. Authorized participants validate what is needed. The process releases the approved value, confirmation, or evidence according to a defined rule—rather than treating contribution as general access.

Dazmii uses “escrow-like” as an operating analogy. It does not mean Dazmii is an independent legal escrow agent or makes trade-secret determinations unless such responsibilities are explicitly established through separate agreements and controls.

How BOP supports the trusted exchange

• Processes ties each field to the step, purpose, decision, and release condition that needs it.
• Records connects the supplier, item, field, source, evidence, version, and relationship.
• Work assigns contributions, questions, corrections, reviews, and approvals to accountable participants.
• Data Operations supports validation, normalization, exception resolution, and controlled downstream promotion.
• Operational Library keeps field definitions, sensitivity guidance, evidence instructions, and reporting methods with the process.

The result is not simply more collected data. It is a visible operating record of why information was requested, who contributed it, who could review it, what was accepted, and what moved forward.

Frequently asked questions

Is packaging material data confidential?

Sometimes. A general material category may be low sensitivity in one context, while a detailed composition linked to a supplier, customer, SKU, volume, or cost may be sensitive in another. Confirm contractual and legal treatment rather than assuming.

Can a supplier simply refuse an EPR data request?

That depends on the applicable obligation, contracts, producer responsibilities, and relationship. The operational process should route a refusal or sensitivity concern to the responsible regulatory, procurement, business, or legal owner rather than forcing a misleading entry.

What if evidence contains more information than the requester needs?

Consider whether the process can use restricted review, redaction, an attestation, aggregation, or a narrower source. Confirm that the selected method still satisfies the applicable obligation.

Does verification permit future reuse?

Not automatically. Reuse should confirm permission, purpose, product and market applicability, effective version, currency, and the participants allowed to receive it.

Official sources

• CalRecycle SB 54 source-reduction guidance
• CalRecycle producer guidance
• Oregon DEQ producer requirements
• Oregon DEQ confidentiality rule concept

This article provides operational guidance, not legal or regulatory advice. Requirements and confidentiality treatment vary and change. Verify current official sources and obtain qualified advice for your circumstances.