A seller account health checklist has one rule that matters more than any item on it: read every store's health page on the same day each week, write the numbers down with the date, and compare them with last week's. Amazon, eBay and Etsy each grade different things, over different windows, on different schedules. A weekly reading catches a number going the wrong way while there is still time to fix the cause.

Each marketplace sets its own rule on how many seller accounts one business may run, and some require approval before a second. Mosaic keeps stores you are entitled to run apart; it does not change what a marketplace allows.

Why one look at the dashboard is not enough

A health page shows the number as it stands today. It does not show yesterday's, and that is the number you need, because the direction tells you more than the level.

The windows make it worse. Each metric looks back over its own period, and the page prints that period beside it. A short window reacts to one bad week at once and forgets it soon after. A long window barely moves for a single late parcel, then holds it for weeks after you fixed the carrier. Two stores with the same bad week can show it on different days, on different metrics, and one of them may not show it yet.

Write the recipe once, then make forty profiles from itIn Mosaic: Presets and extensions. One recipe, forty profiles, forty exits. Free holds 3 profiles. Pro is $49 a month for any number.

How it works: Presets and extensions

What each marketplace counts

The three dashboards do not translate into each other, so read each one on its own terms.

Amazon's Account Health page in Seller Central splits into customer service performance, where the order defect rate gathers negative feedback, A-to-z Guarantee claims and chargebacks, then policy compliance, and shipping performance with late shipments, cancellations before dispatch and valid tracking. The Account Health Rating sums up policy compliance only. A clean rating with a rising defect rate is a store with a problem.

eBay's Performance tab in Seller Hub gives a seller level, Top Rated, Above Standard or Below Standard. It is set by transaction defects, late shipments and cases closed without seller resolution. eBay evaluates on a fixed day each month, over a look-back that depends on how much you sell. A bad fortnight can therefore show up in this month's grade or the next, depending on where it falls.

Etsy's Star Seller figures in Shop Manager are three numbers: how quickly you answer first messages, how many orders ship on time with tracking, and the share of five-star reviews. They are assessed over a run of recent months, which makes them slow to recover once they drop.

The weekly account health checklist, store by store

The daily round is for new warnings and messages (the morning routine across six stores covers it). The weekly pass is a reading, not a reaction.

  1. Pick one day and keep it. Comparing Tuesday's numbers with the previous Friday's mixes two windows.
  2. Open every store's health page. Copy each metric, its target and its window exactly as the page prints them.
  3. Write them under that week's date, one block per store, so next week's reading sits right below.
  4. Mark anything that moved toward its target line two weeks running. That is the list to act on, whatever its level.
  5. Read the policy and performance notices on the same pass. A warning that arrived midweek, while you were in another store, is the item most often missed.
  6. Fix the cause, not the metric: a carrier, a handling time or a listing that keeps drawing the same complaint.

The only part that needs judgement is step 4. The rest is copying.

Where several stores make it hard

With four stores across three marketplaces, the weekly pass is mostly signing in and out of one browser, and the risk is reading the right page in the wrong store. If two of them are Amazon and eBay selling the same stock, the mistakes cross over as well (selling on Amazon and eBay together is about that overlap).

In Mosaic each store is its own profile, with its own cookies, fingerprint and proxy, and it stays signed in between weeks. We would set the pass up like this:

  1. Put the business's stores in one project, one profile per store.
  2. Add each store's health page to that profile's Start pages, so it opens as a tab on launch.
  3. Tag the stores the weekly pass covers, for example "health weekly", and filter the table to that tag. How we split projects, tags and owners is in projects, owners and tags.
  4. Select them all and start them together from the bulk bar.
  5. Keep the weekly readings in each profile's notes in the companion, so the history sits beside the store it describes.

The routine is the same with or without us. What a separate profile per store changes is that you never read one store's numbers while signed in to another, and that a second Amazon store in the same window no longer signs the first one out (Seller Central keeps logging out traces that to the cookie jar).