Answers.Body: <p>Yeah, a simple checkboxes field with a list of the countries would be a good approach to realize this.</p>
  
  <p>Another idea is to make use of the <a href="http://buildwithcraft.com/features/localization" rel="nofollow noreferrer">localization feature</a>, which comes with a Craft Pro license. Then you'd add a new structure entry (in your case the product) in one locale (e.g. "fr"), save it, and all entered content is copied over to the other locales (e.g. "en" and "de").</p>
  
  <p>After that you can switch over to another locale's version of that entry, and make individual edits for it (e.g. change "10 EUR" to "8 GBP"). To disable an entry completely for one locale, use the status lightswitch available for each locale separately at the top right of the info panel.</p>
  
  <p><img src="https://i.sstatic.net/ygQvD.png" alt="Craft CP - Lightswitch to toggle entry status for each locale"></p>
  
  <p>Don't read this as if this "localization feature" solution is the right one. Consider if you really need to translate entry fields (product infos etc.) into other languages<sup>1</sup>, if not I'd definitely do it like you initially intended.</p>
  
  <p>And there's also a chance that you want to use both of these features combined: if you want to list all entry pages translated for each locale and additionally show the visitors where these products are available.</p>
  
  <p>--</p>
  
  <p><sup>1. "Craft Personal and Craft Client store content on a per-locale basis too, so down the road if you want your site to cater to a second locale, Craft is already set up for it."</sup></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-14T09:42:17.033Z
Answers.Text: I am glad my approach sounds like it makes sense. 
  In your other idea using the localization + new structure would I end up with multiple versions products to manage?
Answers.UserDisplayName: jamus
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-14T16:48:54.680Z
Answers.Text: @jamus you don't need a new structure, just add a new locale to your site and you'd have the localization feature working on your old structure! And yes, you kind of have multiple versions of that product to manage (that's the actual purpose for the feature :D), but you can individually select the fields you want to be always in sync (if you change the value in one locale, it automatically changes in all others, too).
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-15T08:41:38.997Z
Answers.Text: I guess I'll have to have a play around to better grasp what you're saying. Thanks for your help (and starting point).
Answers.UserDisplayName: jamus
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-15T09:10:31.627Z
Answers.Text: Yeah, it's probably best to not only think that through in theory alone. All I wanted to say is that you can hand-pick the fields you want to be translatable. You could even select no field at all and you'd end up with your product entries to be totally in sync across your locales and use only the lightswitch to disable it in certain locales. But that wouldn't make that much sense and I'd rather choose that other approach to handle this. If you start using the Localization feature, you'd rather do this to make the whole site being translated to other languages...
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-15T09:12:15.817Z
Answers.Text: ... Being able to select and deselect certain product entries for each locale would only be a nice side-effect of that, @jamus!
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-13T22:17:10.137Z
Answers.LastActivityDate: 2014-08-13T22:17:10.137Z
Answers.UserDisplayName: carlcs
Body: <p>Supposing you have a structure of products but you only want some to be available to certain localities? </p>
  
  <p>I am sure you could add a field to the entries E.g (Available in: eng | fr) and then test the local in the template before listing the entires. However, I'm not sure this is the best way of approaching this.</p>
  
  <p>Initially, it may be that the category the product is within dictates its availability in a country but this is not guaranteed in the future.</p>
  
  <p>Any ideas appreciated.</p>
  
Tags: <entries><localization>
Title: How can you display entries filtered by localisation/localization?
ThreadText: # How can you display entries filtered by localisation/localization?
  
  (Asked by: username_0 on 2014-08-12)
  
  Supposing you have a structure of products but you only want some to be available to certain localities?
  
  I am sure you could add a field to the entries E.g (Available in: eng | fr) and then test the local in the template before listing the entires. However, I'm not sure this is the best way of approaching this.
  
  Initially, it may be that the category the product is within dictates its availability in a country but this is not guaranteed in the future.
  
  Any ideas appreciated.
  
  **Tags:** entries, localization
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-08-13. Score: 2 | Accepted answer
  
  Yeah, a simple checkboxes field with a list of the countries would be a good approach to realize this.
  
  Another idea is to make use of the [localization feature](http://buildwithcraft.com/features/localization), which comes with a Craft Pro license. Then you'd add a new structure entry (in your case the product) in one locale (e.g. "fr"), save it, and all entered content is copied over to the other locales (e.g. "en" and "de").
  
  After that you can switch over to another locale's version of that entry, and make individual edits for it (e.g. change "10 EUR" to "8 GBP"). To disable an entry completely for one locale, use the status lightswitch available for each locale separately at the top right of the info panel.
  
  ![Craft CP - Lightswitch to toggle entry status for each locale](https://i.sstatic.net/ygQvD.png)
  
  Don't read this as if this "localization feature" solution is the right one. Consider if you really need to translate entry fields (product infos etc.) into other languages1, if not I'd definitely do it like you initially intended.
  
  And there's also a chance that you want to use both of these features combined: if you want to list all entry pages translated for each locale and additionally show the visitors where these products are available.
  
  --
  
  1. "Craft Personal and Craft Client store content on a per-locale basis too, so down the road if you want your site to cater to a second locale, Craft is already set up for it."
  
  > **Comments:**
  > **username_0**: I am glad my approach sounds like it makes sense.  In your other idea using the localization + new structure would I end up with multiple versions products to manage?  
  > **username_1**: @username_0 you don't need a new structure, just add a new locale to your site and you'd have the localization feature working on your old structure! And yes, you kind of have multiple versions of that product to manage (that's the actual purpose for the feature :D), but you can individually select the fields you want to be always in sync (if you change the value in one locale, it automatically changes in all others, too).  
  > **username_0**: I guess I'll have to have a play around to better grasp what you're saying. Thanks for your help (and starting point).  
  > **username_1**: Yeah, it's probably best to not only think that through in theory alone. All I wanted to say is that you can hand-pick the fields you want to be translatable. You could even select no field at all and you'd end up with your product entries to be totally in sync across your locales and use only the lightswitch to disable it in certain locales. But that wouldn't make that much sense and I'd rather choose that other approach to handle this. If you start using the Localization feature, you'd rather do this to make the whole site being translated to other languages...  
  > **username_1**: ... Being able to select and deselect certain product entries for each locale would only be a nice side-effect of that, @username_0!  
  
  ---
  
  