Is there a way to let MEWS know that we are in Canada and that an address should be :
Door number/civic address, street name, province/state, country, postal code?
At the moment, it automatically reverts to :
street name, door number/civic address, province/state, country, postal code
which makes any exported list useless to convert to automatic mailing or for import to another software. We are manually correcting any issues we come across, but as soon as we use the Search function, it reverts to the incorrect adress when completing the boxes
Best answer by yann.isakovic
Hi @c.bonenfant I hope you're doing well :) My name is Yann from Mews support and I will try to bring more information here.
There is currently no setting in Mews to change the address field order per country (e.g. to enforce the Canadian format door number + street name + province + country + postal code). Address display and formatting are handled by a single, generic template and localization logic, not configurable per legal environment or property.
That means:
The UI and search/autocomplete will keep filling/ordering the address as street name, door number, province/state, country, postal code.
Exports that use the single “full address” field will reflect that same order and cannot be switched to a Canada‑specific pattern from within Mews today.
Practical workarounds
Use exports with split address fields and reassemble externally
Wherever possible, use reports/exports that give you separate columns (street, city, province/state, postal code, country). Then, in Excel or your mailing/import tool, build the Canadian format yourself with a formula, for example:
This avoids having to manually fix each address and gives you a clean column ready for mail merges or imports.
If a specific export is causing trouble
If the export you rely on only gives a single combined address column, the only options right now are:
Switch to a different report/export that exposes split address fields, or
Keep using a manual process to correct the combined address before importing into other software.
Because this is a limitation of how address formatting is implemented globally in Mews, changing the order for Canada would require a product change. I would suggest that you raise this concern in our feedback page here: Welcome to the Product Ideas Forum so it can be considered alongside the broader address‑localization work already discussed internally.
Hi @c.bonenfant I hope you're doing well :) My name is Yann from Mews support and I will try to bring more information here.
There is currently no setting in Mews to change the address field order per country (e.g. to enforce the Canadian format door number + street name + province + country + postal code). Address display and formatting are handled by a single, generic template and localization logic, not configurable per legal environment or property.
That means:
The UI and search/autocomplete will keep filling/ordering the address as street name, door number, province/state, country, postal code.
Exports that use the single “full address” field will reflect that same order and cannot be switched to a Canada‑specific pattern from within Mews today.
Practical workarounds
Use exports with split address fields and reassemble externally
Wherever possible, use reports/exports that give you separate columns (street, city, province/state, postal code, country). Then, in Excel or your mailing/import tool, build the Canadian format yourself with a formula, for example:
This avoids having to manually fix each address and gives you a clean column ready for mail merges or imports.
If a specific export is causing trouble
If the export you rely on only gives a single combined address column, the only options right now are:
Switch to a different report/export that exposes split address fields, or
Keep using a manual process to correct the combined address before importing into other software.
Because this is a limitation of how address formatting is implemented globally in Mews, changing the order for Canada would require a product change. I would suggest that you raise this concern in our feedback page here: Welcome to the Product Ideas Forum so it can be considered alongside the broader address‑localization work already discussed internally.
As we are working through a large number of bookings at the moment, we have noticed that US addresses are formatted properly. Is it possible for that code to be applied to the CAN addresses as well at some point?
Thanks a lot for coming back to us and for the additional detail about US vs. Canadian addresses – I understand how frustrating this is when you’re working through a large volume of bookings.
What you’re seeing is that the underlying address‑format rules are not yet aligned for Canada in the same way they are for the US. At the moment, there isn’t a switch we can flip on your side to “apply the US logic to Canada”: Canadian addresses are still using the current global pattern, which is why they continue to appear as:
street name, door number/civic address, province/state, country, postal code
and exports that rely on the single “full address” field follow that same order.
Changing this so that Canadian addresses use your preferred format:
door number/civic address, street name, province/state, country, postal code
would require a product/engineering change rather than a configuration update on your environment. Support unfortunately can’t adjust this per country today.
I would still strongly recommend adding this request in our Product Feedback Portal (Welcome to the Product Ideas Forum), specifically mentioning the need to reuse/align with the US formatting logic for Canadian addresses. This helps the team prioritize it among other localization improvements.
I’m sorry we don’t have a direct setting to offer yet, but your feedback is very helpful and is feeding into the broader work on improving address localization.
Welcome Mews customers. Please use the same email address for registration as in your Mews account. By doing so we can help you faster if we might need to check something in your account.
