Published August 15, 2026 · RetroForge Supply Team

Published August 15, 2026 · RetroForge Supply Team

The sample run is where a cartridge project succeeds or dies. Here is what happens between the day you send a ROM file and the day a working prototype lands on your desk, written from the production side.

Buyers tend to treat sampling as a formality. It is a filter. A surprising share of projects change something during the sample stage, whether that is the mapper board, the shell color, or the label finish. The buyers who budget time for two sample rounds almost always ship on schedule. The ones who plan for zero revisions are the ones writing panicked emails in week six.

What You Send Us on Day One

A sampling quote can be prepared from less than you think, but a smooth one needs four things:

• The ROM file. A dump or compiled binary, in the format your target console expects. If you built the game in an emulator-first workflow, tell us which one, because emulator quirks occasionally hide real hardware bugs.
• Mapper or board details. If your title uses a mapper (MMC1, MMC3, and similar for NES projects), we need to know. The wrong mapper means a cartridge that boots fine in an emulator and shows nothing on a real console.
• Shell specification. Color, and whether you need a custom mold or an off-the-shelf shell. Off-the-shelf is cheaper and faster; custom molds add tooling cost and weeks of lead time.
• Label artwork. Print-ready files, ideally vector. We can work from a flat PNG for prototypes, but production runs want proper source files.

One note on rights: we will ask you to confirm you hold the rights to the game data and any artwork before production sampling starts. This protects you as much as it protects us.

Week One: ROM Validation

Before any parts are ordered, the file itself gets checked. Checksums are verified against what you sent, because corrupted transfers do happen and a bad checksum is a five-minute fix at this stage and a disaster later. ROM size is matched against the board layout. Mapper compatibility is confirmed against the boards we stock.

If something does not line up, you hear about it now, with specifics. A factory that reports no problems at validation on every single project is a factory that is not checking.

The First Prototypes Are Hand-Built

First articles are not run on the production line. A technician assembles them by hand, usually two to five pieces, using the same components the bulk run will use. This matters: a sample built from different memory chips than your production lot tells you nothing about your production lot.

Each hand-built unit then gets tested on real hardware. Not one console. Several, because console revisions differ in ways that emulators smooth over. A cartridge that works on a front-loader and glitches on a later revision needs to be caught in the sample room.

What Testing Covers

Our standard sample test pass:

• Boot test on multiple console hardware revisions
• Full playthrough or extended soak run of the title, not just the title screen
• Save memory check where the game uses battery or flash save, including power-cycle behavior
• Fit check: shell seams, label alignment, contact with the cartridge slot

The soak run is the one buyers skip when they self-test, and it is the one that finds intermittent faults. A cartridge that crashes once in four hours of play has a problem, even if it boots perfectly every time.

Revision Rounds and What They Cost

Most projects need one or two rounds. Common changes and their usual impact:

Sample work is billed as engineering time plus parts. For a typical NES or SNES project with stock shells, first samples run a few hundred dollars. That number scales with board complexity, not with how many units you eventually order.

A Realistic Timeline

From cleared artwork and confirmed ROM to shipped first samples, plan on two to three weeks for a stock-shell project. Add a week if the board needs sourcing outside our standard inventory. Custom molds sit on their own schedule entirely and should be quoted before anyone commits to a launch date.

Bottom Line

Sampling is cheap insurance. Treat it as a scheduled phase with a budget of one or two revision rounds, send complete files up front, and test the samples you receive on real consoles for more than five minutes. Do that and the bulk order becomes routine.

Start your sampling quote