# Multi Entry Point Selection for Android, when is this support coming?

**URL:** https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785
**Category:** Sweden \[svenska\]
**Created:** [March 27, 2026, 4:00pm UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785 "2026-03-27T16:00:20Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![avozetta](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/FD804B/32.png) [@avozetta](https://www.waze.com/discuss/u/avozetta)
#### Post date: [March 27, 2026, 4:00pm UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/1 "2026-03-27T16:00:20Z")

</div>

Hi!

During our Scandinavian meeting, we talked again about support for getting a list of choices for multiple navigation points for a location that has them entered in WME. It was very unclear whether this was implemented for iOS, but it has now been confirmed via a bug report that this is the case.

I took the opportunity to ask Waze in that bug report about upcoming support for Android and received a response. It is highly desired by the community, but there is currently no plan to implement it.

---

<div class="post-metadata">

### Author: ![avozetta](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/FD804B/32.png) [@avozetta](https://www.waze.com/discuss/u/avozetta)
#### Post date: [March 28, 2026, 3:40pm UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/2 "2026-03-28T15:40:05Z")

</div>

It would be nice, however, if someone here could confirm the support on iOS and post some pictures of what it looks like. It would motivate us to use that feature in WME more than we do today.

---

<div class="post-metadata">

### Author: ![ulle2](https://www.waze.com/discuss/user_avatar/www.waze.com/ulle2/32/25401_2.png) [@ulle2](https://www.waze.com/discuss/u/ulle2)
#### Post date: [March 28, 2026, 10:04pm UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/3 "2026-03-28T22:04:20Z")

</div>

Do you have an example? /Ulle

---

<div class="post-metadata">

### Author: ![avozetta](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/FD804B/32.png) [@avozetta](https://www.waze.com/discuss/u/avozetta)
#### Post date: [March 29, 2026, 7:58am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/4 "2026-03-29T07:58:55Z")

</div>

You can test these locations right now at Bromma Blocks:

Chop Chop with Main Entrance and Drive-thru: [https://waze.com/sv/editor?env=row&lat=59.35584&lon=17.95338&marker=true&zoomLevel=17&venues=11797074.117643056.17272862](https://waze.com/sv/editor?env=row&lat=59.35584&lon=17.95338&marker=true&zoomLevel=17&venues=11797074.117643056.17272862)

KFC with Main Entrance and Drive-thru: [https://waze.com/sv/editor?env=row&lat=59.35584&lon=17.95338&marker=true&zoomLevel=17&venues=11797074.117643056.15952891](https://waze.com/sv/editor?env=row&lat=59.35584&lon=17.95338&marker=true&zoomLevel=17&venues=11797074.117643056.15952891)

And in a few days, also Bromma Blocks with entrances: [https://waze.com/sv/editor?env=row&lat=59.35584&lon=17.95338&marker=true&zoomLevel=17&venues=11797074.117643056.4810429](https://waze.com/sv/editor?env=row&lat=59.35584&lon=17.95338&marker=true&zoomLevel=17&venues=11797074.117643056.4810429)

---

<div class="post-metadata">

### Author: ![ulle2](https://www.waze.com/discuss/user_avatar/www.waze.com/ulle2/32/25401_2.png) [@ulle2](https://www.waze.com/discuss/u/ulle2)
#### Post date: [March 29, 2026, 12:24pm UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/5 "2026-03-29T12:24:16Z")

</div>

In both cases, I only get one choice and it’s to the entrance. If I select a route, I get the main route to the entrance and the alternative route to the other navigation point.

/Ulle

---

<div class="post-metadata">

### Author: ![avozetta](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/FD804B/32.png) [@avozetta](https://www.waze.com/discuss/u/avozetta)
#### Post date: [March 29, 2026, 2:18pm UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/6 "2026-03-29T14:18:27Z")

</div>

Yes, it’s when you’re planning a route that you should get all the options. Can you send some pictures of what it looks like?

---

<div class="post-metadata">

### Author: ![mahava](https://www.waze.com/discuss/user_avatar/www.waze.com/mahava/32/18241_2.png) [@mahava](https://www.waze.com/discuss/u/mahava)
#### Post date: [March 29, 2026, 2:45pm UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/7 "2026-03-29T14:45:37Z")

</div>

Tested this on the work iPhone but just like on the droid I only get a route to the nearest entry point , tested against Matarket in Strängnäs, the main point is towards Trädgårdsgatan, but as you can see I get it on Nygatan

 ![1000010159](https://web-assets.waze.com/discuss/prod/original/3X/f/a/fae013ec1413723e5a3581ae1f357389fec7ef5f.jpeg)

None of the alternative routes give me any other entry either

Edit [https://waze.com/sv/editor?env=row&lat=59.37532&lon=17.02838&zoomLevel=19&venues=11141714.111613746.5419647](https://waze.com/sv/editor?env=row&lat=59.37532&lon=17.02838&zoomLevel=19&venues=11141714.111613746.5419647)

---

<div class="post-metadata">

### Author: ![ulle2](https://www.waze.com/discuss/user_avatar/www.waze.com/ulle2/32/25401_2.png) [@ulle2](https://www.waze.com/discuss/u/ulle2)
#### Post date: [March 29, 2026, 7:41pm UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/8 "2026-03-29T19:41:47Z")

</div>

Hi, here are some pictures explaining the situation.

- When I search for KFC Bromma Blocks, I only get one option, see image 1
- When I select the only suggestion, I get a route to the entrance, which is the shortest route, see image 2
- If I then choose to show routes, I get another route suggestion that goes to the drive-through, see image 3

/Ulle

 ![KFC Sökning](https://web-assets.waze.com/discuss/prod/original/3X/2/7/270abc8f3a03c39d039c976b11e013da71cd84d3.png)

 ![KFC Rutt](https://web-assets.waze.com/discuss/prod/original/3X/2/f/2fac78338ab26aa85bb0d4b0b64f96c676341795.png)

 ![KFC Visa rutter](https://web-assets.waze.com/discuss/prod/original/3X/1/7/17293ccf54075237e1dab3404a3e2ab68b0c6821.png)

---

<div class="post-metadata">

### Author: ![mahava](https://www.waze.com/discuss/user_avatar/www.waze.com/mahava/32/18241_2.png) [@mahava](https://www.waze.com/discuss/u/mahava)
#### Post date: [March 30, 2026, 2:25am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/9 "2026-03-30T02:25:19Z")

</div>

Behaves the same way if I test that specific target, strange, could it have to do with the feeder sheet having 3 entry points?

---

<div class="post-metadata">

### Author: ![avozetta](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/FD804B/32.png) [@avozetta](https://www.waze.com/discuss/u/avozetta)
#### Post date: [March 30, 2026, 5:06am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/10 "2026-03-30T05:06:22Z")

</div>

Obviously it’s not working as intended for you, strange. Here’s the bug report that shows in the video how it’s supposed to behave, [https://www.waze.com/discuss/t/multiple-entry-point-selection-not-working-in-ios/396972](https://www.waze.com/discuss/t/multiple-entry-point-selection-not-working-in-ios/396972)

---

<div class="post-metadata">

### Author: ![mahava](https://www.waze.com/discuss/user_avatar/www.waze.com/mahava/32/18241_2.png) [@mahava](https://www.waze.com/discuss/u/mahava)
#### Post date: [March 30, 2026, 7:06am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/11 "2026-03-30T07:06:44Z")

</div>

Yeah, exactly. It doesn’t seem to be working as it should on iOS, but on Droid it seems to work as it should (WAD) where it picks the closest one. I’ll see if I can test Ulle’s example on the Droid, and then I’ll add to what I put in the bug report you linked for iOS with reproduction steps.

---

<div class="post-metadata">

### Author: ![avozetta](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/FD804B/32.png) [@avozetta](https://www.waze.com/discuss/u/avozetta)
#### Post date: [March 30, 2026, 7:23am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/12 "2026-03-30T07:23:51Z")

</div>

What do you mean? It’s not implemented on Android!

In the video for iOS, it’s clearly shown that all entry points are listed for the hospital as expected; you should see that on your iPhones too, but for the examples I mentioned above.

---

<div class="post-metadata">

### Author: ![pnylin](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/FF5252/32.png) [@pnylin](https://www.waze.com/discuss/u/pnylin)
#### Post date: [March 30, 2026, 7:29am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/13 "2026-03-30T07:29:10Z")

</div>

I’m only seeing the main entrance on my Samsung (Android).

Edit: Or is “Main Entrance” in this case the alternative navigation point?

 ![Screenshot_20260330_092633_Waze](https://web-assets.waze.com/discuss/prod/original/3X/6/0/6010b9fcc59f33ee5c66d29492b843dea754f543.jpeg)

---

<div class="post-metadata">

### Author: ![pnylin](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/FF5252/32.png) [@pnylin](https://www.waze.com/discuss/u/pnylin)
#### Post date: [March 30, 2026, 7:36am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/14 "2026-03-30T07:36:16Z")

</div>

Okay. I couldn’t watch the video you linked to.

---

<div class="post-metadata">

### Author: ![avozetta](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/FD804B/32.png) [@avozetta](https://www.waze.com/discuss/u/avozetta)
#### Post date: [March 30, 2026, 7:50am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/15 "2026-03-30T07:50:05Z")

</div>

As I mentioned earlier, this isn’t implemented on Android, so it’s expected that only one entrance is shown. In this example, the Main Entrance as it’s marked in WME.

---

<div class="post-metadata">

### Author: ![ulle2](https://www.waze.com/discuss/user_avatar/www.waze.com/ulle2/32/25401_2.png) [@ulle2](https://www.waze.com/discuss/u/ulle2)
#### Post date: [March 30, 2026, 8:01am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/16 "2026-03-30T08:01:08Z")

</div>

Hi

If I choose a route to KFC Bromma Blocks, it takes me to the Main Entrance as pnylin showed, see image 1. If I click on the “Main Entrance” icon, I get two choices, “Main Entrance” and “Drive-in”, see image 2. If I choose “Drive-in”, I’m still routed to the main entrance.

The choice of navigation point should reasonably appear either as an option during the search or once I’ve selected a place that has multiple navigation points. As it is now, you don’t get any information that there are multiple navigation points; you have to actively look for them yourself, which is a poor solution!

/Ulle

 ![Huvudentre](https://web-assets.waze.com/discuss/prod/original/3X/2/1/21dd6ea6d8e3ab336b73ed1431749434f7f7fcce.png)

 ![Val](https://web-assets.waze.com/discuss/prod/original/3X/6/4/64a1c86d8f7ead7244dc9b3de74cf70919376847.png)

---

<div class="post-metadata">

### Author: ![Pee3](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/963EFF/32.png) [@Pee3](https://www.waze.com/discuss/u/Pee3)
#### Post date: [March 30, 2026, 8:16am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/17 "2026-03-30T08:16:36Z")

</div>

For a “country bumpkin”, the entrance isn’t shown at all on my Pixel 7 with Android 16.

 ![1000009300](https://web-assets.waze.com/discuss/prod/original/3X/a/8/a8a8b2b3c403b509ac52676f13b8419217778970.png)

I agree with Ulle that it’s not that easy to find that there are multiple entrances.

---

<div class="post-metadata">

### Author: ![avozetta](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/FD804B/32.png) [@avozetta](https://www.waze.com/discuss/u/avozetta)
#### Post date: [March 30, 2026, 8:22am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/18 "2026-03-30T08:22:45Z")

</div>

Great, then we’ve confirmed that the feature exists on iOS and that the bug has been reproduced in the bug report linked above.

I agree that the solution is less than ideal; the alternatives should really be listed before you plan your route.

---

<div class="post-metadata">

### Author: ![ulle2](https://www.waze.com/discuss/user_avatar/www.waze.com/ulle2/32/25401_2.png) [@ulle2](https://www.waze.com/discuss/u/ulle2)
#### Post date: [March 30, 2026, 8:29am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/19 "2026-03-30T08:29:42Z")

</div>

But at least you get to see customs – you have to be happy for the little things 🤣

---

<div class="post-metadata">

### Author: ![mahava](https://www.waze.com/discuss/user_avatar/www.waze.com/mahava/32/18241_2.png) [@mahava](https://www.waze.com/discuss/u/mahava)
#### Post date: [March 30, 2026, 8:40am UTC](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785/20 "2026-03-30T08:40:23Z")

</div>

Yeah, in beta they’ve implemented it so it should choose the nearest entry point on Android, and that’s how it works too, unless they’ve changed how it’s supposed to work again; however, my iPhone seems to do the same and doesn’t ask.

If the main entrance is still supposed to be selected, then it’s not working as intended; I’ll have to double-check the feature status.

Edit: here is the beta thread [https://www.waze.com/discuss/t/multiple-entry-points-now-open/19792](https://www.waze.com/discuss/t/multiple-entry-points-now-open/19792). If you read down a bit, at the time it was temporary (which then seems to have become permanent) on Android that it picks the closest one but doesn’t ask, but I’ll ask them to clarify what applies now because it’s quite an old thread, as it seems unclear and also seems to work differently,

I do know though that if I’m at Västervikstorget and request a route, I get entry points on Trädgårdsgatan for the grocery store there, and that matches how it’s described.

Edit 2: the feature is marked as production so there shouldn’t be anything that differs.

[Next page](https://www.waze.com/discuss/t/mutli-entry-point-selection-for-android-nar-kommer-det-stodet/401785.md?page=2)
