Shipping Stack

The Complete US Ecommerce Shipping Stack

By EasyShippingX Editorial TeamPublished Updated

Ask a typical seller how shipping works and you will hear a simple story: the order comes in, someone prints a label, a carrier picks it up, and the customer receives it. Four steps, one direction, done. That story describes a label printer, not a shipping operation. A modern US ecommerce business that fulfills thousands of orders a day across multiple channels, warehouses and carriers runs on something much bigger: a complete shipping stack.

This guide breaks the entire shipping operation into ten layers: order, order management (OMS), inventory and warehouse (WMS), shipping platform, carrier handover, tracking, delivery, returns, billing and reconciliation, and analytics. Read it and you will know what each layer does, who owns it, and where the money and risk hide in your own operation.

Ecommerce shipping stack linking order management, warehousing, shipping software and carrier networks.
The path an order takes is far longer than "print a label and ship"

Why This Matters: A Stack, Not a Label Printer

The naive mental model looks like a single pipe. Order goes in, label comes out, the carrier does the rest.

The ecommerce shipping overview connects the layers of the stack to the merchant operating model. Use the 3PL API procurement guide when evaluating the carrier-execution interface for a multi-client 3PL.

Flow: the naive mental model, order to print label to carrier to customer
The naive mental model: order, print label, carrier, customer

In reality, the pipe is a lie. A modern shipping operation is a stack of systems, people, workflows and data that spans the whole order lifecycle, from the sales channel where the order is created to the analytics that tell you which carrier actually made you money. Each layer has a distinct job, holds different data, and is owned by different decision makers.

The stack view matters for a practical reason: costs and failures hide at the seams. A package is not expensive because of one bad label; it gets expensive because nobody reconciled the DIM surcharge on the invoice, or because the routing rule quietly sent a 3-pound parcel through a national carrier when a regional one was 40% cheaper. When you can see the whole stack, you can see where the money and the risk actually move.

Layers 1-2: Order & Order Management (OMS)

Every shipment starts as an order. In a modern US ecommerce business, orders arrive from many sources at once: Shopify, Amazon, Walmart, TikTok Shop and eBay, plus wholesale, POS and direct B2B flows. Each order carries a small but critical data payload: customer, address, SKU, quantity and payment. That payload is the raw material every downstream layer works with, so how it is captured, cleaned and routed at this first step sets the ceiling for everything after it.

The order management layer (OMS) decides how the order should be fulfilled. It is the first place where a raw order becomes a structured, routable instruction. Its core responsibilities are:

  • Split/merge orders. Line items on one order can ship from different warehouses or at different times, and multiple orders to the same address can be consolidated to save on parcel count.
  • Inventory reservation. The OMS checks available stock and reserves units so two orders do not promise the same last box.
  • Warehouse assignment. Based on stock location, shipping address and cost, the OMS picks which fulfillment center should pick and pack the order.
  • Fulfillment priority. Not all orders are equal: expedited orders, VIP customers and marketplace SLA deadlines get pushed to the front of the queue.

The decision makers here are the merchandising and order operations teams. This layer rarely grabs headlines, but a sloppy OMS corrupts everything downstream: wrong warehouse assignments create split shipments, and unreserved inventory creates oversells that turn into cancels and angry customers.

Layer 3: Inventory & Warehouse (WMS)

The WMS layer is where the digital order becomes a physical parcel. Warehouse systems manage inventory, picking, packing and shipping readiness: they know which bin holds which SKU, which picker should walk which route, and which pack station can produce a box that survives transit.

Physically, the order moves through a predictable path: a location lookup, a pick list, a pack station where it is weighed and measured, and a staging area where it waits for carrier pickup. The WMS keeps that physical flow honest by tracking inventory movement in real time, so the count the OMS reserved matches the units actually picked.

This layer also produces the data handoff the shipping platform depends on: weight, dimensions, SKU, destination and the promised service level. Get that handoff wrong, in either direction, and every downstream decision is built on bad input. An understated weight gets corrected at the carrier's scale with an invoice adjustment; an overstated one pays for capacity it never used.

Layer 4: The Shipping Platform

The shipping platform is the decision layer: it is where shipping choices actually get made. Every parcel that leaves the building passes through a rate shopping and label generation decision here, which makes this layer the closest thing the stack has to a brain. Its core responsibilities are:

  • Rate shopping. Querying live rates across carriers for the exact parcel, origin and destination.
  • Carrier selection. Applying cost, transit time and reliability trade-offs, usually through routing rules the business configures once.
  • Label generation. Producing carrier-compliant labels with the right service, barcode and postage.
  • Routing rules. Automating the "which carrier for which package" decision, for example: under 1 lb always USPS, over 5 lb compare UPS vs FedEx, west coast regional network for local zones.
  • Manifest. Batch-confirming all labels of a pickup or drop-off with the carrier.
  • DIM weight calculation. Converting length, width and height into billable weight, so a light box in a big carton pays for the space it occupies, not just its scale weight.

To see why rate shopping matters, take a sample parcel: 2 pounds, Los Angeles to Chicago, ground service. Illustrative list rates look roughly like this: a regional last-mile carrier at about $5.80, USPS Ground Advantage around $7.95, UPS Ground about $12.40 and FedEx Ground around $12.95.

Bar chart of example ground rates for a 2 lb parcel from Los Angeles to Chicago: regional carrier 5.8, USPS Ground Advantage 7.95, UPS Ground 12.4, FedEx Ground 12.95 USD
The same parcel ranges from about $5.80 to $12.95 in example ground rates (illustrative)

The same parcel, the same transit promise, and the range from cheapest to most expensive is more than double. That gap is exactly what the shipping platform exists to capture, package by package, and why DIM weight matters: a 2-pound item shipped in an 18 x 12 x 8 in box bills at 18 x 12 x 8 / 139, about 12.4 pounds, so a sloppy pack job can silently turn a cheap shipment into an expensive one.

Products in this layer, such as EasyShippingX, Shippo and EasyPost, all do the same core job from different angles: they normalize carrier APIs into one interface, apply your business rules, and become the single source of truth for label data and cost. That is why this layer sits between the WMS and the carriers: it is the translation layer that lets one warehouse talk to many carriers without maintaining a dozen integrations.

Layer 5: Carrier Handover

At the carrier handover, the package leaves your control and enters the carrier network. In the US market that network is a mix of two very different kinds of carriers. The national networks, USPS, UPS and FedEx, cover the whole country with predictable zone pricing and broad service menus. The regional and local networks, such as UniUni, GOFO and SpeedX, cover dense corridors and specific geographies, often at lower cost per parcel because their drivers only work a tight area.

A mature operation treats carriers as a portfolio, not a single vendor. The play is zone economics and last-mile density: national carriers take the long-haul and low-density lanes, regional carriers take the dense corridors where their cost per stop is lower and their transit is often faster, and the routing rules in the shipping platform decide the split automatically.

The handover itself is a moment of truth. Package acceptance scans, pickup manifests and the carrier's service commitment (SLA) are all created at this boundary. This is also where liability passes: a parcel that was never scanned in is a parcel you cannot prove you shipped. Operations teams watch this layer like hawks, because the handover is where the shipping platform's promises meet the carrier's reality.

Workers scan labels and load parcels during a warehouse dock handoff.
The handover is where liability passes: scans, manifests and SLAs are all born at this boundary

Layers 6-8: Tracking, Delivery & Returns

Once the parcel is in the carrier network, tracking events start flowing. Each scan (pickup, sort, out for delivery, delivered) is data, and a good stack synchronizes that data with three audiences at once: the merchant's internal systems, the customer's inbox or app, and the customer support team that answers "where is my package?" The best operations don't just display tracking, they monitor it for exceptions and proactively alert the customer before the customer has to ask.

Delivery is the moment the whole stack has been working toward: the carrier completes the final stop and generates delivery confirmation, or proof of delivery (POD). The POD matters beyond customer satisfaction: it is the evidence trail for chargebacks, claims and disputes, and it closes the loop on the SLA the carrier promised at handover.

Returns are the layer most stacks under-build, and they are simply the logistics lifecycle starting again. A return kicks off an RMA, a return label, an inbound scan, an inspection that decides restock vs repair vs dispose, and a new inventory movement that the WMS must book. Returns also flow back into analytics: a high return rate on a specific SKU or a specific carrier lane is a signal, not noise.

Closing the loop is what separates a stack from a collection of tools: tracking data feeds back into carrier performance scoring, so next month's routing rules are built on last month's actual on-time percentages, damage rates and exceptions, not on sales pitches.

Layers 9-10: Billing, Reconciliation & Analytics

The top of the stack is where the money gets settled and the operation gets smarter. Billing and reconciliation is the unglamorous layer that keeps carriers honest: every carrier invoice is reconciled against the labels that were actually created, and against adjustments, DIM disputes, accessorials and surcharges that quietly inflate the bill. Businesses that skip this layer routinely pay 3-5% more than their contracted rates.

Above that sits analytics and optimization: continuous improvement of shipping cost, carrier performance and customer experience. Which carriers actually hit their SLA on your lanes? Which SKUs have the worst damage rate? What does cost per parcel look like by channel, warehouse and zone? These questions are only answerable because every layer below generated structured data.

And that is the key takeaway: a modern ecommerce shipping operation is not one carrier, and it is not one software product. It is a coordinated stack in which each layer has different responsibilities, different data and different decision makers, from the order ops team that splits orders to the finance team that reconciles invoices. Businesses that understand the entire stack reduce costs, improve delivery performance and, most importantly, build a shipping operation that scales when the orders do.

Flow: customer, sales channel, order management, warehouse management, shipping platform, carrier network, tracking and delivery, billing and reconciliation, analytics and optimization
The end-to-end shipping stack: from customer to analytics and optimization

Key Takeaways

  • A modern shipping operation is a coordinated stack, not one carrier or one software product; each layer has different responsibilities, different data and different owners.
  • Costs and failures hide at the seams: unreconciled DIM surcharges, routing rules that quietly send parcels to expensive carriers, and bad data handoffs between the WMS and the shipping platform.
  • The shipping platform is the decision layer: rate shopping, carrier selection, routing rules, manifests and DIM calculation turn carrier choice from guesswork into a repeatable decision.
  • Treat carriers as a portfolio: national networks take long-haul and low-density lanes, regional networks take dense corridors, split automatically by routing rules.
  • Tracking, POD and returns close the loop: tracking data feeds carrier scoring, and returns restart the lifecycle with RMA, inspection and disposition.
  • Reconciliation keeps carriers honest (skipping it usually costs 3-5%), and analytics turns the structured data every layer produces into continuous cost and service improvement.

FAQ

A shipping stack is the coordinated set of systems, people, workflows and data that moves an order from the sales channel to the customer's doorstep and, when needed, back again: order sources, order management (OMS), inventory and warehouse (WMS), shipping platform, carrier handover, tracking, delivery, returns, billing and reconciliation, and analytics. Each layer holds different data, makes different decisions, and has different owners; looking at any single point hides how money and risk flow between the layers.
Mostly at the seams between layers: DIM surcharges on invoices nobody reconciles, routing rules that quietly send a 3-pound parcel through a national carrier, wrong weight and dimension handoffs between the WMS and the shipping platform, and skipped reconciliation (businesses that skip it typically pay 3-5% more than their contracted rates). That is why seeing the whole stack is itself worth money.
Not on every lane. Regional carriers such as UniUni, GOFO and SpeedX win on dense corridors where their cost per stop is lower and transit is often faster; national networks such as USPS, UPS and FedEx win on long-haul and low-density lanes. A mature operation treats carriers as a portfolio and lets the shipping platform's routing rules decide the split parcel by parcel.
Yes, because no single carrier is cheapest on every lane and weight. In this guide's example, a 2-pound parcel from Los Angeles to Chicago ranges from about $5.80 with a regional carrier to about $12.95 with FedEx Ground, more than double. Rate shopping exists to capture that gap, package by package.
Start where the data is cleanest and the decisions most repeatable: get orders and inventory into one place (OMS/WMS), then put a shipping platform in the middle to normalize carrier APIs, apply routing rules, and become the single source of truth for label data and cost; add tracking, returns and reconciliation as volume justifies each layer.