Request product identity first
Every information request should identify the exact product and version being discussed. Ask for the supplier model or source identity, current specification date, product dimensions, materials, functions, power system, included components, unit packaging and available variants. This prevents a document or declaration from being applied to the wrong item.
Keep supplier source information in a review layer. Public copy should use only selected facts that have been checked and approved for publication.
Separate declarations from files
A supplier statement that a document exists is not the same as receiving and reviewing it. Track the state clearly: declared, received, internally reviewed, or supported by identified third-party evidence. A regulatory decision for a particular destination is a separate matter and may require qualified advice.
The Quality and Compliance service describes this evidence boundary in more detail.
Ask product-specific questions
- Material names and the basis of the supplier statement
- Battery chemistry, capacity and charging information
- Available transport files such as UN38.3 or SDS/MSDS where relevant
- Test report or certificate issuer, subject, date and stated scope
- Packaging, labels and manual information associated with the product
- Open market-specific questions for the intended destination
Do not ask only whether a product is “compliant.” Ask what file supports which statement for which product and market.
Record review outcomes
Store the original file, received date, product association and review notes. If a file is incomplete, expired, out of scope or for another model, record that limitation rather than replacing it with a broad claim. The same discipline should carry into the RFQ and production handoff.
This checklist is a sourcing workflow, not legal advice. Buyers should verify current requirements for their specific product, channel and destination.