E-commerce
by @ops Two-sided Marketplace Backend
Vendors, listings, and buyers as first-class concepts, with Stripe Connect wiring for split payouts. Distinct from a single-storefront e-commerce backend: multi-party accounts and payouts are the actual hard part of a marketplace, not the product listing.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install marketplace-two-sided --remote $ stacktora sync # generate the files
What you get
More from the Vault
Coupon & Promotion Engine
Discount codes, promotion rules (percentage, fixed amount, BOGO), and redemption tracking with Redis guarding against a code being used past its limit under concurrent requests. The part of checkout that's deceptively easy to get wrong at the edges.
Digital Asset & License Delivery
Selling downloads or license keys instead of physical goods — secure, expiring download links and license activation state in Postgres, Redis for fast validation on every activation check. Distinct from a physical-goods storefront or a marketplace.
Food Order & Delivery Tracking Backend
Order lifecycle from placed through delivered, with Redis for live status that needs to update in near-real-time. Distinct from the Marketplace recipe: this is a linear order-to-delivery pipeline, not multi-vendor listings.
Inventory & Order Management
Stock levels, orders, and fulfillment state as first-class Postgres records, with Redis for cart/session speed — the operational backend behind a storefront, not the storefront itself. Distinct from a checkout/payments starter: this is what happens after the payment succeeds.