Skip to content
Who it’s for
Platform and distribution teams
What it helps with
The supplier dashboard: percentiles, not averages.
What to bring to the first discussion
  • Your brand, customers and preferred layout
  • The product data, integrations and booking workflow you need

This is an illustrative design. Your project scope determines the content, integrations and functionality that will be implemented.

Try the layout in your preferred palette.

Explore the design using sample content. Change the palette to compare how the layout could suit your brand.

Admin / Platform

Supplier health

Last 30 days

Connected

7

p95 search

1.9 s

−240 ms

Book success

98.4%

+0.3pt

Shed today

1

+1

Supplierp50p95p99AnsweredBudget
sup_alpha410ms980ms1.4s99.2%OK
sup_beta780ms1.9s3.1s97.4%OK
sup_gamma2.1s5.8s6.0s61.0%Shed
sup_delta520ms1.2s2.0s98.8%OK

Searches answered in time

Error taxonomy

supplier_timeout61%
rate_no_longer_available22%
price_changed11%
supplier_error6%

Why it is laid out this way

A supplier's average response time hides the tail that actually loses you bookings. Pulse reports p50, p95 and p99, the share of searches a supplier missed entirely, and the error budget it has left before it is shed from the fan-out.

Built for

Platform and distribution teams

What the template decides

  • Response-time percentiles per supplier, not averages
  • Share of searches returned in time
  • Booking success rate and error taxonomy
  • Error budget and automatic shedding state
  • Revenue and margin contribution per supplier

Your next step

Discuss Pulse for your brand.

Mention this design in your enquiry and tell us about your audience, content and booking requirements. We’ll review the layout, available modules and development scope together.