Royalty Reporting for Licensed Footwear & Slides.
Licensed footwear licensees — companies selling slides, sandals, socks, slippers, and athletic footwear under league, team, player, and collegiate marks — manage royalty reporting where the size run multiplies everything. Every style × colorway combination fans out across a full size run, so a modest style count becomes thousands of SKU-level statement lines; royalty structures split between per-pair unit royalties and percentage-of-net-sales calculations depending on the agreement; footwear frequently carries its own category rate, separate from apparel on the same property; co-branded collab product layers a brand partner's reporting obligations on top of the licensor's; and returns post against individual size-level lines weeks after the originating sale. Royalty Reporting models size runs, per-pair and percentage royalty bases, category rate schedules, and size-level true-ups natively — one connected calculation from sales data to licensor-ready statement.
Royalty Reporting's flagship customers are apparel licensees — and footwear is the closest adjacent workflow the platform runs. The style/size/color SKU primitives built for apparel map directly onto style × colorway × size-run footwear matrices, and the royalty engine is category-agnostic: rates, royalty bases, product categories, and statement formats are configuration. Licensees running footwear alongside an apparel line report both categories to the same licensor from one platform.
What this reporting workflow looks like in practice
Size-run SKU explosion is the defining data problem in licensed footwear. One slide silhouette in one team colorway spans a full size run — a dozen or more size-level SKUs — before the next colorway exists. Multiply across per-team colorways in a league, then across leagues and collegiate programs through CLC and Fanatics College, and a handful of silhouettes becomes thousands of SKU rows. When licensors require SKU-level statement breakouts, every one of those rows is a statement line.
Royalty structures split between per-pair and percentage-of-net. Some footwear agreements calculate royalty as a fixed amount per pair sold; others as a percentage of net sales; structures vary by agreement and can differ between properties in the same portfolio. The royalty basis is modeled per agreement — unit-based lines calculate from pair counts, percentage lines from the contractual net-sales definition, both within the same period close.
Footwear frequently carries its own category rate, separate from apparel on the same property. A licensee holding apparel and footwear rights under one licensor typically reports two rate schedules to that licensor — and a footwear SKU mapped into the apparel category in the ERP applies the wrong rate silently until an audit surfaces it. Category attribution is validated structurally, not assumed.
Co-branded and collab product layers reporting obligations. A slide carrying a footwear brand's own mark alongside a licensed team or player property involves the licensor's royalty on the licensed mark and, depending on the deal structure, reporting obligations to the brand partner as well. Per-SKU attribution of the licensor and every brand partner on the product keeps each party's reporting correct — the same per-SKU split structure that handles cooperative marks in licensed apparel.
Returns true-ups hit size-level lines. Wholesale returns post on a lag well after the originating sale, and each return lands against the specific style × colorway × size line it originated from — not against a style-level aggregate. First-class true-up logic posts the adjustment to the correct size-level line while preserving the original period's statement, so prior statements stay intact and the current period reflects the correction with full lineage.
Socks and multipack configurations change the royalty basis mechanics. A three-pack sells as one unit but may carry a per-pair royalty basis — royalty calculates from the pack's pair count, not the transaction count. Pack configuration is a first-class attribute so per-pair agreements calculate from the correct unit basis across singles, multipacks, and prepacks.
Statement depth varies by licensor — some expect style-level rollups, others SKU-level or size-level breakouts. Statement formats and breakout depth are per-licensor configuration generating from the same calculation data, so changing a licensor's required depth is a template change, not a workbook rebuild.
Spreadsheet risks specific to licensed footwear: (a) size-run row sprawl (thousands of size-level lines from a modest style count), (b) mixed per-pair and percentage royalty bases across the portfolio, (c) footwear vs. apparel category rate divergence on the same property, (d) collab attribution across licensor and brand partner, (e) size-level returns true-ups against prior periods. Each compounds the audit-finding risk in spreadsheet-based reporting.
What Royalty Reporting tracks
Royalty Reporting calculates, reports, and audits royalties by every dimension finance and licensing teams actually work with — not just the high-level totals.
- Licensor (league, team, player association, collegiate via CLC / Fanatics College, event marks)
- Team / school / property
- League / conference
- Product category (slides, sandals, socks, slippers, athletic footwear)
- Category rate schedule (footwear vs. apparel on the same agreement)
- Style / silhouette
- Colorway (per team / school)
- Size run / size
- SKU (style × colorway × size)
- Pack configuration (single pair, multipack, prepack)
- Royalty basis (per-pair vs. percentage of net sales, per agreement)
- Collab / brand-partner attribution (per SKU)
- Mark type (team / league / player / cooperative)
- Sales channel (DTC, wholesale, sporting goods, mass, stadium retail, team store, marketplace)
- Customer / retailer
- Territory
- Minimum guarantee (per licensor)
- Advance balance (per licensor)
- Reporting period (per-licensor cadence)
- Returns (size-level, with lag and true-up handling)
- Audit-period adjustments
- GL journal entry feed
Frequently asked questions
How does Royalty Reporting handle size-run SKU explosion in footwear statements?
SKU is a first-class object at style × colorway × size granularity, with team / property, category, and rate-card attribution carried per SKU. The platform is built for multi-licensor portfolios at six-figure monthly transaction volumes, so full-size-run row counts are the normal case, not a strain. Statement generation rolls the same calculation data up to whatever depth each licensor requires — style-level, SKU-level, or size-level — without maintaining separate workbooks per depth.
Can the platform calculate per-pair royalties and percentage-of-net royalties in the same portfolio?
Yes. The royalty basis is modeled per agreement. Per-pair agreements calculate from unit pair counts — including pack-aware counts, where a sock three-pack contributes three pairs from one transaction line — while percentage agreements calculate from that agreement's contractual net-sales definition after its own deduction waterfall. Both bases run in the same period close, and each statement shows the basis its licensor expects.
How are category rate differences between footwear and apparel on the same property handled?
Category is a rate dimension, not metadata. An agreement covering both apparel and footwear carries a rate schedule per category, and each sales line routes through the rate for its category automatically. The platform also validates ERP category mapping against the contract's category definitions — a slide SKU carrying an apparel category code surfaces for review before it flows into a calculation, because a misclassified SKU applies the wrong rate silently until a licensor audit finds the accumulated variance.
How does co-branded / collab reporting work?
The licensor and every brand partner on the product are attributed per SKU. A collab slide carrying a licensed team or player mark alongside a brand partner's mark calculates the licensor's royalty per the license terms, and the same per-SKU attribution supports whatever reporting the brand-partner arrangement requires. This uses the same per-SKU split structure that handles cooperative marks (league + team, league + player association) in licensed apparel — collab attribution is configuration on that structure, not a separate workflow.
How do returns true-ups work at the size level?
A wholesale return posts weeks after the originating sale and lands against the specific style × colorway × size line it came from. The platform's true-up logic preserves the original period's statement as issued, posts the adjustment in the current period against the originating line, and keeps the full lineage — original sale, return event, recompute, statement version — in the immutable audit trail. Licensor audit support at the size level is a query, not a spreadsheet reconstruction.
Is Royalty Reporting built for apparel licensees rather than footwear licensees?
The platform's flagship customers are apparel licensees, and that is where its deepest reference workflows come from. Footwear is the closest adjacent case: the style/size/color SKU primitives built for apparel map directly onto style × colorway × size-run footwear matrices, and the royalty engine is category-agnostic — rates, royalty bases, product categories, and statement formats are configuration. A licensee running footwear alone, or footwear alongside an apparel line under the same licensors, is setup work, not new platform capability.
What data does the platform need to run footwear royalty reporting?
Sales data (gross sales, returns at the SKU / size level, deductions, customer / channel attribution) from your ERP — NetSuite, Microsoft Dynamics, Sage Intacct, Oracle, SAP, and other common licensee ERPs via API or scheduled SFTP. Product data (style / silhouette, colorway, size run, pack configuration, team / property attribution, product category, collab-partner attribution where applicable) from your ERP product master or PLM. Wholesale orders from EDI feeds; DTC ecommerce and marketplace feeds where relevant. CSV imports work where direct integration is not available.
Built for the full size run.
Show us your style × colorway × size matrix and your royalty bases — per-pair, percentage-of-net, or both — and we'll walk through how Royalty Reporting handles size-level statements, collab attribution, and returns true-ups without spreadsheet rebuilds.