A shipping carton frequently carries quite a few familiar marks. However these marks do not answer the same questions. CE = manufacturer’s declaration of conformity to EU requirements. FCC = U.S. radio frequency equipment requirements and authorization. RoHS = restrictions on use of hazardous materials in manufacturing. UN 38.3 = testing of lithium batteries for transport. A shipment of cameras with batteries is not the same as fulfilling market requirements and providing documentation for safe transport of dangerous goods. The model name is not sufficient; check for the radio module, power supply, batteries, and version number of the shipment. For an order of 8185XM, for example, check for the current version of CE, FCC, RoHS, WEEE declarations, MSDS, and UN 38.3 test reports for the battery.
Start With Destination and Product Configuration
You should start with the destination market and the exact product setup. Write down the product type, radio technologies, power supply, and battery contents. Also write down whether the camera is sold alone or in a kit. Requirements can differ for a WiFi camera, a 4G camera, a power adapter, and a package containing a lithium battery. A document for one module or one regional version may not cover a changed configuration.
Create a compliance matrix with one row per SKU and columns for market, applicable requirement, responsible party, document title, model and revision, issuing or testing body, validity or update status, and shipment scope. Mark each cell as confirmed, pending, or not applicable. This is more useful than asking a supplier to send “all certificates.” Such a request often produces a folder of unrelated files.
For an 8185XM shipment, you would like to request currently valid CE, FCC, RoHS, WEEE, MSDS and UN 38.3 documentation among others. The list above should be used as a request checklist. Please note that the documentation provided does not necessarily guarantee compliance of all variants for all markets. Please check if the documentation provided corresponds to the model delivered, to the radio and power configuration as well as to the legal entity putting the product on the market.
Jortan‘s product documentation team can be asked for the current files against a defined SKU and destination. A request for SKU-specific compliance documents should name the target market, radio version, adapter, battery, and planned shipping route. That makes the response auditable. It also helps prevent a familiar logo from being mistaken for proof of the wrong scope.
Separate the Document Families
For the EU you will need to request the relevant EU Declaration of Conformity together with supporting technical information for the exact product for which CE marking has been applied. CE marking is not a general third party quality mark. The EU Declaration of Conformity should detail the manufacturer, product, relevant legislation or relevant harmonized standards, signatory and date. Subsequent changes to the radio module, adapter etc. or even changes to the overall design of the product may require a review of the scope of declaration.
For shipping finished products in the United States to customers, it is necessary to know which FCC authorization is required for the product as a whole and for the individual radio modules it contains. That identifier and corresponding supplier declaration must be verifiable. A simple FCC logo on a web page or box is not sufficient. The corresponding paperwork for the camera shipped must contain information on the actual radio configuration and the host integration. Special conditions in the grant for a module also apply to the finished product.
RoHS evidence relates to restricted substances in electrical and electronic equipment. Request a declaration and supporting material or test records suitable for the buyer’s supply chain policy and market. A Safety Data Sheet, sometimes called an MSDS, is not a substitute for a conformity declaration. For batteries, UN 38.3 is a transport test requirement. Request the test summary for the actual cell or battery type. Confirm that the packaging and consignment follow current transport rules.
For launch of the 8185XM, request current version of CE, FCC, RoHS, WEEE, MSDS and UN 38.3 documents. Verify current SKU, radio, battery, product revision, issuer and stated scope of documents. Note that the Safety data sheet is a separate document from the UN 38.3 summary for the battery test. Although both documents refer to the battery, one cannot be used in place of the other for launch. List documents that remain unresolved as launch blockers in the matrix.
Match Reports to the Shipped SKU
Open every file and inspect the content. Review model names, hardware versions, frequency bands, adapter ratings, battery types, report dates, referenced standards and issuing organizations. A family report can cover multiple models and the scope of coverage should be described within the report or a formal scope letter. Models with similar names do not necessarily have identical circuits.
A battery camera deserves two parallel checks. These include product compliance for the destination market and transport evidence for the battery shipment. Project records list compliance documents for the 8185XM. Those files should be requested from the supplier rather than inferred from a product page. For a solar-powered option such as the JT-8293QJ camera, separately confirm the shipped battery, panel, adapter, and wireless version. A second product reference, the JT-9697QJ camera, does not establish a certificate scope for either model.
Instead of just referring to the MSDS for the battery, ask for a summary of the UN 38.3 testing for that battery. For each battery manufacturer and model, maintain a list of the following: cell chemistry, pack configuration, and whether the summary actually relates to the packs in the current product. If the cell or pack changes in any way, require current testing evidence before shipping.
Keep a Compliance File that Survives Repeat Orders
Confirmation of the dangerous-goods classification and of the carrier’s rules for the actual consignment must be obtained from the shipper. The buyer’s file must contain the following for the purchase SKU: approved configuration, declaration, relevant test reports, radio evidence, RoHS statement, battery transport summary where applicable, and a version log. Include a change-notification clause for radio modules, power supplies, batteries, firmware-related radio behavior, and manufacturing locations where the supplier’s scope of compliance may change.
Don’t copy a mark to a product’s copy simply because another similar model has it. The market claim must remain tied to the specific SKU it was established for and supporting evidence. While a distributor may re-box a camera, add a different adapter, or throw in a battery, their responsibilities may change. Therefore, the compliance review needs to be embedded within the product launch workflow versus being a freight booking activity. Please don’t hesitate to reach out to us.
Conclusion
Note that CE, FCC, RoHS and UN 38.3 are not generic “marks” that can be interchanged. Each of these documents must be cross-referenced to a specific market, radio & power configuration, battery, and exact revision that was shipped. The 8185XM material serves as a starting document but all current declarations and reports must be reviewed on a SKU-by-SKU basis prior to a distributor’s claim of compliance and prior to their booking of transport.
FAQ
Q1: Is UN 38.3 a camera certification?
A1: It is for lithium battery transport testing. Request a copy of the actual test summary performed on the specific cell or battery pack that was actually shipped with the product.
Q2: Does an FCC mark prove that every regional camera variant is covered?
A2: No. Check the authorization path, radio configuration, identifiers, and any host-integration conditions for the delivered version.
Q3: Can an MSDS replace a CE declaration or UN 38.3 summary?
A3: No. These documents have different purposes. Therefore keep the Safety Data Sheet, the conformity evidence as well as the summary on battery transport separate in the compliance file.
