#marketplace-template.md
Version: 1.0.0
Target Models
- GLM-5.3
- GLM-5.2
- GLM-5 Family
- GLM-4.6
- Future GLM Models
#Purpose
This template provides complete engineering context for designing production-ready digital marketplaces that efficiently connect buyers and sellers, facilitate trusted transactions, manage supply and demand, optimize discovery, enable secure payments, and support sustainable marketplace growth.
It is intended to organize business objectives, marketplace architecture, user roles, transaction workflows, discovery systems, trust mechanisms, payment infrastructure, operational requirements, and long-term ecosystem evolution into one structured engineering specification.
The objective is not building another e-commerce platform.
The objective is engineering a trusted marketplace ecosystem where participants can efficiently discover, exchange, and manage valuable products, services, digital assets, or experiences.
#Core Philosophy
Understand the Business
↓
Understand the Marketplace
↓
Understand Buyers
↓
Understand Sellers
↓
Build Trust
↓
Enable Efficient Transactions
↓
Grow the Ecosystem
↓
Continuously Improve
A marketplace succeeds when every transaction creates value for every participant.
#Marketplace Overview
Clearly define
Marketplace Name
Category
Business Problem
Marketplace Type
Target Audience
Business Goals
Primary Value Proposition
Long-Term Vision
The overview should explain why this marketplace deserves to exist.
#Business Context
Define
Target Market
Customer Segments
Business Model
Revenue Strategy
Market Position
Competitive Landscape
Growth Strategy
Success Metrics
Every engineering decision should support measurable marketplace growth.
#Marketplace Type
Define
B2B
B2C
C2C
P2P
Digital Goods
Physical Goods
Services
Rentals
Subscriptions
Hybrid Marketplace
Marketplace architecture should reflect business requirements rather than industry trends.
#Marketplace Participants
Identify
Buyers
Sellers
Administrators
Moderators
Partners
Support Teams
Enterprise Customers
Internal Operations
Every participant should have clearly defined responsibilities.
#User Journey
Describe
Discovery
↓
Registration
↓
Verification
↓
Browsing
↓
Search
↓
Selection
↓
Transaction
↓
Post-Purchase Experience
The marketplace should minimize friction throughout the complete transaction lifecycle.
#Buyer Experience
Design
Discovery
Search
Filtering
Recommendations
Wishlists
Comparison
Checkout
Order Tracking
Support
Reviews
Buyers should find the right product with minimal effort.
#Seller Experience
Design
Registration
Verification
Store Management
Inventory
Pricing
Analytics
Orders
Payments
Support
Growth Tools
Successful sellers strengthen the entire marketplace.
#Product Management
Define
Listings
Categories
Tags
Attributes
Variants
Pricing
Availability
Media
Specifications
Metadata
Product information should remain consistent and searchable.
#Search & Discovery
Design
Global Search
Category Navigation
Filtering
Sorting
Recommendations
Trending
Personalization
Recently Viewed
Semantic Search
Discovery should help users find the best solution—not simply more options.
#Marketplace Transactions
Describe
Product Selection
↓
Cart
↓
Checkout
↓
Payment
↓
Order Processing
↓
Fulfillment
↓
Confirmation
↓
Post-Purchase Support
Every transaction should be transparent and predictable.
#Payment Infrastructure
Define
Payment Methods
Escrow
Subscriptions
Refunds
Invoices
Taxes
Payouts
Currency Support
Fraud Protection
Payments should maximize trust while minimizing transaction friction.
#Trust & Safety
Design
Identity Verification
Seller Verification
Buyer Protection
Content Moderation
Fraud Detection
Dispute Resolution
Reputation
Review System
Trust should increase marketplace participation.
#Reputation System
Define
Ratings
Reviews
Seller Reputation
Buyer Reputation
Verification Badges
Transaction History
Trust Scores
Quality Metrics
Reputation should reward long-term trustworthy behavior.
#Inventory Strategy
Define
Inventory Ownership
Availability
Reservations
Synchronization
Stock Validation
Order Limits
Restocking
Forecasting
Inventory should accurately represent marketplace reality.
#Notifications
Design
Order Updates
Messages
Promotions
Security Alerts
Payment Updates
Shipping Updates
Review Requests
Marketplace Announcements
Notifications should improve marketplace engagement without overwhelming users.
#Analytics Requirements
Measure
Sales
Orders
Revenue
Conversion
Retention
Average Order Value
Marketplace Liquidity
Supply
Demand
Growth
Marketplace analytics should support strategic business decisions.
#Security Requirements
Define
Authentication
Authorization
Role-Based Access
Payment Security
Data Privacy
Fraud Prevention
Audit Logging
Compliance
Marketplace security protects every participant.
#Performance Requirements
Define
Expected Users
Concurrent Users
Search Performance
Checkout Latency
Availability Targets
Caching Strategy
Scalability Goals
Background Processing
Performance directly influences conversion rates.
#Marketplace Operations
Define
Content Moderation
Seller Management
Support Operations
Dispute Management
Fraud Monitoring
Catalog Management
Campaign Management
Operational Dashboards
Operations should scale together with marketplace growth.
#Scalability Strategy
Design
Horizontal Scaling
Caching
Search Infrastructure
Database Scaling
Queue Systems
CDN
Load Balancing
Disaster Recovery
Marketplace growth should never compromise user experience.
#Observability
Define
Logging
Metrics
Tracing
Marketplace Analytics
Business Monitoring
Infrastructure Monitoring
Alerting
Operational Dashboards
Operational visibility should exist before business problems occur.
#Deployment Strategy
Define
Development
Testing
Staging
Production
Rollback Strategy
Feature Flags
Marketplace Migration
Release Strategy
Deployment should minimize operational risk.
#Business Metrics
Measure
Gross Merchandise Value
Marketplace Revenue
Buyer Growth
Seller Growth
Listings
Successful Transactions
Conversion Rate
Retention
Customer Satisfaction
Infrastructure Cost
Only measure metrics that influence marketplace health.
#Engineering Constraints
Always respect
Business Objectives
Trust
Security
Performance
Scalability
Maintainability
Reliability
Developer Experience
Operational Simplicity
Engineering discipline creates sustainable marketplaces.
#Deliverables
The generated marketplace specification should include
- Marketplace Overview
- Business Context
- Marketplace Type
- Marketplace Participants
- User Journey
- Buyer Experience
- Seller Experience
- Product Management
- Search & Discovery
- Transaction Flow
- Payment Infrastructure
- Trust & Safety
- Reputation System
- Inventory Strategy
- Notifications
- Analytics Requirements
- Security Requirements
- Performance Strategy
- Marketplace Operations
- Scalability Strategy
- Deployment Plan
- Observability
- Business Metrics
- Long-Term Evolution Strategy
Every section should contribute toward building a production-ready marketplace that scales with users, transactions, and business growth.
#Definition of Done
A marketplace specification is considered complete when business objectives, marketplace architecture, participant workflows, discovery systems, transaction processes, payment infrastructure, trust mechanisms, reputation models, inventory strategy, operational requirements, scalability plans, security controls, observability, deployment strategy, business metrics, and long-term evolution plans have been documented with sufficient clarity that engineering, product, operations, and business teams can confidently design, build, operate, and continuously improve the marketplace with minimal ambiguity.
Exceptional marketplaces are not measured by the number of listings or registered users.
They are measured by how effectively they connect buyers and sellers, build long-term trust, facilitate reliable transactions, support sustainable ecosystem growth, enable efficient engineering execution, and continuously create measurable value throughout the lifetime of the platform.