Published August 15, 2026 · RetroForge Supply Team
Cartridge PCB Quality Control: Write an Order-Specific Inspection Plan
A useful quality plan connects the approved product to measurable checks. Name the board, game file, target hardware and acceptance criteria, then state which units or samples each check covers.
On this page 4 sections · jump to what you need
Review materials and assembly
Identify the approved board revision, components, connector finish and shell. Agree how substitutions are handled. For assembly, specify the visual or optical checks relevant to the board, the handling of failed results and any evidence needed.
A factory photograph or an AOI PASS screen does not establish that every unit in your order has received a particular inspection. Ask for the actual project plan.
Define programming and functional checks
- The approved game-file reference and programming verification method.
- Boot and representative gameplay on the named hardware.
- Save, reload and power-cycle behaviour where applicable.
- Any title-specific features or extended checks.
- Coverage, test duration where relevant, and the record of results.
If you need every unit to receive a defined test, request that explicitly and obtain confirmation. Sample testing and full-unit testing are different commitments. Neither should be implied by the word “QC”.
Include the finished retail unit
Inspect shell fit, labels, print version, accessories and quantities inside the package. Agree acceptable cosmetic variation and the transit packing configuration. A board can pass a functional check while the retail set is still incomplete.
Agree release and issue handling
Define which records you review before dispatch, how exceptions are approved and how failed goods are contained or reworked. Confirm the applicable inspection, claim and remedy terms in the accepted order documents and terms of service; this guide does not introduce a separate warranty or fixed claim period.
Do not use an unsupported industry defect percentage as your acceptance standard. A sampling plan needs its own agreed basis, sample size and acceptance criteria; it is not the same as a guaranteed field-failure rate.
Share the platform, board requirements and desired checks through the process and quality review. The final plan should be specific enough that both teams can tell whether the order has met it.
Reviewed October 17, 2026 · RetroForge Supply
Prepare a PCB enquiryWhat to include in your first message
Share what you know. Note anything that still needs a review; project files are not required for the initial enquiry.
- Platform, target hardware and board reference
- Design files available and engineering still required
- Memory, save, programming and electrical requirements
- Shell fit, connector finish and acceptance checks
- Quantity, delivery country and target date
FROM THE GUIDE TO YOUR PROJECT
Put the hardware requirements in focus.
Share the platform, board requirements and files you can provide. Confirm programming, fit and inspection scope with the sample.
Keep planning.
Explore boards & programming ↗Choose fixed-program, rewritable or microSD Game Boy cartridges. Specify usable save RAM, program loading, backup steps and wholesale quote scope before…
Read the guide Boards & engineeringNES Homebrew Cartridge Compatibility: What to Test Before ReleaseCheck NES homebrew cartridge compatibility before a physical release: mapper, save behavior, original hardware, clones and a versioned sample test record.
Read the guide Boards & engineeringAOI Inspection for Cartridge PCBs: What a PASS Result EstablishesUnderstand the role and limits of optical inspection, then specify the electrical, programming and functional checks needed for a cartridge order.
Read the guide