MétaCan
Menu
Back to cohort
Record W2769108999 · doi:10.1108/ijchm-09-2016-0540

Use of dynamic pricing strategies by Airbnb hosts

2017· article· en· W2769108999 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 Journal of Contemporary Hospitality Management · 2017
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicSharing Economy and Platforms
Canadian institutionsToronto Metropolitan University
Fundersnot available
KeywordsDynamic pricingContext (archaeology)BusinessListing (finance)Sharing economyPricing strategiesMarketingEconomicsComputer scienceFinance

Abstract

fetched live from OpenAlex

Purpose The purpose of this paper is to provide a comprehensive analysis of dynamic pricing by Airbnb hosts. Design/methodology/approach This study uses attribute and sales information from 39,837 Airbnb listings and hotel data from 1,025 hotels across five markets to test different hypotheses which explore the extent to which Airbnb hosts use dynamic pricing and how their pricing strategies compare to those of hotels. Findings Airbnb is a unique and complex platform in terms of dynamic pricing where hosts make limited use of dynamic pricing strategies, especially as compared to hotels. Notwithstanding their limited use, hosts who own listings in high-demand leisure markets, manage entire places, manage more listings and have more experience vary prices the most. Practical implications This study identified a great need for Airbnb to encourage dynamic pricing among its hosts, but also warned of the potential perils of dynamic pricing in the sharing economy context. The findings also demonstrated challenges for hotel managers interested in actionable information related to Airbnb as a competitor. Originality/value This is the first Airbnb study to use a comprehensive set of data over a continuous period in multiple markets to look at a number of listing and host factors and determine their relation with dynamic pricing strategies.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.202
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0010.008
Open science0.0010.000
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.035
GPT teacher head0.273
Teacher spread0.237 · 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