Warehouse ERP
Internal operations system unifying orders, quotes, invoices, and inventory across departments — built for a ship-delivery wholesale supplier.
- Modules
- Orders · Quotes · Invoices · Inventory
- Migration
- AWS Lambda + Cognito → Supabase
- Status
- Final feedback cycle
Context
A ship-delivery supplier serving commercial vessels needed to replace a scatter of spreadsheets + legacy tools with a single internal system. Departments (sales, operations, finance) were each tracking parts of the same order in different places.
Challenge
- Quote → order → delivery → invoice workflow fragmented across tools
- Inventory visibility lagged behind reality (manual counts, late updates)
- Authentication + permissions sprawled across AWS Cognito + custom logic
- Legacy stack (AWS Lambda + Cognito) was expensive to operate for the team's size
Solution
A modern, internal Next.js 15 App Router app with Supabase as the single source of truth:
- Unified order lifecycle: quote draft → approval → fulfillment → invoice
- Role-based access (sales / ops / finance / admin)
- Live inventory synced with order state
- Migrated off AWS Lambda + Cognito to Supabase in 2026-04 — same feature set, lower operating cost, faster iteration
Status
Core modules are live internally. The system is in the final-feedback cycle with the client — last round of UX tweaks before full handover and training.
What this proves for SJSoftware
End-to-end internal B2B operations systems are deliverable in months, not years — including legacy stack migration as part of the scope.
Adapts to other operations-heavy SMBs:
- Wholesale & distribution — order intake, inventory across multiple warehouses, dispatch, automated invoicing to retail buyers. Same quote-to-cash spine.
- Light manufacturing — bill-of-materials, production scheduling, raw-material inventory tied to finished-goods stock, batch traceability.
- Logistics & freight forwarding — shipment tracking, customs documents, cost-vs-quote reconciliation, multi-party invoicing.
- Field service operations — work orders, technician scheduling, parts inventory at customer sites, quote-on-completion workflow.
If your business runs on the spreadsheet pattern — sales tracks orders one place, ops tracks fulfillment another, finance bills from a third — the same architecture (single source of truth, role-based access, live inventory) collapses that into one system. Typical timeline: 8–12 weeks for the core, then iteration on real usage.