PeachMe platform

One connected system, from court to control room.

PeachMe connects public journeys, venue operations, the on-court mobile experience, and machine connectivity. This overview separates each product surface while showing how they work together.

Each workspace is matched to the user’s role and assigned venues. Operational and personal data remains inside the authenticated portal.

Platform at a glance

Coverage
Court, venue, fleet, and back office
Product surfaces
Web platform, mobile app, and 4G module
Access model
Role- and venue-scoped
01

Web platform

Public journeys and daily operations in one browser-based platform.

The web platform combines customer-facing booking and commerce with the authenticated portal used to manage venues, fleets, partners, and platform settings.

Primary users: Customers, venue managers, operators, partners, and administrators

Explore the web platform

Start with the browser-based area that matters to you. Each section describes the capability without exposing private portal data.

01.01

Booking & venue operations

Coordinate the daily work around bookable machines, available court time, and venue teams.

Primary users: Venue managers and operators

01.01.01

Venue-scoped overview

Give each venue manager a focused view of assigned locations, machines, and the work that needs attention.

  • Assigned venues, contacts, and machine signals stay in one scope
  • Unresolved access or configuration issues remain visible
01.01.02

Sessions and bookings

Review upcoming sessions, booking status, handovers, returns, history, and operational exceptions.

  • Current sessions and historical bookings are separated for faster scanning
  • Exception and compensation workflows keep unusual cases traceable
01.01.03

Availability planning

Set recurring operating hours, block unavailable periods, and keep machine slots aligned with the venue.

  • Weekly availability and one-off closures can be managed together
  • Bookable capacity stays connected to the assigned machine and venue
01.01.04

Offers, trainers, and reports

Manage venue-specific offers, trainer access, trial activity, and performance reporting from one place.

  • Venue pricing and trainer access remain locally configurable
  • Trial and trainer-pilot reporting provide a shared operating view
01.02

Fleet & connectivity

Keep connected machines identifiable, serviceable, and ready for their next session.

Primary users: Operators and authorized technical teams

01.02.01

Machine inventory

Track every PeachMe machine by model, assignment, operating role, readiness, and current location.

  • A stable system identity follows each machine through its lifecycle
  • Assignment history keeps venue and city changes understandable
01.02.02

Health and usage

See operational state, recent activity, usage history, and the signals that help teams respond early.

  • Fleet summaries surface readiness, warnings, and recent use
  • Machine detail connects status, configuration, and usage context
01.02.03

Kits and deployments

Keep machines, batteries, chargers, remotes, and deployment bundles linked throughout the field lifecycle.

  • Compatible assets are assembled into traceable field bundles
  • Assignment, return, and deployment history stays attached
01.02.04

Connectivity and readiness

Coordinate SIM inventory, network status, intake checks, provisioning, and factory-readiness workflows.

  • SIM binding and data usage are visible without mixing device identities
  • Intake, provisioning, and validation create a controlled path to deployment
01.03

Training configuration & member records

Configure training content and manage the member records that support the on-court experience.

Primary users: Trainers, operators, and community teams

01.03.01

Practice library

Configure reusable training programs and model-aware drills for delivery through the mobile app.

  • Programs can combine reusable presets with custom court points
  • Machine-series limits keep speed and placement settings compatible
01.03.02

Member access

Manage community membership and control access to selected mobile modes and experiences.

  • Member status and role-aware experiences share one account foundation
  • Selected capabilities can be enabled without broad portal access
01.03.03

Training records

Keep session history, booking records, receipts, and usage context connected across the service.

  • Members can revisit their own booking and payment records
  • Operators retain the operational context needed to resolve exceptions
01.03.04

Feedback loop

Capture structured tester and partner feedback and link it to the relevant contact or machine context.

  • Feedback remains connected to the person and product context
  • Operators can review status and follow-up without a separate ticketing silo
01.04

Commerce & rentals

Run retail orders, short-term access, and longer rental journeys without splitting the operational record.

Primary users: Customers and commercial operators

01.04.01

Catalog and orders

Manage sellable products and SKUs, review the order queue, and follow fulfilment through delivery.

  • Product, SKU, stock, price, and publication state remain distinct
  • Order detail carries payment, shipment, tracking, and refund context
01.04.02

Rental lifecycle

Coordinate Practice Pass and longer rentals from reservation and payment through collection and return.

  • Short sessions and longer rentals follow purpose-built workflows
  • Every handover and return remains connected to the customer record
01.04.03

Offers and pricing

Maintain venue and rental offers with the rules, durations, and prices needed for each service.

  • Operator-wide and venue-specific offers can coexist
  • Eligibility, duration, and price stay explicit at booking time
01.04.04

Returns and settlement

Keep return condition, deposits, adjustments, and the final commercial state attached to the booking.

  • Return confirmation records condition and operational completion
  • Adjustments and compensation cases remain reviewable after payment
01.05

Community & partner network

Build a usable view of the people, organizations, and venues that grow the PeachMe network.

Primary users: Partner, community, and outreach teams

01.05.01

Organizations and venues

Organize partner companies, cities, individual venues, sports, environments, and deployment context.

  • Organizations and physical venues remain separate but connected
  • Each deployment unit has a clear sport and indoor or outdoor context
01.05.02

Contacts and relationship history

Keep people, roles, affiliations, notes, and partner-stage history connected without duplicating records.

  • Audience-specific profiles keep relevant relationship fields focused
  • Duplicate suggestions and merge tools protect a cleaner directory
01.05.03

Outreach preparation

Prepare audience-safe partner outreach, suppression checks, message records, and negotiation context.

  • Recipient readiness and suppression checks happen before outreach
  • Message and negotiation records are captured without automatic sending
01.05.04

Members and feedback

Support the community directory and route product interest, tester input, and partner feedback to operators.

  • Member and CRM contact context can be matched without merging their roles
  • Interest and feedback are routed to the teams that can follow up
01.06

Platform management & insights

Give authorized teams the controls and reporting needed to operate a growing platform responsibly.

Primary users: Superadmins and authorized operators

01.06.01

Roles and access

Separate superadmin, operator, venue-manager, and technical responsibilities with scoped access.

  • Portal roles expose only the workspaces needed for each responsibility
  • Venue access and selected features can be managed independently
01.06.02

Reporting and costs

Review utilization, trainer programs, operating costs, and other decision-ready platform summaries.

  • Usage views support fleet, venue, and program-level decisions
  • Recurring and one-off costs retain evidence and reporting dimensions
01.06.03

Communications and growth

Manage communications, referrals, vouchers, trial access, and selected customer-facing website content.

  • Communication records provide an auditable operational history
  • Referral, voucher, trial, and FAQ controls stay in dedicated workspaces
01.06.04

Settings and integrations

Maintain platform configuration, integration health, feature access, and restricted diagnostic tools.

  • Integrations and configuration are reviewed without crowding daily operations
  • Sensitive diagnostics remain restricted to the appropriate technical roles
02

Mobile app

The court companion for booking, training, and machine control.

The PeachMe mobile app guides members from finding a venue to completing a session. It keeps machine controls, training choices, bookings, and account records close at hand while adapting selected tools for linked venue managers.

Primary users: Members, players, trainers, and linked venue managers

02.01

Discover and book

Browse available venues, compare court and machine context, choose a time slot, and continue into payment.

  • Venue discovery supports city, distance, sport, and indoor or outdoor context
  • Booking keeps the selected machine, duration, price, and session time together
02.02

Scan and start a session

Use machine and session QR codes to open the right activation, claim a held booking, or resume active court usage.

  • Deep links and QR scans resolve directly to the relevant machine or booking
  • Interrupted sessions can reopen in the active-session experience
02.03

Guided training and live control

Connect over Bluetooth, choose a practice, and control supported machine actions from the phone or watch.

  • PeachMe, Pro, and Use modes balance guidance, precision, and fast court actions
  • Start, pause, stop, live state, and machine-aware settings stay close together
02.04

Practices and training modes

Run built-in drills, save custom practices, and adapt supported machines for tennis, padel, or supervised junior training.

  • Court-point editors and model limits keep custom programs compatible
  • Padel Mode, Kids Mode, calibration context, and auto-pause add focused safeguards
02.05

Bookings, wallet, and membership

Keep upcoming sessions, booking history, receipts, vouchers, referrals, and membership identity in one account.

  • Membership and booking QR codes support faster venue handovers
  • Apple or Google Wallet passes, notifications, and localized account settings stay optional
02.06

Rentals, shop, and venue-manager tools

Follow Practice Pass rentals and orders, while linked venue managers get a compact desk for on-site work.

  • Rental pickup, return, deposit state, orders, and customer records remain accessible
  • Managers can scan customers, create bookings, record cash, and take machines in or out of service
03

4G connectivity module

A cellular bridge between each machine and the PeachMe control plane.

The PeachMe 4G control board combines a GD32F303 controller with an ML307 modem to keep deployed machines connected independently of venue Wi-Fi. It links machine identity, live status, and authorized cloud commands through a dedicated cellular path.

Primary users: Fleet operators, deployment teams, and firmware engineers

03.01

Independent cellular connection

Use a managed SIM and mobile data connection to reach deployed machines where local Wi-Fi is unavailable or unsuitable.

  • The modem establishes the cellular data session and MQTT or diagnostic transport
  • Fast reconnect and staged modem recovery restore service after network interruption
03.02

Device identity and commissioning

Keep the machine asset, 4G control board, modem identity, and SIM relationship distinct but traceable.

  • A machine ID is written during commissioning and verified in persistent storage
  • Device and broker identities can be derived from board provisioning and modem IMEI
03.03

Heartbeats and live status

Publish the signals operators need to understand whether a machine is online, current, and ready for attention.

  • Heartbeat data can include firmware, sequence, signal quality, and reconnect context
  • Machine-status uplinks feed the fleet view without making the device the business-data source
03.04

Cloud-to-machine command bridge

Receive authorized device commands over the cellular transport and forward compatible machine frames to the main controller.

  • MQTT command topics keep machine and control-board identity in the delivery path
  • Forwarding and result counters help teams trace receipt, translation, and UART delivery

Go deeper

Overview first. Guidance when you need it.

Use Support for step-by-step help, or sign in to the portal if your PeachMe access is already active.

Privacy settings

Choose what PeachMe can load

We use essential cookies to keep language, sign-in, and cart flows working. Optional analytics, embedded maps, or third-party verification services stay off until you allow them here.

Read privacy policy