ERP

EPICO Warehouse

Warehouse Management System

Industry: Logistics & Warehousing
Duration: 6 months
Delivered: 2023
Client: EPICO (demo)

Next.jsTypeScriptPostgreSQLRedis

EPICO Warehouse gives operators a barcode-driven workflow for receiving, put-away, picking and dispatch, all recorded against one inventory ledger. The interface is built mobile-first for handheld terminals, while purchasing and supplier records sit alongside the stock data they affect. Background jobs handle reports and reconciliation so the floor is never blocked by a slow query. As a demo, it illustrates how a ledger-first design keeps stock counts trustworthy and makes operational reporting a by-product of normal work.

The challenge

What the business was up against

Warehouse operations were only as accurate as the last manual stock count. Receiving was recorded on paper and entered later, so the system and the shelves disagreed for most of the working day. Picking relied on tribal knowledge of where items lived, and the same SKU could exist under different names in purchasing and inventory records. Reports were assembled at month end from exported spreadsheets, by which point the numbers were historical rather than actionable. No one could answer a simple question about where a unit was or why the count differed, and dead stock accumulated because nobody could see it.

At a glance

Industry: Logistics & Warehousing
Duration: 6 months
Delivered: 2023
Engagement: Discovery → delivery → support

The solution

What we designed and shipped

We modelled the warehouse around a single inventory ledger, then built every workflow on top of it. Receiving, put-away, picking, transfers and dispatch all write double-entry movements, so the current count is always derived rather than guessed. Operators scan barcodes on handheld devices using mobile-first screens designed for gloved hands and bright aisles. Purchasing and supplier records share the same product identifiers, removing the duplicate SKUs that made reconciliation painful. Background jobs generate reports and ageing analysis from the ledger, turning stock visibility from a month-end event into a continuous view.

At a glance

Primary category: ERP
Services: ERP · Web · Enterprise
Team: Product, design, engineering, QA
Delivery: Two-week increments

Key features

What the platform actually does

Inventory Control

Ledger-based stock counts with full movement history per unit.

Product Catalogue

Unified SKU records shared by inventory and purchasing teams.

Purchase Orders

Supplier orders tracked from raised through received and reconciled.

Supplier Management

Supplier terms, lead times and historical delivery performance records.

Stock Movement

Transfers, adjustments and returns recorded as balanced ledger entries.

Operational Reports

Stock ageing, turnover and movement summaries generated on demand.

Barcode Workflows

Scan-driven receiving, put-away and picking on handheld terminals.

Architecture

How the system is put together

Each tier can be scaled, replaced or taken offline independently. Data flows left to right; failure in a downstream tier never blocks the primary transaction path.

Operator interface

Mobile-first screens built for scanners, gloves and aisle lighting.

Barcode UIScan-first flows for receiving, put-away and picking.
Mobile-first flowsLarge controls and short steps for handheld terminals.

Core services

Domain logic that keeps the ledger and purchasing records consistent.

Inventory ledgerDouble-entry stock movements with derived on-hand counts.
PurchasingPurchase orders, receipts and supplier reconciliation rules.
Supplier recordsTerms, lead times and historical delivery performance.

Async processing

Background work keeps slow jobs off the operator path.

Job queueRetries report generation and integration work reliably.
Report generatorBuilds ageing and turnover reports from ledger data.
CacheHot product and location data served without database hits.

Data

Storage split across transactional, cached and archival layers.

PostgreSQL ledgerImmutable movement history and current stock positions.
RedisCache and short-lived locks for concurrent scans.
Cold archiveClosed periods moved to cheaper long-term storage.

Technology stack

Chosen for the decade, not the demo

Every dependency here has a long support horizon, an active community and a large hiring pool. That keeps total cost of ownership predictable long after launch.

Demo project

Next.jsTypeScriptPostgreSQLRedis