Generate a marketplace with the payout and dispute parts already designed

What you get in the generated ZIP

A typical marketplace generation includes:

app/blueprints/
├── vendor_bp.py              # vendor account, KYC status, payout config
├── product_bp.py             # vendor-scoped products
├── order_bp.py               # multi-vendor orders split per vendor
├── payout_bp.py              # held funds, payout schedule, manual release
├── commission_bp.py          # tiered rules per vendor / category
├── dispute_bp.py             # state machine: opened → awaiting_response → resolved → escalated
├── kyc_bp.py                 # KYC submission + review workflow
├── escrow_bp.py              # held during transit; released on delivery confirmation
└── fraud_signal_bp.py        # signals + scoring (chargeback rate, dispute rate, velocity)

What's already wired

• Vendor KYC: scaffold for Stripe Connect Express + Standard, Paystack split payments, or Flutterwave equivalents. KYC status is checked before vendor can list products or receive payouts.
• Multi-vendor cart: a single buyer cart can contain items from multiple vendors. Checkout splits into per-vendor orders with separate fulfilment.
• Commission rules: per-vendor tier (default 10%), per-category override, volume-based discount. All changes are audit-logged for vendor transparency.
• Escrow-during-transit: physical-goods orders hold the vendor payout until delivery is confirmed (or auto-released after configurable window). Buyer can dispute during the hold window.
• Dispute workflow: state machine with from-state guards. Vendor responds within SLA, admin can escalate, refund-or-pay decision logged.
• Payout schedule: weekly / bi-weekly / on-demand depending on tier. Held funds are visible to vendors with a clear release date. Failed payouts retry with exponential backoff.
• Fraud signals: chargeback rate per vendor, dispute rate, velocity (new vendors with high volume flagged for review). Signals feed a score; high-risk vendors get manual-review hold on payouts.

What ships in docs/

• docs/decisions/ADR-0010-payment-split.md — Stripe Connect vs Paystack split vs build-our-own, with trade-offs
• docs/decisions/ADR-0014-escrow-policy.md — when to hold vs release immediately, dispute window
• docs/diagrams/order-fulfilment.md — multi-vendor order Mermaid sequence diagram
• docs/compliance/aml-controls.md — when AML overlay is flagged, KYC + transaction-monitoring controls
• docs/decisions/ADR-0017-dispute-state-machine.md

Internal links

• Stripe integration for Connect-style splits
• E-commerce use case for single-vendor variants
• for/fintech for the AML overlay

CTA

Try it — free plan, no credit card. archiet.com.

Generate a marketplace, look at the dispute workflow and the escrow policy, decide if that's the shape you'd ship.