'', 'company_email' => '', 'company_phone' => '', 'company_address' => '', 'company_city' => '', 'company_state' => '', 'company_country' => '', 'company_zip' => '', 'company_website' => '', 'company_logo' => '', 'timezone' => 'UTC', 'date_format' => 'Y-m-d', 'time_format' => 'H:i', 'frontend_primary_color' => '#3b82f6', 'frontend_container_max_width' => '', // Booking Settings 'booking_confirmation' => true, 'auto_confirm_bookings' => false, 'auto_confirm_pay_later' => true, 'require_login' => false, 'allow_guest_checkout' => true, // cancellation_policy / cancellation_days / refund_policy were // removed in 3.0.5 — they only inserted text into the booking // confirmation email but did NOT enforce a cancellation cutoff // because Yatra has no customer-facing self-service // cancellation flow. Per-trip cancellation copy on the Trip // editor is the supported way to communicate policy. If those // legacy options still exist in wp_options on upgraded sites // they're harmless orphans — the save endpoint no longer // accepts them, and the email template skips the cancellation // paragraph when the global setting is absent. 'booking_expiry_hours' => 24, 'booking_reminder_days' => 3, 'allow_waitlist' => true, 'waitlist_auto_confirm' => false, // Pro: render available departure dates as a