RydgeSupply | Noah Dawson

RydgeSupply is a wholesale e-commerce platform built for knife distributors and retailers. The architecture separates customer-facing storefront concerns from back-office operations, with a Backend-for-Frontend (BFF) API layer orchestrating data flow and keeping business logic centralized.

This project demonstrates my ability to design and implement a multi-tier system: headless commerce frontend, dedicated admin/management interface, and a unified API layer backed by PostgreSQL.

Overview

RydgeSupply addresses the needs of B2B knife wholesale: high-volume catalog management, tiered pricing, order workflows, and inventory control. Existing solutions often bundle these concerns in monolithic platforms that don’t scale cleanly or allow independent evolution of storefront vs. admin experiences.

RydgeSupply introduces:

Headless storefront — Customer-facing catalog, search, and ordering
Backend management system — Admin interface for products, orders, inventory, and customers
API BFF — Single orchestration layer that talks to both frontend and backend
PostgreSQL — Single source of truth for all business data

The goal is a maintainable, scalable architecture where frontend and admin can be updated independently without breaking core workflows.

Architecture

Headless Frontend

A decoupled storefront that consumes the BFF API. Built for performance and flexibility—the frontend can be updated, A/B tested, or even rebuilt without touching backend logic.

Backend Management System

Full admin interface for wholesale operations:

Product catalog management
Order processing and fulfillment
Inventory tracking
Customer and account management
Pricing and discount rules

API BFF (Backend-for-Frontend)

A dedicated API layer that:

Aggregates data from PostgreSQL and backend services
Shapes responses for each client (storefront vs. admin)
Enforces authentication and authorization
Reduces complexity and coupling between frontend and database

PostgreSQL

Central database for products, orders, customers, inventory, and all transactional data. Schema designed for wholesale workflows: SKUs, quantity tiers, multi-warehouse support, and audit trails.

Features

Catalog Management

Product SKUs with variants (blade type, handle material, etc.)
Bulk import/export
Category and collection organization
Search and filtering

Order Management

Order lifecycle (draft → submitted → processing → shipped)
Invoice generation
Shipping integration

Inventory

Stock levels and low-stock alerts
Warehouse/location tracking
Allocation and reservation for pending orders

Wholesale Pricing

Tiered pricing by quantity or customer segment
Volume discounts
Net terms and credit limits (where applicable)

Admin Dashboard

Overview metrics: orders, revenue, top products
User and role management
Audit logging for compliance

Technologies Used

Headless Frontend

Decoupled storefront built for flexibility—can be framework-agnostic (e.g., Next.js, Astro, Remix) with API-driven content and commerce.

Backend Management System

Dedicated admin application for internal users. Handles CRUD operations, reports, and complex workflows that the public site never sees.

API BFF

Node.js/Express or similar runtime serving as the Backend-for-Frontend. Handles aggregation, transformation, and routing between clients and the database.

PostgreSQL

Relational database for structured data, ACID compliance, and complex queries. Schema supports products, orders, customers, inventory, and business rules.

Project Goals

RydgeSupply showcases:

Separation of concerns — Storefront, admin, and API evolve independently
B2B e-commerce patterns — Wholesale pricing, bulk operations, and order workflows
API design — RESTful or GraphQL BFF that serves multiple clients
Database design — PostgreSQL schema suitable for inventory, orders, and audit trails

Images

Status

🟢 Architecture Complete

Headless frontend: Built
Backend management system: Built
API BFF: Built
PostgreSQL schema: Deployed