Flows category icon
App Builder
Advanced

Marketplace Buyer/Seller Flow

Build a two-sided marketplace core: listings, browsing, and a real transaction/request flow between buyers and sellers.

6 steps22 verify checks2-4 hoursWorks with: emergent · chatgpt · claude · cursor
Start Guided Walkthrough

The Route

0/6 verified

Context Pack

Paste this first. It briefs the AI on requirements, constraints, and the Definition of Done before your first build prompt.

Context Pack
PROJECT CONTEXT:
I am building a two-sided marketplace where sellers post listings and buyers browse and purchase/request them.

GOAL:
Implement working listings, browse/search, and a buyer-to-seller order/request flow with status tracking.

REQUIREMENTS:
- Sellers can create, edit, and unpublish listings
- Buyers can browse, search, and filter listings
- A listing detail page with a working order/request action
- Order records with statuses both sides can see
- Role-appropriate dashboards for buyers and sellers

CONSTRAINTS:
- Orders must be real records, not toasts
- Sellers must not be able to order their own listing
- Every list view needs loading and empty states

DEFINITION OF DONE:
- A seller can post a listing and see it live
- A buyer can find it via search and open its detail page
- Placing an order creates a record both sides can see
- Order status changes propagate to both dashboards

COMMON FAILURES TO AVOID:
- Listings stored in local state and lost on refresh
- Search that filters a hardcoded array
- An order button that only shows a success toast
- Buyers and sellers seeing the same generic dashboard

Paste this into your AI builder first. It teaches the AI what you want before you give it the build prompt.

Related routes

More App Builder flows that share ground with this one.

Flows category icon
App Builder
Generated

Add Real-Time Presence Indicators to a Chat App with WebSockets

A step-by-step flow for implementing real-time online, offline, and typing presence in a chat app using WebSockets, including backend presence tracking, frontend updates, reconnect handling, and verification.

01Inspect the existing chat architecture and choose presence data flow
02Define the presence event contract and server-side state model
03Implement authenticated WebSocket connection handling on the server

+7 more steps to Done

Best forbuilders who have shipped a basic app before

10 steps60-120 minutesIntermediate
Flows category icon
App Builder
Generated

Add Team Invites to a SaaS App

Build a real team invitation system for a SaaS app, including invite creation, email/share flow, acceptance, membership creation, role assignment, validation, and end-to-end testing.

01Audit Existing Team, User, and Auth Models
02Add Invitation Data Model and Migration
03Implement Secure Invite Creation API

+7 more steps to Done

Best forbuilders who have shipped a basic app before

10 steps60-120 minutesIntermediate
Flows category icon
App Builder
Generated

Add a Working Team Invite System to a SaaS App

Build a real invite flow for a SaaS app so existing users can invite teammates by email, store invite records, validate tokens, accept invitations, and join the correct workspace with proper permissions.

01Audit the current auth and workspace model
02Add the invite data model and migration
03Build secure invite creation on the server

+6 more steps to Done

Best forbuilders who have shipped a basic app before

9 steps60-120 minutesIntermediate

Made with Emergent