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).
Background & Context
Some merchants want branded discovery and SEO landings without operating first-party checkout. amazon-ecom (package amazon-ecommerce) is a monorepo for Amazon-outbound product catalogs: shoppers browse Next.js storefronts and complete purchase on Amazon via each product’s amazonUrl. There is no cart, checkout, payments, or orders module in the API or storefronts—by design.
A shared NestJS 11 API persists catalog, users, Cloudinary uploads, and consent-aware analytics. An admin dashboard (Vite + TailAdmin) manages categories, products, and analytics. Two storefronts share the API and distinguish traffic with siteId: BUY4LOW (buy4low) and Garden & Farm Tools (gardenandfarmtools). Production hosts documented in docs: API amazon-ecom-api.vercel.app, storefronts buy4low.com and gardenandfarmtools.com.
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.
Our 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.
What We Delivered
- 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 & Impact
- 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
Operators get multi-channel Amazon merchandising—SEO and brand control on their domains—without pretending Tekvers built a full marketplace checkout where none exists.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.