Case Study: FMCG Warehouse Execution | Shivohm
Case Study: Digital Transformation

FMCG Foodservice:
Warehouse Execution Extension

1. Executive Summary

A leading FMCG foodservice distributor operating on Microsoft Dynamics 365 Finance & Operations faced critical bottlenecks in floor execution. While the ERP managed inventory records, it lacked the agility to enforce FEFO compliance and real-time picking accuracy. We engineered a custom Warehouse Execution Layer that bridges the gap between ERP planning and floor action, resulting in a 35% gain in operational velocity.

2. Client Overview

A regional powerhouse in the FMCG sector serving high-stakes clients including global QSR chains, luxury hotels, and regional café networks.

  • Scale: 4 Strategic Distribution Hubs
  • Complexity: 2,000+ Multi-temperature SKUs
  • Constraint: High sensitivity to product expiry and batch traceability.

3. Problem Statement

The "Execution Gap" manifest in three primary ways:

Manual Lag: Picking lists were semi-digital, leading to data entry delays.
Compliance Risk: FEFO was dependent on worker memory, not system enforcement.
Blind Operations: Supervisors had no view of "work-in-progress" until a shift ended.

4. Use Case

"Enforce compliance at the point of scan." The requirement was to build a system that prevents a picker from moving to the next item unless the exact batch-expiry rules were met, ensuring 100% dispatch accuracy without sacrificing speed.

5. Solution Architecture

Execution Point
Mobile Picking App
(Scanning & FEFO)
Ops Dashboard
(Real-time Monitoring)
Shivohm Intelligence Layer (Node.js)
Rules Engine
Validation Logic
Alert Manager
Audit Logger
System of Record
Microsoft Dynamics 365 F&O
(Orders, Inventory, Batch Data)

6. The 6 Core Elements

Mobile Pick App
FEFO Engine
Error Blocker
Ops Dashboard
Alert Center
Audit Module

7. Integrations

Standardized RESTful endpoints were used to maintain a clean decoupling from the ERP core:

  • Inbound: Sales Orders & Batch Master data from Dynamics.
  • Outbound: Pick-confirmations & Transaction logs back to Dynamics.
  • Reporting: Flat-file sync for legacy compliance reporting.

8. Tech Stack

Backend: Node.js / .NET Core Mobile: React Native (Android) Web: React.js DB: PostgreSQL Cloud: Azure

9. Strategic Implementation Roadmap

Our deployment follows a "Zero-Disruption" framework, ensuring the warehouse never stops moving while we upgrade the brain of the operation.

01

Process Mining & Gap Analysis

On-site shadowing of warehouse personnel to identify "tribal knowledge" routines that the ERP currently misses. We define the FEFO "Hard Rules" here.

02

Sandbox Integration (API Stress Test)

Building the RESTful bridge. We simulate peak-load sales orders to ensure the Node.js middleware handles high-concurrency without lagging the Dynamics 365 core.

03

The "Dark Launch" Pilot

Rollout in a single high-velocity zone (e.g., Cold Storage). System runs in parallel with existing processes to verify batch-validation accuracy.

04

Phased Site Rollout & Hyper-Care

Full deployment across all 4 hubs. Includes 24/7 "Hyper-Care" support and on-floor training to ensure 100% staff adoption within 48 hours.

10. Outcomes & KPIs

35% Faster Picking Time
60% Fewer Errors
99.9% FEFO Compliance
1 Day Audit Preparation

11. Future Enhancements

  • AI Slotting: Dynamic warehouse reorganization based on velocity.
  • Predictive Labor: Scaling workforce based on inbound sales forecasts.

12. Final Takeaways

Custom extensions do not "fight" the ERP; they unlock its value. By moving logic to the action point, we ensured that the ERP remains a clean ledger while the warehouse floor remains a high-speed execution machine.