CartMart B2B marketplace for printing supplies

CartMart β€” B2B Marketplace for Printing Supplies

A web marketplace for businesses trading cartridges, toner and printer components, with a product catalogue, wholesale pricing and a seller account.

Project Goal

Connect professional buyers and suppliers of printing consumables in one marketplace, bringing product discovery, packaging options and commercial workflows into a shared web application.

Concept

CartMart combines a Next.js storefront with a Magento backend. Buyers can explore products by manufacturer, category and price, while suppliers manage listings from their account. The code also includes product requests, counter-offers, CSV import and order-related workflows.

Inside the Marketplace

Real screens from the locally running application, connected to a separate Magento installation with a small demonstration catalogue.

Local CartMart catalogue with six fictional printing supply listings
Product catalogue and purchasing filters
CartMart product details with packaging options and wholesale price tiers
Product details, packaging and quantity-based prices
CartMart seller account populated with demonstration products
Seller account and product listings
Magento product administration for the local CartMart catalogue
Magento catalogue administration

Screenshots show a local demonstration with fictional companies, listings, prices and stock. Product images and the CartMart logo come from the project repository. Payments, emails, external translation and domain writes are disabled. Purchasing, counter-offers, CSV import and invoicing were not verified end to end.

Advantages

  • πŸ”Ž Targeted discovery β€” narrow the catalogue by manufacturer, category, product type and price.
  • πŸ“¦ Purchasing context β€” compare packaging options and quantity-based prices on the product page.
  • 🏷️ Seller workspace β€” view product listings and access dedicated product management tools.
  • 🀝 B2B workflows β€” dedicated interfaces for product requests and counter-offers in the application.
  • πŸ› οΈ Catalogue operations β€” Magento administration for product data, variants and stock.

Technologies

The storefront uses Next.js, React and TypeScript, with Apollo Client for GraphQL and Redux Toolkit for state and REST requests. Magento Open Source 2.4.7-p3 provides the PHP backend, extended by project-specific modules. The local demo uses MariaDB and Elasticsearch.

  • Next.js / React / TypeScript
  • Apollo Client / GraphQL / Redux Toolkit
  • PHP / Magento Open Source
  • MySQL (MariaDB) / Elasticsearch
Next.js React TypeScript PHP Magento GraphQL MySQL / MariaDB
Back to portfolio

Developing a B2B marketplace for printing supplies

Trading printing consumables involves more than displaying products and prices. Professional buyers need to distinguish manufacturers, product types, packaging and quantity-based terms. CartMart provides a concrete example of how a web marketplace can organise that information alongside seller tools.

A catalogue built around purchasing decisions

The CartMart catalogue supports filters for manufacturer, category, type and price. Product pages combine images and descriptions with packaging variants and tiered prices. For a business buyer, this brings important purchasing conditions into the same view instead of leaving them spread across separate lists.

Connecting the storefront and seller workspace

A Next.js application provides the buyer-facing catalogue and account screens. Apollo Client accesses Magento through GraphQL, while REST endpoints handle account and project-specific operations. Magento stores the catalogue, configurable products and stock; custom modules extend the backend with marketplace workflows.

What the local demonstration verifies

The screenshots document a real local Next.js client and Magento installation populated with fictional records. The demonstration covers catalogue browsing, product details, seller listings and catalogue administration. Counter-offers, import, purchasing and invoicing are present in the source but were not verified from start to finish. The example illustrates product structure and interface behaviour, without claiming commercial outcomes.