Royalty Reporting for Merchandising & Product Teams.
Royalty calculation depends entirely on the product master. Every style, every SKU, every product category, season, team, school, league, event, and property — plus cooperative-mark splits where a single SKU carries rights from multiple licensors — has to be mapped to the correct royalty rule before reporting begins. Royalty Reporting makes that mapping a first-class data model, not a month-end scramble.
Built for merchandising and product leaders who own the style/SKU master and drive the mappings that feed every downstream royalty calculation.
Job titles this page is built for
- VP / Director of Merchandising
- Product Manager
- Style / SKU Master Data Manager
- Planning & Allocation Manager
- Merchandise Planner
- Product Development Manager
What this team runs into today
Products are not consistently mapped to licensors — a new style ships before someone updates the licensor attribute, and finance finds the gap at close.
Style/SKU master data is incomplete or inconsistent across PLM, ERP, and the order book.
One style may belong to multiple properties (NCAA-licensed jersey with NFLPA player likeness; MLB throwback with cooperative-rights split) and the royalty has to distribute correctly.
Product category drives royalty rate within a single agreement — and the category attribute lives in three different systems.
Seasonal collections (Fall, Holiday, Spring, Summer) create reporting cycles where products age in and out, but the contracts they're reporting against don't.
How Royalty Reporting changes this team's day
Connect every style, SKU, category, season, property, and cooperative-mark split to the correct royalty rule — gaps surface before close, not after.
Style/SKU-to-licensor mapping at the master-data level — every product carries its licensor attribute, property attribute, and product-category attribute.
Product-category mapping that drives royalty rate within agreements (apparel, headwear, accessories, hardgoods — and finer where contracts split further).
Seasons and collections tracked natively — reports respect the period each product was live, so stale inventory doesn't inflate royalty.
Team, school, league, event, and property mapping for cooperative marks — a single jersey can carry rights from multiple licensors with the correct royalty split.
Product-level royalty rules — overrides for specific styles where contracts deviate from the default category rate.
Exception management for unmapped or ambiguous items — surfaced before close, not after.
Features this team uses most
Common questions from this team
How are cooperative-mark products (multiple licensors on one SKU) handled?
Cooperative marks are a first-class concept. A single SKU can carry rights from multiple licensors — NCAA + NFLPA, MLB Properties + a historical-franchise licensor, league + player association — with the royalty distributing per the contractual split. Each licensor sees its portion in its own statement.
What happens when a new style ships before the licensor mapping is set?
Unmapped products surface in an exception queue before they hit a royalty calculation. Finance and merch see the same exception view, so the mapping decision happens once and stays consistent. The data model refuses to silently apply a default rate to a product that wasn't classified.
Does the platform integrate with PLM and ERP product masters?
Yes. Product attributes can sync from PLM systems and ERP product masters; the licensor-mapping layer sits on top of those attributes so existing product workflows continue unchanged. Style/size/color is a native data primitive — not a configured workaround.
Built for your product master.
Show us your style/SKU structure, your licensor portfolio, and your cooperative-mark splits — we'll walk through how the product-to-royalty mapping lives in one data model instead of three.