Every seller I have talked to who runs three or more Amazon marketplaces describes the same daily hazard. Seven browser tabs, each with its own Seller Central logged into a different country, and the layout of every tab is almost identical to the next one. Almost. Just different enough that the wrong action happens on the wrong marketplace once a week, and once a quarter it costs real money.
The dashboard people build to escape that usually replicates the shape of the problem. Seven tabs turn into seven sidebar sections. The seller adds one dashboard to memorise on top of the seven Amazon layouts. Nothing has been simplified. Something new has been added on top.
OttoCentral is our attempt at the other direction. The panel has one inventory view, one orders view, one report view, and every one of them takes a marketplace as an input. When you switch the marketplace, the shape of the page does not change. What changes is what fills the columns you already know.
Mental models beat feature lists.
The reason a spreadsheet works for a lot of sellers is not that spreadsheets are powerful. It is that the seller only has to learn one grid, and every problem gets shaped into rows and columns. The mental model is the whole product. The features are consequences of it.
A multi-marketplace panel wants the same property. One grid, filtered by marketplace, with the same shortcuts and the same keyboard behaviour everywhere. What the marketplace switcher changes is data; what stays constant is the shape of the tool.
What the shared shape actually buys.
- A seller who onboards on US and later adds Germany does not re-learn the panel. The German column shows German prices and German taxes, but the workspace is the same workspace.
- Cross-marketplace questions become obvious. "Is this SKU out of stock anywhere?" is a filter, not a query across seven tabs.
- Support gets simpler. There is one thing to teach a new hire. Marketplace-specific quirks show up inline as callouts on the rows they affect, not as separate pages the hire has to learn.
The tradeoff.
A shared shape means we do not lean into every marketplace's quirk with its own custom UI. Amazon Japan does a couple of things Amazon US does not; Amazon UK has a VAT surface the others do not. Our answer is to render those differences as local details on the same row, not as a whole different page. The seller keeps the mental model; the exceptions surface as exceptions, in place.
The tradeoff is legible. A marketplace with a strong idiosyncratic workflow will always be a couple of clicks less native in a shared panel than in a marketplace-only tool. That is a cost we accept, because the alternative is asking a seller to learn a new tool per marketplace, and we started this project because we watched that cost eat weeks of onboarding.
What one panel does not fix.
Amazon still runs its own rules. Marketplaces still have their own fee schedules, their own suspension policies, their own PII treatment, their own listing quirks. A panel cannot flatten any of that away and pretending it can is dishonest. What a panel can do is stop making the shape of the tool one more thing the seller has to keep in their head.