Product documentation should follow the aerosol project from its first brief through samples, packaging, production and shipment. For an OEM buyer, the useful question is not whether a supplier can name a document. It is whether the document matches the selected product, formulation, packaging, batch and destination-market need. This guide provides a conservative checklist for discussing that file set with an aerosol manufacturer.
Start with the product brief and specification inputs
Record the product direction, application, target market, spray format, reference sample or formulation direction, can, valve, actuator, packaging and artwork revision. Keep the current project version identifiable. A specification or product brief should distinguish confirmed inputs from items still under formulation, sample or compatibility review.
Discuss safety and technical documents where applicable
Depending on the product and destination market, buyers may need to discuss SDS, TDS, COA, ingredient or formulation declarations, transport documentation or DG/UN1950 documentation. Ask which documents are available and applicable to the selected product or formulation. Confirm the named holder, scope, validity and market relevance instead of treating a document as catalogue-wide proof.
Keep artwork and product information aligned
The approved label or carton should match the product name, formulation direction, packaging configuration and agreed project information. Review artwork revisions with the product and packaging records. Market-specific legal or regulatory wording must be confirmed by the responsible buyer and relevant documentation; this guide is not legal or regulatory advice.
Record component and packaging information
Keep the can, valve, actuator, cap, fill format and outer packaging identifiable in the project file. The Packaging & Artwork Guide and Can, Valve and Actuator Guide provide related buyer checklists. Component changes should be recorded before the product or artwork is treated as final.
Connect samples and compatibility records
Record the sample version, component combination, artwork revision, buyer feedback and approval status. If the project requires compatibility or pilot review, keep the decision and open questions with the sample record. The Sampling, Compatibility & Pilot Testing Guide explains this boundary without prescribing a universal method or duration.
Link batch and QC records to the project
Ask how batch identification connects raw materials, packaging, production records, finished-product inspection and outgoing documentation. RustGo’s Quality Control & Batch Traceability Guide provides a buyer-facing review framework, while the Quality Control page describes the capability context. The exact acceptance criteria and records should be agreed in the relevant specification or order documentation.
Prepare the documentation questions for an RFQ
Send the product brief, target market, packaging inputs, sample status, expected supply model and documentation questions. Ask which documents can be provided, for which product or batch, and at what project stage. Avoid requesting a generic “compliance pack” without identifying the product, formulation, destination and intended use.
Documentation checklist
- Product brief, specification inputs and current revision.
- Sample, formulation and compatibility review records.
- Can, valve, actuator, packaging and artwork references.
- Applicable SDS, TDS, COA or formulation/ingredient documents.
- Transport or DG/UN1950 documents where applicable.
- Batch identification, production and inspection records.
- Destination-market questions supplied by the buyer.
- Document holder, scope, validity and product/batch link.
- RFQ questions and requested delivery stage.
For the broader commercial workflow, review OEM / ODM / Private Label and Aerosol Manufacturing. Send the project and documentation questions through Request a Quote.
This is a buyer-planning guide, not legal or regulatory advice, a certification statement, a document-retention policy or a guarantee that a specific document applies to every product or market.
