Built for Explore Andros.
Designed to organize our work.

Recommend understandable Direct prices using Rentlio data and support controlled updates for the 2027 revenue strategy. The long-term ambition is daily revenue automation across roughly 60 listings; the current workflow is deliberately manual scan, review, and publish. Near-term low-season occupancy is a stated business goal, alongside protecting strong summer periods. Sources: Build Explore Andros Revenue OS and Build Revenue Automation System.

The project began as an alternative to the cost of an external revenue platform, inspired by PriceLabs. Building around existing Rentlio access allows Explore Andros to own its Andros-specific rules, historical snapshots, and explanations while keeping Rentlio responsible for channel distribution. PriceLabs is a reference, not the implemented engine. TODO: formal cost comparison, maintenance budget, and success targets.

Explore Andros pricing decision-makers and operators reviewing calendars and approving Direct-price updates. The interface was explicitly requested to use language an amateur can understand. TODO: named approvers and any multi-user permission model.

Revenue OS is now live at revenue.exploreandros.gr for viewing. Scanning and syncing remain in the local application. Anemomiloi and Archontiko Eleni have observed property-specific entry links. Pages: Foundation, Pricing Rules, Pricing Calendar, Change Log, and Competitors. The former “Things to check” page was removed on 2026-09-29; minimum-stay conflicts appear inside the calendar instead. Build history and source-file references: Build Explore Andros Revenue OS. Cloud calendars cover Castel Abaso, Anemomiloi and Archontiko Eleni. A separate hosted test URL remains TODO.

Live view-only cloud release published on 2026-10-11. The connected local application retains Rentlio scanning and controlled publishing until a secure hosted backend is ready. Castel Abaso was the initial pilot; Anemomiloi and Archontiko Eleni were added on 2026-09-29. The competitor monitor and date-range improvements were completed in the Rate Checker chat on 2026-10-07. Latest reported integration checks: 16 tests passed plus browser validation.

Manual scanning is active; no automatic pricing schedule is reported. Publishing exists and has been exercised for Castel Abaso. Anemomiloi publishing was explicitly enabled. Archontiko Eleni was introduced as review-only; later month-selection controls do not establish that its publishing gate was lifted. TODO: verify its current permission before describing it as enabled.

The README still labels the initial collector v0.1 and contains obsolete read-only statements. Current application release version is TODO; pricing configuration and foundation versions are separate from a product release.

• Multi-property selector with independent calendars, suggestions, overrides, and history.
• Rentlio scans for one selected property or all configured properties.
• Versioned 2026/2027 pricing foundations and daily current-versus-suggested Direct prices with explanations.
• Manual date-level price and minimum-stay overrides with “Use automatic” reset.
• Locked booked dates showing actual booked nightly price, channel, and rate name.
• Price-only publishing from the current Athens date onward, with selected From/To dates and confirmation.
• Red “MIN-STAY BLOCKED” calendar indicators and explanations.
• Light/dark modes, Explore Andros branding, and scan/publication history.
• Rate Checker CSV import with duplicate-file protection; embedded Competitors monitor with saved date/guest results, nightly comparisons, median, positioning, and coverage.

Agreed direction: expand toward roughly 60 listings; keep automatic pricing deferred until needed. Complete reliable comparable-property coverage before allowing market observations to influence pricing.

Pending: confirm Archontiko Eleni approval; validate Anemomiloi competitor results and distinguish monitoring from engine influence; refresh stale operating documentation. Minimum-stay publishing is paused, with a review requested for 2026-10-29; current reminder activation has not been rechecked.

Proposed later: secure hosted scanning/publishing, scheduled reconciliation, broader historical backtesting, and monitored automation. Owners, dates, and acceptance targets remain TODO.

Rentlio API supplies properties, unit types, units, rate plans, Direct prices, restrictions, availability, and reservations. Python collector/pricing services store snapshots in SQLite. Credentials are stored in macOS Keychain, with an environment-variable fallback; reservation snapshots deliberately exclude guest names, contact details, notes, and raw payloads.

Rate Checker contributes CSV observations and the Chrome-assisted Competitors monitor. Rentlio remains responsible for deriving/distributing OTA prices. The initial suggestion of PostgreSQL/Supabase was not the implemented storage choice. Sources: Build Explore Andros Revenue OS, Improve Andros rate checker, and project README.

Cloud calendars are available through the live URL. Scanning, syncing and competitor checks require the local Python service, SQLite database, access to the configured Rentlio account, correct property/unit/rate-plan mapping, operating inventory, and approved pricing foundations. The competitor screen also requires the Chrome helper and a signed-in Booking.com session for Genius prices.

Known scope: Castel Abaso has 3 unit types/3 physical units; Anemomiloi has 11 types/17 physical units; Archontiko Eleni has 5 types/8 physical rooms. Counts are the documented onboarding snapshots, not a new inventory audit. TODO: central mapping owner, hosting/recovery owner, and current write permissions.

• Current publishing boundary: Direct price only; exclude booked and past dates, and restrict writes to selected property and From/To date range. Minimum stays, availability, closures, and other restrictions are not sent.
• Master-rate hierarchy: Castel Abaso DIRECT is the manual parent. Its initial verified derivatives were Airbnb +10% and Booking Expedia +45%, before OTA promotions. Do not apply these percentages to other properties without checking their mappings.
• Anemomiloi: 7 hotel/apartment types use Hotel Breakfast DIRECT; 4 studio types use Studios Breakfast DIRECT. Archontiko Eleni: Breakfast DIRECT is the controlled parent; Room Only/OTA plans remain derived.
• Date handling: recalculate against today's Europe/Athens date. Booked dates show booked prices and receive no recommendation or write.
• Foundations: 2027 foundations use 2026 evidence plus 10%. Summer bands are June, July 1–15, July 16–31, August 1–15, and August 16–31. Enforce configured minimum/maximum prices and preserve manual overrides.
• Dynamic suggestions: arrival-window occupancy, booking recency, last-minute/short-gap effects without stacking related discounts, historical price protection, neighboring-date checks, and €5 rounding for normal suggestions.
• Holiday revision on 2026-09-29: Orthodox Easter, Holy Spirit weekend, and the August Dormition peak retain maximum-price protection. New Year, Epiphany, Clean Monday, Independence Day, Ohi Day, and Christmas use low-season baseline +10%, weekend adjustment, and live demand rather than automatic maximums.
• Publishing verification: batch writes and read back results; record the outcome in Change Log. A historical oversized-request failure was fixed with yearly batches.
• Competitors: monitoring is implemented; automatic influence on pricing is not established by the monitor integration. Confirm comparable observations and engine activation separately.

TODO: consolidate exact per-property numeric thresholds and exception precedence from the active rule configuration into a versioned rule register.

Sources: Build Explore Andros Revenue OS; Improve Andros rate checker. Earlier minimum-stay publishing and broad holiday maximum rules are historical, not current policy.

• The cloud release is view-only. Scanning and syncing depend on the local host process; a secure hosted backend and automatic pricing schedule are not yet established.
• Archontiko Eleni's publishing approval remains unconfirmed.
• Competitor monitoring does not prove market-driven pricing is enabled. Castel Abaso's curated competitor set remains unresolved in its build chat.
• Minimum-stay conflicts are visible, but their restrictions are not fixed by price-only sync.
• Rentlio plan markups do not establish final guest-visible OTA prices after promotions.
• Initial README claims are stale; current behavior must follow later recorded changes.
• TODO: verified backup/restore procedure, complete issue ownership, and current operating coverage.

Source: Build Explore Andros Revenue OS and Improve Andros rate checker. Named decision owners and future review cadence: TODO.

Give each booking a personalized portal for reservation details, house information, arrival, check-in, service requests, and support. Reduce repeated questions about parking, Wi-Fi, hot water, appliances, and access while organizing submissions for reception. Anemomiloi is the pilot; the intended reach is the Explore Andros portfolio. Sources: Guest Space Strategy and Build Explore Andros guest space.

Build one reusable portal engine around Rentlio rather than manually creating a portal for each property or adopting another full platform. Explore Andros combines accommodation with transfers, cars, tours, activities, and cruises, so tailored service discovery and shared property content are central benefits. RentalReady inspired the initial structure; the selected design was the center “Modern & Visual” option. TODO: formal total-cost comparison and long-term maintenance ownership.

Guests use a reservation-specific link without creating a password. Reception and operations staff review check-ins, add manual entries, assign requests, and follow work through completion. Staff access remains private in the MVP. TODO: approved staff email allowlist, named request owners, and escalation cover.

• Guest Space MVP
• Guest Operations
• Anna test booking — Deluxe 2
• Sofia test booking — Superior 3

Prepared routes include /guest for token exchange, /api/rentlio/webhook, and an internal invitation endpoint. These routes are architecture references, not issued guest invitations. Branded production origin remains TODO; guest.exploreandros.gr and stay.exploreandros.gr were examples/proposals, not confirmed deployments.

Working, privately deployed MVP, summarized as current on 2026-10-07. Guest submissions persist into the connected operations dashboard. The Rentlio adapter, webhook handler, token/session mechanisms, and mappings are prepared, but live Rentlio synchronization and automated guest-link delivery are not connected.

Reported validation includes production build, linting, responsive layout review, check-in persistence, access locking, and protected endpoints. Current product release number: TODO; “MVP/v1” describes scope, not a verified semantic version. Next milestone: approved content and a real internal reservation pilot.

• Personalized reservation card with property, separate room name/category, dates, guest count, status, and map.
• Check-in form using name, mobile number, arrival time, and notes, with confirmation popup.
• Arrival/parking/directions, timed access, house rules, Wi-Fi/property guides, support, and departure content.
• Tailored availability-request forms for port transfer, car rental, RIB cruises, island tours, and outdoor activities.
• During-stay requests for cleaning, towels, maintenance, and late checkout.
• Staff request and check-in queues with priority, assignment, search, review attribution, and urgent maintenance highlighting.
• Receptionist manual request/check-in entry into the same queues.
• Reservation filter and expandable reservation groups; Open and All history views.
• Reusable property content and responsive layout. Local Favourites and the broader Andros guide section were removed pending complete guides.

1. Approve Anemomiloi house rules, parking, directions, Wi-Fi, appliances, access, contacts, and service details.
2. Finalize required service fields, displayed prices if any, staff responsibility, and response/confirmation procedure.
3. Connect live Rentlio credentials, verified property/unit and status mappings, webhook secret, and reachable webhook endpoint.
4. Complete automatic stable guest-link generation, reservation-note creation, direct-booking email delivery, and assisted OTA delivery tracking.
5. Configure staff access, notifications, follow-up reminders, rate limits, audit logs, retention/deletion, and monitoring.
6. Test creation, modification, cancellation, expiry, and one real internal booking before public rollout; then add properties through content and mappings.

Longer-term ideas remain proposed: complete Andros guides, multilingual content, payment/service-provider connections, and repeat-guest accounts. No delivery dates or owners are committed.

The hosted MVP uses Cloudflare D1 for reservation snapshots, token hashes, check-ins, requests, and webhook deduplication. Property content and service content are separate from the Rentlio adapter. Guest submissions are already connected to Guest Operations.

Rentlio API/webhooks are prepared but not live. Explore Andros and Anemomiloi website content supplies service/property information and imagery. WhatsApp, phone, and email support links are present; automated notifications are pending. No confirmed connection to Housekeeping Staff Space, Xola, GoCars, payment providers, or smart locks exists. Sources: Build Explore Andros guest space and its project README.

Production depends on approved property content, actual room mappings, status definitions, credentials, webhook reachability, staff access configuration, an email delivery provider, and a selected production origin. Anemomiloi Rentlio property ID 31385 is recorded in Revenue OS, but GSO's own property/unit mapping must still be validated and installed; the README's example IDs are placeholders. Guest URL handling and Rentlio-note delivery must be reconciled before launch.

• Guest access uses a random reservation-specific invitation token, stored only as a hash, exchanged for an HTTP-only secure session. Guests do not need passwords.
• The prepared webhook flow deduplicates event IDs and refetches the current reservation. Cancellation handling revokes tokens; production event coverage remains to be tested.
• Current access-window implementation releases sensitive instructions 24 hours before arrival and removes them at departure. Property-specific timing still needs approval.
• Check-in arrival choices run from 15:00 to 23:30. Service time choices run from 06:00 to 23:30. Service date pickers disallow dates outside the stay.
• Mobile number replaces email in check-in and receptionist entry. Port transfer is the service name; airport references were removed.
• Service submissions are availability requests with no immediate payment or automatic confirmed booking.
• Request states are new, in_progress, waiting_guest, confirmed, completed, cancelled. Check-in states are submitted, reviewing, approved, needs_update; guest edits return them to submitted/awaiting review.
• Open view excludes completed/cancelled requests; All retains history. Maintenance is urgent and urgent reservation groups appear first.
• Planned delivery: automatic dedicated email for eligible direct bookings; reception copies the link from the Rentlio reservation note into Airbnb/Booking.com conversations.
• Planned updates should preserve a stable link. The current invitation endpoint revokes earlier links when explicitly regenerating; these operations must remain distinct.

TODO: production token lifetime, staff response times, retention, approved unlock timing, and guest-link storage rules.

Source: Build Explore Andros guest space.

• Current private hosting prevents external Rentlio webhook delivery until production access is configured.
• Live credentials/mappings, reservation notes, automated email, notifications, and staff allowlist remain pending.
• Test bookings and placeholder property information are not production reservation data.
• Broader Andros guides, image-rights confirmation, retention/deletion, monitoring, rate limits, and access audit remain launch work.
• The README says to keep invitation URLs out of CRM free text, while the later agreed workflow stores them in a Rentlio reservation note. Resolve this explicitly with controlled staff access and minimal link exposure before activation.
• Original invitation expiry was described as 30 days; checkout-plus-24-hours was proposed. No completed change is established. TODO: verify actual lifetime before live booking links.

Source: Build Explore Andros guest space. Named operational owners remain TODO.

Replace inaccurate verbal hour reporting for roughly 10 cleaners moving among hotels and houses with low-effort records of who worked, where, when, and for how long. Schedules change at short notice and the manager coordinates through WhatsApp. This tool records cleaning activity; it is not yet a full attendance or payroll system. Source: Build Andros housekeeping MVP and Housekeeping Time Control.

Fit the team's actual flexible workflow: keep WhatsApp coordination, avoid a second assignment schedule, and make starting/switching/finishing cleaning quick. Cleaner feedback drove fewer interactions and optional details after completion. Internal development also permits specific exception review and a compact report format for this team. TODO: formal build-versus-buy costing and maintenance owner.

Approximately 10 cleaners use individual accounts on their own phones. Managers administer staff/rooms, inspect current work and exceptions, correct times, manage deleted records, and download date-range reports. The pilot property is Anemomiloi Andros. Actual enrolled cleaner count and named managers remain TODO.

Staff Space is the documented live custom domain. Original Sites address is the deployment reference.

Role-specific views include room selection, active timer, cleaner day history, manager dashboard, Daily Activity, Deleted records, and Daily PDF report. Managers generate real QR/NFC links at /nfc/:token; do not publish actual operational tag tokens in this master. Build and setup references: Build Andros housekeeping MVP.

Deployed operational pilot with individual staff login; no ChatGPT account is required for cleaners. The custom domain was activated on 2026-10-03. Automatic switching, manager review, and offline recording were published on 2026-10-04; Daily Activity controls on 2026-10-05; compact one-page-per-cleaner PDF reports on 2026-10-06.

Validation reported role/ownership checks, overlap prevention, offline queue/reconnect behavior, correction audit, deletion/restoration, and PDF rendering. Physical NFC writing/reads and reminder delivery still require tests on actual team phones. The latest manager view supports arbitrary date ranges and presets; Apply dates updates activity, cleaner hours and records. PDFs follow the same selected range. Product version label: TODO; deployment/build references are available in the source chat.

• Individual staff username/password login remembered on the same browser until sign-out or account-access reset.
• QR/NFC room identity and large room buttons; NEXT ROOM automatically closes the previous job and starts the next.
• Instant COMPLETE; optional Extra work, task type, notes, and private photo afterward.
• One active job per cleaner; multiple cleaners can record their own labor on the same room.
• Manager daily work/current timers, cleaner totals, exception review, corrections with reasons and original history.
• Cleaner filter, newest/oldest sorting, and recoverable manager-only deletion/restoration.
• Offline start/switch/complete queue with duplicate protection and reconnect sync.
• Opt-in phone push reminders with manager-adjustable threshold.
• Date-range PDF for all or selected cleaners, with period totals and sessions grouped by cleaner; compact layout, branding and Greek text support.

Current pilot: use simple real QR stickers first; NFC may be added later using the same room URL. Confirm all team phones, room setup, reminders, and offline behavior on site.

Deferred/proposed: OTHER WORK for travel/linen/non-cleaning duties; separate working-day start/end; contextual workload comparisons. A review of manager corrections and working-day tracking was reported scheduled for 2026-10-25 at 10:00 Athens; current schedule state has not been rechecked.

Future architecture only: reuse stable unit identity for Maintenance and Property Manual modules. Rentlio task creation appeared in the original concept, but later scope keeps Rentlio disconnected and WhatsApp as the planning channel.

Recovery work: independent backups, exports, and tested restore procedure remain TODO.

OpenAI Sites hosts the application on Cloudflare Workers, with D1 for staff/work records and R2 for private photos. SiteGround manages custom-domain DNS. Browser storage holds the cleaner's cached room/day data and unsynced work events; a service worker caches the public app shell. PDFs are generated locally in the browser using pdf-lib and embedded fonts.

Phone reminders use Web Push and an hourly cloud task. WhatsApp remains a human coordination channel, not a confirmed API integration. Rentlio, payroll, and Guest Operations are not connected. Source: Build Andros housekeeping MVP and project README.

Requires real cleaner accounts and room records, usable team phones, generated room URLs/labels, a first online visit for offline setup, retained browser storage, eventual connectivity for sync, and notification permission where reminders are used. SiteGround DNS and Sites/Workers/D1/R2 support the live service. Managers must review conflicts and forgotten timers. TODO: named data/recovery owner and confirmed hardware rollout.

• First room requires START. Selecting/opening a different valid room while active ends the previous job and starts the next at the same timestamp. Same-room scans leave the timer running. The final room requires COMPLETE.
• Completion saves time immediately with Normal default; optional details added afterward never extend the job.
• One unfinished job per employee is enforced in storage; concurrent staff may clean the same room independently.
• Tags identify the room, login identifies the employee. Static QR/NFC links do not prove physical presence; no continuous GPS is used.
• Daily totals use Europe/Athens boundaries, split overnight sessions across days, and include labeled in-progress time.
• Offline events preserve captured phone time and deduplicate retries. Sync requires the page open; queues authenticate their owner and reject stale/conflicting work.
• Managers correct with reasons and preserved original/changed times. Manager-only deletion is recoverable and audited; deleted records are excluded from totals. Restore cannot overlap other work and does not restart a former active timer.
• Reminders default to 90 minutes; manager range is 15–600 minutes. Checks run hourly, so reminders can arrive up to an additional hour later. Reminders never stop timers.
• Reports include all or selected cleaners, including those with no work. Open timers use report-generation time; deleted records are excluded. The current date-range reports include period totals and session details grouped by cleaner. The earlier daily-only, one-page format is historical; full records remain available in the dashboard.
• Photos are private JPEG/PNG/WebP, maximum 5 MB. Minimum password length was reduced to 4 characters, with numbers-only passwords allowed, at the user's request.

These are recorded implementation rules, not a statement that cleaning totals equal paid working hours.

Source: Build Andros housekeeping MVP.

• Cleaning timers are not attendance/payroll totals. Automatic switching may include walking, linen collection, or travel in the previous room's duration.
• Auto-finished does not prove a room was inspected or guest-ready. Normal means no extra work reported, not a quality certification.
• Offline support requires an initial online visit and an open page for sync. Clearing browser data or losing a phone can lose unsynced records. Photos/notes require connectivity.
• Offline completions may still receive reminders until the server gets the update. Push is not an exact ringing alarm and depends on phone settings.
• Static tags do not verify presence. Physical NFC/QR and phone-notification tests remain site-specific.
• Independent backup/restore is not documented as configured. No travel/other-work tracking, payroll, working-day attendance, or email password recovery; staff text is English.
• Compact PDFs deliberately shorten notes and may combine overflow sessions; the dashboard retains full records.

TODO: issue owners, remediation dates, actual pilot adoption, and recovery test evidence.

Source: Build Andros housekeeping MVP. Working-day measurement remains a separate open decision.

Compare the actual guest-visible price of Explore Andros accommodation across Direct/Rentlio, signed-in Booking.com/Genius, and Airbnb; detect OTA undercutting and incorrect mappings. Scope expanded to an Anemomiloi competitor monitor so pricing can be reviewed inside Revenue OS without opening each site manually. Source: Improve Andros rate checker.

The tool preserves Explore Andros's exact property and unit mappings, handles shared Booking hotel pages, and checks the signed-in prices the user actually sees. A Chrome helper was built because a standalone HTML page cannot use the user's Booking session by itself. Integrating competitors into Revenue OS reduces manual tab switching. TODO: quantified time saving and maintenance budget.

Explore Andros staff responsible for pricing, rate parity, listing mapping, and competitor review. The automatic checker runs in the user's signed-in Chrome profile. TODO: named audit owner and distribution/access policy for the internal extension.

Current competitor interface: Revenue OS, then Competitors. Distribution remains a local standalone HTML plus the “Explore Andros One Listing Checker v1.9.0.zip” Chrome package from Improve Andros rate checker; no hosted standalone URL is confirmed.

Known Direct sources include Anemomiloi, Castel Abaso, and Archontiko Eleni.

The recorded Anemomiloi competitor set is Edem Suites, Saint Louis, Iro Suites, Vassiliki Studios, and Paradise Art Hotel. These are the sources stored in the build history, not a fresh competitor-market audit.

Working internal Chrome extension and standalone HTML lineage. Latest recorded helper release is v1.9.0 on 2026-10-07, adding the bridge to Revenue OS; v1.8.0 added the competitor tab. The latest own-listing count explicitly recorded was 57 in v1.7.3; later competitor entries form a separate group, so do not treat “57” as a newly verified total of all current rows.

Code/package and browser interaction checks are reported, but complete end-to-end audits depend on the user's signed-in Chrome session. No completed all-listing audit report was supplied in the reviewed history.

• Standalone date/guest controls, exact listing links, manual entry, euro/percentage comparison, cheapest channel, undercut warnings, and local autosaving.
• Chrome-assisted Direct, signed-in Booking/Genius, and Airbnb extraction.
• One-listing-at-a-time controls; remembered or fixed Booking room mapping for shared-property pages.
• Configurable Booking mobile discount estimate, default 10%, kept separate from the observed desktop/Genius price.
• Listing search by name, alias, category, IDs, and URL.
• September audit mode: sequential listing checks, first available two-night stay search, pause/resume/stop, saved progress, and CSV troubleshooting export.
• Competitor Direct/Booking checks, stay totals and average nightly prices, temporary background tabs, and saved results per date/guest combination.
• Revenue OS competitor median, position, coverage, chosen Anemomiloi room comparison, and responsive date-range picker.

Next: install/reload helper v1.9.0, validate the Revenue OS connection, and collect representative signed-in checks. Complete the own-listing audit and use its CSV to investigate failed extraction, wrong room mappings, unavailable channels, and genuine undercuts.

Pending coverage: Gialia House Direct URL; dependable Direct prices for Edem/Vassiliki; verified Airbnb links where currently disabled. Expand comparables for other properties only after review.

Later/proposed: improve robustness against provider-page changes, define refresh/freshness policy, and decide whether validated market observations should influence pricing. No autonomous daily scan schedule or automatic Rentlio publishing is established.

Own listings use Rentlio booking engines, Booking.com public property pages opened in the signed-in Chrome session, and Airbnb listing pages. Competitors use official Direct engines where extractable plus signed-in Booking.

Direct competitor coverage recorded on 2026-10-07: Saint Louis, Iro Suites, and Paradise Art support Direct + Booking; Edem is Booking-only because its official site uses an enquiry form; Vassiliki is Booking-only because dependable public Direct prices were unavailable.

Revenue OS receives CSV observations with checksum-based duplicate protection and now uses the v1.9.0 helper bridge for its Competitors page. Mobile rates are calculated estimates, not an independently observed source.

Requires Chrome, the installed/reloaded helper version, active Booking.com/Airbnb sign-in where applicable, valid dates/guest counts, and correct property/unit mappings. Security checks and room-selection prompts may require intervention. The Revenue OS monitor additionally requires its local service. TODO: extension distribution owner, regression examples, and audit cadence.

• Compare the same stay dates and guest count across channels. Store stay total and average nightly price; total divided by stay nights is a normalization, not a verified daily tariff for each night.
• Use actual signed-in Booking/Genius prices; do not substitute public prices as Genius or fabricate a flat Genius discount.
• Mobile estimate = observed desktop/Genius price × (1 − configured mobile discount). Default is 10%; label the result Estimated and allow disabling it.
• Process one listing/competitor at a time. A listing's channel checks may use separate background tabs; close temporary tabs after extraction unless user action is required.
• Clear stale prices when dates/guests change; saved results must retain their date/guest context.
• Shared Booking property IDs require the correct unit/room mapping. Unavailable target rooms must not silently substitute another room.
• Missing URL, unavailable stay, extraction failure, and observed rate are distinct states; missing is not zero.
• Strip transient tracking/session values from canonical stored URLs; add fresh stay parameters.
• Competitor comparisons do not publish Rentlio rates automatically.

TODO: current children-age handling, tax/fee and cancellation-policy equivalence, observation expiry, and alert thresholds. Early HTML treated children as infants because ages were not collected; no later correction was established.

Source: Improve Andros rate checker.

• Page extraction can break when providers change layouts, require sign-in, or show security checks. Complete signed-in audits remain necessary.
• Booking Mobile is an estimate; eligibility and stacking vary.
• Edem and Vassiliki do not have dependable Direct extraction in the recorded implementation.
• Gialia House Direct remains unresolved; unverified Airbnb entries are disabled rather than guessed.
• An earlier Livadia mapping was incorrect and later replaced; use v1.6.5 or later for that correction.
• Child-age handling and like-for-like taxes, meals, cancellation terms, and room capacity need explicit validation.
• The September audit is a dated diagnostic mode, not proof of a continuously scheduled service.
• TODO: audit results, current aggregate coverage, issue owners, and resolution dates.

Source: Improve Andros rate checker.

Reduce manual finance checks by comparing each booking with its Notion income entry and showing the reviewer only bookings with no matching entry. Administrators see the complete data and possible matches; Nina reviews missing entries and confirms completed work.

Built for Explore Andros’s own booking sources, cash reports and review rules. The platform has separate admin and reviewer access.

• Accommodation: Rentlio reservations reconciled with Notion income entries for June–September 2026; searchable selection of one or several listings, custom From/To ranges across months, and status filters; excluded listings remain outside review.
• Car Rental: June–September 2026 GoCars export checked against Notion car-rental records, with month filters and evidence for administrators.
• Review queue: missing entries only for Nina; one-click confirmation; green resolved status; resolved bookings hidden by default or placed at the bottom.
• Admin review: Unresolved, Resolved, High priority and All filters; manually starred urgent bookings appear in High priority while unresolved. complete reservation view, possible and shared matches, Notion evidence links and available Drive invoice links.
• Pages: Accommodation admin · Accommodation reviewer · Car Rental · Activities & Transfers. Each page checks the signed-in account’s permissions.

• Check Notion first using guest/reservation name, amount and date, scoped to the relevant listing or service.
• Allow entries from 14 days before arrival/pickup through 14 days after departure/return.
• A different name can match by exact amount and nearby date. Shared or ambiguous entries stay for admin review instead of being automatically confirmed.
• Car-rental vehicle tags support matching; equal amounts with a different vehicle tag require admin review. Named split payments may match when their sum equals the reservation amount.
• Cash bookings do not receive a missing-invoice flag under the current review policy. Finding an entry confirms its presence; it does not by itself verify full payment or invoice compliance.
• Possible grouped accommodation bookings require supporting evidence beyond identical dates. Group amounts can be compared with a lead guest/company invoice in the myDATA review.
• Saved reviewer confirmations have an audit history and can be undone.

• Rentlio: reservation data and metadata for accommodation.
• Notion: connected income databases are the primary evidence for missing-entry review; Drive links indicate recorded invoice evidence.
• GoCars: manual reservation export imported and scanned on 10 October 2026. Automatic historical booking access is not connected.
• FareHarbor: booking API access is pending; the activities and transfers tab is not yet populated.
• AADE myDATA: secondary accommodation invoice checks use the relevant business VAT and invoice series. The reviewer’s missing-entry queue is based on Notion.
• Imported scan results are snapshots. Refreshing the review list does not fetch new GoCars reservations or re-query Notion.
• Account credentials and API keys are kept out of this directory. Each tool retains its own login.

Next steps: verify GoCars historical API access; populate activities and transfers after FareHarbor access is available; improve matching from reviewed examples; make source refreshes easier.

• 2026-10-10: imported and reconciled the June–September GoCars export; published car-rental admin and reviewer queues with saved one-click resolutions.
• 2026-10-11: Added cross-month date ranges, searchable listing selection and priority review filters. added Finance Review to the Systems Hub with its live link, workflows, rules and integration limitations.

Keep property maintenance reports, responsibility and repair history together so issues raised by the team can be followed through to closure.

Fit Explore Andros’s property list and bilingual team workflow, with direct WhatsApp reporting and private issue records. The broader knowledge-base/intranet idea provides context; the implemented tool documented here is the maintenance tracker. TODO: formal build-versus-buy assessment and maintenance budget.

Administrators and team members reporting, assigning and following up property issues. Approved WhatsApp senders can submit reports through the reporting channel. TODO: confirm the current roster and named product/technical owners.

Open Property Maintenance. The live intranet includes property task views and ticket records. Source chat: Knowledge Base. TODO: stable deep links, source repository URL and separate test environment.

Live team pilot on the custom intranet domain. The build history confirms working text-to-ticket WhatsApp intake, task filters and persistent login. The initial property catalog contains 34 titles; this is an onboarding snapshot, not a current inventory audit. Documentation added on 2026-10-13. Current product version: TODO.

Property-specific tickets; assignment, timestamps, notes and private photos; Open, Closed and All views; High, Normal and Low priority filters with counts; visible priority/status labels; bilingual interface; persistent team login; approved-sender WhatsApp report intake and duplicate-message protection.

Confirm captioned-photo reporting end to end, validate property names against Rentlio, and check live rejection of unknown properties/unregistered senders. Sender acknowledgments and correction replies are planned. Daily open-ticket digest exists but was last documented paused; verify readiness and template approval before enabling it. TODO: owners, target dates and acceptance evidence.

PHP application on SiteGround, MySQL records and private server photo storage. YCloud receives WhatsApp Business reports through a signed webhook; a Cloudflare Worker relay queues eligible events in private KV, and a SiteGround collector pulls them every ten minutes. Rentlio is a proposed catalog-validation source, not a confirmed live integration. No shared backend with Guest Space or Housekeeping is established.

SiteGround hosting/database, staff accounts and permissions, maintained property names/aliases, approved reporter mapping, YCloud/WhatsApp Business connection, relay and scheduled collector. Secrets and private uploads stay outside the public web root. TODO: named recovery owner and routine restore-test evidence.

• Open tasks are the default; status tabs run Open → Closed → All. Priority and status filters preserve each other’s selection.
• Report format: Anemomiloi problem description #report. Use the full property name or a unique leading name, then the issue. No dash is required; older dash/colon formats remain supported.
• The final word must be #report. Ordinary messages are ignored; ambiguous property names are rejected rather than guessed.
• Only approved active senders may report. Unique inbound message IDs prevent duplicate tickets.
• Reporting uses one-to-one messages, not WhatsApp group scanning. A photo needs its caption in the same message.
• Tickets can take up to ten minutes to arrive. Assignment remains open unless an explicit rule assigns it.
• Login is renewed with use and was configured for up to one year of inactivity; explicit Sign out removes the saved session.

• 2026-09-18: Live WhatsApp text-report test created a ticket; duplicate delivery was handled without another ticket.
• 2026-09-20: Daily digest documented as paused pending real-ticket readiness.
• 2026-10-02: Published open-first task views, priority filters, simpler space-separated WhatsApp reports and persistent login.
• 2026-10-13: Added Property Maintenance to the Systems Hub, with its live launch card and documentation.

WhatsApp intake is periodic, not instant. The source documentation still calls for a real captioned-photo test and additional rejection-path checks. Automatic acknowledgments are not implemented. Digest status and broader business-verification tasks need reconfirmation. Deployment-specific backups are recorded, but routine backup coverage and tested restores remain TODO. This page does not expose account passwords, private contact numbers or operational tokens.

• Keep reports simple: property name, issue and a final #report marker.
• Use a signed relay and scheduled pull because direct webhook delivery encountered SiteGround’s incoming bot challenge.
• Use ten-minute collection to stay within the documented relay allowance.
• Default to open work and retain status/priority filters to focus follow-up.
• Keep ticket photos private and preserve team sign-in across browser restarts.

Turn property bookings into consistent owner reports, with clear payment classifications, deductions and net-income allocation. Reduce repeated manual preparation while retaining review of uncertain payments.

Reuse the report process already reviewed for Explore Andros properties, connect existing Rentlio and myDATA sources, and preserve editable Excel formulas. TODO: documented build-versus-buy cost comparison and maintenance budget.

Explore Andros staff preparing and reviewing owner settlements. Owners receive exported reports; a separate owner self-service role is not confirmed. Product and technical owners: TODO.

Open Owner Reports. Source chat linked above. Separate test URL, source repository and issue tracker: TODO.

Live at the custom domain as of 2026-10-20. Account login and the existing ChatGPT sign-in both remain required. The live property selector was verified with 34 eligible properties. Report exports were checked against the previously reviewed workbooks. Product release version: TODO.

Property and reporting-period selection; new reports imported from Rentlio; saved report review; myDATA invoice candidates; editable Official / Offline payment splits; unresolved amounts retained for review; formula-based Excel export; larger booking details; authenticated report and export access.

Resolve remaining payment and commission questions in individual reports. Confirm whether account login should replace or continue alongside ChatGPT sign-in. TODO: broader per-property accounting policies, reporting roles, operating ownership and recovery plan. These are follow-up items, not completed features.

Rentlio supplies eligible properties and reservations; myDATA supplies invoice candidates. Source work also used linked invoice evidence from finance records. Credentials are held on the server. A continuously synchronized Finance Review integration is not established. Exact storage and refresh schedule: TODO.

Configured Rentlio and myDATA access, correct property exclusions, evidence for payment classification, approved property-specific calculation settings, working account/ChatGPT access and custom-domain routing. TODO: backup schedule and restore verification.

The reviewed reports calculate 70% owner / 30% Explore Andros on net income, after applicable residence tax, embedded VAT and OTA commission. The reviewed €8-per-night and 13% inputs are report settings, not a verified universal rule for every property. Do not treat an absent invoice match as proof of cash payment; amount-only matches are not confirmed identity matches. Preserve uncertain amounts in Bookings for review and avoid double-counting tax on split payments. Exclude Explore Andros Properties (umbrella account), Chora Sea Nest, Cycladic Getaway and Celestial Villa from report imports/exports.

2026-10-19: built the private reporting platform, live Rentlio/myDATA imports, editable payment splits and Excel exports matching reviewed reports. 2026-10-20: enabled 34 eligible properties, fixed the live selector, enlarged booking details and published report.exploreandros.gr with account login plus the existing ChatGPT restriction. 2026-10-20: added to this hub.

Some payments and commission references still need human review. Invoice status and payment method are different facts. Eligibility in the property picker does not establish that every property shares the same tax or commercial agreement. The additional ChatGPT access restriction is still active. Named recovery owners, current software version and restore evidence remain TODO.

Calculate the agreed share on net income; keep uncertain classifications visible; protect reports and Excel downloads with login; enforce the same property exclusions throughout the workflow. Preserve the existing ChatGPT restriction until a change is approved.

Keep Explore Andros’s agency relationships and 2027 accommodation offers organized: partner contacts, past feedback, communication history, follow-ups and pricing documents in one internal workspace.

Combine the company’s own property/rate information, agency context and branded offers in one workflow. The user explicitly separated the internal relationship workspace from the agency-facing PDF. TODO: formal alternatives, cost and maintenance assessment.

Explore Andros team members managing agency relationships. Agencies receive tailored PDF offers; the internal workspace is not the agency-facing presentation. Named product/technical owners: TODO.

Open B2B Partnerships. Source chat linked above. Separate test URL, source repository and issue tracker: TODO.

Private hosted internal workspace created on 2026-10-14. Agency profiles, contacts, follow-ups, feedback, communication logs and pricing documents are implemented. Records currently save only in the browser, with backup export. Product release version: TODO.

Agency profiles and contact details; follow-up tracking; previous-season feedback; communication logs; pricing-document organization; browser-local persistence and backup export. Branded partner PDFs include accommodation periods, room bedding/capacity, optional services and booking/cancellation terms.

Populate and review the full 2027 agency roster, 2026 feedback and communication history. Resolve the overlapping May rates and ambiguous cancellation boundaries before finalizing offers. Shared server-side storage, permissions and cross-device synchronization are future needs, not confirmed implementations. Owners and deadlines: TODO.

The uploaded 2027 Anemomiloi rate PDF and user-provided agency information are source inputs. The hosted workspace uses browser-local storage and exported backups. Branding and hotel imagery support the PDF offers. No live CRM, email, Rentlio or shared database connection is confirmed.

The same browser/storage for existing records, exported backups, approved rate tables, agency contacts and confirmed policies. Source pricing documents and offer PDFs must remain accessible. TODO: ownership for data entry, storage migration and retention.

Keep internal agency records separate from the PDF sent to a partner. Present mandatory environmental tax separately from optional extras. The latest Stap Reizen offer uses the main hotel photo and partner branding. The €50 / €80 private-transfer prices apply specifically to Andros port → Anemomiloi Andros Hotel for 1–4 / 5–8 guests; transfers to or from other Andros locations are priced on request. Do not silently resolve overlapping rate dates or cancellation-policy boundaries.

2026-10-14: created the private 2027 partner preview, then converted the website into an internal B2B workspace with browser-local records and backup export; refined agency PDFs and policies. 2026-10-15: clarified transfers to/from any Andros location and limited the listed port-transfer prices to Anemomiloi Andros Hotel. 2026-10-20: added to this hub.

Records are browser-local: shared team editing and cross-device synchronization are not confirmed, and clearing browser data can remove unexported records. The source work flagged overlapping 1–3 May rates, the exact 21-day cancellation boundary and the 60–90-day group deadline for clarification. A hosted URL does not imply centrally saved agency records.

Use the website for internal B2B organization and the PDF for agency presentation. Keep complete rate tables practical and branded; distinguish optional services from mandatory tax; retain unresolved commercial terms as open decisions rather than inventing answers.