Feature requests
Anyone can read and search the board. Submitting a request and voting are for paid subscribers. Every entry carries its current status, so you can see what has been accepted, what is being weighed, and what has been declined and why.
7 entries on the board — 3 open, 2 shipped, 0 submitted by subscribers. Yours would be the first.
Sellers reasonably expect two products from the same brand to share information, and today they share nothing.
SellerHint’s response: Already on the public roadmap. No synchronisation exists today, in either direction
Campaigns could be reviewed in SellerHint but had to be created on eBay, so setting one up meant leaving the workspace and losing context.
SellerHint’s response: Already on the public roadmap. Cross-store campaign creation is not planned
Sellers who are away from their Mac have no way to review orders, messages or inventory in SellerHint.
SellerHint’s response: Already on the public roadmap. No synchronisation with SellerHint for Mac is included
Judging whether a campaign is working meant exporting reports from the marketplace by hand.
SellerHint’s response: Already on the public roadmap. Attribution modelling and forecasting are not in scope
Small teams sometimes want to split order and message work between people.
SellerHint’s response: Already on the public roadmap. Not planned for either product. There are no seats, roles or permissions.
You can now read and reply to a case in SellerHint, but resolving one — refunding, escalating, accepting or declining a return, closing it — still means going to eBay at the point where speed matters most.
SellerHint’s response: Already on the public roadmap. Responding to a case is already available and is not part of this item
Some sellers list on more than one marketplace and manage each one separately.
SellerHint’s response: Already on the public roadmap. SellerHint is currently centred on eBay seller operations
A status is a summary. Where a request is tracked on the public roadmap, that entry carries the full scope and the exclusions, and the card links to it.
What were you trying to do, and what happened instead? A problem can be solved several ways. A feature name on its own often cannot be acted on at all.
The workaround you already use — a spreadsheet, a second browser tab, a manual check before every dispatch — is usually the clearest description of the gap.
Once a quarter and forty times a day are different problems, even when the ask sounds identical.
SellerHint for Mac and SellerHint Web are separate products. Saying which one you are working in, and which workspace, keeps the request from being read against the wrong behaviour.
If your ask is already here, voting on it is worth more than a second entry. Duplicates are merged into the original so the count stays meaningful.
Never include a password, an authentication token, an API key, or buyer payment details. Screenshots are helpful; check what is in them before sending.
Reading and searching the board are open to everyone. Sending a request needs a paid plan, so the board stays small enough for every entry to be read by hand.
No paid plan yet? See what each plan includes.
A feature request is the right route for something SellerHint does not do yet. For something that is broken, behaving unexpectedly, or blocking work right now, use support instead — it is read sooner and does not wait on a vote.
SellerHint