Footwear D2C Meta Ads: Fit, Catalog, and Margin Decisions

For the surrounding account decisions, compare Fashion D2C Meta Ads: Inclusive Sizing and Fit Decisions and use Home Decor D2C Meta Ads: Catalog and Room-Context Decisions as the next diagnostic.

In short

The decision is which footwear product sets deserve Meta spend after fit-related returns, variant stock, and variable costs are counted. Use your own SKU feed, delivered-order ledger, return reasons, and contribution data. Do not import a footwear return rate, buyer profile, price band, or conversion benchmark.

A product can have attractive attributed revenue while its advertised sizes are depleted or its post-return contribution is weak. Rank product sets on sellable variant depth and matured economics, then build creative around the fit questions recorded for those products.

Category economics as first-party inputs

Work at product × size × color where inventory is held. Record:

• AOV = recognized revenue ÷ fulfilled orders for a declared product set and period.
• Return rate = returned orders ÷ delivered orders eligible for return measurement. Keep fit-related returns as a reason subset, not a separate denominator.
• In-stock variant rate = sellable variants ÷ active variants in the product set. Define the stock floor that makes a variant sellable.
• Post-return contribution = recognized revenue − product cost − fulfilment − outbound and return shipping − payment fees − discounts − Meta spend.
• Contribution per delivered order = post-return contribution ÷ delivered orders for the matured cohort.
• Size-guide use rate = eligible sessions that opened the guide ÷ eligible product-detail sessions. Its association with conversion or returns is not causal evidence.

Reconcile feed inventory to the commerce source before ranking. Store product ID, variant ID, size label, stock quantity, price, availability, feed timestamp, and storefront timestamp. A product-level “in stock” flag is insufficient when the advertised size is unavailable.

Creative and offer decision: fit evidence meets sellable depth

Build fit guidance from product records and customer questions: internal length, width, last or shape notes, fastening, material behavior, model-worn size with permission, and a measurement method. Avoid “fits everyone” and unsupported size equivalence.

Group products by an owned decision, not aesthetics alone:

• Depth set: products with enough sellable sizes to support paid demand.
• Fit-evidence set: products with complete measurements, size guidance, and matured return reasons.
• Margin set: products clearing the business’s post-return contribution floor.
• Holdout set: products withheld because core variants, evidence, or margin are inadequate.

Creative should point to the exact variant-aware page. Record product-set membership and feed state at launch so a later result can be interpreted against what was actually available.

Measurement dictionary

• Paid ROAS = Meta-attributed revenue ÷ Meta spend. Attribution is not incrementality.
• MER = total recognized revenue ÷ total paid-media spend. It is not blended ROAS.
• Return-adjusted attributed revenue = Meta-attributed recognized revenue − refunds attributed under the same method and matured window.
• Variant sell-through rate = units sold ÷ (units available for sale at the start + documented receipts during the period).
• Fit-related return share = returns coded to fit ÷ returns with a recorded reason. Missing reasons remain missing.
• Post-return contribution rate = post-return contribution ÷ recognized revenue. List every included cost.

Illustrative operating model

Illustrative operating model — not a benchmark or expected result. Replace every assumption with your data.

Input	Product set A	Product set B
Fulfilled orders	300	200
AOV	$100	$150
Recognized revenue	$30,000	$30,000
Product and fulfilment costs after matured returns	$17,000	$20,000
Meta spend	$6,000	$7,000
Meta-attributed revenue	$15,000	$17,500
Sellable variants ÷ active variants	36 ÷ 40	18 ÷ 40

The model reconciles: set A revenue is 300 × $100 = $30,000; set B revenue is 200 × $150 = $30,000. Paid ROAS is $15,000 ÷ $6,000 = 2.5× for A and $17,500 ÷ $7,000 = 2.5× for B. Post-return contribution after Meta is $30,000 − $17,000 − $6,000 = $7,000 for A and $30,000 − $20,000 − $7,000 = $3,000 for B. In-stock variant rate is 36 ÷ 40 = 90% and 18 ÷ 40 = 45%.

Equal paid ROAS does not create equal economics or stock readiness. These fictional values teach the ranking method; they say nothing about footwear accounts.

Guardrails

• Suppress a product set from paid promotion when the defined core-variant floor is missed; record the rule as an internal stock control.
• Validate variant ID, size, price, destination, and availability between feed and storefront before launch and at each review.
• Mature return cohorts before comparing contribution.
• Keep fit copy descriptive; do not infer body attributes or promise a fit outcome.
• Pre-register the product-set threshold, primary metric, review window, and stop rule.

Can software help?

Bach.ai audits your connected Meta account against 100+ checks, ranks what it finds by estimated impact, and proposes specific fixes. It stays read-only until you approve a change, then executes the approved change on Meta; connected Google Ads data is used for intelligence only. Think of it as an automated audit layer that surfaces issues and proposed fixes for your review — not a replacement for your team’s judgment, and it does not generate your creative.

Common mistakes

• Ranking products on attributed revenue before returns mature.
• Advertising a product-level stock flag while core sizes are unavailable.
• Treating size-guide use as proof that the guide caused a purchase.
• Mixing product sets with different cost boundaries in one contribution metric.
• Importing a price, return, or fit benchmark from the category.

FAQ

Which footwear products should receive catalog spend?

Choose sets that meet your documented sellable-variant, fit-evidence, and post-return contribution thresholds. The thresholds come from inventory risk and business economics, not a category rule.

How should I measure fit-related returns?

Use (returns coded to fit) ÷ (returns with a recorded reason) and also report missing reasons. For the overall return rate, use (returned orders) ÷ (delivered orders eligible for return measurement).

Does a size guide reduce returns?

Usage and lower returns can be associated in observational data without establishing cause. Test guide variants against matched eligible traffic and compare matured return outcomes before making that claim.

Can two product sets with equal paid ROAS receive different budgets?

Yes. Paid ROAS omits product cost, returns, fulfilment, and stock depth. Post-return contribution and sellable inventory can support different decisions even when attributed revenue ÷ Meta spend matches.