Authentic domain model
Listings represented more than 20 coffee-specific attributes across origin, quality, commercial terms, logistics and documentation instead of reusing a generic product schema.
01Selected team experience
Global Coffee Trading Marketplace
A domain-specific marketplace for global coffee trading and supply-chain operations — combining seller onboarding, subscriptions, structured product listings, discovery, CRM, billing and market reporting.
- Next.js 15
- React 19
- TypeScript
- MongoDB
- Zoho CRM
- Zoho Billing
- Tailwind CSS
- Chart.js
02Challenge
The problem
Coffee transactions depended on spreadsheets, email and inconsistent product descriptions. Buyers and sellers lacked a shared structure for quality, origin, logistics, documents and pricing.
- Standardize complex coffee descriptions without flattening domain detail
- Give sellers access to a broader buyer network and clearer listing workflows
- Make quality, origin, warehouse and pricing data searchable and comparable
- Organize certifications, quality records and shipment documents
- Coordinate onboarding, subscriptions, CRM, payments and reporting
- Create a foundation for escrow, bidding, disputes and market intelligence
03Solution
How it was solved
The product modeled coffee as a first-class domain rather than generic inventory. A Next.js application provided resumable onboarding, detailed listings, live marketplace filters and reporting, supported by MongoDB and Zoho commercial operations.
04Evolution
Delivery path
01 · Account registration
A new participant creates an account and begins a multi-step onboarding workflow that can be resumed.
02 · Contact verification
Email and SMS verification establish reachable contact channels before commercial activation.
03 · Profile completion
Company and stakeholder information is captured and synchronized with Zoho CRM.
04 · Subscription selection
The participant chooses a plan, enters the billing flow and activates marketplace access.
05 · Coffee listing
A guided, section-based form captures origin, quality, pricing, logistics and supporting documents.
06 · Marketplace publication
Approved inventory becomes discoverable through structured commercial and quality filters.
07 · Market analysis
Pricing history, summary tables, charts and exports provide a foundation for commodity intelligence.
05Architecture
Platform topology
Database connection caching supported serverless execution. External Zoho operations were separated into a dedicated service layer, while reusable form and reporting components kept domain-heavy interfaces maintainable.
Buyer / seller / operator portals
│
▼
Next.js 15 + React 19 application
│
▼
Next.js route handlers
├─ authentication + verification
├─ onboarding + profiles
├─ marketplace listings + filters
├─ subscriptions + payments
└─ reporting + exports
│
├─► MongoDB / Mongoose
├─► Zoho CRM + Zoho Billing
├─► Resend email + AWS SMS
└─► payment libraries / future escrow path06Product
Product surface
Marketplace discovery
Search inventory by warehouse, origin, species, variety, quality, screen size, organic status, SCA grade and harvest year
Coffee details
Origin, region, species, variety, process, harvest, organic status, SCA grade and elevation
Size & pricing
Units, unit type and size, asking price, reserve price and minimum quantity
Logistics
Warehouse, address, availability date, container ID and shipping responsibility
Documentation
Certifications, quality records and shipment documents supported by a guided listing assistant
Commercial operations
Onboarding, subscriptions, payment-page creation, CRM synchronization and reporting
07Engineering
Technical highlights
Live-data filtering
Filter options were aggregated from current marketplace inventory, so newly listed origins and varieties became searchable without manual configuration. Numeric aggregation supported SCA-grade and harvest-year ranges.
Modular listing workflow
A section-based form architecture with Formik, Yup and reusable controls made complex listing requirements easier to validate, maintain and guide.
Resumable onboarding
Onboarding was modeled as an explicit multi-stage business workflow rather than a single completion flag.
Serverless data access
Cached MongoDB connections and focused Next.js route handlers supported authentication, marketplace data, subscriptions, payments and webhooks.
Reporting foundation
Reusable Chart.js and TanStack Table components established pricing-history, summary, visualization and export capabilities for future market intelligence.
08Integrations
Connected systems
Zoho CRM
Company and stakeholder profiles synchronized into the commercial operations layer during onboarding.
Zoho Billing
Plan selection, payment-page creation, subscription activation and billing webhooks connected access to commercial status.
Resend & AWS SMS
Email and SMS channels supported contact verification and onboarding communication.
Payment foundation
Stripe libraries represented an early or future payment path alongside the active billing integration and longer-term escrow vision.
09Scope
What the team delivered
Unified onboarding, subscriptions and marketplace activity
Structured complex quality and logistics data
Created filters from live inventory
Connected CRM and billing workflows
Built reporting and export foundations
Established a base for bidding, escrow and deeper analytics
10Services
Repos & services
Anonymized service family across the platform.
| Service | Responsibility | Stack |
|---|---|---|
| Marketplace Web Application | Onboarding, account access, inventory discovery, listing management and reporting | Next.js 15, React 19, TypeScript, Tailwind CSS |
| Domain API Layer | Authentication, verification, marketplace data, filters, subscriptions and webhooks | Next.js route handlers, Mongoose |
| Commodity Data Store | Users, onboarding, verification, subscriptions, transactions and coffee inventory | MongoDB |
| Commercial Operations Layer | CRM synchronization, billing activation, verification messaging and payment foundations | Zoho CRM, Zoho Billing, Resend, AWS SMS |
11Outcomes
Results that matter
Unified onboarding, subscriptions and marketplace activity in one domain-specific application
Structured complex quality, commercial, logistics and document data
Created marketplace filters from live inventory
Connected CRM and billing workflows for commercial activation
Built reporting foundations and a base for bidding, escrow and deeper analytics
Domain-led marketplace design, complex product forms, dynamic search, onboarding workflows, CRM/billing integrations and serverless application architecture.
12Boundaries
Scope & caveats
These implementation boundaries keep the public description technically honest.
- The product is best described as an advanced prototype or early MVP rather than a mature production marketplace.
- Commercial activation depends on configured CRM, billing and verification workflows for each deployment.
- Listing persistence, document storage and lifecycle enforcement continue to evolve with product needs.
- No verified transaction-volume, liquidity or growth metrics are claimed for this case study.
13Visuals
Product visuals
14More work
Related experience
Virtual World Platform — Backend & Live Operations
A real-time backend and live-operations platform for a persistent virtual world — combining player progression, content releases, analytics and support operations across Go, NestJS, PostgreSQL, DynamoDB, Redis, NATS and Kafka.
View case study →
AI Outreach and CRM Automation
AI voice outreach connected to campaign operations and CRM follow-through — coordinating lead intake, structured outcomes, CRM updates, calendar booking and email follow-up across Vapi, Pipedrive, Twilio, FastAPI and AWS.
View case study →
Resilient Browser Video Platform
A resilient browser recording platform that lets users correct mistakes without starting over — coordinating screen, camera and audio capture, incremental upload, cloud processing, reversible editing, sharing, teams and billing.
View case study →
Related Peerprise services
15Next step