Get help with SellerHint

How do I contact support?

The support page lists the contact channels and the information worth including. Support contact details are being finalised and will be published before the product is offered.

What information should I include in a bug report?

What you were trying to do, what you expected, what happened, the steps to reproduce it, any exact error text, and your product and version along with your macOS version or browser.

Remove buyer names, addresses, phone numbers and email addresses from screenshots first, and never send passwords, tokens, API keys or full payment card numbers.

Read the documentation

Where can I see known incidents?

The service status page lists the components being tracked and any current or recent incidents.

Where can I request a feature?

On the feature request board. Submit a request there, and vote on the ones other subscribers have already asked for. Describe the problem and the workflow rather than only naming a feature, because that is what makes a request actionable.

Who can submit and vote on feature requests?

Subscribers on a paid plan: Pro on SellerHint for Mac, with a Mac App Store subscription, and Pro or a custom plan on SellerHint Web.

Reading and searching the board are open to everyone, so you can check whether your request already exists before you decide on a plan. Only the submission form is limited to paid plans.

What happens if I request something that has already been requested?

Search the board before you submit. If the same request is already there, vote on it instead of sending it again — a repeat is removed from the request list rather than published twice, so the count on the original stays worth reading.

If something on the board is close but not the same as your request, say so when you submit and explain how yours differs.

Does a feature request with the most votes get built?

Not automatically. Votes show how widely a problem is felt, and that is one input into what gets built. A request with many votes can still be declined, and when it is, the reason is published on the board rather than the request being deleted or left open.

Anything accepted moves to the public roadmap, where its scope and exclusions are stated. No release dates are published on either page.

What do the statuses on the feature request board mean?

Open means received and published for other subscribers to vote on. Under review means it is being read properly. Under consideration means it is understood and being weighed against other work. Planned means accepted as work to do. In progress means it is being built. Shipped means released, and where a changelog entry has been published it states what changed.

Not planned means considered and declined, with the reason published rather than the request being deleted or left open. There is no status for a duplicate, because a repeat is removed from the list instead of becoming a second entry.

Where can I see recent changes?

The changelog lists releases per product and channel. There are no public releases yet.