# Champion Asia source audit **Reviewed:** 13 October 2026 (Asia/Taipei) **Scope:** Publicly discoverable pages linked from the Champion Asia group's Japanese-facing site, its product pages, three capability PDFs, three certificate PDFs, the TPCA member listing, and the supplied `.hk` domain. This is an auditable crawl of discovered sources, not proof that every unlinked or robots-blocked URL has been found. ## Deliverables - `champion-asia-page-inventory.csv`: URL-by-URL inventory with language, page type, and status (`parsed`, `reviewed`, `inaccessible`, or `suspect_not_used`). - `champion-asia-capability-claims.csv`: 91 claim-level rows with source URL, normalized value, original label, factory/entity, production tier, material, conditions, dates/freshness, evidence label, and manual-check note. ## What was reviewed The inventory covers the Japanese home, company/factory overview, about page, FAQ, design and delivery pages, product index and 21 listed product cases, news pages 1–2, column pages 1–2, three technical PDFs, three certificate PDFs, the TPCA profile, and three company/alternate domains. The 21 product case records are product examples; most do not name a production factory or volume tier, so their numbers must not be generalized into factory-wide guarantees. The main `championasia.hk` URL timed out repeatedly. The Japanese site at `championasia.co.jp` belongs to Nisshun Co., Ltd., which presents itself as a Japanese group subsidiary and describes Champion Asia group capabilities. TPCA identifies the company as Guangdong Champion Asia Electronics in Huizhou, China, and describes a Vietnam build plan. This is not evidence of a Taiwan factory. The alternate `yhcsyq.com` and `zhilincaiwu.com` pages showed company-like content mixed with gambling/spam navigation or footer elements; they are listed as suspect and excluded from capability evidence. ## Technical evidence and conditions The mass-production, sample/medium-lot, and FPC/RFPC PDFs were parsed and their important numerical rows manually compared against the extracted source text. The capability table keeps different production tiers separate. In particular, the sample/medium PDF has distinct ranges for layer count, board thickness, impedance, warpage, aspect ratio, copper weight, and line/space. The mass-production PDF is not a universal group envelope. The FPC/RFPC PDF separately describes 2–6-layer FPC and 2–10-layer RFPC, with copper-weight-specific line/space values and material names. Factory capacity figures are recorded only with the factory names and source conditions. The Longnan third factory's 300,000 m²/month is explicitly a planned overall figure; it is not treated as current operating capacity. The Japanese company pages disagree on the total number of bases/factories, and at least one capacity statement differs across materials. Those conflicts remain unresolved in the data. The product pages include detailed examples (e.g. 64 layers/12.5 mm FR-4 S1000H, 44 layers, HDI, rigid-flex, high-frequency material examples). These are cited to their individual pages, but the pages generally do not assign them to a specific factory or prototype/medium/volume tier. The dataset explicitly records that limitation. ## Certificates and freshness The ISO 9001 PDF shows an expiry of 31 August 2024, and the ISO 13485 PDF shows an expiry of 26 June 2025. Both are expired as dated on the copies reviewed; do not market them as currently valid. The UL PDF is only partially machine-parsed and its current status is not established. A list of certifications on the Japanese company page lacks linked certificate evidence and facility mapping; it is a company-published claim, not independently verified status. The company and product pages do not expose reliable publication/update dates for many technical claims. The PDFs also lack clear revision dates in the extracted text. The audit date is not a claim publication date. Planned Vietnam milestones in older news are now in the past; the current facility state needs fresh confirmation. ## Manual check boundary The numeric rows were checked against browser-extracted PDF text and source-page text. I did not render every PDF page image for a second visual/table-layout audit. `spec_03.pdf` is one page and its values were checked line by line. Certificate expiries were checked in the extracted text. The UL table has a parse warning. The inventory marks an individual rigid-flex case page where technical text could not be reliably extracted. The current files are a credible source ledger and extraction draft, not an independently audited supplier qualification. No claim means the factory has current open capacity, will accept a particular order, or will meet a buyer's drawing. Confirm factory/site, revision, production tier, material stackup, and date directly before a buyer makes a sourcing decision. ## Evidence URLs - [Champion Asia / Nisshun Japanese-facing site](https://www.championasia.co.jp/) - [Group company and factories](https://www.championasia.co.jp/company/) - [About](https://www.championasia.co.jp/about/) - [Product index](https://www.championasia.co.jp/products/) - [FAQ](https://www.championasia.co.jp/faq/) - [Mass-production PCB capability PDF](https://www.championasia.co.jp/file/spec_01.pdf) - [Sample and medium-lot PCB capability PDF](https://www.championasia.co.jp/file/spec_02.pdf) - [FPC/RFPC capability PDF](https://www.championasia.co.jp/file/spec_03.pdf) - [TPCA member profile](https://www.tpca.org.tw/en/company_infor.php?no=1401) - [Supplied `.hk` domain](http://www.championasia.hk/) ## Suggested ongoing tracking fields For a maintained research dataset, add `record_created_at` and `record_updated_at` (ISO 8601, including timezone or UTC), plus `source_last_checked_at` and `source_published_or_revision_date`. Keep these separate: the date we captured/edited a record is not the date the manufacturer published or revised the claim. Also consider `record_id`, `source_page_title`, `source_language`, `claim_translation`, `translation_method`, `reviewer`, `verification_status`, `verification_method`, and `next_review_due`. The current CSVs have a source date/freshness field but do not yet include record creation/update timestamps.