ForbiddenShelf

How ForbiddenShelf was built in five weeks.

How ForbiddenShelf was built: five weeks from brief to curated buying floor with role-based dashboards, PayPal-split payouts, and an editorial standard.

ForbiddenShelf is a curated wholesale marketplace for independent fashion. The shortest honest answer to "is this legit" is the build itself: five weeks from a written brief to a live floor, every change reviewed, every commit named.

Five weeks from idea to live floor

The catalog and role gates shipped first. Wholesalers, retailers, dropshippers, and buyers each got a dashboard wireframed against a real workflow before any code landed. PayPal Marketplace was wired up next, so payouts were real before any wholesaler reached the catalog. The editorial homepage shipped last, after the rest of the floor was already serving traffic.

The brief that started everything

The reposition was decided up front: curated rather than crowdsourced, performance-based rather than subscription, independent rather than consolidated. That single page kept feature creep out of the build. If a feature did not serve the buying floor, it did not ship. The brief is still the brief; this article is the report against it.

Designed for the buyer, not the founder

Every dashboard was sketched against the role that would live in it. Wholesalers needed a fast submit-and-wait flow. Retailers needed catalog browse and a storefront builder. Dropshippers needed a clean ship-it queue. Buyers needed a checkout that felt like a boutique, not a bulk catalog. The roles drove the structure; the structure drove the build. None of the four dashboards is a generic admin grid.

Where the editorial standard came from

Typography, palette, and copy doctrine were treated as product decisions, not skin. The marketplace reads like a trade column because that is the audience. The doctrine โ€” short sentences, strong nouns, useful before clever โ€” is enforced by an automated copy audit that runs on every commit. A regression toward the old discount-coupon pitch fails the build.

What we chose not to ship

No subscription tier. No paid placement. No retailer-of-the-week ad slot. The floor stays curated by saying no to the features that would crowd it. Performance-based fees โ€” ten percent across the order, paid only on completed sales โ€” are the only revenue line. That constraint is what keeps the editorial floor editorial. Anything that would have flattened the catalog into a search-result wall was cut early.

What comes next

The roadmap is a set of commitments to the people already on the floor: faster onboarding for new wholesalers, deeper merchandising tools for retailers, and a shared events calendar for partner brands. None of it is a feature list for its own sake. Every item answers a problem the floor already raised. The next step from here is the manifesto at why a curated, performance-based marketplace.

Five weeks from idea to live floor
Catalog and role gates shipped first. Editorial homepage shipped last. Every dashboard was wireframed against a real role before any code was written.
The brief that started everything
Curated rather than crowdsourced. Performance-based rather than subscription. Independent rather than consolidated. The brief kept feature creep out.
Designed for the buyer, not the founder
Wholesalers, retailers, dropshippers, and buyers each got a dashboard sketched against a real workflow. The roles drove the structure.
Where the editorial standard came from
Typography, palette, and copy doctrine are product decisions. The doctrine is enforced by an automated copy audit in CI.
What we chose not to ship
No subscription tier, no paid placement, no ad slots. Performance-based fees are the only revenue line.
What comes next
Faster onboarding, deeper merchandising tools, a shared events calendar for partner brands. Commitments to the people on the floor.

Frequently asked questions

How long did ForbiddenShelf take to build?
The marketplace went from a written brief to a live, curated buying floor in roughly five weeks. The catalog, role-based dashboards, PayPal-split payouts, and editorial homepage all shipped inside that window.
Who runs the marketplace day to day?
A small operator team owns every approval, every payout, and every editorial decision. The platform is curated by humans; the tooling underneath is automated where automation does not compromise review.
Why should a boutique trust a marketplace this new?
Because every order is settled through PayPal-split payouts on completion, every wholesaler is reviewed before they reach a retailer storefront, and there is no subscription holding either side to a contract. Trust is structural, not promised.

Explore further