What Is Landed Cost and Why It Hides Inside Apparel Margin
It is the Tuesday after quarter close. The CFO at a $22M womenswear brand is on a call with the head of merchandising, and the margin number on the deck is 4.2 points lower than the one merchandising used to greenlight the Spring reorder six weeks earlier. The factory FOB cost is the same. The retail price is the same. What changed is that finance finally loaded the freight invoice from the November container, the customs entry from December, and the chargeback for the late ASN on the Nordstrom PO. The reorder is already in production. The margin gap is locked in for two seasons.
What is landed cost in apparel and why does it hide inside margin?
What is landed cost apparel finance teams should be reporting on is not the factory invoice. It is the fully loaded per-unit cost of getting a finished good from the cut-and-sew floor into your warehouse, ready to ship. That includes the factory FOB price, ocean or air freight, duties and tariffs (including any Section 301 or reciprocal tariff in effect), customs brokerage, marine insurance, drayage, inbound handling at the 3PL, and a proportional share of production overages or rejects that you paid for but cannot sell at first quality.
Most brands in the $5M to $100M band track the first number. Some track the first two. Almost none carry a true landed cost on the SKU master at the moment a merchandiser is building an assortment or a planner is sizing a reorder. The number lives in a spreadsheet that finance updates after the season closes, which means every OTB decision, every markdown call, and every channel margin comparison made during the season is made on the wrong base.
This is a Breakpoint 6 problem in the 6 Breakpoints framework. Reporting becomes reactive and political instead of operational because the inputs to margin are not in the same system as the orders, the inventory, or the production records. The CFO and the CMO end up arguing about whose number is right instead of deciding what to do next.
Why does the factory invoice feel like the real cost?
Because it is the cleanest number in the building. The factory sends a commercial invoice tied to a PO. The PO ties to a style. The style ties to a season. Everything matches. It is easy to load, easy to reconcile, and easy to put into a cost field on the product record.
Everything else is messier. Freight invoices arrive 30 to 60 days after the container clears, often covering multiple POs and multiple styles. Duty entries come from a broker in a separate system, sometimes with HTS classifications that finance has to reconcile back to the original PO line. Brokerage fees, demurrage, detention, and chassis charges show up as one-off invoices that nobody connects back to a SKU. Inbound handling at the 3PL is a per-carton or per-unit charge buried in a monthly bill. None of these arrive in a format that maps cleanly to a style or a color, which is the unit the rest of the business plans in.
So the path of least resistance is to leave the factory cost on the product record and treat everything else as a period expense. The P&L still closes. Gross margin still reports. But the per-SKU margin you are looking at on Tuesday morning is not the per-SKU margin the business actually earned.
How big is the gap between FOB and true landed cost?
The pattern that shows up when I segment customers by reporting maturity is consistent. Brands that have moved landed cost onto the SKU find that for goods imported from Asia by ocean, the spread between FOB and landed sits in the 18 to 35 percent range once duties, freight, brokerage, and inbound handling are loaded. Air-freighted styles, which most brands use for late production or hot reorders, can spread 60 to 120 percent over FOB. Duty rates on apparel HTS codes are not small. Cotton knit tops, wool outerwear, and synthetic activewear all land in different duty brackets, and the difference between a 16.5 percent and a 32 percent duty rate is a margin point you cannot recover at retail.
The number is not the headline. The headline is the variance between SKUs within the same buy. Two styles in the same PO can have different effective landed costs because one shipped on time by ocean and one was air-freighted three weeks later to make a wholesale ship window. Merchandising looks at both styles as having the same cost on the product record. Finance, after the season, sees one at 58 percent IMU and one at 41 percent. By the time anyone can act on that, the next PO is already cut.
When does the gap start to bite?
It bites at the $10M to $20M revenue band, which is the predictable breakpoint zone for the brands we work with. Below $10M, the founders usually know which styles are the air-freight problem children because they personally approved the expedite. Above $20M, the variance compounds across enough POs and enough channels that nobody has the working memory to hold it.
For a $15M brand running wholesale and DTC with a 3PL, the same operational tax that produces 6 to 9 hours a week of reconciliation across Shopify, the 3PL, and wholesale shows up in the cost ledger. One FTE is effectively doing data plumbing. Some of that plumbing is the cost side: matching freight invoices to POs, allocating duty entries to styles, and trying to keep a spreadsheet that finance trusts and merchandising will actually look at. The spreadsheet is always three weeks behind real life.
Why is landed cost a Breakpoint 6 problem?
What I see in the reporting telemetry month over month is that the dashboards finance and ops teams open most often are the ones where the inputs are trusted. If margin reporting depends on a quarterly spreadsheet exercise that finance does in isolation, the dashboard becomes a political document. Merchandising does not trust it because the cost numbers feel stale. Finance does not trust merchandising’s IMU numbers because they are built on the FOB cost. The CEO ends up asking for a third version that splits the difference.
This is exactly the failure mode Breakpoint 6 describes. Reporting becomes reactive because the system of record cannot answer the question in real time. People stop using the dashboard for decisions and start using it to defend positions taken on instinct. The cost is not just bad margin. It is bad allocation of buy dollars, because OTB is sized against a margin assumption that does not survive contact with the freight invoice.
Run OTB weekly during selling season, but only if the landed cost on the SKU is current. Running it weekly on stale costs is worse than running it monthly on accurate ones, because you are making faster decisions on a wronger base.
What does landed cost look like when it lives on the SKU?
The architectural fix is to treat landed cost as a system field on the product record, populated by a defined allocation method, updated as actual costs come in, and visible to every team that touches a margin decision.
The allocation method matters. Most brands use one of three approaches. The first is value-based allocation, where freight and duty are spread across a PO in proportion to the FOB value of each line. This is simple and usually defensible for duty, since duty is typically calculated on value. The second is volume-based or weight-based allocation for freight, since ocean freight is priced on container space and not on goods value. Allocating a 40-foot container’s freight across a PO by FOB value will systematically overcost expensive styles and undercost bulky low-cost styles. The third is hybrid, where duty goes by value and freight goes by cubic meters or kilograms.
The right answer for apparel is hybrid. Knit basics that fill a container by volume should carry their share of freight on volume. Outerwear shipped in compressed bales is different from the same dollar value of folded tees. Brands that allocate everything by value end up with reorder economics that look fine on paper and lose money in practice.
What about returns, markdowns, and channel mix?
Landed cost is the start, not the end. The true margin on a SKU also depends on what happens after it ships. Returns should post to inventory in days, not weeks, because a returned unit that sits unprocessed for 30 days is a unit you could have sold at full price and now sells at markdown. Channel mix changes the picture too. A unit sold through wholesale at keystone carries a different effective margin than the same unit sold DTC at full price minus a return rate of 18 percent, minus the cost of the inbound 3PL handling on the return.
The brands we work with that handle this well, including the multi-entity wholesale operators like Lufema running B2B portals across multiple brand catalogs, treat landed cost as the cost layer and then layer channel-specific costs on top. Wholesale carries EDI compliance costs, chargeback reserves, and trade discounts. DTC carries return processing, payment processing, and customer acquisition. Each channel has its own margin profile against the same landed cost base.
If your retailer chargebacks exceed 1 percent of wholesale revenue, the EDI integration is the problem, not the warehouse, and that chargeback rate is also a margin number that should be visible at the SKU level, not buried in a wholesale operations report nobody reads.
What about drops and same-day fulfillment?
Drop-driven brands face a sharper version of the problem. When Magnolia Pearl ships a drop with same-day fulfillment from the warehouse, the air freight that got the goods in on time is already locked in. The duty on the goods is locked in. The margin on the drop is determined before the first order is taken. If the landed cost is not on the SKU when the drop is priced, the merchandising team is pricing on factory cost and discovering the actual margin at quarter end.
International duties add another layer. A drop that sells 30 percent internationally has a different landed-cost-to-revenue picture than one that sells domestically, because the inbound duty into the US is sunk and any DDP arrangement with the international customer is an additional cost layer. Brands that ship internationally without a clean view of landed cost are guessing at the gross margin on every cross-border order.
How do you fix it without a six-month project?
Three moves, in order.
First, move the factory FOB out of a static cost field and into a cost history on the SKU, with an effective date. Costs change between POs. You want to know what the cost was on the units in inventory right now, not the cost on the last PO you cut.
Second, define the allocation method for freight and duty and apply it consistently to every PO. Hybrid for freight (volume or weight) and duty (value) is the defensible default. Document the method so finance and merchandising are working from the same definition.
Third, close the loop between accounts payable and the SKU. When a freight invoice or duty entry arrives, it should post against the PO it relates to and update the landed cost on the SKUs in that PO. This is the part that requires the orders, inventory, and production records to be in one connected system. If freight invoices live in the accounting system and POs live in a separate planning tool, the loop stays open and the spreadsheet lives forever.
This is the kind of work that is usually invisible until it is done, and then the margin number on Tuesday morning starts matching the margin number at quarter close. That is the real test.
What this means for an apparel operations team
Landed cost is not a finance project. It is the foundation of every margin decision the merchandising and planning teams make during a season. If the cost on the product record is the factory FOB, the IMU on the line plan, the OTB allocation, and the reorder economics are all built on a number that is 18 to 35 percent lower than reality. The variance is not random. It systematically favors air-freighted and high-duty SKUs, which are the ones most likely to get reordered because they sold through.
The operational move is to make landed cost a field that lives where the orders, inventory, and production already live. The allocation method needs to be agreed once and applied consistently. Freight and duty invoices need to post back to POs and update SKU costs as actuals come in. Until that loop closes, margin reporting will keep arriving three weeks late and the conversation between finance and merchandising will keep being a negotiation instead of a decision.
The brands that solve this stop having the Tuesday-after-close conversation. The margin on the deck is the margin in the bank. The reorder gets sized against the right number. That is what Breakpoint 6 looks like when it is fixed.
Where is your operation on the 6 Breakpoints curve?
The assessment scores your apparel operation across all six breakpoints (product data, production, inventory truth, order flow, warehouse execution, reporting) and identifies which one is hurting you most.
Frequently asked questions
Lalith writes about operational reporting and analytics for apparel brands, covering how connected data across inventory, orders, fulfillment, and warehouse execution translates into reporting that supports real decisions. As Senior Product Manager for Reporting and Operational Analytics at Uphance, he builds the dashboards and KPI work that let finance and operations teams stop arguing over numbers and start running the business. His articles cover landed cost, COGS reconciliation, month-end workflows, margin analytics, and the data hygiene patterns that determine whether reporting can actually be trusted at the executive level. He argues that reporting becomes political only when the operational layer underneath it is fragmented.
Venkat is the Founder and CEO of Uphance and the author of the 6 Breakpoints of Apparel Operations framework. He writes about operational clarity for apparel brands as complexity grows across channels, warehouses, partners, and teams. His work focuses on why disconnected operations, not growth itself, create the chaos most mid-market brands feel between $5M and $100M in revenue, and on the operating-model patterns that decide whether scaling a brand strengthens execution or fractures it. He argues that the status quo is the real competitor in apparel software, and that the right move is fewer systems with deeper connection, not more dashboards.
