Sellers need their own app
Listings, inventory, orders, and payouts are a whole product, and it has to see exactly the slice of data that belongs to that seller.
A marketplace is a store plus a second application for the people supplying it, and the hard part is that both halves write to the same rows. Stacks gives you the commerce models, the team and role system for sellers, and the queue that moves money and mail between them without a second service.
The work that arrives whether you planned for it or not.
Listings, inventory, orders, and payouts are a whole product, and it has to see exactly the slice of data that belongs to that seller.
A buyer pays the platform and the platform pays a seller, on different schedules, with fees in between.
Reviews, reports, and moderation queues are launch requirements, not a phase two.
A catalogue nobody wrote is a catalogue nobody can filter unless indexing is automatic.
All of it in the same install, typed against the rest of your application.
Teams, roles, and gates scope every query to a seller, so a seller dashboard is the same actions with a policy in front.
Products, orders, coupons, and payments already exist; the marketplace part is the ownership column and the payout job.
Scheduled jobs, batches, and retries move ledgers on a cadence, with failures visible in the dashboard rather than in a log file.
The commentable and likeable traits plus dashboard model views give you review and report queues without a bespoke admin.
Buyers and sellers get mail, SMS, and push from the same notification classes, routed per recipient.
Searchable and filterable attributes are declared on the model, so a new facet is a model edit, not an indexer rewrite.
Every one of these ships in the same install. Follow one to see what it covers.
Buddy scaffolds, runs, and ships this the same way it does the rest of the app.
Projects of this shape usually grow into one of these.