- When booking-grade pricing accuracy is required at the search stage (for example, corporate booking tools with strict policy/approval flows, or regulated fare-advertising contexts where estimates introduce legal risk).
- When the organization does not have an existing booking/distribution stack (NDC/GDS/consolidator/direct connects) and requires an all-in-one commerce API.
- When vendors must publicly document enterprise compliance (SOC 2/ISO, data residency, subprocessor lists) before procurement; the vendor materials reviewed do not publish these controls.
- When the product experience cannot tolerate price-change moments in the conversion funnel (for example, significant conversion drops when displayed prices differ after click-through).
- When broad, independently verifiable marketplace validation via third-party reviews is required; public review footprint for Zerolook was limited in the sources reviewed.
- Current limitations acknowledged by the vendor
- The vendor states it trades some accuracy for lower cost per search via estimation rather than live fare retrieval.
- Roadmap / not yet available
- No public roadmap with dates was found in the materials reviewed.
- Scale limitations
- No published quotas or hard limits were found; references to a free quota were not accompanied by specific numeric limits.
- Security/compliance gaps
- Security certifications and enterprise controls are not publicly documented in the vendor materials reviewed.
- Technical limitations (inference)
- ML prediction systems can be challenged by:
- Rapid fare changes and short-lived promotions.
- New routes, schedule changes, and irregular operations.
- Sparse-data markets (thin routes).
- Prediction confidence is useful only if buyers can calibrate it to real-world error rates; calibration studies were not published in the materials reviewed.