Shisha buyer guide · Article 172

Which Shisha Charcoal Documents Belong to Product, Batch, and Shipment?

Read each document by the goods, revision, lot, shipment or entity it actually covers. Use a scope matrix to connect product requirements, measured results and shipping records without treating one file as proof of everything.

Review current shisha products and specifications →

Stacks of charcoal cubes in transparent packs
Shipment preparation contextExisting Unimax photo for context; not proof of document completeness or carrier acceptance.
01Read the scope
02Identify the reference
03Link the evidence
04Review reuse and release

01 · Read the scope first

Ask what the document identifies and what it can establish.

Shisha charcoal product batch shipment documents should be reviewed by their scope, not just their titles. A specification can define an approved requirement without reporting a measured result. A test report can describe an identified sample without proving the condition of every carton. An invoice can identify the sale without showing that the product passed a burn evaluation.

Use five working categories: product, batch, shipment, company and destination. These are a buyer filing framework, not fixed legal categories. A document may span more than one level; inspect its actual identifiers, dates, issuer, represented goods and limitations before deciding what it supports.

For each file, record the question it answers, the reference it links to and the decision it is meant to support. Keep “available,” “reviewed” and “accepted by the required recipient” as separate statuses.

02 · Product-level references

Use specifications and SDS for their different purposes.

A product specification records the requirements or targets for an identified grade or configuration. Check the product identifier, revision, measurement basis and agreed limits. Confirm whether the document is a general product sheet or the exact version accepted for the order. It does not become a batch result merely because it lists numerical values.

A safety data sheet communicates product identification and hazard-related information. OSHA’s U.S. SDS framework, for example, covers identification, hazards, handling, storage and revision information. That framework helps explain the role of an SDS; it is not a destination-independent rule for every charcoal shipment.

Check that the SDS describes the actual product and responsible entity and that the version is suitable for the intended review. Treat it separately from quality acceptance and the carrier’s shipment declarations. Do not carry an old SDS into a new shipment without confirming its applicability and current transport requirements.

Sources: OSHA: SDS information framework (U.S. scope)

03 · Batch-level evidence

Require a link between the result and the represented material.

For a requested certificate of analysis, ask whether it reports actual results for an identified lot or sample. Record the identifiers, dates, methods, reporting basis, issuer and quantity or production scope represented. The heading “COA” alone cannot establish that it covers your order.

A laboratory report may be sample-specific. Check who selected the sample, what it represents and whether handling or method differences limit comparison with the approved requirement. Keep numerical results distinct from an acceptance decision against an agreed specification.

Internal QC records can support review within their recorded scope, such as an identified measurement, inspection or release step. Confirm what records exist and what summaries or extracts can be shared. Do not assume access to confidential process data or claim that every shipment has a particular record unless confirmed.

If several lots are packed into one shipment, maintain the lot-to-shipment mapping. If one lot is split across orders, state the actual quantity allocated. A result for one identified lot should not silently clear an unrelated lot.

04 · Shipment-level records

Reconcile the transaction, packs and transport references.

The commercial invoice identifies the sale and its value; the packing list describes the physical package contents, counts, weights and relevant measurements. They should be reconciled with each other and the actual goods. Neither document is a substitute for product test evidence.

Transport documents serve the agreed carriage and release process. Review the parties, routing, cargo particulars and draft-to-final issue stage with the carrier or forwarder. Keep provisional references visibly provisional until the final document is issued.

Origin documents support an origin declaration or a particular origin procedure. Ask the broker which form and scope apply and whether any preference is being claimed. Inspect whether the evidence covers this consignment or another permitted scope; do not assume that one origin document is universally reusable.

Loading and receiving records add physical shipment context when linked to the container, seal, dates, packs and quantities. Preserve that linkage for arrival inspection instead of collecting an unlabeled folder of photos.

Sources: ITA: Common Export Documents (document-role guidance)

05 · Company-level evidence

Verify the party without turning company status into product proof.

Company documents may help identify the contracting entity, authorized contacts or a stated operating role. Check the exact legal name, issuer, relevant address, document purpose and any stated validity or scope. Reconcile differences among the seller, producer and document issuer rather than assuming they are interchangeable.

A company registration, factory presentation or carrier shipper status addresses a different question from a batch result or a shipment release. Even a genuine company document does not establish that a specific lot meets the accepted product specification.

For any certificate or status presented, verify what the issuer actually confirms and whether the named facility, product or activity is within scope. Ask how a change of contracting entity, production source or responsible issuer affects the next order’s evidence.

06 · Destination and transport context

Use current requirements before reusing a document.

Destination-level requirements depend on the actual product, route, parties and procedure. Have the appointed customs broker confirm any permits, certificates, forms, filing requirements and relevant official sources. A broker’s U.S. document overview is useful in its stated U.S. scope; it is not proof of another country’s requirements.

Carrier acceptance is also a separate review. IMO identifies IMDG Amendment 42-24 as mandatory from 1 January 2026, and TT Club’s charcoal guidance explains the removal of the earlier exemption. A historical non-DG acceptance should not be treated as clearance under current rules.

Maersk’s Indonesia export page, as a specific example, requires DG charcoal bookings from pre-audited shippers and loading acceptance, and links its charcoal documentation procedures. Product-level safety information and shipment-linked declarations therefore need separate checks against the chosen carrier’s current instructions. This example does not confirm Unimax’s acceptance status.

Ask the insurer or intermediary to confirm which policy and shipment identifiers, commodity description, route and evidence of cover apply. Keep cover confirmation separate from a carrier’s acceptance or the existence of a safety document. Public official, carrier, broker and insurer guidance was reviewed on 16 October 2026; obtain actual shipment-specific confirmation. This article is a document-review framework, not legal or customs advice.

Sources: IMO: Current IMDG Code · TT Club: Charcoal transport guidance · Maersk: Indonesia export procedures · Livingston: U.S. customs documents (U.S. scope)

07 · Cross-reference and release

Make the links explicit before the next decision.

Build a document register linking the order to the approved product revision, represented lots, allocated quantities, shipment references and destination requirements. Assign a reviewer and decision stage to each item. Show pending results, unverified scope and missing links explicitly.

For example, a specification might identify Grade A revision 3, while a COA names lot L-01 and the packing list includes lots L-01 and L-02. Record the coverage gap for L-02 and request the required evidence or review; do not rename the COA as shipment-wide proof.

Review changes by their effect: a revised product may require product-reference review; a new lot needs the agreed lot evidence; a new shipment needs reconciled shipping records; a changed destination needs a fresh requirements check. Let the responsible parties determine the exact documents and timing rather than inventing a universal expiry period.

Before the relevant release, record the accepted scope, reviewer, revision, date and unresolved later-stage items. Share the shipment references with the receiving team, then use arrival findings to close the order record and prepare the repeat-order baseline.

Buyer tool

Document-scope matrix

Use this proposed filing framework, then check the actual wording of each file. Add the document ID, issuer, revision/date, represented goods, linked order/lot/shipment, reviewer and acceptance decision. The level can overlap; the evidence scope must remain explicit.

DocumentScope to inspectWhat it can supportWhat it does not establish alone
Specification sheetProduct / approved revisionRequirements or targets for the named configurationMeasured quality of every lot
SDSProduct / responsible issuer / revisionProduct identification and safety information within scopeBatch conformity or complete shipment acceptance
COA or test reportIdentified sample or lot, as actually statedReported results with methods and represented scopeUnidentified lots or unmatched test conditions
Internal QC recordRecorded process step, lot or inspection scopeThe specific observation or decision recordedAll factory activity or unrestricted access to records
Invoice and packing listSale / actual shipment configurationCommercial data and physical pack particularsProduct performance or technical compliance by themselves
Transport / loading recordsBooking, consignment, container and release processCarriage particulars and identified shipment contextA substitute for quality evidence
Origin documentDeclared origin and the document’s actual coverageOrigin evidence within the confirmed procedureAutomatic preferential duty or universal reuse
Company / destination evidenceNamed entity, activity or applicable route requirementIdentity/status or a defined approval within scopeConformity of an unrelated batch or different destination

Status options: confirmed requirement, draft under review, submitted, accepted, pending later issue, or not applicable with a review basis. A file being available is different from the receiving party accepting it.

Questions buyers ask

Is every document called a COA batch-specific?

Check the actual sample or lot reference, results, methods and represented quantity. The title alone does not establish batch coverage.

Can one document belong to more than one level?

Yes. An identified document may connect a product, lot and shipment. Record those links explicitly and keep any limits on coverage.

Can a document be reused for the next order?

Only after its scope, revision, validity and the new order’s requirements have been reviewed. Do not assume reuse merely because the grade name is unchanged.

Confirm the evidence scope before production.

Send the route, pack format, product requirement, volume and timing. Include the documents requested by your quality team, broker, carrier and insurer, then ask Unimax to confirm what is supported and how the product, batch and shipment references will be linked before production.

Discuss document scope

Review current shisha charcoal products · Contact Unimax

Related buyer guides

Documents to review before shipment · Arrival inspection checklist · Batch records for buyers