The Apparel Operator's Reporting Starter Kit: Five Reports That Actually Change Decisions

Ask an apparel operator how many reports they run and you'll typically get a number in the dozens. Ask how many they actually use to make decisions and the answer drops to a handful. The rest are dashboards built for the meeting and forgotten the next day — expensive to maintain, rarely consulted, almost never authoritative. This post is about the five that earn their keep, and why each of them has to run from one connected operational data source to be worth anything.

Why five, and why these five

The reports that change decisions in a mid-market apparel brand share three properties: they answer a question leadership can act on that week, they resolve cleanly to a single operational ledger (no "real number is somewhere between 280 and 320" variance), and they force a specific operational response when the numbers go wrong. Everything else — slick visualisation, executive-deck KPIs, custom BI — is downstream of these five.

1. Sell-through by style and channel

The single most useful report in apparel. For every active style, across every active channel (DTC, wholesale, marketplaces), what percentage of stock has sold against the launch or season window, and at what pace. The decision it drives is whether to reorder, markdown, replatform the piece to a different channel, or let it run down.

What it has to show

• Percentage sold versus available, per style, per colour, per size, per channel
• Rate of sale over the last 7, 14, and 28 days
• Expected stockout date at current rate
• Reorder lead time and decision window

Without channel granularity, the report hides the story. A style might be 90% sold on DTC and 20% sold on wholesale. The aggregate says "sold through." The channel view says "DTC caught fire; wholesale buyers didn't pick it up." Very different decisions.

Where it fails

When DTC inventory, wholesale inventory, and marketplace inventory live in different tools, the "sell-through by channel" report requires exports and reconciliation. By the time it's built, the decision window is already closing. A connected operational platform reports this from one ledger in real time.

2. Wholesale backlog and fulfilment status

For wholesale-plus-DTC apparel brands, the wholesale backlog is the single number most correlated with cash flow and retailer relationship health. Which POs are open, which units are committed, which have shipped, which are late, which customers have aged receivables tied to unshipped stock.

What it has to show

• Open POs by customer, with total units, allocated units, picked units, shipped units
• Ship-window status: on-time, at-risk, late, cancelled
• Dollar value of backlog by customer and total
• AR status: what's invoiced, what's paid, what's aged

The decisions this drives are allocation priority (which POs to pull stock for first), shipping escalation (which customers need a carrier upgrade), and retention risk (which accounts are seeing repeated late deliveries and are one step from pulling the next season's order).

3. Inventory ageing by location

Inventory that sits too long is inventory that's about to be marked down. The ageing report tells leadership what percentage of each SKU is fresh (0–60 days), ageing (60–120), stale (120–180), and dead (180+), broken out by location.

What it has to show

• Units and dollar value in each ageing bucket per SKU
• By location (owned warehouse, each 3PL, retail store)
• Trend: is the stale bucket growing or shrinking?
• Markdown recommendation threshold (configurable per season)

The decisions this drives are markdown timing, inter-location transfers (move stale stock from a slow location to a faster one), and purchasing discipline (stop ordering the same style that ages out every season).

Where it fails

If inventory data lives in the 3PL's system (one view) and your ERP (another view) and the Shopify inventory record (a third view), the ageing report averages across three realities. Connected data resolves this automatically — the receipt date that starts the clock lives in the same record as the current location and current stock.

4. Margin by style, landed-cost-corrected

The report leadership thinks they have and usually don't. Gross margin per style, calculated against true landed cost (fabric, trim, manufacturing, freight, duty, insurance all rolled into unit cost), net of returns, net of channel fee and payment processing, with revenue attributed by channel.

What it has to show

• Per-style landed unit cost (with the constituent cost buckets visible)
• Sold quantity by channel and total
• Gross revenue and net revenue (post-returns, post-fees)
• Gross margin per unit and total
• Rank by margin contribution in the period

The decisions this drives are pricing (is the style priced correctly given true cost?), reorder (are the high-margin styles being restocked enough?), and markdown strategy (a style can be aged but margin-positive even at discount, or margin-negative at full price — very different calls).

Where it fails

The landed-cost rollup is where this report breaks for most brands. If fabric and trim cost lives in a production tracker, freight and duty land in accounting, returns data lives in Shopify, and the unit cost used in margin reporting is a flat standard cost from the product master — the "margin by style" number is blended, not actual. A connected platform rolls landed cost into inventory at receipt, so every sale's margin reflects the real cost of the specific unit.

5. Production WIP against plan

The upstream counterpart to sell-through. For every open production PO, where is it in the manufacturing cycle, how does that compare to the planned lead time, and what's the expected receipt date versus the committed allocation against that receipt?

What it has to show

• PO by style, vendor, total quantity, production stage
• Stage dates (sampled, approved, cut, sewn, packed, shipped, received)
• Expected receipt date versus original plan
• Wholesale pre-book commitment against that receipt
• Gap: at current pace, will the receipt hit the commitment window?

The decisions this drives are wholesale communication (tell the buyer now if a delivery is slipping, not at the ship date), allocation re-planning (if a receipt is late, which POs get partial ship?), and vendor management (which factories consistently miss lead times?).

What's missing from this list, on purpose

The five above are operational. Intentionally missing: CAC, LTV, marketing attribution, email conversion, NPS, retention cohort curves. These are important for a DTC brand's marketing and finance teams, but they don't drive the operational decisions that run a mid-market apparel business. A separate analytics stack (GA4, Northbeam, Klaviyo reports) covers them. Mixing them into the operational reporting layer crowds out the five that actually matter.

What this looks like in practice

An apparel brand running these five reports from one connected operational system can answer the week's most important questions in under five minutes without exporting anything. Sell-through by channel drives Monday's reorder meeting. Wholesale backlog status drives the Tuesday ops call with warehouse and customer service. Inventory ageing drives the Wednesday merchandising review. Margin by style drives Thursday's pricing conversation. Production WIP against plan drives the Friday production stand-up.

The same brand running the same five reports from three disconnected systems spends most of the week reconciling and has the conversations a week later, against data that's already stale.

Related reading: Apparel operations reporting on Uphance, Single source of truth in apparel, The 6 Breakpoints of Apparel Operations. To walk through which reports your team runs today and where the reconciliation work lives, start with a discovery conversation.