Supply Chain Architecture Advisory
Supply Chain Platforms That
Keep Inventory Where
Demand Actually Is
Architecture advisory for supply chain platforms, WMS and 3PL integration, demand planning systems, and the data contracts that keep your OMS, warehouse, and SCM in agreement.
WMS & Warehouse Architecture
3PL Integration
Demand Planning Platforms
20+Years Technology Leadership
WMSArchitecture & Integration
3PLFulfilment Networks
SCMPlatform Architecture
DemandPlanning Integration
VendorManagement Systems
The Reality
What Breaks First
in Supply Chain Technology
Demand Signals Disconnected from Replenishment
Demand planning runs on last month's data while the OMS has real-time sell-through velocity. The replenishment plan is always lagging reality - you're restocking what sold last month, not what's selling now.
Inventory in the Wrong Fulfilment Nodes
Stock is available in the network but positioned at the wrong warehouse. Mumbai orders are being routed from Delhi. Last-mile cost spikes. SLA misses increase. The root cause is inventory positioning that doesn't reflect order geography.
WMS and OMS Run Independently
The warehouse has inventory the OMS doesn't know about. Orders are released to fulfilment against theoretical stock. Pick failures happen because the WMS and OMS are only reconciled at end of day, not in real time.
Vendor Onboarding Takes Months
Adding a new supplier requires manual catalog setup, PO template configuration, and custom EDI mapping. By the time the vendor is operational, the season or the opportunity has passed.
3PL Data Lives in Their Portal
Your third-party logistics provider sends weekly reports. You have no API access to inventory positions or dispatch events. Your OMS is running on data that's 24-48 hours behind actual warehouse state.
Cold Chain Has No Compliance Tracking
Temperature-sensitive products move through your supply chain without automated temperature excursion alerts, expiry tracking, or FEFO enforcement at pick. Compliance is managed manually, audited after the fact.
Procurement Is Outside the System
Purchase orders are raised in email and tracked in spreadsheets. There's no system visibility into inbound lead times, supplier confirmation status, or expected receipt dates - so inventory planning is based on estimates, not actuals.
Visibility Stops at the DC Gate
You know what left the distribution centre. You don't know where it is in transit, when it will arrive at the downstream fulfilment node, or when it's available to promise. Customers are told delivery dates based on hope, not data.
Inbound Lead Times Not in the Plan
Demand planning generates replenishment orders based on depletion rate without factoring in actual supplier lead times. Orders are raised too late. Stockouts happen while the PO is in transit. Reorder points are theoretical, not calibrated.
SCM Platform Bought, Never Integrated
A demand planning or SCM platform was licensed, partially configured, and abandoned when the integration to the ERP and OMS proved more complex than expected. It's now running in parallel with spreadsheets, not replacing them.
Advisory Areas
What I Help Supply Chain
Businesses Solve
SCM Platform Architecture
Designing the supply chain platform layer - module boundaries, data contracts between SCM, OMS, WMS, and ERP, and the integration patterns that keep demand signals and inventory positions synchronized across the fulfilment network.
Demand Planning Integration
Building the data pipelines that feed demand planning systems with real-time OMS sell-through velocity and historical sales data - so replenishment decisions are grounded in current demand, not last month's batch export.
WMS Architecture & Integration
Designing the WMS integration layer - inbound ASN flows, bin-level inventory sync to OMS, pick-pack-ship event processing, and the real-time bidirectional sync that keeps warehouse and order management in agreement.
3PL Integration & Fulfilment Network
Defining the integration patterns for third-party logistics partners - ASN, GRN, inventory visibility, order release, and dispatch events - so your systems maintain accurate inventory ownership without depending on the 3PL's reporting portal.
Vendor Management System Design
Designing the vendor portal and onboarding workflow - catalog submission, PO acknowledgement, lead time commitments, and inbound ASN - with a self-service vendor interface that reduces procurement team manual work.
Procurement Platform Architecture
Bringing procurement into the system with PO lifecycle management, supplier confirmation tracking, inbound ETA visibility, and automated GRN reconciliation - replacing email-and-spreadsheet procurement with a connected workflow.
Inventory Positioning Strategy
Designing the fulfilment network logic that routes inventory to nodes based on order geography and SKU velocity - so stock is positioned where demand actually is, not distributed equally or based on historical intuition.
Cold Chain & Compliance Systems
Designing cold chain compliance layers - FEFO picking enforcement, temperature excursion monitoring, expiry tracking, and regulatory traceability documentation - for pharma, grocery, fresh produce, and FMCG categories with temperature-sensitive SKUs.
Supply Chain Architecture Flow
From Demand Signal
to Fulfilled Order
Supply chain architecture is a loop, not a pipeline. Demand signals drive procurement, procurement drives inbound, inbound drives warehouse inventory, and warehouse inventory constrains OMS fulfilment. When any stage runs on stale data, the whole loop degrades. Here's what each stage needs to work correctly.
01
Demand Signals from OMS
Real-time order velocity from the OMS is the most accurate forward demand signal available. Historical sales by SKU and fulfilment node feed the statistical baseline. The demand planning system needs both: real-time velocity for short-horizon signals and historical data for seasonality and trend models. The integration latency between OMS and demand planning determines how quickly the replenishment plan responds to demand shifts.
02
Demand Planning & Replenishment
The demand planning system generates replenishment requirements per SKU per fulfilment node, factoring in current stock levels from WMS, inbound in-transit quantities, safety stock policy, and supplier lead times. Output is a time-phased replenishment plan: what to order, when, and in what quantity. The plan is revised continuously as new OMS velocity data arrives, not regenerated weekly from a batch export.
03
Procurement & Vendor Confirmation
Approved replenishment requirements become purchase orders routed to the right supplier. Vendors confirm the PO and commit to an ETA via the vendor portal or EDI. Those ETAs update in-transit inventory records in the demand planning system, adjusting the reorder recommendation for the lead time already committed. PO status - pending, confirmed, dispatched, partially received - is visible to the planning team without email follow-up.
04
Inbound & GRN at Warehouse
Supplier dispatch creates an ASN (Advance Ship Notice) that flows to the WMS before the goods arrive. When the inbound shipment arrives, the WMS performs GRN (Goods Received Note) against the ASN - checking quantities, condition, and expiry (for perishables). GRN events update the demand planning system's in-transit inventory and trigger putaway in the WMS. Discrepancies between ASN and GRN generate automatic supplier notifications and update the outstanding PO balance.
05
Warehouse Operations & OMS Sync
The WMS manages bin-level inventory, pick-pack-ship workflows, and returns processing. Each inventory event in the WMS - putaway, pick, cycle count adjustment, damage write-off - updates the inventory ledger that the OMS reads when making fulfilment decisions. The OMS only releases orders to the WMS when the WMS confirms available inventory at the bin level. This bidirectional sync is what prevents pick failures and ghost stock from compounding.
06
Fulfilment & Supply Chain Analytics
Dispatch events from the WMS close the order in the OMS and feed back into supply chain analytics: actual fulfilment rate by SKU, node, and time period. These actuals are compared against the demand plan to measure forecast accuracy. Persistent gaps between forecast and actuals are surfaced as inputs to improve the demand model. Supply chain analytics also tracks supplier lead time performance, inbound quality rates, and WMS productivity - closing the loop from demand signal to delivery outcome.
Domain Knowledge
Supply Chain Platforms &
Systems I Understand
Supply chain complexity sits in the integration gaps - between the demand plan and the WMS, between the WMS and the OMS, between procurement and inbound visibility. Understanding each platform's data model and API surface is necessary but not sufficient; knowing how they need to connect is where architecture decisions matter.
SCM Platforms
SAP S/4HANA SCMOracle SCM CloudBlue YonderKinaxis RapidResponseManhattan SCMInfor SCMMicrosoft Dynamics SCM
WMS Platforms (India & Global)
Increff WMSVinculum WMSFynd WMSSnapFulfilOracle WMS CloudManhattan WMSSAP EWMHighJumpCustom WMS
3PL & Fulfilment Partners
Delhivery FulfilmentEcom Express WarehouseXpressBees 3PLShadowfaxFedEx Supply ChainDHL Supply ChainMahindra Logistics
ERP & Procurement Systems
SAP S/4HANASAP Business OneOracle NetSuiteMicrosoft Dynamics 365Tally ERPZoho ERPCoupa (Procurement)
Cold Chain & Specialized
FEFO PickingCold Chain ComplianceTemperature Monitoring APIsExpiry TrackingPharmaceutical DistributionFresh Produce Logistics
Integration Patterns
ASN / GRNEDI IntegrationInventory Ledger DesignMulti-Node InventoryOMS-WMS SyncDemand Planning APIsReal-Time vs Batch Sync
Platform Deep Dive
Supply Chain Platforms
I Work With
Supply chain platform selection is often less important than the integration architecture. A well-integrated mid-market WMS outperforms a poorly-integrated enterprise SCM platform. Here's the advisory lens I apply across the major platform categories.
Increff, Vinculum & Fynd WMS
Increff WMSVinculum OMSFyndMulti-Channel
Increff, Vinculum, and Fynd are the dominant WMS platforms in India's commerce market. Increff specialises in fashion and apparel with strong size-set management. Vinculum covers WMS, OMS, and multi-channel fulfilment in one platform, widely used in D2C and marketplace-first businesses. Fynd extends into in-store inventory and omni-channel retail. Advisory covers WMS-OMS integration design, sync frequency, inventory event architecture, and the bidirectional data contracts each platform exposes.
SAP SCM & Oracle SCM Cloud
SAP S/4HANASAP EWMOracle SCMDemand Planning
SAP and Oracle SCM platforms are enterprise-grade with deep functionality but significant integration complexity. SAP EWM (Extended Warehouse Management) and Oracle WMS Cloud require careful data contract design with your OMS and ERP. The common failure mode is an SAP SCM implementation that runs in batch sync with the OMS, making real-time fulfilment decisions unreliable. Advisory covers the integration architecture, sync patterns, and the data model decisions that determine whether the platform works in real operations.
Blue Yonder & Kinaxis
Blue Yonder DemandKinaxis RapidResponseDemand Planning
Blue Yonder (formerly JDA) and Kinaxis are specialist demand planning and supply chain visibility platforms. Their value depends entirely on the quality of the data flowing in - OMS sell-through velocity, WMS inventory positions, and supplier lead time actuals. Advisory covers the integration architecture for feeding these platforms with real-time data, and defining the API contracts between your OMS and the demand planning layer so replenishment decisions are genuinely data-driven.
3PL Integration Patterns
API IntegrationASN / GRNInventory EventsOrder Release
3PL integration requires four data flows: inbound ASN from your procurement system to the 3PL WMS, GRN confirmation back from the 3PL on receipt, real-time inventory positions from the 3PL to your inventory ledger, and order release from your OMS to the 3PL pick workflow. The pattern that fails most often is relying on the 3PL's portal for inventory data rather than building an API integration - you need events, not reports, to maintain accurate inventory positions in real time.
Vendor Management & Procurement Portals
Vendor PortalPO ManagementLead Time TrackingASN
A vendor management platform gives suppliers self-service access to POs, delivery windows, and ASN submission - replacing email-based procurement with a connected workflow. The integration challenge is syncing PO data from your ERP or procurement system to the vendor portal in real-time, and flowing vendor ASN submissions back to the WMS for inbound preparation. Advisory covers vendor portal architecture, onboarding workflow design, and the ERP-to-portal data contracts.
Cold Chain & FEFO Systems
FEFO PickingTemperature APIsExpiry TrackingCompliance Docs
Cold chain adds temperature compliance, expiry-based inventory management, and regulatory traceability on top of standard WMS functionality. FEFO (First Expiry First Out) picking rules must be enforced at the WMS pick instruction level, not managed manually by warehouse staff. Temperature excursion monitoring requires IoT sensor integration with the WMS, with automatic quarantine of affected batches. Advisory covers the WMS configuration decisions, IoT integration patterns, and compliance documentation architecture for pharma, grocery, and FMCG categories.
Modernization
Connecting the Supply Chain
Without Disrupting Operations
Supply chain modernization carries significant operational risk. Switching WMS systems mid-season, changing 3PL partners during peak, or re-integrating an SCM platform while orders are flowing requires precise sequencing and fallback planning.
The approach I use is layer-by-layer. Establish the inventory ledger first - a single source of truth for inventory positions across all nodes. Integrate the WMS to that ledger. Then connect demand planning. Then extend to 3PL partners and vendor management. Each layer validates independently before the next builds on it.
The goal is a supply chain where inventory positions are accurate in real time, replenishment decisions are data-driven, and the fulfilment network can be extended to new nodes without re-architecting the integration layer.
- WMS and OMS inventory synchronized in real time
- Demand planning grounded in current OMS sell-through data
- 3PL inventory visible in your system, not just their portal
- Inbound ASN and GRN flowing between supplier, WMS, and ERP
- Vendor lead times tracked in the system, not via email
- Cold chain FEFO enforced at pick, not managed manually
- New fulfilment nodes added without re-integrating the OMS
Practical AI
Where AI Helps
Supply Chain Operations
Supply chain AI use cases that work are grounded in data you already have - OMS velocity, WMS inventory positions, supplier lead times, and historical fulfilment data. These are the applications worth looking at seriously.
Demand Forecasting Intelligence
ML-based demand forecasting on top of OMS velocity data and historical sales, with seasonality, promotional, and external signal inputs - producing more accurate SKU-level replenishment signals than statistical models alone.
Inventory Positioning Optimisation
Optimising inventory allocation across fulfilment nodes based on predicted order geography and SKU velocity - minimising last-mile cost and SLA misses by positioning stock closer to where demand will actually occur.
Supply Chain Anomaly Detection
Detecting unusual patterns in inventory movements, inbound receipt rates, and supplier lead times before they cause stockouts or overstocking - surfacing risks early enough for intervention rather than after the damage is done.
Supplier Performance Scoring
Scoring supplier performance on lead time adherence, fill rate, quality reject rate, and ASN accuracy - building the data layer that informs vendor management decisions and identifies which suppliers create supply chain risk.
Supply Chain Operations Copilot
Natural language queries across supply chain data - inventory positions, inbound ETAs, stockout risks, and fulfilment exceptions - letting planning and operations teams get answers without pulling reports from multiple systems.
Who This Is For
The Businesses That
Reach Out to Me
Retail & Commerce Businesses
Growing retail operations where WMS, OMS, and ERP are running as separate silos. Inventory accuracy is declining, fulfilment costs are rising, and replenishment is always reactive. The supply chain architecture needs to catch up with the order volume.
FMCG & Consumer Goods Companies
Managing primary distribution alongside D2C and marketplace fulfilment. Supply chain architecture must connect distribution, warehouse, and last-mile layers with a consistent inventory view across all channels.
Commerce & Supply Chain SaaS
Building WMS, SCM, or fulfilment platforms for retail customers. Platform architecture, multi-tenant WMS design, API-first integration patterns, and supply chain data model design are the advisory areas most relevant here.
Teams Modernising Legacy Supply Chains
A supply chain built for 1,000 orders a day that's now processing 100,000. Every new warehouse, 3PL partner, or channel integration requires custom engineering. You need a supply chain architecture that extends without bespoke work per integration.
Why This Matters
Supply Chain Is Where
Commerce Margins Are Made
Supply chain architecture decisions have direct P&L consequences. Inventory positioned in the wrong nodes drives up last-mile cost. WMS-OMS sync gaps cause pick failures that cost fulfilment labour and customer trust. Demand plans disconnected from real-time OMS data create overstock and stockout cycles simultaneously.
The businesses that manage supply chain costs well aren't the ones with the most expensive platforms. They're the ones with the cleanest integration architecture - where inventory positions are accurate, demand signals are real-time, and every system reads from a shared source of truth.
20+
Years in Technology Leadership
31+
Products Shipped to Production
35M+
API calls/day at peak scale
5
India, UAE, Maldives, USA & Canada
FAQ
Common Questions
What's the difference between OMS and SCM in commerce?
OMS manages the customer-facing order lifecycle - from placement through fulfilment to delivery. SCM manages the upstream supply side - demand forecasting, procurement, vendor management, and inventory positioning across the fulfilment network. They need to be tightly integrated: OMS demand signals should drive SCM replenishment decisions, and SCM inventory positions should constrain OMS fulfilment routing.
We have SAP but it's not integrated with our WMS. Where do we start?
Start with the data contracts: what does SAP need from the WMS and what does the WMS need from SAP? Typically SAP needs GRN confirmation, inventory positions, and dispatch events. WMS needs approved POs, item master, and inbound ASNs. Map those flows, define sync frequency and error handling, then implement the integration in stages - inbound first, then inventory sync, then outbound dispatch.
How do you approach demand planning integration?
Demand planning integration needs two data streams: real-time OMS order velocity at the SKU-location level, and historical sales data for trend and seasonality models. Without both, the demand plan is either lagged or disconnected from what's actually selling. The integration architecture needs defined latency - near-real-time OMS signals, daily historical reconciliation.
Our 3PL gives us reports instead of API data. Is that a problem?
Yes, if you're managing more than a few hundred orders per day. Report-based 3PL data means your OMS is always behind on inventory position and dispatch status. The practical path is either getting the 3PL to enable their API (most enterprise 3PLs have one), building a data ingestion layer from the reports, or switching to a 3PL with better connectivity.
How do we build visibility into multi-warehouse inventory positioning?
Multi-warehouse visibility requires a single inventory ledger that aggregates positions across all fulfilment nodes. Each location publishes inventory events; the central ledger applies them in order. The OMS reads from this ledger when making fulfilment routing decisions, not from individual WMS systems directly. This is the architecture that makes multi-node fulfilment reliable.
What's your approach to cold chain compliance systems?
Cold chain compliance requires FEFO picking enforced at the WMS pick instruction level, temperature monitoring integrated with the WMS (not a separate system), and traceability documentation generated automatically at dispatch. Manual cold chain management doesn't scale and creates compliance gaps. Advisory covers WMS configuration choices, IoT integration patterns, and regulatory documentation architecture.
How long does supply chain platform integration typically take?
WMS-to-OMS integration for a single warehouse typically takes 6-10 weeks. Adding 3PL integration adds 4-8 weeks per partner. SCM demand planning integration is a longer engagement - 12-20 weeks for a meaningful implementation. The right sequencing is usually: WMS first, then 3PL, then demand planning.
What's the best way to start?
Book a 30-minute strategy session. Bring the specific supply chain problem - WMS integration, 3PL data gaps, inventory positioning, SCM platform selection. One specific problem makes the conversation productive immediately.