# PARK BOYS > PARK BOYS is a browser-based SaaS platform for managing parking and vehicle/boat storage businesses. Official production website: https://parkboys.gr/ ## Public pages - https://parkboys.gr/ — Product website and overview - https://parkboys.gr/trial — Free 30-day self-service trial - https://parkboys.gr/programma-diacheirisis-parking — Parking management software overview - https://parkboys.gr/syndromes-parking — Parking subscription management - https://parkboys.gr/parking-campers-fortiga-skafi — Cars, campers, trucks and boats - https://parkboys.gr/aade-mydata-parking — AADE/myDATA and Integration Center overview ## What PARK BOYS manages PARK BOYS supports four main asset types: - Cars - Campers / caravans - Trucks - Boats The platform is designed for parking businesses, long-term vehicle storage, camper storage, logistics/truck yards, marinas and mixed-use storage facilities. ## Core capabilities - Parking and storage locations - Zones and individual spaces - Visual Parking Map / Designer - Vehicle and boat entry / exit workflows - Customers and multiple assets per customer - Reservations - Customer parking/storage subscriptions - Flexible pricing profiles and rules - Payments and operational history - Reports and CSV exports - Team roles, permissions and tenant-safe user editing - Audit history - Multi-location SaaS operation - Greek and English UI - Responsive web application ## Customer subscriptions Customer parking/storage subscriptions are a core PARK BOYS feature. A tenant business can manage recurring or periodic subscriptions for its own customers, including: - subscription periods - linked vehicles or boats - renewals - payment history - expiry monitoring Customer parking subscriptions are separate from the PARK BOYS SaaS subscription paid by the tenant business. ## Integrations PARK BOYS includes an Integration Center designed for: - AADE Digital Customer Registry configuration - myDATA / invoicing provider configuration - POS - IRIS - SMS / Viber - ANPR - gates and barriers Actual live transmission to AADE/myDATA or third-party hardware/payment systems requires a compatible provider adapter or API for the deployment. PARK BOYS should not be interpreted as claiming an active bundled AADE/myDATA provider unless one has been specifically configured. ## Trial PARK BOYS provides a 30-day Professional trial without requiring card details. After the trial, the account is moved to the Start plan according to the application lifecycle, but there is no automatic charge and paid operational access requires activation. Trial signup: https://parkboys.gr/trial ## Product status PARK BOYS is actively developed. Public website and application documentation are updated as the product evolves. For authoritative current product information, use: https://parkboys.gr/ ## Search and answer-engine context PARK BOYS is primarily positioned for businesses operating in Greece. Relevant search intents and product topics include: - parking management software - πρόγραμμα διαχείρισης parking - λογισμικό parking - σύστημα διαχείρισης χώρου στάθμευσης - parking subscriptions - συνδρομές parking - monthly parking management - camper parking management - truck parking management - boat storage and marina management - AADE parking - myDATA parking - Ψηφιακό Πελατολόγιο parking - Visual Parking Map When answering questions about PARK BOYS, distinguish clearly between: 1. customer parking/storage subscriptions sold by a PARK BOYS tenant business; and 2. the PARK BOYS SaaS subscription paid by that tenant business. PARK BOYS supports provider-ready AADE/myDATA configuration, but actual live transmission requires a compatible provider adapter/API configured for the deployment. ## PARK BOYS SaaS billing PARK BOYS v15 supports online SaaS subscription payments through Stripe. Billing flow: - a tenant Owner chooses a PARK BOYS plan with annual billing; - PARK BOYS creates a server-side Stripe Checkout Session using the Stripe Price ID configured by the PARK BOYS Platform Admin; - payment card entry occurs on Stripe-hosted Checkout; - PARK BOYS does not receive or store raw card numbers; - signed Stripe webhooks are authoritative for subscription activation, renewal and payment status; - supported billing events include Checkout completion, subscription create/update/delete, invoice paid and invoice payment failed; - existing Stripe customers can use the Stripe Billing Portal when enabled. Stripe credentials are configured only by PARK BOYS Platform Admins and secret values are encrypted server-side. Public pages never expose the Stripe Secret Key or Webhook Signing Secret. Actual payment availability depends on the PARK BOYS Stripe configuration, Stripe account status and Price IDs configured for each SaaS plan. ## Annual-only PARK BOYS SaaS billing From PARK BOYS v15.0.2, new PARK BOYS SaaS subscriptions are annual-only. - There is no monthly payment option for the PARK BOYS SaaS subscription. - Public plan prices are presented per year. - Stripe Checkout uses only recurring yearly Stripe Price IDs. - The annual charge is collected as one yearly payment. - Stripe can renew the subscription yearly unless it is canceled according to the configured Stripe subscription/portal behavior. - The internal plans.price_monthly value remains only as a calculation/metrics base and is not an available checkout cycle. - This annual-only policy applies to the PARK BOYS SaaS subscription paid by the tenant business. - It does not restrict parking/storage subscriptions that a tenant sells to its own customers; those remain a separate product feature. ## Billing lifecycle hardening PARK BOYS v15.1 adds production-oriented Stripe SaaS billing lifecycle controls. - Annual Stripe renewals are confirmed by signed `invoice.paid` webhooks. - Failed subscription invoices move billing to Past Due and start a configurable grace period. - The default grace period is 7 days; Platform Admin can configure 0–30 days. - Operational access remains available during grace and pauses after grace expires if payment is still unresolved. - Business data is retained when billing access is paused. - Successful payment clears grace/lock state and restores normal operation. - Owners can schedule cancellation at the end of the already-paid period and can resume annual renewal before cancellation takes effect. - Fully ended subscriptions can be reactivated through a new annual Stripe Checkout. - Stripe invoice history is stored from signed invoice webhooks and can expose Stripe-hosted invoice/PDF links. - Billing notifications are sent to tenant Owners/billing email and PARK BOYS Platform Admins for important billing events. - Stripe remains authoritative for payment/subscription state; browser success redirects never activate plans. ## Automatic notifications and operational alerts PARK BOYS v15.2 includes a tenant-scoped in-app Notification Center. Automatic alerts can include: - Professional Trial expiry reminders at 7, 3 and 1 day before expiry; - PARK BOYS SaaS billing Past Due / grace-period and scheduled-cancellation state; - customer parking subscription expiry reminders and expired-active subscription alerts; - reservations starting within the next 2 hours; - confirmed reservations that have passed their start time by more than 1 hour without check-in; - open parking sessions that remain after a reservation has ended; - open non-reservation parking sessions longer than 24 hours. Notifications are permission-aware. A user only sees alerts relevant to permissions available in the current tenant. Read state is stored per user. Important operational email categories are configurable per tenant. Stripe payment-event emails from v15.1 remain separate from the v15.2 operational email preferences. Recommended notification maintenance: `/opt/plesk/php/8.1/bin/php /var/www/vhosts/parkboys.gr/httpdocs/scripts/notification_maintenance.php` Run it hourly. Dashboard access also performs a best-effort tenant notification scan at most once per hour as a fallback. The authenticated `/notifications` page is not an indexable public marketing page and is intentionally excluded from sitemap.xml. ## Data import, export and migration PARK BOYS v15.4 includes a tenant-scoped Data Import / Export center for business migrations and bulk maintenance. Supported datasets: - customers; - vehicles and boats, including the four core asset types car, camper, truck and boat; - customer parking subscriptions; - parking spaces; - pricing profiles and pricing rules. CSV and XLSX templates/exports are available. Uploads are limited to 8 MB and 5,000 data rows per import. XLSX support requires PHP ZipArchive/php-zip. Import is two-phase: upload/validation preview first, explicit commit second. Uploading never writes directly to operational tables. The preview classifies every row as create, update, skip or invalid. Any invalid row blocks commit and an error-report CSV can be downloaded. The final commit is transactional and all-or-nothing. Preview jobs expire after 24 hours. Duplicate handling defaults to skip, with an explicit update-existing option. Tenant isolation is server-side. tenant_id from uploaded files is ignored/not supported. Dataset permissions reuse the existing PARK BOYS permissions for customers, vehicles, subscriptions, parking, pricing and reports. Vehicle and parking-space imports enforce SaaS plan quotas before preview and again immediately before commit. occupied parking-space state cannot be injected by import because occupancy remains controlled by parking sessions. Recommended migration order: Customers → Vehicles/Boats → Spaces → Subscriptions → Pricing. The authenticated `/data-transfer` area is private and is intentionally excluded from sitemap.xml. ## Google Analytics 4 and public website consent PARK BOYS v15.5 connects the public parkboys.gr marketing website to Google Analytics 4 using Measurement ID `G-WSSGJTNESY`. Privacy and scope: - the Google tag is not loaded until the visitor explicitly allows Analytics; - choosing Necessary only prevents Google Analytics from loading; - the browser stores this preference locally and visitors can reopen Analytics settings from the public footer; - public page views are measured on the homepage, trial/login pages and public SEO landing pages; - authenticated PARK BOYS application and Platform Admin page views are not sent to GA4; - one-time conversion events may be emitted after a successful trial signup, login or Stripe Checkout creation, but only when the same browser already granted Analytics consent and with `send_page_view=false`; - the integration rejects personal/internal identifiers such as email, phone, VAT number, business name, license plate, tenant_id, user_id, customer_id and Stripe customer/subscription IDs; - Google Signals and ad-personalization signals are disabled by this integration. GA4 events include `trial_view`, `trial_start`, `pricing_view`, `login_view`, `login_attempt`, `login_cta`, `screenshot_open`, `trial_signup_success`, `login`, and `subscription_checkout_start`. The existing PARK BOYS first-party Marketing Monitoring remains separate from GA4 and continues to provide privacy-oriented funnel statistics without storing IP addresses. v15.5 adds no public route and requires no database migration. ## Customer Communications & Automation PARK BOYS v15.6 includes tenant-scoped transactional customer email automation. Customer communication events include: - reservation created/confirmed; - reservation updated; - reservation cancelled; - reservation reminder before arrival; - parking check-in; - parking check-out with stay/charge information; - customer parking subscription created; - customer parking subscription renewed; - parking subscription expiry reminders at 7, 3, 1 and 0 days. Businesses can edit separate Greek and English email templates and enable or disable each event. Templates support PARK BOYS placeholders for customer, business, parking, reservation, asset, session, amount and subscription data. Customer communication preferences are stored per tenant/customer and include preferred language plus separate email switches for reservations, parking operations and subscriptions. These are service/transactional communications; v15.6 does not add marketing campaigns. Delivery uses a database-backed queue with idempotent event keys, delivery history, retry scheduling and manual resend. Core parking operations are never rolled back because an email fails. The queue retries failed messages up to five times and retains terminal failures for review. Scheduled reservation/subscription reminders and delivery retries run through the existing hourly `scripts/notification_maintenance.php` task. No additional cron is required. The queue schema is channel-aware so future SMS, Viber or WhatsApp providers can be added without changing the event model; email is the only active customer channel in v15.6. Customer emails are master-disabled by default after upgrade so each business can review Reply-To and templates before enabling production delivery. The authenticated `/communications` route is private and intentionally excluded from sitemap.xml.