CONNECTING WAREHOUSE, ORDER MANAGEMENT, AND TRANSPORT FOR A MULTINATIONAL RETAIL GROUP

Smartlog SWM and STM with OMS integration was implemented for a large multi-category modern retail business handling approximately 1,500–1,700 trips per month. The project focused on stabilizing data flows across warehouse, order fulfillment, and transportation processes, including Shipment Order creation, allocation logic, pick-detail control, and rollcage/MHE visibility. The objective was to reduce integration-related exceptions and build a more reliable operating foundation for large-scale retail fulfillment.

ABOUT OUR CUSTOMER

Our customer is a large multi-category modern retailer operating across FMCG, food, and non-food categories.

The network handles approximately 1,500–1,700 transport trips per month, with warehouse, fulfillment, transportation, and store operations closely connected.

OPERATING CONTEXT

At large retail scale, a single order may pass through several systems before reaching the store.

In this project, key process interfaces between SWM, STM and OMS affected Shipment Order creation, allocation, pick details, and rollcage/MHE status management.

When data or status updates were not synchronized correctly, issues could affect outbound processing, delivery scanning, and asset recovery.

KEY CHALLENGES

Duplicate transactions during order processing.
Concurrent allocation activities could create duplicate pick details.

Dropped outbound orders under high data volumes.
Large order batches transmitted between systems could lead to duplicate order keys and failed Shipment Order generation.

Inconsistent rollcage/MHE status.
Asset status was not always synchronized across warehouse, transport, and store operations.

Manual exception handling.
When integration issues occurred, users and support teams often relied on manual or semi-manual recovery steps.

SMARTLOG'S APPROACH

Smartlog focused on standardizing the interfaces between warehouse, order management, and transportation rather than treating each system as an isolated application.

Stabilized Shipment Order creation
Smartlog helped standardize data flows between GOLD/OMS and downstream operational systems.

Standardized allocation logic
Allocate/fairshare logic and pick-detail controls were refined to reduce duplicate or inconsistent transactions.

End-to-end rollcage/MHE visibility
Asset status was managed across warehouse, transport, and store processes.

Reduced manual exception handling
Exception workflows were standardized to make issue recovery more consistent for operations teams.

RESULTS

The available project materials do not yet provide quantified before-and-after KPIs for OTD/OTIF, cost savings, or processing time.

The confirmed operational value includes:

• More stable fulfillment flows

• Reduced risk of dropped orders and duplicate transactions

• Improved rollcage/MHE control

• More reliable data exchange between systems

• Less reliance on manual exception handling

BUSINESS VALUE

In large-scale retail, scalability depends not only on individual applications but also on the reliability of data flows between them.

By improving integration across SWM, STM and OMS, the business gains a more stable foundation for order fulfillment, outbound operations, and asset control.

This helps support future growth in order volumes and omnichannel distribution without increasing operational complexity at the same rate.