MétaCan
Menu
Back to cohort
Record W3122135500 · doi:10.1287/mnsc.1120.1627

Revenue Sharing and Information Leakage in a Supply Chain

2012· article· en· W3122135500 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueManagement Science · 2012
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicSupply Chain and Inventory Management
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsRevenue sharingRevenueBusinessIncentivePrivate information retrievalSupply chainInformation leakageInformation sharingLeakage (economics)MicroeconomicsRevenue managementIndustrial organizationYield managementRevenue assuranceInformation asymmetryOrder (exchange)Marginal revenueEconomicsRevenue modelMarketingFinanceComputer science

Abstract

fetched live from OpenAlex

This work explores the potential of revenue-sharing contracts to facilitate information sharing in a supply chain and mitigate the negative effects of information leakage. We consider a supplier who offers a revenue-sharing contract to two competing retailers, one of whom has private information about uncertain market potential and orders first. This order information may be leaked to the uninformed retailer by the supplier to realize higher profits. We show that the incentives of the supplier and retailers are better aligned under a revenue-sharing contract, as opposed to under a wholesale-price contract, reducing the supplier's incentive to leak. This is true for a wide range of wholesale prices and revenue-share percentages and is more likely when the revenue-share percentage is higher and when variation in demand is greater. Preventing information leakage may result in higher profits not only for the informed retailer and supplier but surprisingly even for the uninformed retailer. Our results are robust when the model is generalized along various dimensions. This paper was accepted by Yossi Aviv, operations management.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.499
Threshold uncertainty score0.752

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0010.010
Open science0.0000.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.014
GPT teacher head0.217
Teacher spread0.202 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it