Paper distributor marketing + partial ecommerce stack
Paper Company
Trade International / HP Papers Pakistan—Next.js marketing/shop, NestJS/MongoDB API, and React admin with SMTP order email as primary checkout.
Background & Context
Paper Company is the software stack for Trade International, positioned as sole distributor of HP Papers in Pakistan (tradeinternational.net.pk). Code lives under ne/ as three independently versioned packages—not a single root workspace: Next.js 14 storefront (ne/website), NestJS 10 ecommerce API (ne/ecommerce-nest), and CRA admin (ne/ecommerce-dashboard).
Public site presents company divisions (trading, indenting, tenders, HP Papers) and a shop UX for paper SKUs (gsm/size/sheets). Nest exposes ecommerce-style resources (products, cart, orders, coupons, payments, shipping, brands, customers). Integration reality: the storefront catalog is local in-repo data, not live Nest product queries; checkout primarily emails orders via Next.js POST /api/orders (Nodemailer). Dashboard stores JWT but api.ts does not attach Authorization; category controllers and analytics modules are missing on Nest despite dashboard calls; Stripe toggles in Settings are simulated UI only.
The Challenge
A paper distributor needed a branded web presence (corporate divisions + HP Papers shop narrative) and an ecommerce-shaped admin/API stack—without falsely claiming a fully wired Nest checkout. Without a coherent paper distributor marketing + partial ecommerce stack foundation, Paper Company stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Paper Company: Trade International / HP Papers Pakistan—Next.js marketing/shop, NestJS/MongoDB API, and React admin with SMTP order email as primary checkout. Credible corporate + shop presence for HP Papers distribution positioning. Tekvers delivered a maintainable paper distributor marketing + partial ecommerce stack system for Paper Company using Next.js 14, NestJS 10, MongoDB, Mongoose, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Brand + shop marketing surface
Home, about, contact, services, indenting, tender, `/hp-paper`, `/shop`, `/products`, cart/checkout routes with local `productService` catalog.
Nest commerce core (partially consumed)
Products (including gsm/size/sheets), cart, orders, coupons, payments records, shipping methods, brands, customers, auth (register/login/forgot-reset, JWT `me` / change-password), Swagger `/api/docs`.
Honest integration seams
Document mismatched `checkoutService` paths, missing category HTTP API, missing analytics module, and dashboard auth-header gap so future work is scoped accurately.
What We Delivered
- Next.js 14 Trade International / HP Papers Pakistan storefront
- NestJS 10 `/api` ecommerce modules (products, cart, orders, coupons, payments, shipping, brands, customers, auth, health)
- CRA admin: products, product-setup, orders, customers, analytics (endpoint gaps surfaced), settings
- SMTP order confirmation via Next `POST /api/orders`
- Paper-oriented product attributes (gsm, size, sheets)
- CORS/host map for Vercel website, API, and dashboard deployments
- Explicit non-features: Amazon outbound model, Cloudinary module, Stripe SDK, live Nest-backed storefront catalog
Outcomes & Impact
- Credible corporate + shop presence for HP Papers distribution positioning
- Partial ecommerce backend ready to finish against the documented mismatches
- Clear operator story: email-first checkout today; Nest checkout path unfinished
Trade International can market divisions and paper SKUs online while engineering closes Nest↔storefront↔dashboard wiring—without Tekvers inventing Stripe or live catalog sync that source does not provide.
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.