Solutions
An existing store
For an operator bringing a store they already run.
What you have
A storefront you already run, on a platform you already pay for, selling products you already chose.
What you want
An honest reading of whether those products still stand up, and a decision about what to do next.
What is in the way
FlowFinds does not migrate or take over a store. What it can do is analyse a product you name, on the same evidence and the same rules it applies to its own finds.
What FlowFinds will not do here
It will not import your catalogue, connect to your platform, rewrite your existing storefront, or take over your domain. There is no migration path and none is announced. A store generated by FlowFinds is generated for a product claimed through FlowFinds; it is not a redesign service for a store that already exists.
Saying that plainly matters more on this page than on any other, because an operator with a working store has the most to lose from a tool that quietly assumes control of it.
What it does do: the analyse tool
Name a product you already sell and the same engine that scores the feed scores it. You get the same three-leg reading — urgency, scarcity, feasibility — and the same evidence rows behind each leg, with the claim, the source URL and the date.
The number that is usually new to an established operator is the age. The age of a reading is the age of its weakest leg: for each leg the engine takes its freshest source, then takes the oldest of those. A product you chose eighteen months ago on good demand evidence, with sourcing evidence nobody has revisited since, reports as old. Evidence younger than ninety days counts at full strength and decays towards a floor at one year, so the reading downgrades itself as its inputs go quiet rather than waiting for you to notice.
A leg below the floor ranks the product last rather than removing it, and a leg with no sources is reported as one evidence step short by name. You are told which axis is missing, not handed a composite score that conceals it.
The pricing read is separate, and it is about listings
Where enough matching listings can be observed for the same product, the offer engine establishes the lowest one it can stand behind and sets a price below it. The undercut is measured and stated flatly. Every comparison also states what it is matched on: a listing whose capacity, size or rating differs from your unit is not a price for your unit, so the basis is written out rather than left to be inferred.
Where it cannot price, it says which of four things happened rather than producing a softer number: too few matching listings to observe a range; our retrieval failed, named as ours; the observed set spans variants we cannot separate; or the last check has aged past what we will assert and could not be refreshed. For an operator who already has a price, a refusal to compare is more useful than a comparison against the wrong variant.
What you do
| Step | Who acts | What exists afterwards |
|---|---|---|
| Name a product you already sell | You | A queued analysis against the same engine the feed uses |
| Score the three legs | FlowFinds | A reading with dated evidence rows and a stated weakest leg |
| Read the age, not the score | You | An explicit answer about how stale your original reasoning has become |
| Attempt an observed-listing comparison | FlowFinds | Either a measured undercut with a stated basis, or one of four named refusals |
| Decide whether to keep, reprice or retire | You | A decision made outside FlowFinds, on evidence produced inside it |
| Claim something new if you choose to | You | A separate exclusive claim with its own store and offer, alongside what you already run |
What it costs
Analysis draws on the find engine allowance, metered per feature in a rolling five-hour window inside a weekly cap. The free tier has no card and no trial clock and does not expire, and it is enough to analyse a handful of products before committing to anything. The tiers and per-feature rate card are on pricing.
Nothing about your existing store is charged for, because nothing about it is touched.
Honest limits
- No import, no migration, no platform connection and no takeover of an existing storefront. A FlowFinds store is generated for a FlowFinds claim.
- Analysing a product you sell does not claim it. Exclusivity applies to the FlowFinds inventory, and analysis does not reserve anything.
- The reading is of public dated evidence. It has no access to your sales, your traffic or your margins unless you supply them.
- Where too few matching listings exist, the comparison is withheld and diagnosed rather than estimated.
- A supplier cost you enter is a declaration, and every margin derived from it is marked as resting on your declaration.
- The verdict engine reports on claims held in FlowFinds. It will not monitor a store it does not run.
The scoring and the analyse tool are described under Product Hunter, and the four refusal states under supplier. If the analysis points at a new product, continue at your second product.