Marketplace platform

One platform. Three connected workspaces.

A customer app for discovery and booking, a provider workspace for service operations, and an admin console for marketplace oversight.

Capabilities and their current status.

These statuses describe the available evidence and integration scope. Demonstrated does not establish production readiness.

  • Demonstrated

    Locations and session times

    Customers can review a provider location and select a date and session time.

  • Configured per service

    Branches and working times

    Provider branches and working times are set for the service.

  • Configured per service

    At-home service coverage

    At-home fulfilment and coverage zones are set per service.

  • Demonstrated

    Address and coverage checks

    At-home bookings require a service address and check it against coverage zones. Without configured zones, every address is treated as covered.

  • Demonstrated

    Programs and session capacity

    Programs show upcoming sessions and inclusions. Recorded tests demonstrate capacity limits and capacity released after cancellation.

  • Demonstrated

    Session packages and attendance

    Recorded journeys demonstrate package purchase, credits, redemption and provider-recorded attendance.

  • Partly integrated

    Provider assignment and matching

    Assignment and zone matching are not connected end to end to booking creation. They are not available as an automatic booking handoff.

  • Requires engineering

    ASAP dispatch and live tracking

    Current bookings use scheduled slots. Immediate dispatch and live tracking would require engineering.

Memberships and included sessions.

Implemented · production use not established

Customers book included sessions and see their remaining session allowances. Eligible customers can request cancellation for review, and operators process policy-based cancellations and refunds for unused sessions.

This scope does not establish recurring-subscription or renewal readiness. Production use of the membership lifecycle has not been established.

Customer → Provider → Admin: follow one booking record.

An illustrative handoff explains how a booking connects the three roles. The provider and admin captures below show the same demo booking; the customer demonstration is a separate run.

  1. Customer app: the customer chooses a service and a scheduled time. These choices provide the service and schedule for the booking record.
  2. Provider workspace: the provider reviews the booking’s service, time and status to understand the work.
  3. Admin console: the marketplace team reviews that same booking’s service, schedule, status and recorded payment information.

Booking status and payment state are separate. Payment is not recorded in this operational example; it does not demonstrate provider acceptance or completed delivery.

Revisit a doorbell and installation cart.

The existing cart already holds the linked installation and booked time. The demo reconfirms that time and selects an existing covered address; it stops before payment.

  1. Review product and linked installation
  2. Revisit existing cart; no items added again
  3. Reconfirm existing 4 PM selection
  4. Select existing covered Home address; stop before payment
Doorbell existing-cart revisit · 40 s · demo data · linked installation and existing 4 PM time reconfirmed; covered Home address selected · includes a still and slowed sections · stops before payment · AI-generated catalog illustrations. Open full size ↗

Video description: A customer reviews an AED 699 doorbell with linked AED 149 installation, then revisits an existing cart without adding items again. The installation and its booked time are already in the cart; the existing 4 PM selection is reconfirmed. Product and installation appear together at AED 890.40 including VAT. The cart first says Address still needed, then the existing Home address is selected and shown in coverage. This demo stops before payment. It includes a still, slowed sections and AI-generated catalog illustrations.

Products and services, easy to find.

Search the catalog and review the details before choosing what to buy or book.

Catalog search results for AC with Service and Supply item labels.
Home Services catalog search · Demo data · In testing, not released · recorded 30 Oct 2026. Open full size ↗
Supply item detail with a filter-maintenance illustration.
Supply item detail · Demo data · In testing, not released · AI-generated illustration · fictional demo catalog. Open full size ↗

A distinct view for each operational role.

Providers see their bookings. Marketplace operators review the service, schedule, status and recorded payment information. These console examples show a separate operational run.

Provider booking detail with service name, schedule and a warning that payment is not recorded.
Provider workspace view of the same booking as the admin overview · Demo data · payment not recorded · synthetic booking · customer details masked. Open full size ↗
Admin booking overview with the service name, scheduled time, booking status and payment marked Not recorded.
Admin console booking overview · Demo data · payment not recorded · synthetic booking · identifiers masked. Open full size ↗

A booking conversation is also in testing.

A rules-based assistant can offer service choices and prepare a cart for review. It is not yet released to customers; the current demonstration stops before payment.

Booking assistant offering swimming classes at School Area.
Swimming-class choices · separate class catalog · Demo data · In testing, not released · no booking or payment · local demo. Open full size ↗

Your next step

Bring products, installation and operations together.

Discuss your catalog, service locations and the customer journey your marketplace needs.

Request a demo