Amazon's new Seller Central experience: Account Health evidence checks

Amazon's official Seller Forums guidance says the new Seller Central experience groups work into areas such as My Business, Products, Supply Chain, Orders, Finance, Customers, Marketing, and Action Center. Recent forum activity shows sellers are still adjusting to that navigation while Amazon says account data and settings stay unchanged.

For US sellers, and for UK sellers managing Amazon.com or comparing Amazon.co.uk workflows, the risk is not the redesign itself. The risk is answering an Account Health, performance, finance, return, or catalog problem from the wrong workspace and losing the evidence trail before Amazon reviews the case.

Short answer: map the notice before you respond

A Seller Central workspace change can make a broad problem look scattered. The first job is to identify the one Amazon record that is driving the next action, then collect the surrounding evidence without changing settings too early.

• Screenshot the Action Center, Account Health, Performance Notifications, and any appeal or document-upload screen tied to the issue.
• Record the marketplace, notice date, policy name, case ID, ASIN, SKU, order ID, transaction ID, or verification request shown on the task.
• Save the old navigation path if your team used it, plus the new workspace where the same record now appears.
• Export the report or dashboard behind the signal before editing listings, shipping templates, return settings, bank details, or business information.
• Keep Amazon.com and Amazon.co.uk records separate when the same account team manages both marketplaces.

Separate workspace location from case type

The new layout can group tools more cleanly, but Amazon still reviews different problems through different logic. A seller who treats every task as a generic Account Health case can blur the root issue.

• Use performance evidence when the problem is Order Defect Rate, Late Shipment Rate, Valid Tracking Rate, cancellation rate, or customer-impact metrics.
• Use finance evidence when the live blocker is a reserve, deferred transaction, negative balance, reimbursement, fee debit, or unavailable disbursement.
• Use catalog evidence when the record points to ASIN identity, variation structure, product-detail accuracy, brand authorization, or compliance attributes.
• Use verification evidence when Amazon asks for identity, entity, bank, tax, address, or document consistency records.
• Use support-case evidence only to show what was already asked and answered; it should not replace the underlying order, ASIN, finance, or policy proof.

Build a cross-workspace evidence packet

Most recovery files now need evidence from more than one workspace. That does not mean the appeal should become longer. It means the seller should know which workspace supplies which proof before writing the response.

• From Orders, preserve order status, ship-by date, delivery promise, tracking, return, refund, buyer-message, and A-to-z claim records.
• From Finance, preserve Payments, Transaction View, reserves, adjustment lines, reimbursement entries, chargebacks, and disbursement status.
• From Supply Chain or inventory areas, preserve FBA shipment IDs, receiving quantities, stranded inventory, reserved units, removals, and reconciliation records.
• From Products, preserve the ASIN page, contribution history, variation family, brand attribute, compliance status, and recent listing edits.
• From Customers or performance areas, preserve feedback, Voice of the Customer, service-quality signals, contact reasons, and buyer-impact patterns.

Audit team habits after the switch

A redesign can expose weak internal routines. One user may still look for the old page, another may answer from the new task screen, and a third may change settings without preserving the original state. That creates avoidable contradictions.

• Assign one owner to freeze evidence before any team member edits settings or submits a response.
• Update internal SOPs with the new workspace path for Account Health, Orders, Finance, Returns, Listings, and Cases.
• Review user permissions so only trained staff can submit appeals, upload verification documents, edit banking data, or change critical shipping settings.
• Keep a short change log when a setting is corrected, including who changed it, why, and what evidence was preserved first.
• After each case, note which workspace actually held the decisive record so the team does not repeat the wrong search path.

The new Seller Central experience should usually be handled as an evidence-control issue, not an appeal argument. It becomes a recovery problem when the seller misses a task, answers from the wrong record, uploads mismatched documents, or mixes finance, performance, catalog, and verification facts in one unclear case.

The practical closing test is whether a reviewer can follow one clean chain: the Amazon task, the workspace where it appeared, the exact case type, the evidence preserved before changes, and the narrow response that answers that case. If that chain is still unclear, return to the performance or Account Health owner context before another submission makes the record harder to defend.