The setting
connects independent retailers with small brands and suppliers. Its lets brands list and sell products, and lets retailers find, order and pay for them.
Logged-out discovery needs protection without treating new retailer interest as abuse.
Catalog protection preserves supplier data, while low-friction browsing preserves the first moments of retailer discovery.
Who you’d be doing this for
“I was checking three candle brands between customers, then the site kept making me prove I wasn’t a bot.”
Taemin Fujita · Retail Store Owner · a character in this brief
Runs a specialty home-goods shop and uses logged-out browsing to assess new suppliers before sharing purchasing details.
What is at stake
Legitimate logged-out shoppers are repeating challenges while automated traffic harvests the same discovery paths. You have to weigh catalog protection against the first browsing moment that leads a retailer toward an order.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- catalog protection vs. first-browse access
- enforcement precision vs. adversary adaptation
- shared defaults vs. endpoint flexibility
- fast containment vs. durable trust signals
Why Faire
Marketplace discovery depends on retailers being able to evaluate brands before they are ready to sign in or order.
Written with these in mind
Not your kind of problem? 59 more at Faire, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Faire. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Detection and Response Engineer · no longer posted
- Looking for and monitoring threats within identity systems our employees authenticate through, the laptops they work on, the SaaS applications that run the business, our enterprise network, and the internal infrastructure behind it.
- AV Engineer (opens in a new tab)
- You would rather turn a recurring failure into a runbook, a standard, or a training session than fix it repeatedly.
- Support live events across our offices, from smaller-tier events teams self-run to full productions, covering setup, sound checks, mic handling, and day-of support.
- Staff Security Engineer - Bot & Traffic Defence (opens in a new tab)
- Build higher-confidence bot and trust signals so that Faire can enforce more aggressively without turning legitimate logged-out buyers away.
- Author and tune edge security controls as code: WAF rules, rate limiting policies, and challenge mechanisms, against real adversaries who respond to every change you make.
- Senior Software Engineer - Product Security (opens in a new tab)
- Collaborate with foundational teams such as Risk, DevOps, and IT to assess and improve access controls and audit trails throughout the software development lifecycle and beyond.
- Senior Client Platform Engineer · no longer posted
Reporting read before this brief was written
The pieces closest to the situation in this brief.
As of September 2026, Alibaba.com plans to add agentic AI capabilities to its B2B marketplace so autonomous agents can search for suppliers, draft inquiries and compare quotations on buyers' behalf.
Alibaba.com to Add Agentic AI to B2B E-Commerce Platform — Distribution Brief (opens in a new tab) · distributionbrief.com · Sep 30, 2026
Faire's Trend Scout tool, in beta since March 2026 under VP of Marketplace Intelligence Amara Ndoye, is reported as of September 2026 to lift opening-order placement with new brands by 22% versus standard browse.
Faire in 2026: Is the Wholesale Marketplace Rewriting B2B Commerce? – Online Store News (opens in a new tab) · onlinestorenews.com · Sep 19, 2026
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on moving faster inside a system others depend on.
Shoppers who see an unfamiliar device cannot remove it without recovery or support.
You must weigh fast account containment against signing out the shopper who is still trying to pay.
Verified logs show suspected metadata requests through browser-linked agent workflows.
You must weigh irreversible containment against keeping legitimate source retrieval available for consumer research.
The same setting, from another role
Each is set around Faire’s Wholesale discovery marketplace, written for a different role. They’re separate briefs, not the same scenario.
Brand Success Managers are finding key account context only after a renewal conversation has already happened.
You have to decide who reads Salesforce, Kustomer and Zendesk history before a call, and who decides which of those findings becomes the rank a manager sees.
Brands with direct wholesale storefronts are questioning whether marketplace discovery reaches anyone new.
You must weigh a useful acquisition programme against claims the available evidence cannot support.
Eighteen brands may leave Insider Partnership because new retailer orders do not clearly show incremental acquisition.
You must weigh renewal revenue against terms that brands can defend from their own order history.
Other problems with a similar purpose
In each of these, as in this one, the aim is to build a security or safety control whose guarantees actually hold when they're tested for real.
One compromised account exported 11,400 blocks and records before it was disabled, and a key customer wants this control before renewing.
You have to prove it cannot be bypassed while compliance exports keep working.
Support ends in 90 days for the library that masks secrets, and it now hides output that engineers need.
You have to keep every secret covered while giving engineers back a readable log, and get security sign-off before cutover.
Support and engineering still hold broad, open-ended production access to candidate records, including role paths nobody uses.
You have to retire those roles for good and still let responders act during an urgent incident.
