White-label foundation
Your catalog. Your service model.
Start with a reusable marketplace foundation, then define the brand, terminology and operating rules your business needs.
One example configuration, in the actual app.
These screens show a single local demonstration catalog: services and supply items in search, then one product detail. They are not a comparison of different brands or proof of a deployed customer marketplace.
Be clear about configuration and engineering.
Brand, catalog and service rules are scoped together. Requirements beyond the existing configuration are treated as engineering work.
| Area | Existing configuration | Engineering boundary |
|---|---|---|
| Brand and catalog | Supported themes, content and vertical terminology. | New layouts and core workflow changes may require engineering. |
| Service delivery | Provider branches, working times, at-home fulfilment and coverage zones are configured per service. | ASAP dispatch and live tracking require engineering; bookings currently use scheduled slots. |
| Provider assignment | Service and coverage configuration does not establish automatic assignment. | Assignment and zone matching are partly integrated. Connecting them end to end needs further integration work. |
Your next step
Build your marketplace around your brand.
Bring your catalog, audience and operating rules. We’ll scope existing configuration and any additional engineering.
Discuss white-label