Service locations on a map: a pin should lead to the right door
Connect service choice, location details, accessible map alternatives and directions to the right entrance.
Article language: English

In this article
A customer stands outside a warehouse gate with a folder of drawings under their arm. They wanted to see materials, so they chose the nearest pin on the website. The warehouse really does belong to the company. It also has a very solid gate. But nobody displays samples there.
This is a fictional situation at a company that equips studios. In one city it has a showroom with displays, a warehouse for collecting orders and an office for design meetings. The map uses the same symbol for all three. The distance is correct, but the customer's question remains unanswered: where should they go for this particular purpose?
Nearest does not always mean right
Before choosing a map format, establish why people visit. One person wants to collect a prepared parcel. Another wants to compare material samples. Someone else is looking for the meeting place named in a message. They need different information even though each path ends at an address. Do not begin the design with a list of streets and coordinates alone.
In our example, each location needs a recognisable role. “Showroom and displays” explains more than “location 01”. “Warehouse - collection of prepared orders” does not suggest people can browse the range there. “Office - meetings by appointment” helps someone judge whether they can simply arrive. Names should serve people unfamiliar with the company's structure.
With three locations, these differences can be shown without elaborate filters. With more, choosing a service should narrow the list according to what is actually offered. First “I want to collect an order”, then the matching locations. A “location type” filter alone requires people to know whether the showroom, warehouse or both handle collections.
Do not assume a shared logo means shared capabilities. Hours, available services and entry instructions should belong to the individual location. If the warehouse accepts collections only until 15:00, the showroom's longer hours must not appear on its card. A shared telephone number does not change that difference either.
After a service is chosen, show the number of matching locations. If none provides it, distinguish that from temporarily missing data. You can offer a contact to arrange another route if the company really provides one. Moving the map somewhere else without explanation does not answer the service question.
Location information is part of a service page and its specific scope (in Polish). If a page promises material demonstrations, the location link should lead to a place where people can see them. A generic map of every address shifts the final decision to the customer even though the company knows the answer.
The list should allow a choice without deciphering the map
A map helps people see positions and relationships between places. A list lets them read the name, service, address and hours in an ordinary order. Design both as views of the same set of locations. Someone starting with the list should be able to make a decision as meaningful as someone clicking markers.
W3C WAI lists maps among complex images needing a text equivalent of essential information. On the page described here, a practical solution is a list of locations with information needed for a visit. An interactive map still needs its own behaviour tested; a text description of an image does not replace that acceptance check.
A list row should distinguish two locations on the same street. A name, building number and role help more than identical “view details” labels. If the street name is shortened on a small screen, the full address must be available before navigation starts. Customers should not discover the difference only in an external application.
Connect the selected list item to the correct pin. Clicking the warehouse in the list should indicate the warehouse, not the city's first address. Do not lose the selection indicator after zooming. A pin number can help, but should not be the only way to recognise a location, especially if filtering changes list order.
Define what moving the map means. Does the list include all matching locations or only those in the current view? Either can be designed clearly. The problem starts when a customer moves the map and half the results disappear without an explanation. Name the current scope and how to search again if necessary.
After a filter change, check what happens to the previously selected location. If the warehouse does not match the new service, do not leave its active route button beside a list of showrooms. Show that a new selection is needed, or retain the card with a clear explanation of the mismatch. List, details and marker should describe the same state after several changes, not only on first opening.
Also test when the map does not load or the customer has not started it. The location name, address, services and contact should remain available. Do not hide them only in a window opened through a pin. Otherwise a temporary map problem becomes a problem finding the company.
A building address and the way to the entrance are separate information
A pin placed in the middle of a large property may identify the address correctly but guide someone poorly to the door. In our warehouse example, the collection entrance is on a side street. The office is a floor above the showroom but has a separate entrance. Confirm those differences with someone who knows the place, then tell customers.
Separate the address from a short access instruction. Street and number should be copyable. “Entrance from the courtyard, door marked office” describes the last stretch. Do not put the entire instruction inside the address field sent to navigation if it could cause a different point to be selected. Prepare information for reading separately from data used by the route button.
A photograph can help identify the right door if it is current and actually shows the customer's route. Describe it according to its function, and do not leave a necessary instruction only in the image. “Entrance B” will not solve anything if the only sign on site is the company name on door A.
For collection of goods, specify the handover location. Delivery and personal collection (in Polish) also involve readiness confirmation and collection rules. A map should not imply a parcel is waiting at every point carrying the logo. The selected location's card must match the place specified in the order.

Give verified access conditions when they affect the choice: stairs to the office, an entrance at pavement level or how to report at the gate. Describe specifics the company can confirm. A generic “accessible location” label may be too vague for someone planning a visit. If assistance or an entrance method must be arranged in advance, provide a way to make contact.
Describe hours in the context of the particular activity. The showroom may be open after parcel collection has ended. Meetings may be by appointment only. If you show “open now”, define what that message confirms. Give collection hours to someone planning a pickup. Staff being present in the building alone does not establish that the order can already be collected.
For exceptional changes, show the date and scope. “Collections until 13:00 on Friday” must apply to the right location and day. Do not leave such a note without a year or date if it might stay on the page longer. Once the exception ends, someone must restore the ordinary information or the system must do so under an agreed rule.
Aeneia Design
Let us design a choice of location that can actually handle the customer's request. We will connect the map, list and entrance details into a clear path from choosing a service to reaching the right place. Organise locations and the route to a service point
The route button should preserve the chosen destination
When a customer presses “get directions”, pass the correct location to the map being used. Check the result with two similar addresses and an entrance on a different street. Opening an application alone does not establish that the destination is the right door. Acceptance should include the name and point visible after the transition.
If distance is shown, explain its basis. Distance from an entered city, an approximate position and the customer's current location are different information. Treat travel time separately. Without appropriate data, do not substitute one measure for another or describe distance as a promise of quick arrival.
Using AI to propose a route adds a separate check of address, destination point and travel time (in Polish). That is a separate assessment of the proposal's accuracy. In the page design, first ensure that the source location card has no contradictory data and identifies the destination unambiguously.
For manual search, account for similar town and street names. If an entered name yields several possible origins, allow the correct one to be selected and show it with the results. Do not silently select a city of the same name in another region. Customers can judge distance sensibly only when they recognise the place from which it is measured.
Geolocation, the determination of a device's position, can help, but location choice should not depend on it. If a customer does not share their position, let them choose a city, enter a town or browse the list. Do not show “no locations” when what is really missing is the starting position for the search.
Do not set the nearest location as the confirmed collection point by default. Distinguish a suggestion from a choice. If the customer changes location in a later form, show the current name and address in the summary too. An earlier card should not leave them with a destination different from the one the system ultimately saved.
The choice must be available without a mouse
Google Maps documentation describes markers with screen-reader text and keyboard support when interactions are configured appropriately. The appearance of a pin alone does not establish those properties. Design and acceptance should therefore include the marker's name, selection and return after closing details.
On the page, test moving from the filter to the list, then to the chosen location's details and route button. Keyboard navigation should show which element is active. If details open in a separate window, define how it closes and where focus returns. Moving the map image should not itself move operation to an arbitrary element.
On a phone, begin with the task rather than a zoom gesture. A customer wants to find the warehouse, read the hours and start a route. A small card covering the whole map can still be useful if it permits those actions and a return to the list. A striking map without the chosen location's readable name does not meet the same goal.
The result should be recognisable when reached by another route too. A company's internal search may lead directly to a particular location, while a QR code on printed material may open the same card at the entrance. Separate articles discuss designing internal search (in Polish) and a QR code that leads to the right page (in Polish). In both cases, show the name, role and current information without forcing another location selection.
Someone must confirm the information before the customer visits
Prepare information for the location owner to approve: services handled, address, entrance, hours, contact and route destination. Do not replace this with a reading from a random business directory. Someone at the location should know whether customers will still reach the right place after a gate changes.
After a location moves, check its old card and links to it. A customer may have saved the address or a QR code from an older printout. Show information about the change and the current location with its role. Do not silently turn an old warehouse into a new showroom: someone returning for collection might think only the street had changed.
Decide who updates the data and how a change is reported. A warehouse closed exceptionally should have the same message on its card and in the list. If data comes from several places, identify which is the basis for publication and who resolves discrepancies. Screen design alone cannot establish whether a newer time in an operations spreadsheet has already reached the site.
In Aeneia Design's website work, a map can be connected to an organised account of services and locations. The project scope covers the location-selection journey and its information, states and actions. The company must confirm the services and on-site data before publication.
For acceptance, give someone a purpose: collect a parcel, see samples or attend an arranged meeting. Do not tell them the location name. Check what they choose, which hours they read and which entrance the route reaches. Customers should arrive at doors ready for their visit. The impressive warehouse gate can remain an attraction for people who actually came to collect an order.










