JuanClick 1.60.0 — Clearer counters and shared shop scheduling Release date: 8 November 2026 (Asia/Manila) App: https://juanclick.ph/businesses.php Visits: https://juanclick.ph/shop-visits.php MyApps: https://bizcore360.net/myapps/#juanclick VISUAL FIXES The cashier counter now uses a single compact branch heading and shorter cart summary. Products are visible on the first phone screen; Review & pay opens the complete item review and payment controls. Secondary tools and optional billing instructions are grouped under More. Owner figures appear before secondary money details and branch-management lists. Filters and business groups expand when needed. Keyboard focus, touch targets, narrow screens, landscape, zoom/reflow and persistent viewport messages were checked. SHARED SHOP OPERATIONS Owners can set each service's duration, with the branch default retained when no override exists. Overnight hours are supported: the opening weekday owns the shift past midnight. Optional staffing rosters restrict service bookings to scheduled availability; cross-branch travel buffers prevent overlapping or too-close assignments. Roster edits cannot silently invalidate existing reservations. Revoked staff rosters can still be cancelled. Seating branches can name physical tables and set seats. Accepted reservations receive a fitting available table, with server checks against double booking. Existing pooled seating stays available when no tables are configured. These are shared capabilities selected by branch workflow, not hardcoded to barbershops or cafes; all current and future templates use the same foundation. Existing shop identity, reservations, sales and staff history remain intact. These are table assignments, not a graphical floor-plan editor. Open a branch from My Businesses, then Services & schedules. Owners configure operations; staff can view their own relevant roster. Changed tools include accessible sample Show me guides with captions, pause, replay and close. Demos do not change real records. VISIT ALERTS An explicit device preference now connects visit updates to the existing background Web Push system. Visit consent is independent of planner/message consent. Notifications use generic text without customer, service or shop details on the lock screen. Stale events, inactive owners/accounts, revoked sessions and duplicate deliveries are checked before sending; failed deliveries retry within bounded expiry. Notification taps open My visits. The notification sender runs outside cashier transactions. HOSTING DEPENDENCY: the live sender has no successful automatic run. Prior hosting setup records state that Crontab Access is disabled. Until hosting enables and schedules the existing worker, enabling background alerts correctly reports sender unavailable. Closed-app delivery is NOT advertised as working. Keep My visits open for in-page updates. SMS remains pending by user choice; no paid provider was added. Browser permission, operating-system settings and service delivery can delay alerts even once the sender is healthy. iPhone web push requires a supported Home Screen installation. INSTALLATION AND UPDATES This remains the existing installable web app; no separate native installer is created. Use the JuanClick Install/Home Screen guide. Existing app identity and login/session protections are preserved. Quick version checks offer Update or Later on safe overview pages and defer while editing or running demos; counter payments are not interrupted. Internet is required. VERIFICATION AND LIMITS Backend checks use isolated synthetic accounts and schema fixtures. Tests cover overnight boundaries, service durations, roster/travel conflicts, table capacity, roles, full account deletion with operation and alert records, consent, stale notification suppression, retries, receipt authentication and transactional migration rollback/concurrent edits. Browser checks cover owner, cashier, operations, visits and sample guides. Original screenshots and JSON reports are preserved with the release. Browser notification testing used a simulated display transport where the automated browser denied native notification permission. This tests service-worker routing and receipts, not actual Web Push delivery. The portable NVDA test was stopped at the user's request after audible startup; manual screen-reader acceptance is unfinished. Physical Android acceptance is recorded separately if the connected phone becomes available; desktop viewport screenshots are never presented as physical-phone evidence. Live publication verification covers source hashes, schema integrity, public/authenticated-route boundaries, current version feed and MyApps assets. Unrelated portfolio sites are unchanged. This release does not claim a retrofit of all historical JuanClick features or unrelated programs.