eCommerce logistics consulting: connect shop, WMS and carriers

eCommerce logistics does not stop when an order is submitted. Stock, allocation, picking, packing, labels, tracking, delivery and returns cross several systems and responsibilities, and exceptions must remain visible.

Operational situations to recognise

• Stock differs across the shop, ERP, marketplaces and warehouse.
• Orders or labels are transferred manually between systems.
• Picking, shipping or return exceptions sit outside a traceable workflow.
• Ownership is unclear across the commerce team, warehouse, 3PL provider and carriers.

When eCommerce logistics consulting can help

• You are opening a warehouse or reorganising its processes, workstations and systems.
• You need to select or change a 3PL provider and compare requirements, responsibilities and integrations.
• The shop, ERP and WMS need to be connected, or the existing integration no longer supports the process.
• Orders, documents or labels are transferred manually.
• Warehouse availability does not match stock published on sales channels.
• Shipping, tracking or returns are not synchronised correctly.
• Responsibilities are unclear across the company, warehouse, suppliers and carriers.

The intended operating flow

The target is an order-to-return process that people can read and monitor, with defined data sources, documented exchanges, operator-friendly states and explicit exception handling. Priorities and delivery timing depend on the actual scope and systems involved.

What I examine

I examine checkout, ERP or OMS, availability, stock allocation, receiving, locations, inventory, picking, packing, multi-parcel shipments, labels, collections, tracking, delivery and returns. The map covers commerce platforms, marketplaces, WMS, 3PL providers, carriers, data and ownership.

When data exchange is the main issue, eCommerce integration with ERP, PIM and WMS covers sources and integration mechanisms in more detail.

Operational experience with Umbria Hub

My work as co-founder and CTO of Umbria Hub lets me assess the operating consequences of technical decisions. An availability rule affects goods receiving and what can be promised by the shop; incomplete data can slow picking and packing; labels, shipping and tracking must also work in exceptional cases; returns and errors need states and ownership that operators can understand.

This experience helps verify the architecture against day-to-day warehouse work. Umbria Hub is not a mandatory solution: the consulting engagement can concern an internal warehouse or any 3PL provider involved in the project.

What the client receives

The agreed scope can include an order-to-return flow map, systems architecture, build-versus-buy assessment, requirements and acceptance criteria, integration specifications, focused operational software, documentation and a monitoring plan.

Decisions that define the solution

• Where available stock and the authoritative order status live.
• Which events trigger allocation, preparation, shipping, tracking and returns.
• How retries, duplicates, reconciliation and operational exceptions are handled.
• When to extend an ERP or WMS, introduce middleware or build a focused function.
• Who owns the flow, the data and intervention when something fails.

How the work proceeds

1. Map the current process, including exceptions and manual steps.
2. Define the target architecture and choose between integration, products and focused development.
3. Deliver a pilot or first verifiable release within the agreed scope.
4. Move to production with monitoring, documentation and improvement.

Responsibilities and the boundary with Umbria Hub

giuseppemorelli.net provides consulting, architecture, integrations, automation and software: I personally handle analysis, technical decisions, specifications and delivery within the agreed scope.

Umbria Hub provides 3PL operations: storage, picking, packing, shipping and operational returns management. When a client uses another provider or an internal warehouse, the project is designed around the systems and responsibilities actually in place.

Relevant published work

The Portfolio includes the mobile-first application for managing TCA Trasporti’s vehicle fleet, a documented example of operational software used around real users and processes.

Technologies and systems

ERP, OMS, WMS, APIs, webhooks, queues, exchange formats, operator panels, carrier services and commerce platforms are tools. They are selected and connected around the process, responsibilities and constraints found during analysis.