Amazon Says Your Product Contains a Button or Coin Battery—but It Does Not: What Evidence Proves It?

Begin with an unopened production unit from the exact variation and revision now sold. Record the package identifier, ASIN, model, lot or revision mark, and date. Then open and inspect the full system. The point is not to accumulate photographs; it is to eliminate plausible places where a coin cell could exist.

1. Follow every power path in the main unit. Inspect external inputs, primary compartments, service panels, internal backup or memory cells, clocks, displays, and detachable modules. A product described as “AC-powered” may still contain a backup cell.
2. Open the remote and every controller. Show each control beside the main unit, then record its model mark, closed compartment, open compartment, and installed cell. “The main unit has no battery” does not answer what powers the remote.
3. Inventory every included accessory. Check sensors, key fobs, timers, thermometers, lights, microphones, styluses, wireless triggers, spare modules, replacement parts, and separately packed batteries.
4. Read every customer-facing record. Search the manual, quick-start guide, packaging, inserts, QR-linked instructions, and replacement-parts material for battery designations and version-specific directions.

Next, compare variations. A black and a white model, a two-pack and a single unit, or a U.S. and international version may have different remotes or backup cells. Do not borrow evidence across child ASINs merely because the products look similar. If old and new inventory are mixed, the immediate task is version control—not an appeal asserting one universal configuration.

A false classification can survive a text edit because the remaining record still describes a coin-cell product—or because the edit did not resolve which model is being sold. Amazon has not published the logic or weight used to classify these ASINs. Treat the following as audit points supported by policy fields and recurring seller cases, not as a claim that any single word automatically triggers a flag:

1. Read the title, bullets, and description as a reviewer would. Look for a wrong battery designation, a generic “battery-powered” claim, or language copied from an older revision. Replace only inaccurate wording with the exact current power source.
2. Inspect A+ Content, images, and video. An obsolete coin-cell diagram, old remote, mismatched compartment, or render from another variation can contradict the physical product. Replace it with current, unedited product evidence.
3. Open every manual and linked file. A generic family manual, legacy CR2032 instruction, or wrong model number can preserve the old classification after the visible listing is corrected. Publish the correct version-specific file and keep the revision record.
4. Compare the battery and power-source attributes. Check the battery type, “batteries included” status, quantity, rechargeability, and power-source fields. A CR2 entered as CR2032 is a factual error; a real CR2032 value is not something to delete for approval.
5. Audit parent and child ASINs separately. One variation may inherit an image or claim from a sibling that uses another remote or battery. Separate materially different configurations instead of borrowing evidence across them.
6. Trace old contributions and prior revisions. If earlier content described a coin-cell design, document what changed, when it changed, which lot adopted the new design, and which revision is now offered or stored at FBA.

Seller reports illustrate the range. In a June 2025 case, the seller said early detail-page content referred to a coin-cell remote while the final production remote used AAA. In a different February 2025 case, references to CR2032 were truthful because the USB-powered product replaced that cell. The first situation calls for version reconciliation; the second calls for an explanation that preserves accurate compatibility language.

The strongest packet is not a stack of unrelated files. It is a traceable chain:

1. ASIN and variation: identify the exact child ASIN, marketplace, title, and seller SKU.
2. Model and revision: connect the ASIN to the model, part number, production revision, lot, or date code visible on the physical unit and package.
3. Complete configuration: list the main unit, remote, controller, accessories, separately packed batteries, and replacement modules included with that variation.
4. Power-source map: identify each power input and each cell by manufacturer, designation, quantity, location, replaceability, and function.
5. Technical record: connect the model to the current manual, bill of materials or electrical specification, and exact battery manufacturer datasheet.
6. Catalog record: compare the same facts with the live detail page, backend attributes, images, manuals, and parent-child structure.
7. Appeal conclusion: state whether any component contains or is designed to use a cell meeting the federal definition, and identify the evidence that supports each factual premise.

This chain prevents a common identity gap: the seller submits a battery datasheet, but nothing proves that the datasheet belongs to the battery installed in the photographed remote; or the photographs show a model, but nothing connects that model to the appealed ASIN.

Build the packet fact by fact. Strong evidence is contemporaneous, model-specific, internally consistent, and understandable without guessing. Supporting evidence adds context. Weak evidence may be true but fails to connect the product, power source, and ASIN.

The wording below comes from Amazon’s public help material, Amazon moderator responses, or notices quoted by sellers. Seller-quoted text is not a federal conclusion and may not be a universal Amazon template.

Amazon announced on May 22, 2025 that product and food safety compliance requirements would move from Manage Your Compliance into Policy Compliance within Account Health, beginning May 29, 2025, with migration expected to finish in July 2025. See the official migration announcement. Some 2026 screens or moderator replies may still use a Manage Your Compliance label, but it should not be presented as the universal current starting point.

Amazon’s current public appeal instruction and an April 16, 2026 moderator response in a thread opened April 14 describe this route:

1. In Seller Central, go to Performance, then Account Health.
2. Open the Product policy compliance tab and the applicable issue type.
3. In Next steps, select Submit for the affected product.
4. Select Appeal requirement.
5. Choose the reason that matches the request.
6. Explain why the requirement does not apply or why the product was incorrectly identified.
7. Submit through that action.

Labels and available fields can vary by account and request, and the signed-in action panel controls. If a true in-scope notified ASIN is directed to Amazon’s authorized third-party testing, inspection, and certification channel, follow that route; the official TIC page explains that an authorized provider may submit validation information to Amazon. Do not assume every in-scope request permits self-upload, and do not use the TIC route to manufacture evidence for an out-of-scope product.

A June 8, 2026 Amazon moderator response in a thread opened June 4 addressed a specific LiPo appeal in which the first form had no attachment control but created a case after submission. The moderator instructed that seller to add the six-sided images, battery evidence, manufacturer declaration, and manual pages directly to the existing case. This is useful case-specific guidance, not a public guarantee that every appeal creates the same case or upload option. Do not invent file limits or send documents to an unrelated email; follow the controls and linked case available for the ASIN.

Write the explanation as an evidence map rather than an emotional history:

1. Identify the request, ASIN, exact child variation, model, and revision.
2. State the complete sold configuration and every power source, including remotes and accessories.
3. Apply the federal definition narrowly: explain why no identified cell has diameter greater than height and why no component is designed to use one, if that is true.
4. Identify any inaccurate catalog data that was corrected, with dated before-and-after evidence.
5. Index each attachment and state the single fact it proves.
6. Ask Amazon to remove the button/coin-battery compliance requirement from the identified ASIN because the documented configuration is outside that classification.

Across the reviewed seller cases, repeated rejection was common and a published final resolution was usually absent. The threads do not prove why Amazon rejected any individual packet, but they expose recurring evidentiary gaps:

1. Identity gap—the evidence does not reach the ASIN. A text-only denial proves neither the physical configuration nor the model, cell, or complete sold set. Photographs may also omit the model label; a datasheet may cover a different cell; the declaration may name a product family; or the submitted manual may belong to another variation.
2. Configuration gap—only the main unit is shown. The remote, controller, backup cell, sensor, spare module, or separately packed accessory remains unaccounted for.
3. Visual gap—the compartment never proves the cell. Six exterior sides show no battery; a closed cover hides the compartment; or a loose AAA cell is photographed away from the product.
4. Catalog gap—the listing still contradicts the packet. A backend attribute, A+ image, manual, parent contribution, or legacy revision still identifies a coin cell or a different product.
5. Authority gap—a letter asserts more than its basis supports. An unsigned or generic manufacturer letter, unrelated laboratory report, SDS, or certificate does not establish the exact design and revision.
6. Scope error—the seller’s legal premise is wrong. The product accepts a CR2032 but the appeal rests on “battery not included,” or a coin-cell remote is omitted from the analysis.

Reusing the same explanation and files does not address any of these gaps. Nor does commissioning a UL 4200A report that pretends a nonexistent coin-cell design was tested. After a rejection, create a four-part delta log: what Amazon said, what the prior packet proved, what remained unproved or contradictory, and what genuinely new evidence now resolves it.

One March 2026 seller case eventually showed an active ASIN after the seller changed an ambiguously used word “buttons” to “keys” and added an image of the AAA remote. That is a confirmed case-specific outcome, not proof that either edit caused reinstatement and not a universal recipe.

If no part of the exact ASIN—including the main unit, backup circuit, remote, controller, and included accessories—contains or is designed to use a button or coin battery, an Amazon button cell battery misclassification should be answered with one coherent record: ASIN and model identity, complete configuration, exact power-source evidence, current revision, truthful catalog corrections, and an indexed appeal submitted through Account Health.

If any component is designed for a covered cell, the absence of that battery from the box does not create an out-of-scope case. Follow the current in-scope request instead. The decisive distinction is not what the seller hopes the ASIN to be; it is what the documented product actually is.