Unifying Sales, Inventory, and Manufacturing Data: The Apparel Operations Connectedness Test

"Our systems are connected" is one of the most confidently wrong things said inside growing apparel brands. Connected usually means "exports can be pulled from each system and reconciled into a spreadsheet." That is not connected. That is reconciled, with labour. Connected means something specific and operationally testable.

This piece walks through five questions that test whether your sales, inventory, and manufacturing data is actually unified. If you can answer all five in under a minute each, without exporting, you're in rare company. If you need to "go pull a report," the gap between what your team believes and what your systems actually deliver is the gap that is costing you margin visibility, production accuracy, and season-to-season learning.

The five connectedness questions

Question 1: For this PO, what's the current status?

Pick an open production PO. The connected answer covers: quantity ordered, expected receipt date, supplier confirmation, in-transit status, partial receipts so far, current landed-cost rollup, and units already allocated to wholesale pre-book against the expected receipt. If the answer involves opening a production tracker, a spreadsheet, and an accounting export, the data isn't unified — it's partitioned.

Question 2: For this style, what's the sell-through across all channels?

Pick a style from the current season. The connected answer: DTC units sold, wholesale units shipped (and wholesale units still open on POs), marketplace units sold, current inventory at each location, and the rate of sale per channel. In one view. If sell-through by channel requires three exports and a pivot table, the sales data isn't unified with the inventory data.

Question 3: For this season, what's the margin by style?

Pick last season. The connected answer: unit cost including landed (fabric, trim, manufacturing, freight, duty, insurance), sold quantity by channel, revenue by channel, returns cost, net revenue, and gross margin per unit. This tests whether manufacturing data (cost) is connected to sales data (revenue) through inventory (the unit). Most brands can get to a blended season margin; few can get to per-style margin in under five minutes. The gap is where pricing decisions get made on incomplete information.

Question 4: For this wholesale account, what's the history?

Pick a wholesale customer. The connected answer: orders placed across seasons, unit volumes by style, payment history, AR status, credit notes, returns, and the current open pre-book. This tests whether sales data (wholesale orders), inventory data (units shipped), and financial data (AR, credits) are tied to the customer in one place. If finance has one view and sales has another, the data isn't unified, and the account-review conversations are based on different numbers depending on who's talking.

Question 5: For this forecast, how does it reconcile to production?

Pick next season's forecast. The connected answer: by style, what units are we forecasting, what's the wholesale pre-book commitment, what's the DTC expected demand, what POs are placed with which suppliers, what quantity is committed for what lead time, and what's the gap between forecast and committed production. If the forecast and the production plan exist in different tools owned by different teams, unification has already failed where it matters most — at the planning layer.

Why the connectedness gap is expensive

For apparel brands, unconnected data is not just an inconvenience. It is a direct cost with three components:

Margin visibility erodes

If you can't see per-style margin across the season without building a spreadsheet, you are pricing, discounting, and re-ordering on blended information. The drop pieces that look like winners might be margin-negative after returns and landed cost; the slow movers might be your margin engine. Without connected data, the merchandising team is making decisions on the wrong signals.

Production-to-demand alignment drifts

Production plans get built from last season's performance. If last season's performance is reconciled by hand in a spreadsheet, the input to the next production plan is noisy. Noise compounds. Brands that can't connect manufacturing data to actual sell-through end up with chronic over-production on slow styles and chronic under-production on fast ones. The inventory ageing report is the late-stage symptom.

Season-to-season learning slows

A brand that can look at this season and honestly answer "which buyer type bought which colours into which sizes" learns from every season. A brand that can't answer that without exporting from three systems learns more slowly, and the competitive gap widens year over year. This is the most expensive and the least visible of the three costs.

What actual unification looks like

Data unification for apparel operations is architectural, not cosmetic. It means one system holds the three data surfaces on a shared schema:

• Manufacturing data: styles, BOMs, tech packs, production POs, vendor records, WIP status, landed cost at receipt.
• Inventory data: units by location, committed vs available, by SKU (style × colour × size), with movement history tied to production receipts and sales transactions.
• Sales data: wholesale orders, DTC orders, marketplace orders, POS transactions, returns, with every line tied to the SKU and the originating unit.

When these three surfaces live on the same data spine, the five connectedness questions are answerable in a click because the data is already joined at the schema level. No reconciliation because there is nothing to reconcile. No reports because the operational view is the report.

This is the core argument for running apparel operations on an apparel-specific ERP that treats manufacturing, inventory, and sales as first-class modules inside one system — rather than three connected tools. The difference between generic and apparel-specific ERP becomes most visible here, because generic ERPs typically require a customisation layer to treat apparel manufacturing as an in-system module rather than a bolt-on.

What the move actually involves

For brands currently running sales, inventory, and manufacturing data across three to five tools, the unification project has three phases:

1. Pick the system of record. For apparel brands between $5M and $100M, this is typically an apparel-specific ERP that holds PLM, production, inventory, orders, and warehouse in one data model.
2. Migrate the three data surfaces onto it. Product master from PLM. Open POs from the production tracker. Current inventory from the 3PL and warehouse. Open orders from the wholesale spreadsheet and Shopify. This is the 8–16 week implementation project; the complexity is in the data mapping, not the tooling.
3. Retire the parallel tools. The wholesale spreadsheet gets archived. The standalone PLM gets sunset or kept for design-team workflows only. The production tracker moves into the ERP's production module. The reconciliation spreadsheet stops being built because there is nothing to reconcile.

Where to start

Run the five connectedness questions against your operation this week. Count how many require exporting, and how many can be answered in under a minute in one system. The ratio tells you whether your data is unified or reconciled.

If the answer is "four out of five require exporting," the connectedness gap is real and the cost is compounding. The fix is not another integration tool. The fix is an operational system architecture that treats sales, inventory, and manufacturing as one model instead of three connected ones. Start with a discovery conversation that walks through your current data flow and identifies where the unification breaks.

Related reading: Single source of truth in apparel, 6 Breakpoints of apparel operations, Production management.