Auto-parts ERP · 2026
ERP Repuestos
Production ERP for selling auto parts, managing products, stock, equivalences, sales, purchases and finance.
- Type
- ERP
- Domain
- Auto parts
- Status
- Production
Problem
Auto-parts businesses need SKU control, product families, part brands, vehicle applications, equivalent products and financial workflows tied to real sales and purchases.
Contribution
Adapted a TypeScript ERP architecture into a parts-focused system with Next.js, Express, PostgreSQL and Drizzle, aligning frontend schemas, backend DTOs and the database model around products, inventory and equivalence groups.
Key points
- Product catalog centered on SKU, family, category, part brand and part type instead of generic retail attributes.
- Equivalence groups connect interchangeable SKUs with vehicle models, years, engine details and application notes.
- Operational modules cover stock, quotes, sales receipts, purchases, cash sessions, receivables, payables and inventory reports.
How it is built
- Next.js frontend with protected dashboard routes and shared resource-table primitives.
- Express API organized into auth, products, inventory, equivalences, sales, purchases, finance, contacts, reports and system modules.
- PostgreSQL schema specialized for spare parts, central inventory and vehicle-model application groups.
Stack
Next.js · React · TypeScript · Node.js · Express · PostgreSQL · Drizzle ORM · TanStack Query · Zustand · React PDF · Tailwind CSS · Zod