# Bazario

> Bazario is a person-to-person marketplace engine with full source code for operators to customize and run as their own SaaS.

Source page: https://saascode.ai/products/bazario
Machine-readable record: https://saascode.ai/products/bazario.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $249 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

Bazario is a person-to-person marketplace. You (the operator) run the marketplace; independent sellers open their own shops and list inventory; buyers discover items, negotiate, and pay. The platform holds the payment until delivery, pays the seller, records your commission and supports two-way reputation.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/bazario — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://bazario.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

4 roles seeded on the demo (of the 5 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Shop staff** (`member`) — `user@demo.com` / `demo123`
  Works listings, orders and messages inside one shop. Lands on `/dashboard`.
- **Buyer** (`buyer`) — `buyer@demo.com` / `demo123`
  Browses listings, negotiates offers and tracks purchases. Lands on `/dashboard`.
- **Shop owner** (`org_admin`) — `org-admin@demo.com` / `demo123`
  Runs the shop, listings, orders, team and payouts. Lands on `/dashboard`.
- **Marketplace owner** (`super_admin`) — `admin@demo.com` / `demo123`
  Runs marketplace policy, money, disputes and moderation. Lands on `/admin`.

Or open a role directly: https://saascode.ai/demo/bazario?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 5** — distinct roles accepted by the role CHECK constraint: admin, buyer, member, org_admin, super_admin
- **tables: 82** — distinct CREATE TABLE statements across every applied migration
- **migrations: 108** — .sql files in supabase/migrations
- **page modules: 103** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 192,372** — lines of code (comments and blank lines excluded) across 1195 TypeScript files (167,531) and 139 SQL files (24,841); node_modules and .next excluded
- **api route files: 261** — files named route.ts under src/app/api
- **http operations: 351** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 82 tables, 156 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-08-13

## Complete capability inventory

5 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### What Bazario is and who uses it

- **marketplace_core** — A buyer finds a listing, optionally makes an offer, the seller accepts, the buyer checks out, the payment is held, the seller ships, the buyer receives and confirms, the inspection window closes, the funds release to the seller's balance, both sides review each other, and a payout moves the money out. Every step of that path is recorded, and every money movement is a journal entry.

### Money — tariffs, protected payment, ledger and payouts

- **protected_checkout (Provider-backed checkout with held proceeds, release, refunds and reversals)** *(seller-authored)* — Provider-backed checkout with held proceeds, release, refunds and reversals
- **seller_payouts** — A seller connects their own provider account and completes the provider's identity and capability checks. Until those capabilities are active, that seller cannot sell — the product says so plainly rather than letting an order fail after a buyer has paid.

### Trust — messaging, reviews, moderation and disputes

- **marketplace_messaging** — Buyers and sellers talk in private threads scoped to a listing or an order, with attachments, read state and notifications. Only the participants can read a thread. Contact-pattern controls exist to catch attempts to move a deal off-platform, applied proportionately rather than as a blanket block.
- **marketplace_moderation (Listing reports and operator enforcement)** *(seller-authored)* — Listing reports and operator enforcement

## What each system gives the operator

*stated.*

- **What Bazario is and who uses it** — Run independent shops and buyer transactions without losing marketplace-wide control.
- **Money — tariffs, protected payment, ledger and payouts** — Keep charges, held proceeds, commissions and payouts aligned through every transaction.
- **Trust — messaging, reviews, moderation and disputes** — Keep private participation accountable when reports, reviews or disputes need intervention.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Independent shops and active buyers meet in one accountable marketplace.

A niche marketplace becomes difficult to operate when discovery, seller activity and order ownership live in separate tools. Buyers lose context between the listing and the purchase, sellers cannot see where work moved next, and the operator ends up reconciling every exception by hand. The commercial cost appears as abandoned orders, inconsistent shop service and a support queue that grows faster than transaction volume. A marketplace business needs one operating picture of who is selling, who is buying and which transaction each action belongs to, so growth does not trade away accountability.

### Each completed sale preserves a clear path from charge to payout.

Marketplace money becomes risky the moment a charge, a seller balance and the operator's commission stop telling the same story. A buyer sees a payment, a seller expects proceeds, and the operator must answer both while delivery, refunds or disputes are still moving. If those states drift, support has no reliable explanation, finance cannot reconcile the sale, and payouts become manual judgment calls. The business needs every transaction to retain a legible money history from the initial charge through held proceeds and final payout, especially when the normal path changes.

### Private marketplace activity stays governable when a transaction goes wrong.

Trust breaks in the gaps between ordinary marketplace work: a conversation nobody else can inspect, a review posted at the wrong moment, a report without follow-through, or a dispute whose money moved before the case finished. When those gaps are invisible, honest buyers and sellers absorb the cost while the operator reacts without a reliable record. A marketplace needs enough accountability to intervene without turning every private interaction into an open surveillance surface. The consequence of getting that balance wrong is not just support load; it is a reputation system participants stop believing.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **A Node host** (required) — The application declares Next 16.2.10 and React 19.2.3; the Node version is not pinned.
- **Supabase** (required) — Supplies the product's database and application services.
- **A scheduled runner** (required) — Three jobs are declared in `vercel.json`; on another host, wire those schedules to the shipped endpoints.
- **An email delivery provider** (required) — Choose one of the shipped Brevo, Mailgun, Resend, SendGrid or SMTP providers.
- **Upstash** (optional) — The example configuration exposes the optional hosted integration.
- **Sentry** (optional) — The example configuration exposes optional external error monitoring.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 192,372 lines across the application and its database, 82 tables defined by 108 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Bazario demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 4 of them: Shop staff, Buyer, Shop owner, Marketplace owner. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 103 page modules and 351 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: A Node host, Supabase, A scheduled runner, An email delivery provider. Optional: Upstash, Sentry. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 108 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $249?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Bazario: a person-to-person marketplace engine with operator control](https://saascode.ai/inside/bazario-person-to-person-marketplace-engine.md)
- [Bazario vs Sharetribe: own the marketplace engine or rent the core](https://saascode.ai/inside/bazario-vs-sharetribe.md)
- [Best P2P marketplace software for operators in 2026: four ownership models](https://saascode.ai/inside/best-p2p-marketplace-software-operators-2026.md)

## Links

- Catalog page: https://saascode.ai/products/bazario
- Product record: https://saascode.ai/inside/products/bazario
- Live demo: https://bazario.saascode.ai
- Every product: https://saascode.ai/llms.txt

