How our ranking works

As of: 2 September 2026

way.food sorts search results and overviews by fixed main parameters. Here we explain what they are, how much each one weighs and what does not influence the ranking. The full version is Annex 1 to our provider terms.

Search results

The following main parameters are listed in descending importance: what sits higher up weighs more than everything below it. A lower-ranked parameter cannot make up for a higher-ranked one. No other factors play a role in the ordering.

  1. Fit. Providers with a concretely bookable package that matches your guest count and budget always come before providers who could only make you an individual offer. Concretely bookable means: guest count, budget range and the essential features match without any negotiation. This parameter takes precedence over all others. A higher subscription, a better score or better reviews never overtake a matching, bookable offer.
  2. Subscription tier. Premium Plus comes before Premium, Premium before Basic, Basic before Free. The subscription is a paid service and influences placement more than all following parameters combined. Within the same fit group a provider on a higher tier always comes before a provider on a lower tier, so a Free provider does not move ahead of a Basic provider through better reviews. Providers without a paid subscription are fully listed and bookable. The paid tiers buy the placement within the group, not the listing and not precedence over a matching offer. If a provider is on a free trial, we place them like the respective tier.
  3. Match with optional search filters, such as the preparation method. Matching providers move up, but only within a subscription tier. A filter never excludes anyone and changes neither the order of the tiers nor the precedence of fit.
  4. Internal quality and reliability score. Every provider starts neutral and the score moves within a fixed range. It rises through successfully completed and confirmed bookings, good published reviews and quick replies to enquiries. It falls through no replies, provider cancellations, very poor reviews, rule violations after a warning and declined requests, where the reason for declining is weighted differently. A plausible decline because the venue is outside the service area has no negative effect. We may correct the score in individual cases, for instance to fix errors. Every correction is logged, cannot be bought and does not change the order of the subscription tiers.
  5. Average of published customer reviews. What counts is the average star rating, not the number of reviews. A better average helps within the order that points 1 to 4 have already set.
  6. Deposit rate. The final tie-breaker: it only applies when providers are level on all points above. Then a lower deposit rate sits slightly higher. In practice it hardly matters.

Overviews without a search

The home page, the map and provider lists show providers without a specific search. There we group by subscription tier, Premium Plus before Premium before Basic before Free, and shuffle randomly within a group. Quality, reviews or behaviour play no role within these groups. City pages sort by subscription tier and then by distance. For “similar providers” we first separate providers with a paid subscription from Free providers and then consider category, country, distance and the specific tier.

Concierge matching

When we match an enquiry personally, the only algorithmic parameter is the distance to the venue. A member of staff makes the selection, not the algorithm. The subscription tier may be shown to that person but does not sort there.

What does not influence the ranking

  • The only paid influence is the subscription tier. There is no paid single placement, no “featured” or “sponsored” programme and no editorial preference. Nobody can buy a specific position or have one fixed manually.
  • Click counts, profile views, conversion rates, the number of reviews and the price level are not ranking factors in the search results.
  • In the search results, distance only decides whether a provider is eligible for your venue at all, not the order of the providers who are eligible.
  • There are no affiliate or referral programmes that improve the ranking. We do not favour providers affiliated with us.

Why this order

What you can actually book comes first: bookability and fit. Then comes the subscription placement, through which we finance the platform and which we disclose transparently here; it deliberately only works between offers that are comparable after the fit check. Only then do quality and reliability from real booking activity decide, followed by the review average and, at the very end, the deposit rate.

How you influence the results

Your guest count, your budget and the optional search filters determine which offers count as a match. Providers improve their position through concretely bookable, matching offers, through the choice of their subscription tier and through reliable handling, quick replies and good service.

way.food Logo
Book catering Discover Open bookings FAQ Info for Providers Account
Envelope 1 Envelope 2 Envelope 3 Phone
Follow us
Subscribe to Newsletter
Register Book catering Log in

home

Discover & book

  • Book catering
  • Discover bookable packages
  • Find providers on the map
  • Open bookings

For providers

  • Sign up free
  • Info for Providers
  • Prices
  • About us
  • Blog
  • FAQ
  • Log in
  • Register
English Deutsch Nederlands
Imprint | Privacy Policy |
Terms and Conditions | Cookies |
Ranking
© 2026 way.food
unlimited.studio Website

We use cookies

We use cookies to personalise content and ads and to analyse traffic on our website. We also share information about your use with our advertising and analytics partners. Your consent is voluntary and can be withdrawn at any time.

Learn more in our Cookie settings and in our privacy policy.

Customize
  • wayfood_cookie_consent

    1 year

    Used to store the user's cookie consent preferences.

  • wayfood_session

    2 hours

    Used to identify the user's browsing session.

  • XSRF-TOKEN

    2 hours

    Used to secure both the user and our website against cross-site request forgery attacks.

  • cf_clearance

    30 minutes

    Cloudflare. Remembers that the bot check was passed so the page does not check again on every request.

  • preferred_locale

    1 year

    Remembers the selected language.

  • remember_web_*

    5 years

    Keeps you signed in when "Remember me" was selected.

  • locationConsent

    1 year

    Remembers in the browser's local storage whether you agreed to the location request for the map search.

  • mapbox.eventData.uuid

    1 year

    Anonymously counts map loads so our map provider can bill them. Without the map there is no food truck search.

  • rc::a

    1 year

    Google reCAPTCHA. Detects automated access and protects the forms from abuse.

  • rc::b

    Session

    Google reCAPTCHA. Detects automated access and protects the forms from abuse.

  • rc::c

    Session

    Google reCAPTCHA. Detects automated access and protects the forms from abuse.

  • _GRECAPTCHA

    6 months

    Google reCAPTCHA. Detects automated access and protects the forms from abuse.

More details
  • _gcl_au

    3 months

    Google Ads. Measures which ad led to a visit.

  • _gcl_ls

    3 months

    Google Ads. Stores the same measurement in the browser's local storage.

  • IDE

    1 year

    Google Ads. Recognises the browser on ad placements to measure the effectiveness of our ads and to personalise advertising.

  • test_cookie

    15 minutes

    Google Ads. Checks for a few minutes whether the browser accepts cookies.

  • _fbp

    3 months

    Meta Pixel. Distinguishes visitors to measure the effectiveness of our ads on Meta.

  • _fbc

    3 months

    Meta Pixel. Stores the identifier of the ad that led to the visit.

  • wf_ads_attribution

    3 months

    Stores the Google Ads click identifier (gclid) so a later booking can be attributed to the ad that led to the visit.

More details
  • _ga

    2 years

    Main cookie used by Google Analytics, enables a service to distinguish one visitor from another.

  • _ga_5G4EQB1M2H

    2 years

    Used by Google Analytics to persist session state.

  • _hjSessionUser_*

    1 year

    Hotjar. Recognises a browser across sessions to attribute usage analyses.

  • _hjSession_*

    30 minutes

    Hotjar. Holds the current session together so page views are attributed to the same session.

More details