Amazon-outbound catalog platform
Multi-Channel Marketplace
Dual Next.js storefronts and NestJS/MongoDB API for Amazon-linked catalogs—browse on-site, buy on Amazon (no in-app cart).
The challenge
Merchants needed branded multi-site catalogs with SEO landings and traffic insight—without building (or claiming) a full checkout platform when Amazon already completes the purchase. Without a coherent amazon-outbound catalog platform foundation, Multi-Channel Marketplace stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The solution
Multi-Channel Marketplace: Dual Next.js storefronts and NestJS/MongoDB API for Amazon-linked catalogs—browse on-site, buy on Amazon (no in-app cart). Deployed dual branded catalogs with shared backend data. Tekvers delivered a maintainable amazon-outbound catalog platform system for Multi-Channel Marketplace using NestJS, Next.js, React, TypeScript, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Approach
Outbound commerce model
Products carry pricing, SKU, stock, images, tags, brand, highlights, specs, and optional `amazonUrl`. Storefront CTAs send shoppers to Amazon; no in-app cart.
Multi-site identity
Analytics events (`page_view`, `click`, `outbound_click`, `consent_update`, `location_update`) use hashed IPs (`ANALYTICS_IP_SALT`) and per-storefront `siteId`; admin can filter summaries by site.
SEO and content surfaces
Programmatic `/local` pages, blog keyword guides, sitemaps (including local chunks), `robots`, and `llms.txt`. BUY4LOW adds `/contact` + SMTP; Garden & Farm Tools does not.
Deliverables
- ▸NestJS 11 API: auth, users/addresses, categories, products, uploads, analytics, Swagger
- ▸BUY4LOW Next.js 16 storefront (`web/`) with contact SMTP route
- ▸Garden & Farm Tools Next.js 16 storefront (`web2/`)
- ▸Vite React admin (TailAdmin) for catalog + analytics
- ▸Cloudinary multipart upload (max 5 MB)
- ▸Consent/cookie flows feeding `VisitorConsent` records
- ▸Seed scripts for admin user and products
- ▸Explicit non-features: cart, checkout, payments, orders
Outcomes
- ▸Deployed dual branded catalogs with shared backend data
- ▸Documented public vs admin API; Amazon handles purchase completion
- ▸Analytics separated per storefront with privacy-aware IP hashing
Impact
Operators get multi-channel Amazon merchandising—SEO and brand control on their domains—without pretending Tekvers built a full marketplace checkout where none exists.
Tech stack
Want something similar?
I build production systems like Multi-Channel Marketplace—from architecture through launch. Tell me what you need.
Contact me →