Bazario
Bazario is a person-to-person marketplace engine with full source code for operators to customize and run as their own SaaS.
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.
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.
- marketplace_core
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.
- protected_checkout (Provider-backed checkout with held proceeds, release, refunds and reversals)
- seller_payouts
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.
- marketplace_messaging
- marketplace_moderation (Listing reports and operator enforcement)
Released balance becomes payable. Payouts run on a schedule or on request, with failure recovery and per-payout statements. Negative balances and reserves are handled explicitly rather than netted silently.
You can read a conversation from the admin panel only when it has been flagged, the access is recorded with a reason, and privacy controls apply. Operator access to private messages is an audited exception, never a browsing surface.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Pabbly Connect
Freshsales
Pipedrive
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 69 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 82 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · categories · category_attributes · checkout_quotes · conversations · credit_balances · credit_transactions · currencies · data_exports · data_imports · dispute_evidence · disputes · enforcement_actions · faq_categories · faq_items · favorites · feature_flags · inbound_webhook_events · inbound_webhooks · languages · ledger_accounts · ledger_journals · ledger_postings · listing_media · listing_reports · listing_variants · listings · marketing_audience_members · marketing_audiences · messages · notification_log · notification_rules · notifications · offers · order_items · orders · organization_limit_overrides · organizations · payment_accounts · payment_events · payouts · placement_campaigns · placement_events · plans · platform_secrets · platform_settings · product_purchases · products · provider_prices · push_devices · report_templates · reviews · roles · scheduled_tasks · seo_meta · shipments · shops · subscriptions · tariff_versions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 4 required, 2 optional.
The application declares Next 16.2.10 and React 19.2.3; the Node version is not pinned.
Supplies the product's database and application services.
Three jobs are declared in `vercel.json`; on another host, wire those schedules to the shipped endpoints.
Choose one of the shipped Brevo, Mailgun, Resend, SendGrid or SMTP providers.
The example configuration exposes the optional hosted integration.
The example configuration exposes optional external error monitoring.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
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.