About SellerHint | SellerHint

The problem it exists to solve

Selling on eBay at any scale creates a second job behind the listings. Product information ends up spread across spreadsheets, folders and marketplace screens. The same change gets made repeatedly, store by store. Quantities drift. It becomes unclear which store a particular record belongs to, and a routine edit can reach a live listing before anyone intended it to.

None of those tasks is difficult on its own. They are difficult because the information needed to act is scattered, and because acting on the wrong assumption reaches something that is still selling.

SellerHint is built around that operational work: keeping product information organised, preparing changes carefully, reviewing what is happening across stores, and making the boundary between your records and the marketplace explicit.

What the name means

SellerHint is the moment a complicated seller task becomes clearer — and the system that gets you there.

The hint is the organisation, context and information that makes the next action obvious. Not a tip, and not advice: the product does not tell you what to do with your business. It arranges the work so that what needs doing is visible, and leaves the judgement to you.

The mark

The light bulb is the moment of clarity. The S inside it is the system behind that moment — the catalog, the store scoping, the comparisons and the warnings that have to be in place before anything can look simple.

Clarity

You can tell what you are looking at, without inferring it.

Order, payment, fulfilment, shipment and delivery are separate values rather than one status. A product record is never confused with the listing it is linked to.

Guidance

What needs attention finds you, instead of waiting to be discovered.

Low-stock thresholds, product warnings, listings ending soon, GTC Guard relist monitoring, and import conflicts raised for you to resolve.

Control

Nothing reaches the marketplace that you did not deliberately send.

Saving locally and sending changes to eBay are separate actions. Inventory Sync previews every quantity change first. Products linked to live listings are protected from deletion.

Organisation

One place for the work behind a listing, including the parts buyers never see.

Catalog, drafts, templates, images and per-store values in one record, alongside cost, notes and storage location that stay private to you.

Efficiency

Less switching, less repetition, fewer tabs.

Search, filters, customisable columns, CSV import, and orders, marketing, schedules and messages in the same workspace as the catalog.

Intelligence

The tedious analysis is done for you; the decision stays yours. This is careful engineering, not artificial intelligence.

Normalised SKU and title matching during import, exact marketplace identity for every remote action, and cross-store quantity comparison — each surfacing what it found rather than acting on it.

Product principles

Saving is not publishing

Editing your own records and changing something that is selling are different actions, and the product keeps them apart.

Stores stay separate

Information belonging to one connected store is never automatically shared with another. Cross-store contamination is one of the most damaging and least reversible mistakes a multi-store seller can make.

Exact marketplace identity

Remote actions use the exact eBay item identity within the correct store context, not a SKU string that might legitimately be repeated.

Narrow tools over broad ones

Inventory Sync changes quantity rather than pushing whole listings, because a broad synchroniser is the fastest way to damage a healthy catalog.

Confirm before anything irreversible

Case Center can issue refunds, so it asks twice. Financial and irreversible actions get a review and confirmation step, and actions eBay does not currently permit are not offered at all rather than failing when pressed.

Say what is not supported

Limitations are published next to capabilities. A tool you can predict is more useful than one that appears to do everything.

Why local-first matters for the Mac product

Your catalog is your business record. Keeping product information, images, drafts and seller-only notes on your own machine means you can work without waiting on a service, and your data is not held hostage by a subscription lapse. It also means backups are your responsibility, which the product says plainly rather than quietly assuming someone else is handling it.

Local-first does not mean offline. Authorising a store, reading from eBay and sending changes all require a connection, and marketplace secrets are handled at the SellerHint backend boundary rather than inside the Mac application.

How the two products relate

SellerHint for Mac is the primary product. SellerHint Web is a separate browser-based product with its own account, backend, database and storage. They are not two views of the same system: they share no accounts, no subscriptions, no data and no store connections, and no synchronisation between them is implemented.

See the full comparison

Where the product is going

The public roadmap describes current direction, including the work that is explicitly not planned. It carries no dates, because a date that has not been committed to is a promise nobody made.

Read the roadmap