Analytics and Reporting
Warpspeed's analytics layer ties live operational events to financial cost so margin is visible per order, per SKU, and per carrier. Built on the same data store the dashboard reads, so finance and operations stop arguing about whose number is right.
TL;DR
Most fulfillment reporting has the same failure mode. The 3PL sends a monthly invoice with bundled lines, the brand opens a spreadsheet, the finance team spends three days reconciling, and by the time anyone has a clean number the month is two weeks gone. Decisions get made on stale data or on intuition. That is fine for a small operation. It breaks at scale.
We built the analytics layer to close that loop. Every cost event, freight charge, labor minute, and packaging unit is captured at the order level as it happens. The same data feeds the daily operational dashboard, the monthly financial reports, and the API that hands raw rows to your warehouse for BI. One source, three audiences.
Section 01
Most 3PL invoices report fulfillment cost as a bucket. Pick fees, pack fees, packaging materials, and freight live on separate lines and a brand has to allocate them back to a SKU manually if they want unit economics. Our SKU P&L does the allocation in real time. Every line on the invoice is keyed to the specific orders and SKUs that triggered it.
Fields surfaced on the SKU P&L view
| Field | Description |
|---|---|
| Units shipped | Count of units fulfilled in the period |
| Average fulfillment cost | Pick, pack, packaging, and base fees per unit |
| Average freight cost | Outbound shipping cost per unit, including surcharges |
| Returns rate | Returned units divided by shipped units in the period |
| Returns cost per unit | Reverse freight, restocking labor, and write-downs per unit returned |
| Net contribution per unit | Sale price minus all fulfillment-side costs above |
| Inventory days on hand | Average on-hand units divided by daily sell-through |
| Holding cost | Storage fees, capital cost, and shrink applied per unit |
Brands use this view in two ways. Merchandising uses it to retire SKUs that look profitable on the gross-margin line but lose money once freight and returns are included. Finance uses it to set retail prices that recover actual costs in zones where freight has crept up. Both decisions are invisible without per-SKU economics[1].
“Gross margin lies. Contribution per unit shipped does not.”
Section 02
Freight is the largest variable cost in most D2C fulfillment models, and the one most likely to surprise a brand. UPS, FedEx, and USPS publish annual rate increases that have averaged in the mid single digits, and dimensional weight changes can move effective costs even when the headline rate looks flat[2]. Without a clean view by zone and weight band, a brand learns about a creep at the close of the quarter, not when it starts.
The freight report breaks out shipped volume across carrier, service level, weight band, and destination zone. Each cell shows units, total cost, average cost per unit, and a 90-day trend line. A click drills into the underlying shipment list. Brands using more than one carrier can compare cost per zone for the same service level and identify routing rules that pay back in a single peak season.
Section 03
Peak season planning in U.S. e-commerce now spans late October through early January for most brands, with Black Friday and Cyber Monday remaining the hard pinch point. Industry coverage of peak readiness consistently calls out the cost of underestimating the curve, with carriers imposing peak surcharges that materially increase per-unit freight cost during the window[4].
Our forecasting view combines a brand's own velocity with industry-level calendar effects to project labor demand, inventory positioning, and freight spend. The model is not a black box. The dashboard shows the input variables and lets a brand override any assumption with their own marketing plan. The intent is to give buyers and ops leads a starting point that is better than a prior-year copy, not to pretend the forecast is a fixed answer.
Peak planning views
| View | Question it answers |
|---|---|
| Demand by week | What unit volume should we plan for each week of Q4? |
| Labor required | How many pickers and packers per shift to hit SLA? |
| Inventory positioning | Which SKUs need extra safety stock heading into the window? |
| Carrier capacity | Where will we hit carrier pickup limits and need a backup? |
| Freight spend forecast | What will outbound freight cost during the peak surcharge window? |
Section 04
Returns are the single most under-instrumented part of e-commerce fulfillment. The National Retail Federation reported that returns equaled roughly 14.5% of total U.S. retail sales in 2023, with online returns running notably higher than in-store rates[5]. A brand that does not track returns at the SKU and reason-code level is leaving money on the table every quarter.
The returns view captures every authorization, the unit-level disposition decision, the reverse freight cost, and the customer-facing reason code. Aggregated, it answers questions a brand should ask every month. Which SKUs return at twice the catalog average? Which suppliers cluster around defect- related codes? Which marketing channels generate the highest returns rate per dollar of revenue? The answers point directly at product, sourcing, and ad spend decisions.
Returns analytics fields
| Field | Description |
|---|---|
| Reason code | Customer-selected and operator-confirmed reason |
| Disposition | Restock, refurbish, donate, dispose, or return to vendor |
| Reverse freight cost | Inbound shipping cost paid by the brand |
| Restocking labor | Labor minutes per returned unit, by disposition path |
| Cohort retention | Did the customer reorder within 90 days of the return? |
Section 05
A single brand's data is informative but blind. Without an external reference, it is impossible to know whether a 4% returns rate is good or terrible for the category. We surface several published benchmarks inside the dashboard to give context. The Pitney Bowes Parcel Shipping Index is the anchor for parcel volume and growth, with the most recent edition reporting 22.4 billion U.S. shipments in 2023 and a steady recovery toward the 2030 forecast[3]. The NRF returns report grounds returns benchmarking. FreightWaves and Supply Chain Dive provide the qualitative color.
External benchmarks surfaced in dashboards
| Benchmark | Source | Use |
|---|---|---|
| Parcel volume growth | Pitney Bowes Parcel Shipping Index | Calibrate growth assumptions in capacity planning |
| Returns rate by category | National Retail Federation | Compare brand returns rate to industry average |
| Carrier rate trend | FreightWaves carrier coverage | Anticipate annual rate increases and surcharge cycles |
| 3PL technology investment | Penn State Third-Party Logistics Study | Frame conversations with leadership about platform spend |
None of these benchmarks replace internal data. They contextualize it. A brand whose returns rate is 11% in apparel is performing well against the category average. The same number in electronics is a warning. Without the reference, a finance team has to guess which side of the line they sit on.
Section 06
Analytics that live only inside the 3PL dashboard cannot answer the questions a brand asks across systems. Marketing wants to join order-level freight cost with paid advertising spend. Finance wants returns by SKU joined to gross margin from the catalog. We built export and warehouse paths to support both.
Every report in the dashboard exports to CSV at the row level. A nightly job pushes the same datasets to a brand-owned cloud bucket if requested. For warehouse loads, the API exposes raw event streams that feed Snowflake, BigQuery, or Redshift through a simple ELT pipeline. We do not charge for export volume. The data belongs to the brand.
“The 3PL that locks your data hostage is not a partner. It is a vendor that forgot the difference.”
Section 07
The dashboard is always live. The reports that matter for decisions get sent on a schedule. A weekly operations digest goes to the brand owner with SLA, exception, and inventory health summaries. A monthly P&L pack arrives within three business days of month end with freight, fulfillment, and returns broken out at SKU level, ready to drop into a board memo.
The cadence is configurable. Brands that prefer daily emails can subscribe. Brands that want everything pushed into Slack can wire the webhook channel into a workflow tool. The point is that the reports are written to be read, not designed to overwhelm an inbox.
For finance and ops
Send us a sample order export and we will rebuild your last 90 days of P&L against the Warpspeed analytics layer. You decide whether the numbers change the way you think about pricing.