On this page7 sections
Compatibility gate
Make the product pass five yes-or-no questions
Exact identity
Can the product code and version be preserved on the quote and package?
Device match
Are supported operating systems, models, connectors and functions named?
Power match
Are input, charging method, battery and included power accessories stated?
Market match
Are language, radio, labeling and responsible-party requirements addressed?
Support match
Is the process for dead-on-arrival or incompatible units written down?
Version sheet
The same product name can hide a different unit
Keep a version sheet beside every candidate. For wireless earbuds and Bluetooth earphones, record the stated Bluetooth version or supported profiles only when the source provides them. Add codec or app details when they change how the item will be used.
Also record connector type, microphone, control behavior, charging case, included cable and replacement tips. “Works with phones” is not a useful compatibility statement.
Device families
Ask a different deciding question for each category
| Device type | Questions to settle first |
|---|---|
| Smartwatch | Supported phone systems and versions, app source, languages, sensors, charging and update path. |
| Phone accessory | Exact device generation, connector, dimensions, power rating and included parts. |
| Wireless earbuds | Pairing, controls, microphone, battery statement, case input and individual-unit test. |
| Supplier or distributor | Which legal business, product version and after-sales responsibility the claim identifies. |
Sample bench
Test the functions a real user will notice
- Photograph the item, code, package label and included parts before testing.
- Pair or connect with at least the intended supported device type.
- Check charging, buttons, microphones, channels, indicators and reset steps.
- Repeat the same short checklist across more than one unit when possible.
- Record observed run time as a dated sample result, not a universal battery promise.
- Record errors, on-screen messages and firmware information exactly as shown.
Route and carton
Batteries and radio products need current route checks
Ask the carrier or logistics service which battery, radio, documentation, packing and destination rules apply to the exact shipment. Record whether batteries are installed, packed with equipment or shipped separately, plus watt-hour information where applicable.
Keep product net weight separate from final packed weight. A catalog page or chat contact cannot determine route acceptance, customs treatment or regulatory obligations.
Failure plan
Decide who handles an unusable unit before ordering
Write down the test window, evidence required, exclusions, return destination, repair or replacement path and who pays each transport cost. A percentage promise is incomplete if the method for reporting failures is missing.
Pause when the model changes between page, chat and invoice; when required documents cannot be linked to the exact version; or when payment is requested before the compatibility and responsibility record is complete.
