MétaCan
Menu
Back to cohort
Record W2626041611 · doi:10.1111/itor.12431

Cooperative advertising programs: are accrual constraints necessary?

2017· article· en· W2626041611 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

VenueInternational Transactions in Operational Research · 2017
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicConsumer Market Behavior and Pricing
Canadian institutionsAthabasca UniversityOntario Tech University
Fundersnot available
KeywordsBusinessIncentiveAdvertisingMonopolyConstraint (computer-aided design)PaymentAccrualBudget constraintMarketingMicroeconomicsEconomicsFinance

Abstract

fetched live from OpenAlex

Abstract This paper investigates how the use of an accrual constraint in a cooperative advertising program affects channel members' profits in a bilateral monopoly, as well as their pricing and advertising decisions. The main findings indicate that, compared to unconstrained cooperative advertising programs, when an accrual constraint is used and the manufacturer's contribution to the retailer's advertising costs exceeds the accrued cooperative advertising budget, the retailer reduces both her retail price and advertising efforts to the level where cooperative advertising is not offered; while the manufacturer also reduces his wholesale price and advertising efforts, but this time, the wholesale price remains higher than when there is no cooperative advertising. These strategic moves translate to less (more) profits for the manufacturer (retailer). The use of an accrual constraint is counterproductive for the manufacturer as the retailer uses the accrued advertising fund as a side payment rather than a direct incentive to invest more in advertising. The manufacturer and retailer are better off when unconstrained cooperative advertising programs are supplemented with other incentives, including side payments and advertising support services.

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.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Scholarly communication, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.456
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0010.001
Scholarly communication0.0020.003
Open science0.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0050.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.122
GPT teacher head0.404
Teacher spread0.282 · 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