Logistics Automation

Fleetbase Logistics Integration

Instead of manually creating deliveries in the logistics platform after OMS generates a shipment, this integration automates the entire flow. Shipment creation in OMS triggers automatic delivery task creation in Fleetbase, with tracking events flowing back to OMS in near real time via webhooks.

IBM Sterling OMSFleetbase APIsJavaSpring BootWebhooksREST APIs
Problem

After OMS generated a shipment, warehouse teams had to manually create delivery tasks in the logistics platform — duplicating data entry, introducing delays and creating risk of shipment information mismatches.

Solution

Java middleware receives shipment events from OMS, calls Fleetbase APIs to create delivery tasks automatically, and consumes Fleetbase webhooks to push tracking and status updates back into OMS.

Outcome

Removes manual shipment entry into the logistics system, eliminates duplicate data entry, and provides centralized shipment visibility between OMS and the logistics platform.

Key Challenge

Designing reliable webhook consumption that handles delivery events in near real time while keeping OMS shipment status accurate without over-polling Fleetbase APIs.

Working prototype — end-to-end shipment automation demonstrated Logistics Automation

Overview

Manual logistics handoffs are one of the most common sources of fulfillment errors in enterprise commerce. After OMS generates a shipment, someone has to create the corresponding delivery task in the logistics platform. This integration automates that handoff completely.

The Manual Process It Replaced

Previously, after OMS created a shipment, warehouse teams manually entered shipment details into the logistics platform. This duplicated data entry, introduced delays and created risk when information was entered incorrectly.

Automated Shipment Flow

When OMS creates a shipment, Java middleware receives the event. The middleware calls Fleetbase APIs to create a delivery task automatically. Fleetbase handles driver assignment and makes tracking information available immediately.

Tracking Back to OMS

Fleetbase generates delivery events as the shipment progresses. These events are consumed by the middleware via webhooks, which then updates OMS shipment status and tracking details through REST APIs. This keeps OMS as the source of truth for order and shipment state.

Webhook Architecture

The prototype uses Fleetbase webhooks to receive delivery updates in near real time. This approach reduces unnecessary polling and enables faster status synchronization between the logistics platform and OMS.

Key Challenge Solved

Designing reliable webhook consumption that handles out-of-order delivery events, retries on middleware failures and keeps OMS shipment status accurate without creating duplicate updates.

← Back to Projects Work with me