Table of Contents
What’s a ChemSHERPA-CI File?
If you're supplying parts to a regulated supply chain, especially in electronics, automotive, or industrial manufacturing you’ll be asked for a ChemSHERPA-CI file.
It’s not optional anymore. It’s the Component Information (CI) file in XML format that documents:
- What materials are in your product
- Which substances are included
- Whether those substances are flagged under REACH, RoHS, etc.
- And who supplied what
It’s your compliance passport to reach Tier 1 and OEM customers—especially across Japan, Korea, and global electronics ecosystems.
Before You Start: What You’ll Need
Here’s your pre-game checklist:
- Your product’s BOM (Bill of Materials)
- Full material composition for each part
- Supplier-level substance declarations
- REACH SVHC and RoHS thresholds flagged
- Weight data (mg or g) for each component
- Either:
- JAMP’s free ChemSHERPA data entry tool*, or
- A compliance platform* that auto-generates ChemSHERPA-CI XML from your product structure
Step-by-Step: How to Create a ChemSHERPA-CI File
- Step 1: Download the Right Tool (If Doing It Manually)
- Go to the official JAMP ChemSHERPA portal
- Download the ChemSHERPA Data Entry Tool (CI Tool) — latest version (2025)
- Make sure your system supports Japanese locale if needed
If using a platform like Acquis, you can skip manual XML entry, data flows from BOM imports.
- Step 2: Input Product Header Information
This includes:
- Part name & ID
- Manufacturer/supplier name
- Contact info
- Version + date
- Unit weight and quantity
Pro Tip: Match part numbers exactly to the PO or contract terms your customer is using. Any mismatch may trigger rejections.
- Step 3: Add Material Declarations
For each component:
- Define the material type (plastic, metal, etc.)
- Assign a JAMP material class code
- Add weight in mg/g
- Define its relationship to the parent part (e.g. solder in PCB)
Don’t guess. Ask suppliers for actual weights or use lab data if needed.
- Step 4: Add Substance-Level Detail
Now the compliance layer begins:
- Add all known substances in the material
- Use CAS numbers for accuracy
- Flag any that are on the REACH Candidate List
- Check RoHS thresholds (0.1% / 0.01%)
- Add reasons if not disclosed (e.g. proprietary, unknown)
ChemSHERPA automatically flags when SVHC limits are exceeded.
- Step 5: Validate Your File
Once you’ve entered all data:
- Run ChemSHERPA’s built-in validation checks
- Fix any structural errors or missing fields
- Export the XML file (.shci format)
Most errors happen due to:
- Mismatched weights
- Missing CAS numbers
- Improper material group codes
- Typo in supplier info
- Step 6: Submit or Upload
- Send the XML to your customer or
- Upload it to your compliance portal
- Archive the file with version control
OEMs may validate using their own tools. If it fails validation, you’ll be asked to resubmit—so get it right the first time.
Common Mistakes (Avoid These)
- Weight totals don’t match BOM
- “Unknown” substances used without justification
- SVHC >0.1% not flagged
- Using outdated JAMP schemas
- Missing supplier traceability (name + email mandatory)
Don’t Let XML Stop You
If you're still trying to piece this together manually, you're burning time and opening yourself up to failure. We help manufacturers create ChemSHERPA-CI files at scale with no manual entry, no error loops, and no supplier excuses.
Want a done-for-you solution?