OPTIMA Hotel Rate Scraper

property-processed

Charged once per property at the start of a run. Covers the fixed per-property overhead of resolving the booking site's shape and facility metadata and building the crawl plan.

date-scanned

Charged once per (property x check-in date) scanned, whether that date came back bookable or sold out - both are results. This is the fixed part of the work: one request for the date, however heavy the page. Predictable up front: properties x days in your date range. A date that could not be collected, or whose page returned the wrong check-in date, is not charged.

room-plan-row

Charged per row written to the dataset: one room x plan combination on one check-in date, with its selling price, pre-discount price, discount rate and member price. A sold-out date writes one row. Rows that record a date we could not observe (availability: null) are not charged. This is the variable part of the work - a property with many plan variants returns far more rows per date than a small ryokan, and this is where that difference is priced rather than averaged into the per-date price.