Release
Exclusivity is enforced by the database, not by application logic
One claim per product, guaranteed by a unique index — because the same bug reopened twice when two code paths were allowed to answer the same question.
A FlowFinds claim is permanent and exclusive. When you claim a product it leaves every other founder's feed and it is yours from that point. That promise is only worth what enforces it, and for a while what enforced it was application logic in more than one place. The same defect reopened twice.
It is now a unique index on the product in the claims database. Two code paths can no longer disagree about whether a product is taken, because only one of them can win an insert. A hold is the softer version: a thirty-minute reservation while you decide. Several founders may watch the same unclaimed product at once — a hold is not a global lock — but only one claim can ever exist.
Exclusivity applies to the look as well as to the purchase. A product under someone else's claim or hold is not shown to you as available at all, so you never form an attachment to inventory you cannot have. The single exception is deliberate: one walkthrough product is shared, so a first-time visitor can complete the whole journey without consuming real inventory.
The same principle runs through tenant isolation generally. Every query returning work is scoped to the owning account at the point the data is read, rather than filtered afterwards in the interface. A screen that hides a row is not a boundary.
Read next
How the Product Hunter finds and claims a product.
More from FlowFinds
- Newer: A find is only as current as its most neglected axis
- Older: One allowance per feature, not one pooled bucket
- Everything else is in the news index.
To fact-check anything above before you publish it, write to [email protected].