1. Identity and SKU verification
We record the physical SKU, storage label, firmware/build identifier, processor information available from the system, included accessories and packaging. If two supplier documents disagree, the claim stays unpublished until the shipped unit is checked.
2. TV and HDMI setup
We connect the unit to more than one HDMI display class where practical, confirm boot behavior, menu readability and output negotiation, and note any television settings that materially change the experience. “Compatible with an HDMI TV” is tested separately from claims about output resolution.
3. Controller behavior
We verify how each included controller connects, which receiver or battery type it uses, whether both controllers can operate in local multiplayer, and whether normal couch-distance input remains stable. We also document the pairing/reset steps that support teams can reuse.
4. Storage and software image
We confirm the visible storage capacity and, when relevant, the library image attached to each capacity tier. Game or system counts are treated as SKU-specific inventory facts, not evergreen marketing numbers. Individual title compatibility can vary by emulator and should not be represented as universal.
5. Real use and support notes
We time a normal first boot, navigate the library, launch representative categories, save/exit where supported and intentionally reproduce common failure points such as wrong TV input or an unpowered controller. The final support guide should reflect what a first-time buyer actually sees.