Channel and Territory: Why the Same Unit Produces Different Royalties

The royalty on a unit is not a property of the product

Looking at a style-color record, the natural mental model is that the mark implies a licensor and the licensor implies a rate. That model works for a single-channel, single-territory wholesale business and fails quietly for everyone else. The rate is not attached to the product — it is resolved from the transaction, and the transaction carries two attributes the product record does not: the channel the unit moved through and the territory it was sold into.

The consequence surprises finance teams the first time they see it laid out. One style-color, produced in one run, leaving the same warehouse on the same day on four different sales, can generate four different royalty amounts per unit — not because anyone made a mistake, but because the agreement priced those routes to market differently and stated their bases differently. Once a portfolio includes direct-to-consumer, a marketplace, an outlet or an international territory, per-unit royalty stops being a number the product master can hold.

It is worth naming the boundary against the adjacent failure, because the two get confused. Stale-master drift is an amendment that never reaches the calculation — the agreement moved, the operational copy did not, and the calculation keeps applying a superseded term. That has its own guide, linked below. This guide is about the step before it: how a sale acquires its rate and base in the first place, from a rate card that is entirely current. A perfectly propagated, perfectly versioned rate card still produces the wrong royalty if the transaction cannot say which channel and which territory it belongs to.

How a unit acquires its rate: the resolution chain

A rate card in licensed apparel is rarely a single percentage. It is a set of rules, each stating a rate and the conditions under which it applies. Resolving a sale means finding the one rule that governs it, which requires walking the dimensions in a fixed order rather than matching on all of them at once: the mark carried on the unit, the property that mark belongs to, the agreement granting that property, the product category the agreement recognises, the channel, the territory, and finally the effective date that selects which version of the matching rule was in force on the transaction date.

The order is not cosmetic — it is what makes resolution deterministic. A product category means nothing until you know which agreement applies, because two licensors will categorise the same fleece hoodie differently. A channel rate means nothing until you know the category, because channel rates are usually stated as overrides to a category rate rather than as standalone values. That is the point most often missed: channel and territory enter the card as modifiers, not as primary keys. A calculation that treats channel as a peer of category — a flat lookup on the pair — matches the wrong row whenever the card names a channel exception for some categories and not others.

Two rules matching one sale has to be decided before it happens, not during a close. The convention that survives audit is most-specific-wins: a rule naming category, channel and territory beats one naming category and channel, which beats one naming category alone. Where two rules are equally specific and genuinely conflict, that is an ambiguity in the agreement rather than a system problem, and the resolution belongs in writing with the licensor. A tie broken silently by row order in a lookup table is a decision nobody made and nobody can defend.

Nothing resolves without a date. Rate cards carry effective dates, channels get granted and withdrawn mid-term, territories get added by amendment. A sale resolves against the rule set as it stood on its transaction date, which means the line needs that date and the card needs its history rather than being overwritten in place.

Channel changes the rate — and more often, the base

Agreements price channels differently because the licensor participates in realised value rather than in the licensee's cost structure. A unit sold wholesale realises the invoiced wholesale value; the same unit sold through the licensee's own store or site realises the retail value, which is materially higher on identical product. Paid the same percentage of the same wholesale value in both cases, a licensee could shift volume to direct channels and grow revenue on the mark without the royalty following it.

Agreements respond in one of two ways, and they are not equivalent. Some set a different rate for the direct channel while keeping a wholesale or deemed base — sometimes defined as the price charged to wholesale accounts for the same style, sometimes as a stated fraction of retail. Others keep a comparable rate and change the base to the actual retail value received. The structure that changes the base is the one that produces the largest reporting error when it is missed, because the gap between the two bases is the entire retail margin on the unit. A rate difference moves the percentage; a base difference moves the value the percentage is applied to.

That is the classic under-report: extracting all sales from the ERP at invoiced value and reporting every channel on it. The extract is correct, the arithmetic is correct, the statement foots, and every direct-channel unit has been reported on the wholesale value rather than the retail value the agreement specifies, short by the whole retail margin. Nothing looks wrong from either side — the licensor sees consistent per-unit royalties across the period, which is exactly what a correctly reported single-channel business also looks like.

Channel also changes what may be deducted. Direct selling generates costs that feel like deductions and usually are not: platform fees, payment processing, consumer shipping, marketplace commission. A deduction exists only when the agreement names it. Treating a cost of selling directly as a reduction of the royalty base is an unsupported deduction, and it is the exact shape of finding auditors look for when a licensee's direct volume is growing.

The channels, line by line

Each channel below carries the same three things after its name: the base the agreement usually states, why it is priced that way, and the reporting consequence that most often goes wrong. Rate figures are deliberately absent — the structure is the point, and the rates belong to your agreements.

Wholesale. Base: invoiced value of shipped product, net of permitted deductions. Why: it is the reference channel most rate cards are built around. Consequence: the easiest channel to report, and the reason the others get reported wrongly — the wholesale extract is the path of least resistance and silently becomes the base for everything.

Own retail. Base: frequently the retail value received, or a deemed wholesale value where the agreement states one. Why: the licensee captures the full retail margin on the mark. Consequence: point-of-sale data lives in a different system from the invoice ledger, so own-retail volume is the volume most likely to be missing from the extract entirely rather than merely mis-based.

Own e-commerce. Base: normally the same treatment as own retail, at order value net of permitted deductions. Why: same reason. Consequence: this is where territory and channel collide, because a site does not know which territory it is selling into until the ship-to address is entered, and it will accept an order from anywhere.

Outlet. Base: usually the own-retail basis applied to the outlet's realised price rather than full-price retail. Why: the licensor participates in what was actually realised. Consequence: reporting outlet at full-price retail overstates the base; reporting it at the closeout treatment when the agreement calls it own retail understates it. Outlet is neither, and agreements that name it treat it as its own thing.

Closeout and off-price. Base: the actual disposal price, often with the deduction list narrowed. Why: heavily discounted disposal would otherwise pull realised royalty down without limit. Consequence: closeout is frequently restricted as well as rated — capped as a share of period units, limited to named accounts, or requiring approval. Reporting the units correctly does not discharge the cap.

Promotional and premium. Base: often a deemed value such as cost or a stated fraction of wholesale, because there is no arm's-length price. Why: units given away still carry the mark into the market. Consequence: these units sit outside the sales ledger most often, moving on a no-charge order type that a revenue-based extract filters out before anyone sees it.

Team, institutional and direct-to-organisation. Base: usually invoiced value, but the channel is often carved out with its own rate or approval requirement. Why: selling to the team, school or event operator is commercially different from selling to a retailer, and the licensor may have granted those rights elsewhere. Consequence: this volume is invoiced through the same order-to-cash process as retail accounts, inherits the wholesale channel code by default, and disappears as a distinct channel on the statement.

Read down that list and the pattern is that the base moves more than the rate does. A channel rate difference adjusts the percentage; a base difference between wholesale value and retail value on the same unit replaces the value that percentage is applied to. A review of channel handling that checks the rates and never questions the base can pass while every direct unit is reported on the wrong value.

The marketplace problem: one order, two legitimate treatments

Marketplace volume is the modern hole in most royalty workflows, because a marketplace sale is not one kind of sale. It is two, with different bases and often different rates. In the first structure the licensee sells inventory to the marketplace operator, which takes title and resells it — economically and contractually a wholesale sale, with the invoiced wholesale value as the base and the end consumer as the operator's customer. In the second the licensee lists product, remains the seller, and the operator provides the storefront and payment rails for a commission. That is a retail sale in which the marketplace was the channel: the base is the retail order value, and the withheld commission is a cost of selling rather than a deduction, unless the agreement names it.

The test that distinguishes them has three parts, and they usually agree. Who took title to the goods, and when? Who set the price the consumer paid? Who bore the return, the chargeback and the credit risk? Operator on all three, and it is a wholesale sale to the operator. Licensee on all three, and it is a direct retail sale through a marketplace channel. Where the parts disagree — common in fulfilment arrangements where the operator holds and ships inventory it does not own — title and price control decide it, and the arrangement is worth documenting with the licensor rather than settling internally.

The first failure mode is reporting all marketplace volume as one thing. A licensee running both structures with the same operator, which is ordinary, will be wrong on part of it in one direction. Reported entirely as wholesale, the direct portion sits on a fraction of its correct base. Reported entirely as retail, the operator-owned portion sits on a base that was never the licensee's revenue.

The second failure is double-counting, which inflates rather than understates. The same order can enter the data twice — once as a shipment, when inventory moves to a fulfilment location under a transfer the ERP records as a sale, and once as a consumer order in the settlement feed. Both records describe real events; only one is a royalty-bearing sale. The control is a deduplication key that survives both paths — the marketplace order identifier carried on the settlement line and the shipment line — plus an explicit rule that moving inventory to a location the licensee still owns is not a sale. Double-counting is easier to miss than under-reporting because nobody audits for overpayment, and it corrupts the same unit reconciliation that would otherwise catch the under-report sitting next to it.

Territory: granted, destination, and ship-from

Three geographies attach to one sale and are routinely conflated. The granted territory is a contract term — the geography in which the agreement permits sales. The sales destination is where the unit was sold into: for wholesale, the market the account sells in, usually evidenced by the ship-to address; for direct, the consumer's delivery address. The ship-from location is where the unit physically left, a logistics fact about the distribution network.

The destination normally governs, and that is the reading consistent with what a territory grant is for: the licensor is allocating markets, and a market is where product reaches consumers, not where a warehouse sits. A licensee shipping from one distribution centre into several countries is selling into several territories; three distribution centres serving one country is one territory. Ship-from is a fact about your operation and almost never a contract term, but because it is always populated and always clean, it gets used as a territory proxy in extracts more often than anyone would defend if asked directly.

Two edges are worth naming. Wholesale sales to an account that itself exports create a destination the licensee cannot see on the invoice — the ship-to is the account's domestic warehouse and the units end up abroad. Agreements handle that with distribution restrictions on the account rather than with a different royalty treatment; the sale was made into the ship-to territory, and the onward movement is a compliance matter, not a restatement. Cross-border e-commerce is the case that generates the most volume and the least attention: a site accepts an order from a country the agreement never granted, prices it, ships it and books the revenue, because whether a destination is inside the granted territory is a licensing question and the checkout is a commerce system.

Territory carries a currency implication too, since a sale into another territory is often a sale in another currency. That is a separate layer with its own failure modes — which rate source, which conversion date, and the double-conversion problem where a commerce platform and a royalty workbook each convert once. This guide does not cover it; the multi-currency guide linked below does, and the two are answered in that order, because you cannot convert a base you have not correctly determined.

Leakage: selling into a territory you were not granted

Leakage is a sale of licensed product into a territory the agreement did not grant. It is a scope breach rather than a reporting error, but it creates a reporting obligation the moment it is detected, and how the disclosure is handled matters more than the size of the leakage. The mechanism is almost always a channel with no territory awareness — an e-commerce checkout, a marketplace listing visible in markets nobody targeted, a wholesale account reselling across a border. The sale completes normally, the revenue books normally, and the only artifact is a ship-to country in a field nobody filters on.

What the agreement requires on detection varies, and the clause is worth reading before the first incident rather than during one. Common treatments include reporting the units and remitting at a stated rate while ceasing the sales, remitting at the highest rate on the card, treating the units as unauthorised with a separate remedy, or giving notice within a stated window. What is never a treatment is quietly reporting the units as if the territory had been granted. That converts a scope issue with a defined remedy into a misrepresentation on a statement, and it removes the licensee's ability to say the error was found and disclosed.

The control is a boundary test that runs on the sales data before the statement is built, not a policy asking sales teams to be careful. For every royalty-bearing line, compare the ship-to territory against the territories granted for that property, in that channel, on that transaction date; lines outside the set go to an exception list to be reviewed rather than reported. It is cheap to run and it is the only thing that finds leakage before an auditor does, because leakage is invisible in every aggregate view — a small number of lines inside a channel total that looks entirely normal.

Territory times channel: rights are granted per pair

The most consequential thing about these two dimensions is that they are not independent lists. An agreement does not grant a set of territories and separately a set of channels with every combination permitted. It grants channels within territories — and the combinations it withholds are usually the commercially interesting ones. The patterns recur: a domestic territory granted for all channels while an adjacent territory is granted for wholesale only, because the licensor has a different licensee serving consumers there; a territory granted for e-commerce but not physical retail; marketplace excluded where the licensor manages its own presence; closeout permitted domestically and prohibited internationally, so discounted product does not surface in a full-price licensee's market.

This is where most misreporting starts, and the reason is structural rather than careless. A rate card modelled as two independent dimensions has a cell for every pair, and a cell with no rule resolves to a default instead of to an exception — the sale gets a plausible rate and reports cleanly. A card modelled as a set of granted channel-territory pairs, each carrying its own rate, has no cell for an ungranted pair, so the sale fails to resolve. A sale that cannot resolve should stop the close, not fall back to a default. Converting silent defaults into hard failures is the single most useful change most licensees can make here.

The same structure governs the reporting side. A statement presenting royalty by category and separately by territory has told the licensor nothing about which channel operated where. Where an agreement grants per pair, the statement generally has to report per pair — and a licensee whose data cannot produce that cross-tab discovers it at the worst possible moment.

The data requirement: what has to be on the sales record

None of this is resolvable unless the transaction itself carries the attributes the resolution needs. Eight fields on the sales line do that work, and each of them fails in a specific way when it is missing or inferred.

Channel code, on the transaction. Valued from a controlled list that matches the channels the agreements actually name — not free text, not a derivation. Free text produces variants nobody maps; a derivation produces a value that looks authoritative and cannot be traced back to anything a licensor could test.

Sold-to type. Retail account, distributor, marketplace operator, institution or team, consumer. This is what lets a statement separate populations the agreement treats separately, and it is the field that makes team-direct and institutional volume visible instead of leaving it inside a wholesale total.

Title-transfer flag. Whether title passed, and when. This settles the marketplace question mechanically rather than case by case, and it settles drop-ship the same way. Without it, both get classified from shipment shape, which is the one signal that points the wrong way.

Marketplace identifier and order key. Carried on any marketplace-originated line, on both the settlement record and the shipment record. This is what makes the two structures separable and what makes a repeated order recognisable — it is the deduplication key, and there is no substitute derived after the fact.

Ship-to country or region. At the granularity the agreements grant at, which for a collegiate or regionally restricted programme is finer than country. A boundary test can only be as precise as this field.

Ship-from location. Kept because logistics needs it, and explicitly excluded from territory resolution. Recording it without marking what it is for is how it ends up standing in for a destination nobody captured.

Price-basis marker. What value the line is denominated in: invoiced wholesale, retail order value, or a deemed value. A base is only interpretable if you know which one you are looking at, and this is the field that turns the base-swap error from an invisible one into a testable one.

Transaction date. Selects the rate version and the granted channel-territory set in force when the sale happened. Everything above resolves against the agreement as it stood that day, not as it stands at close.

One of those deserves its own paragraph, because it is the most common structural mistake in this area: channel must be derived from the transaction, not from the customer master. The customer-derived approach is appealing because it is easy — tag each account with a channel once, join it in at extract time — and it works right up until one customer buys through two channels. That is not exotic: a national account that also operates a marketplace, a retailer taking full-price wholesale in one programme and closeout in another, a team organisation buying for its own shop and separately for on-field use. The moment any of those exist, a customer-level tag misclassifies part of that customer's volume permanently and consistently — which is worse than misclassifying it randomly, because a consistent error looks like a pattern rather than a defect.

Territory has a milder version of the same problem. Deriving it from the customer's registered address rather than the line-level ship-to puts every unit a multinational account takes into its headquarters country. The ship-to is the field that carries the answer, and where it is genuinely unavailable the correct response is an exception rather than a substitution.

Worked example: one SKU, four sales, four royalties

Illustrative figures throughout, chosen because they divide cleanly. They are not benchmarks, they are not rates observed in any agreement, and they are not drawn from any brand.

The setup. One style-color — a fleece hoodie carrying a team mark — under one agreement. Wholesale price $40.00 per unit; retail price $80.00 per unit. The illustrative rate card states a category rate of 10% applied to net invoiced wholesale value, with a direct-channel rule of 8% applied to net retail value. Territory A is granted for all channels. Territory B is granted for wholesale only. The agreement permits returns as a deduction and names no others.

Sale one, wholesale to a national account in Territory A. 1,000 units at $40.00 gives gross of $40,000; permitted returns and credits of $2,000 leave a base of $38,000. Channel is wholesale, territory is granted, so the wholesale rule resolves: 10% of $38,000 is $3,800, or $3.80 per unit.

Sale two, own e-commerce to a consumer in Territory A. 200 units at $80.00 gives gross of $16,000; returns of $1,000 leave a base of $15,000. The direct rule resolves: 8% of $15,000 is $1,200, or $6.00 per unit — 58% more royalty per unit than the wholesale sale on identical product, because the base nearly doubled while the rate fell by two points.

Sale three, own e-commerce to a consumer in Territory B. 100 units at $80.00 gives $8,000 with no returns. But Territory B is granted for wholesale only, so this sale does not resolve. Had the pair been granted, the direct rule would have produced 8% of $8,000, or $640. What it actually produces is an exception: 100 units of leakage requiring the treatment the agreement specifies for unauthorised territory sales, plus a disclosure. The $640 is what to be prepared to remit as a floor, not what to quietly report.

Sale four, a marketplace order where the licensee is the seller of record. 300 units at $80.00 gives gross of $24,000; the operator withholds commission of $3,600 and returns of $600 are permitted. The three-part test resolves this as a direct retail sale through a marketplace channel — title stayed with the licensee until the consumer bought, the licensee set the price, the licensee bears the return. The base is gross less the permitted deduction only: $24,000 less $600 is $23,400, and 8% of that is $1,872, or $6.24 per unit. Commission is a cost of selling, not a deduction, because the agreement does not name it.

One product, one agreement, one period. Per-unit royalties of $3.80, $6.00 and $6.24 on the three granted sales, plus a fourth that should never have completed. Earned royalty on the granted sales totals $3,800 plus $1,200 plus $1,872, or $6,872 on 1,500 units — against 1,600 units shipped. That 100-unit gap between units shipped and units reported is the only visible trace of the leakage.

The same example, resolved incorrectly, and what it costs

Now run sale two the way a wholesale-only extract runs it. The e-commerce orders are pulled through the ERP at the wholesale value the system holds for the style, because that is what the wholesale pipeline was built around. 200 units at $40.00 gives $8,000; the same returned units restate to $500 at wholesale value, leaving a base of $7,500. The direct rate of 8% still applies, and 8% of $7,500 is $600.

Correct: $1,200. Reported: $600. The gap is $600 on 200 units, or $3.00 per unit — exactly half, because the base was halved and nothing else changed. No error was thrown. The units are right, the rate is right, the extract ties to the ERP, the statement foots. Every control that checks internal consistency passes, because the statement is internally consistent.

Price it over a period. Say direct-to-consumer volume on this style and its siblings runs 12,000 units across a contract year: at $3.00 per unit the year is understated by $36,000. If the audit clause permits a three-contract-year lookback and the error ran throughout, the exposure is $108,000 in principal — before any interest the agreement provides for, before audit costs, and before whatever the same error is doing under every other agreement in the portfolio that uses a retail base. Those figures are illustrative arithmetic on the illustrative inputs above, not a claim about typical exposure.

The point of pricing it is that the per-unit error is small and the aggregate is not, and the aggregate is the only form in which anyone sees it. A $3.00 gap is invisible in every summary view, every month-over-month comparison and every accrual review. It becomes visible in exactly one place: a reconciliation comparing reported units and reported value by channel against what actually shipped.

Failure modes and the reconciliation you can run

The failure modes here are a short list, and each produces a specific signature. Reported units below shipped units means volume that never reached a statement — an unmapped channel code, a point-of-sale feed never connected, promotional units on a no-charge order type the extract filters out, or leakage sitting in an exception list nobody cleared. Reported units above shipped units means double-counting, and the marketplace transfer-plus-settlement pattern is the first place to look. Units tying while value does not means the base is wrong — the base-swap error priced above, and the signature that matters most, because it is the one the unit count alone cannot find.

The reconciliation is a cross-tab, built deliberately on a dimension pair rather than on totals. Take total units shipped by channel and by ship-to territory for the period, from the source systems rather than from the royalty extract, and compare against total units reported by channel and territory on the statements. Do it per property: a portfolio total nets one property's over-count against another's under-count and shows a clean number.

Then add a value column to the same cross-tab — reported royalty base by channel and territory, divided by reported units, giving realised base per unit per cell. Read that column down. Direct cells should show a materially higher base per unit than wholesale cells wherever the agreement uses a retail base. A direct-channel cell whose base per unit sits at the wholesale level is the base-swap error, visible in one number. That derived column is the highest-yield check in this whole area and it takes one query.

Two supporting checks close the rest. The boundary test: every royalty-bearing line whose ship-to territory is not in the granted set for that property, in that channel, on that date goes to an exception list — and the list has to be cleared, not merely produced. The resolution audit: count the lines that resolved to a default rather than to a named channel-territory rule. In a healthy configuration that count is zero, and any non-zero value is a list of sales the rate card does not actually have an answer for. Run both in the period rather than at year-end, because every mechanism described here is silent by construction, and an annual check finds a year of one-directional error at once.

Licensed sports apparel

Pro-sports apparel carries the widest channel spread of any licensed category: the same style moves through wholesale to national accounts, the brand's own e-commerce, a marketplace, off-price disposal at end of season, and direct sales to the team organisation. Team and institutional direct is the channel that goes missing, because it is invoiced through the same order-to-cash process as a retail account and inherits the wholesale channel code by default. That matters beyond the rate, because the rights differ: on-field, sideline and team-issued product frequently sits under different terms from retail product carrying the same mark, and team-direct is where the two populations get mixed. A licensee that cannot separate team-direct volume on the transaction cannot report either population against the terms that govern it — and the season shape of this business, with concentrated shipping and postseason windows, means the error arrives in large blocks rather than as a trickle.

Collegiate merchandise

Collegiate adds a channel that behaves like nothing else in licensed apparel: sales to the institution itself and to campus retail. Campus stores, athletics departments and institutional purchasing are commercially distinct from wholesale to a national retailer, and agreements routinely treat them separately — a different rate, an approval requirement, or a restriction on who may sell into them at all. The structural difficulty is that a collegiate portfolio multiplies the channel-territory grid by the school roster. Every school is effectively its own property with its own granted set, and territory here is less about international borders than about defined regional or campus-adjacent restrictions, which means the ship-to field has to be finer than country for a boundary test to mean anything. A configuration carrying one grid for the whole collegiate agreement rather than one per institution will resolve most sales plausibly and some wrongly, with no way to tell which is which.

Licensed footwear

Footwear runs proportionally more volume through closeout and off-price than most apparel categories, because the size-run structure guarantees broken runs accumulate faster than they sell through — a style that performed well still leaves a residue of unsellable size distribution, and that residue has to go somewhere. Closeout is where the carve-outs live, and it is frequently both rated differently and restricted: capped as a share of period units, limited to approved accounts, or requiring notice. That makes closeout the channel where a reporting obligation and a compliance obligation sit on the same lines — reporting the units at the correct treatment does not satisfy a cap, and a cap breach is not cured by having reported it accurately. Footwear also tends to have a more international wholesale footprint than its direct channels, so the pattern of a territory granted for wholesale but not for direct is common, and cross-border consumer orders from the brand site are correspondingly more likely to land outside the granted set.

Headwear and accessories

Headwear and accessories carry a proportionally larger share of marketplace and promotional volume than apparel, for the same reason they carry it at lower unit prices: they are impulse and gift items with low shipping cost, which is exactly the profile that performs on marketplaces and in promotional programmes. Both of those channels have the weakest data. Promotional and premium units frequently move on no-charge or deemed-value order types a revenue-based extract never sees, and marketplace volume arrives through settlement files rather than the invoice ledger. The result is a category where a large share of units sits in the two channels least likely to reach the extract, and where low unit value makes the per-unit error look immaterial until it is multiplied by the volume. This is the category where the units-shipped versus units-reported reconciliation earns its keep, because the value gap will not attract attention on its own.

Home and fan gear

Home and fan gear — blankets, drinkware, flags, wall decor and the hardgoods adjacent to a licensed apparel programme — is where drop-ship is structurally common, and drop-ship is precisely what blurs the title-transfer test. In a drop-ship arrangement the product ships directly from the licensee to the retailer's consumer, on the retailer's order, at a price the retailer set. Physically it looks like a direct-to-consumer shipment: one unit, a consumer address, a parcel carrier. Contractually it is usually a wholesale sale, because the retailer took title, set the consumer price and bears the return. The shipment shape says direct and the commercial substance says wholesale, and a channel derivation keying off shipment characteristics rather than title and price control will classify the entire drop-ship book as direct, applying a retail base to sales invoiced at wholesale. The same three-part test that settles the marketplace question settles this one — which is the argument for holding a title-transfer flag on the line rather than inferring channel from how the parcel moved.

Golf merchandise

Golf adds a channel most apparel programmes do not have: on-course and green-grass retail selling into pro shops and resort operations, plus event and on-site retail at tournaments. Both are commercially distinct from wholesale to a sporting-goods retailer, and both tend to be invoiced through the same wholesale process, which is how they lose their channel identity. Event retail also carries a territory question ordinary channels do not. A tournament sells to whoever is standing there, so the consumer's home market is unknowable and the sale's destination is the event site. Agreements addressing event retail generally resolve territory to the event location, which is workable but has to be encoded — an event sale cannot be resolved by a ship-to address, because there is no shipment. Where an event mark is involved as well, the mark, the channel and the territory all resolve differently from the same licensee's ordinary golf apparel business.

Motorsports merchandise

Motorsports has the same event-retail structure as golf in a sharper form, because trackside and at-event merchandise is a larger proportion of the business and the calendar moves across territories through the season. A series racing in several countries generates event-retail sales in each of them, and each is a sale into that territory through the event channel. That is exactly the territory-times-channel case from earlier in this guide, arriving as a routine operating fact rather than an edge case. An agreement can grant event retail at a circuit in a territory where it grants no wholesale and no direct rights at all, and the reverse is equally common. Resolving those sales requires the event location as the territory and the event channel as the channel, on the transaction date, against a grant that may have been amended for the season. A configuration built around a domestic wholesale business resolves every one of them to a default, produces plausible royalties, and hands a licensor with a global rights structure a statement that cannot be tested against the grants it actually made.

What this guide covers, and what sits next to it

This guide is about determination: how a sale acquires its rate and its base from channel and territory, and what has to be true of the data for that determination to be possible. Three adjacent questions have their own treatments, and the seams are worth stating.

Propagation is the neighbouring problem, not this one. When a channel is granted mid-term or a territory added by amendment and the change never reaches the file the calculation reads, that is stale-master drift, and its guide works through the four causes and the reconciliation. Drift is a current rate card failing to arrive; this guide is about a current rate card failing to be applied to the right cell. A licensee can fix drift completely and still misreport every direct sale in the portfolio.

Conversion is the layer above territory: once a sale is correctly attributed, and that territory settles in a currency other than the one the obligation is denominated in, which rate source and which conversion date applies takes over — and converting twice produces a fourth plausible number. That is the multi-currency guide, read after this one rather than before. Category is the layer beneath both: what counts as a unit and what counts as the base differ by product category before channel or territory touches them, which is why the resolution chain puts category ahead of both.