Connect eCommerce, warehouse, WMS and carriers in one operating flow

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.

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.

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.

What I handle personally

I handle analysis, architecture, specifications, integrations, automation and operational software where required. giuseppemorelli.net does not provide physical warehouse and fulfilment operations.

The boundary with Umbria Hub

I am co-founder and CTO of Umbria Hub; this is direct operational experience, not a client case study. giuseppemorelli.net provides consulting, architecture, integration, automation and software; Umbria Hub provides 3PL operations: storage, picking, packing, shipping and returns. This page does not present Umbria Hub as an automatic choice for a client.

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.