Hello, this is Franck from Sitolog. Today we're going to talk about Merlin's characteristics. So,
there's quite a bit to show you. The first thing is going to be how to
display product characteristics in the top table, in the product table. Then,
I'm going to show you how to filter them. Then we're going to look at the characteristics tab here.
Uh, in this tab, I'm going to show you how to associate and modify product characteristics
for several products at once. For example, we'll also see at the bottom how to create
characteristics. We'll also see how to duplicate characteristic values ​​between
different characteristics. Quite an interesting feature. We'll also see, always from
this tab here, how to filter products at the top based on characteristic values, what
we call ascending filters. And finally, at the end, a quick overview of the
import tool, which also allows you to create or modify characteristic values ​​in
products. So how do you import characteristics? So first part,
we're going to start by displaying the characteristics in the product table up there. So I'm going
to right-click on this bar to save a little space. I don't know if this is a little
technique you already know. And then, uh, to view the characteristics,
we're simply going to configure the columns of this table. So for that, I remind you,
you click on column, you go to the right tab, eh, product characteristic and
so on. So what concerns us is the product table and you go all the way down.
Here, you have a section called one column per characteristic. So you drag it
to the right. So, a little reminder, the columns that we place here in the configuration, we
can move them, eh, reorder them, we can keep them but deactivate them. This allows
us to say, we don't display this or that value, this or that column while keeping uh in
our setting. Uh, we can also change their width from a numerical point of view. And finally,
we can change their title, eh. For example, the supplier reference column, I can very
well name it, uh, something else, reference of my suppliers, for example. There you go, something
like that. Okay, that was just a little reminder because we often ask the same question. So,
I added a column per characteristic which is here. Another little note. You see that
it is marked with 3 minuses in red here. That means that it is a section that will
significantly slow down the display. So, there aren't many sections of this type. Uh,
in the list, there must be three or four. I'm not even sure I can find them. There you go, we have some
here, we have some that concern the photos and then maybe some that concern
the variations, sorry, here. There you go. And then finally the characteristics. So that
slows down the display quite significantly simply because it
greatly complicates the read requests at the server level and some servers may have
difficulty producing the requested results. Okay, however, it doesn't crash anything,
it just might slow down your workflow a little. So I'm validating this configuration.
So, it's refreshing. Before commenting on the display, just to
point out that I advise you not to do exactly what I just did,
that is to say, modify your current configuration, but rather to create a
configuration specific to this type of work. So you call characteristics for example,
eh. You see, I do it to modify my prices for my texts and various things, the
stocks. And then the same when I go to work on the characteristics, I create a
characteristic configuration which also normally contains this section. Okay, apparently I removed it,
so I'm going to add it again. This allows me to show you the technique again. I click on column. I
go to the bottom of the list in the product tab. I take one column per characteristic,
I drag it and I validate. There you go. So what Merlin does after that is that it refreshes
the display of my products. So of course according to my category selection here. So
currently, I'm asking it for all the women's products in recursive mode, that is to say women
and subcategories of women. So it displayed all these products to me according to the fact that they
belong to the category or categories that I selected. So a filtering by
category by default. And then above all, I end up with three new columns here which
correspond to the different characteristics of my different displayed products.
So here, it's a dynamic display. So the number of columns that you will have
here depends on your database, depends on your products. If I didn't have any products in
my list here which contained a value of the composition characteristic, at that point,
this column would not have been displayed. So if you select absolutely all the products
in your database, you will end up here with as many columns as there are characteristics
associated with at least one product. So in some cases we may find ourselves with a very large
number of columns. So what is important to mention right away is that these columns
here in this table are not editable. I cannot modify the word viscose. I cannot
delete it. I cannot replace a characteristic value. I also cannot
add a column of characteristics not yet associated. This is purely for display, it is
information. So what is the point of having this information here? There are at least two.
For example, you can sort, so not sort but yes classify or sort according to a composition, finally
according to one characteristic or another or two with a click control. You can also
create column filters. For example, here, I right-click, I click on
filter on this column. I will ask it contains or equal to cotton. I validate. I only have
products that contain cotton. So this is often quite useful for making a
quick selection of products based on certain characteristic values. Later, I
'll show you something else, an even more advanced method, I would say more practical for filtering
products based on characteristic values. This is called ascending filters.
So we'll see that later in the video. The second reason why it can be
interesting to display the characteristics is mainly for exporting the data.
If you need to export to a marketplace that asks you for the characteristics,
well, you'll display them like this. Then, select your lines, do a group action,
click on export. You choose what you want to export. So in this case, for
us, it's just the product table. So I'm just going to take the products and you export
with the parameters you want. So there are two main types of export. There's
this one. So when we choose the first two options here, which provides a file that is perfectly
suited to reimporting into a Prestashop database, either the same one
or another, possibly even in another version of Prestashop. Merlin will be
able, thanks to these columns here, to reimport the characteristics, recreate them, recreate their
values, and automatically reassociate them with the products in a single operation.
And then the second format, this one at this point, creates a file exactly as it is
displayed here. So it's not intended for reimporting into Prestashop, it's more intended
for marketplaces or other tools for which you need a format
identical to what you have up there. So the second part, the characteristics tab. So I
'm going to restore the interface. I right-click again on this bar to bring up the
bottom part, and I'm also going to delete my thread that I have here. So I go to this column, click
Right and delete the thread from this column. Good. So in this tab, you have two parts.
In the top part, we will be able to display, visualize sometimes in a certain way modify
the characteristic values ​​associated with the products that are selected above.
And then in the bottom part, we will be able to visualize all the existing characteristics
in the database as well as their values. Create new characteristics and new
values. Also duplicate characteristic values ​​from one characteristic to another.
So let's see that. So I'm going to reduce the bottom part to have a little more space
here so that it's more understandable. So I'm going to start by selecting several products at the
top. Voz, we're going to take all the products there that are displayed and I'm going to click on
display. So, what the program does is that for each of these products up there, it
went to get the value of the characteristics already associated that we find here. So there,
we have the product numbers, characteristic numbers, the name of the characteristic,
the ID of the characteristic and its value. We can perhaps rebalance
the display a little. This also allows me to show you that here in all the tables,
you have what is called the table menu. I don't know if I've already talked about it. And you have
a function here for automatically adjusting the column width. Another little tip,
here it's not very clear because I no longer have what we call the separators
or the breaks. I'm going to recreate the breaks. So the breaks are brown or beige lines
that actually group the values ​​of the common values, so the product lines.
Look, I do it in ID product. Here, I right-click, I'm going to add a break
on this column. And automatically, you see, my lines are grouped by set of, how to
say, products, eh, by product. So here in PR3, I have all the properties of product 3 here
all the properties of product 2. So here you have, uh, the values ​​associated with product
2 for example. So product 2, it's this one, it's the blouse. So that's information.
You can also modify this information, that is to say for example if I modify
the cotton composition here to something else, well you click there on the word cotton and it opens you,
uh, the selector eh. So you can either choose an existing standard value from
the list like viscuse, or I'm going to do it here for short sleeve, uh here in the bottom part,
create what we call a custom value. So a custom value, I'm going to call it
perso 1. A custom value is a characteristic value that cannot be
used by another product. So it's a unique value. In which case should we use
standard values ​​and in which case should we use custom values? So that
's a Prestashop or e-commerce problem. It's not entirely specific to Merlin, but I
'll explain it anyway. A standard value like short sleeve or all those that are there.
If at some point you modify the name, the value, at that point, the
modified value will apply to all the products that are associated with that value. So on the one hand,
it's practical. But on the other hand, perhaps if your values ​​are, for example,
lengths or dimensions, and at some point you want to modify this value because the
dimension of the product changes, at that point it's better to choose a custom value because
you don't necessarily want to impact the dimension of the other products as well. There you go. So
the choice between a standard value and a custom value is up to you. It's
not a rule, a golden rule. So here I chose a custom value. I validate.
And I find myself here with my property now custom 1. And see a little information
in the custom column, I have a checkbox in French
that tells me it's a custom value. So as you can see, this table
Here, it displays the characteristics, allows me to modify them one by one, to define whether they are
custom values ​​or not, and then finally, it also allows me to unassociate them, basically to delete them.
So, for example, if I want to remove my custom value here, this property,
and also the composition of this product, well, I select both and I click
on unassociate. It asks for confirmation before deleting. I delete. There you go.
So both products have lost these two characteristics.
Just a quick note, when you modify characteristic values ​​in this table,
you can notice that here in the top left, the refresh button flashes. So this is the
case when you actually have the characteristic columns included in your
display, as was the case earlier, what I showed you first, in fact.
So the refresh button here tells you that the data displayed in this table is not
necessarily synchronous with the data in the database. So the data in the database has been
modified via the middle table here. But to save time, Merlin doesn't
automatically refresh the data up there synchronously. It would slow down the application too much. So it's up to
you at some point if you want to because you need the information that's there
to export it or whatever. At that point, you have to click on the refresh button like I'm
doing now. to refresh the data at the top and therefore have it synchronous with the table
below. There you go. So I'm going to reselect everything again to refill my table.
So, another note, you don't have in this table apart from the unlink button here,
so mass deletion, you don't have a mass copy or
multi-line modification function as is the case on the products table for example or practically all the
other tables. We'll see in a moment that all multi-line modifications are made
from finally the tables at the bottom here and the button here which is currently grayed out which is called
associate value. So we'll see that in a moment, but I'll show you anyway, so we'll
expand a little. You have functions for filtering or sorting, etc. You can copy
values, but you don't have the two bottom lines, you know, which allow you to copy a
line into a selection of other lines. So we don't work that way on this table.
So the mass processing is done from the bottom part here of the
characteristics tab. So the first operation is to display the characteristics present
in the database. So by clicking on the little button here, eye or display. There you go. So all
the existing characteristics are listed. If I select one that contains values,
they are listed. Here, I have secondary tables here that give me the translations
into the different languages ​​present in the database. Here also the translations of the values
​​of the different characteristics, and finally, on the right, a tab to define custom values
. We saw earlier, we created one. We can also create them here. So,
I was saying this part at the bottom here will allow me to make mass modifications,
that is to say to change the characteristics of the products selected above. So for that,
you just have to choose one or more different characteristics
with a control. So here my different values ​​are displayed. So that's practical
too. I'm going to put back here a break that is normally present by default that I
had to delete. So I'm adding a break so that I find here a grouping
by characteristic. So I first have the compositions at the top then the styles at the bottom.
Well look, I'm going to choose a composition and I'm going to choose with a control a style
a military style. There you go. So I have two values ​​that are selected here. I have
x products selected up there. So I might not do it on all of them. We're going to simplify
a little. We'll leave it like that. We'll do it on all of them. So I have all my products selected,
my values ​​selected. All I have to do is click here on the associate value button. So
that associates the values ​​at the bottom with the product selected at the top and so it will update
the table here in the center. I click. There you go, it performs the operation. It's finished. It did
n't even take a second. And you see, I have the military style that has been added everywhere
and also my composition which has become either. So there was a replacement of the
composition value because all the products already had a composition and from memory
the products didn't yet have a style and now they have a
style characteristic which is military. So if I modified a value, for example the style, I made a mistake,
I didn't want the military but I wanted the rock, it's just as simple. I select
my rock value and I click again on associate value and automatically all the products
change to rock value in rock property in the style characteristic. To delete a
property, again, I showed you earlier, you click here in the
middle table and ungroup. So, if you want to save time, for example, to avoid
selecting all the styles, if I wanted to delete all the styles for all these products,
I would use a filter. I would right-click here on the word style. Filtered on this column
equals style. I validate. I could also have done it on the value by the way.
Uh, so filter only the rocks. There, I have my thread which was which has, sorry. So I have
all the styles. I select all the rows with the button and I ungroup.
I delete. So there, I have, uh, apparently all my rows which have disappeared but in fact
only the styles. Why don't the other rows appear? Simply because I
left my filter here, eh. So characteristic equals style. So now I just have to
delete this filter. So if, as is the case here, the column is empty, it's an interesting case.
Uh, when there are no lines, sometimes you can't filter, you ca
n't, excuse me, unfilter. So at that point, you have to use the function that's there, which I
've already shown you, perhaps the red filter here that removes all the column threads. And so,
we end up with all our products that no longer have style-type characteristics.
Let's now see how not to associate but to modify a characteristic value. For
example, I would like to replace the word "be", the value "be", with the word "be natural". So,
I could of course go to the bottom table, look for the material composition then the
"be", and once I've found it, modify it. But already a very practical shortcut. I just have to
click on one of the lines here that contains this value. For example, the first one here "be",
and you see that the bottom tables have automatically synchronized. In any case,
they point today, finally now, sorry, to the value "be". All I have to do
is modify my value. So I can do it here, but it's more practical to do it
in the translations table. Here, I directly replace "either" in editing with "either natural."
I'll also do it for English while I'm at it. We'll do "natural silk." There you go.
So, my modification is made here. It's important to understand that at the same time
as I did it, it was made in the Prestashop database. The modification is
made instantly. So in Prestashop, it's done. In the table here in the middle, "either natural"
was modified at the same time. So there, there is an automatic synchronization of the display
for more clarity. On the other hand, once again, here, you see in the top table,
the refresh button is flashing, that is to say that the information here has not been updated
. Besides, it's been a while since I updated it because the notion of the fact that the
products are in themselves is not even displayed. So if I really wanted to have the information
correct at the top, I start the operation again, I click on refresh and at that moment,
we find the composition information, which is natural. Here, we're going to reselect everything. So,
this synchronization at the top, eh, refreshing the top table,
honestly don't do it every time. Uh, it's only to be done when you've finished
working on your characteristics because the tables, the top table,
the columns, uh, of characteristics, once again, are only informative. So you
don't risk overwriting your data with the fact that they are not synchronized.
So I would like to point out that the modifications in these different tables
here support multi-line modifications like Magic Edit.
Here, I have selected several values. For example, let's imagine that I'm going to add
a common word to the end of all these values. Uh, so, I'm going to select them all.
I'm going to right-click in my menu. So, you don't see it here, but
the Magic Edit tool appears. I select it. My Magic Edit tool appears. So here,
this isn't a training course on Magic Edit, so I'll do it very quickly. I'm just going to use
the tool, not this one, but add some text in front. Here, or sorry, rather at the end. And I
wanted to add the brand of these materials at the end. So here, I added my brand name,
a space. I don't know the brand name, but I have my brand name. There, I apply it, and
you see, I have all my values ​​that have been modified in a single step. So you can
do this on the values ​​of the characteristics but also on the names of the characteristics
themselves in this table here or in this table there. Let's see, for example, how to modify the
values ​​of so-called personalized characteristics. So, we'll start by creating some. I'm going to
choose a single product in the top table. So, it already has two characteristics. I'm going to
create a weight and a personalized weight for it. So, I'm going to create a new value. So,
I'm going to click here on customize and I'm going to give it a weight of 310 g.
So I'm just going to put the value 310. There you go. And once it's created here,
so there it's stored in the database if you like in the form of a value, it's not
yet associated with the product. So now I'm going to associate it with the product. So my
weight with a custom value of 310 g is associated with my product. If I want
to modify this value at some point, I have several ways of doing it. I can either delete it,
so unassociate it and recreate a new custom value, or directly here.
So select it in the middle table and here in the bottom table, simply modify the
value. For example, there's a small adjustment, it weighs 311 g. So I modify my value.
Then I actually have the choice. You can either just do what
I just did because in fact already at this stage the modification is taken into account
but you can also, it's the old method, the prestapressing one. You had to
click again on associate the value. But if you don't do it in
Merlin, it works too. Okay? So simply editing here is enough.
So, as a reminder, a custom value is a value that is specific to a single product,
which cannot be shared between two products. So, it is not possible to modify a
custom value at the same time on two or more products. However, you can create a
custom value on different products in bulk, even if it's the same value. I'll try
to show you this with an example. So, I'm going to take two products. We're going to take these two
products here, which I call the label generator. I'm also going to associate a weight with them. So, I
click on the weight characteristic, I go to custom value, I check the option, and I
create a custom value of 500 g for them. So, what happens? And I associate. So, in fact,
my two products end up with a value of 500 g, but it's called custom.
That is to say that in the database, although it is the same value, we have two different lines and
we can independently modify this value for one product or the other. For example,
I will take the first product here, the value 500, I will modify it, I will change it to 501.
I will do this quickly with a copy and paste to do it in all the languages. I
will show you the trick. Simply, if you have a lot of languages, avoid
editing it line by line. You have a mass copy function here. So there you go, I modified
my custom 501 value. So it modified it on product number 8 but it did not modify it
on product number 9. This one still has a custom value of 500. But initially,
I created my two values ​​in a single operation by selecting the two lines in
the top table before checking customize, entering my value and clicking on associate.
So, how do we create standard values ​​and not personalized ones? Well,
it's not more complicated. We start by choosing our characteristic. For example, style. Here,
we have the existing values. And to create a new style, well, I click on the plus button in the
table here of values. I just have to enter my value. I'm going to call it modern. I validate
and my new characteristic value here is created. I have it here in French. I can have fun
translating it into English. Here, I'm going to remove the e. There you go. Good. And now, this
standard value can be associated with several products. So here, I have, uh, from memory, two products that
are selected. There you go. If I select my modern value, I show you again,
I associate it and my modern style is associated with my two products to create values,
new values ​​in a new characteristic. So creating new
characteristics, how do we do it? Well, it's the same thing. You also have a plus button here.
So we're going to create, for example, a characteristic that I'm going to call, uh, the designer.
There you go, I validate. So my designer characteristic is created, selected here at the bottom.
All I have to do is create values, either personalized or, again, standard.
I'm going to create, for example, two values, one that I
'm going to call Ali's designer and another that I'm going to call, I do it twice, Leo.
There you go. Now let's suppose that I don't want to create new values ​​by entering them
manually as I just did, but copy the values ​​that were created in a
certain characteristic, create them in another characteristic without having to retype everything. Well,
I just have to select them, excuse me, select the characteristics into which I want to copy
. So I already have designer here. For example, I'm going to copy them
into style. So I also select style by doing a check. So, in fact, we have to
do things in the right order. We have to start by selecting the two styles, finally the
two characteristics. I'll get there. So designer, my source and style, my target. Then,
select the values. I select Léo and Dali. And here, you have a copy
/duplicate button. So this will copy these two values, let's say in the two characteristics,
but since they are already in designer, it will copy them only in style. I duplicate and
that's it. And you see, if I only go to style, I have my characteristics,
my previous characteristic values, and then here Dali and Léo have been added.
Now let's talk about deleting characteristic values, or even
entire characteristics. Now, I would really like to draw your attention. I almost want to shout to
wake you up because this is really a trap. Let me explain. Let's say I delete the
modern style here because I want to recreate it, modify another one, replace it with something else.
If I do this directly, that is, I take the modern style and I click on the minus
here, what will actually happen? So Merlin warns me but most people like me
don't really read the information in detail and will click delete. But what will
happen in this case? Not only will the modern style be deleted from the database
, but it will no longer be available for the products. And so all the products for
which the modern style was associated will lose this association and therefore will lose
the style characteristic. Look, I do it, I delete. Here, the button tells me to refresh
because the data is no longer synchronous. If I refresh, my two products also no longer have the
style. So, I can't tell you the number of times I've seen people who
deleted a characteristic value and ended up with hundreds of products
having lost the deleted characteristic. Well, not just the value but no longer having
the characteristic at all. So if you have to, if that's what you want to do, great,
that's fine. But if you simply want to replace one value with another, one value with another
, excuse me, it's better to select the value in question, for example, natural,
brand name here. And in fact, if you want to remove this term brand name,
well modify your value. Don't delete it to replace it with another. You delete it,
you rename it, you modify it and at that moment your products, all the products that are
associated with this value are modified but they do not lose the composition, they do not lose
the characteristic. So it's exactly the same for the characteristics themselves.
For example, let's take designer that I just created with Léo and Dali. I'm going to take Dali,
I'm going to associate it with my two Hauto products. There you go. If I delete my
designer characteristic with the minus button here and I confirm, well my two products, finally all
the products that had a designer property either, that is to say it is lost permanently.
This is also why sometimes it is better to create custom characteristics like
here the weight of 501 and 500 for the other product because if I modify them or delete them again
it only does it for one product. So here for example if I want to delete this value
501 and well I can do it. I just have to unassociate, I delete. So I have the first
product has lost its weight, but the second has kept its weight of 500 because in fact the
two values ​​are really unassociated because they are personalized. So a question
that comes up frequently is how to order the characteristics on your site? Well
in Prestashop you have a section called position that you see here in Merlin entitled
pause containing values ​​from 1 to the number of characteristics. Well it is this
number in fact this position which defines the display order. To change the display order of the
characteristics on your product page, simply use Merlin to click on the title
of the position column until you sort the rows here in ascending order of position and have this
little cursor here in the shape of a vertical V. Then take the values ​​you want
to move, for example, composition that I would like to put in second place here. So I take it,
I click here, I drag it and I release it. And so automatically, you see, Merlin
has recalculated the display order of each of the rows. Another method is
to sort automatically according to a given property, for example in ascending order
of ID or in alphabetical order of the name of the characteristics. So for that, I start by
clicking on the column that interests me. So for example, characteristic here, so in this
alphabetical order, I select all my rows. I go to the position column and I will
use a property of the Magic Edit tool to automatically recalculate these position values
​​here. So I click in the column, I'm going to choose Magic Edit in the entire column from
the menu. Magic Edit opens and I'm going to use the bottom tool which is called add index.
actually a sequence or a series of numbers and I'm going to ask it to count from
1 by incrementing from 1 to 1. Of course, I don't put a separator and I apply. So there, I made a
mistake, it actually added my series to the end of my content. So I'm going to cancel. In fact,
I forgot to start by emptying the content. So I choose delete the content.
Complete deletion. and my index addition setting that I reset to 1 and I apply. And there, you see,
I have my positions which go from 1 to 6 according to the alphabetical order of my characteristics and I
save and I close. To be really complete on this alphabetical order sort function,
I would have to show you a property, finally an advanced setting of Merlin. So,
I'm not going to show it on the bottom table, otherwise you won't see it, but I'm going
to do it on another column here at the top. Look, when I right-click in a column,
in the menu that appears here, so we have the magic edit function that I just used,
but here you have a new function called sort option.
which allows you to define how the sorting will be done when I click on the
column title. And in particular, you have functions like this one that allow you to take into
account the numerics within the strings. Because in a classic alphabetical order, well,
the number 10 comes before the number 2. And yes, in alphabetical order, 1 0 comes before 2.
Whereas if we really want to sort by taking into account the numerical order, then
you have to check this option. And you have other options here to ignore or
take into account accents, capital letters, spaces, and so on. So a whole bunch of
possible options so that when you click on the feature title, your rows are well
ordered according to the order you want. We're now going to talk about the concept of a bottom-up filter.
So, what does this somewhat barbaric term mean? At the beginning of the training,
I showed you that you could sort products by, for example, right-clicking in one
of the characteristic columns. For example, either natural filter on this column and equal
to either natural. And there, I have more than the products in either natural appearing with my
column filter visible here. So that's practical, it's quick, except that it requires first
displaying all the products and then once all the products are displayed,
which can be relatively long when you have a lot of them, you also have to think about displaying the
characteristic columns and finally setting this filter. So there is a much
faster method, especially when you have a lot of products, which we call bottom-up filters, which will
give us the same result. So I'm going to remove my pre-filter, or rather my column thread
here. There you go, delete all the column threads. And then I'm going to go to my bottom table
here in the characteristics tab and let's suppose that I want to see that the maxi dresses, okay,
these are the products that have the maxi dress property. So, I go to properties.
So first, I'm going to deactivate the display of the center here to show that we don't need it.
I'm also going to deactivate the display of the characteristics columns to show
that I also don't need it. So I remove it, I validate. The display is redone. You see,
I no longer have my characteristics displayed anywhere. So I come back to the bottom, I have my
characteristics table, I go to my property characteristic, I look for my value here which is called
Maxyob and you see you have a column here represents a blue filter. Well, I'm going to check
this box. So that tells me that I'm setting up a filter going up on this
characteristic and I'm even going to select two. I'm also going to take short dress. So
I take two characteristics. Here we also see the presence of a filter. Basically,
it's just an indication telling me that there are wires that have been put in place on certain
values ​​of the property characteristic. Now I just have to tell it to take
these filters into account to display my products up there, taking this filtering into account.
I have several ways to do this. Either I click here, you see, on this little icon to
display these options and click on the pre-filter option, it's called pre-filter up on
products or another way to click here on another pre-filter and click here on pre-filter up
from characteristic. It's exactly the same function. So I'm going to do it there. I click here,
I refresh and there I will normally have all the products that respect my bottom filter.
So what filter did I put that means I no longer have any products? But if I look
closely, I put a type E pre-filter. So I asked it to respect two properties. I'm going to
ask it to show me the products that have the short dress characteristic and the
maxi robe characteristic. Both at the same time, but I don't have any. In fact, I need to put the
property where. So in order for it to display the products that have either
a short dress or a maxi dress as a property characteristic. This time, I refresh. And there, I have
products. So, I have three. We'll check that these three products have one of these two
characteristics by displaying their value. There, it tells me that product 4 has a
short dress as a property. If I select all the products, property 5 is a maxi dress and product
6 is also a short dress. We can clearly see that these three products meet my condition. So,
once again, what's the point of doing this? Well, I can absolutely
select my entire site. So I go to category, all categories in
recursive mode, display, and the search is super fast because this ascending prefilter acts at the
SQL query level directly when searching for products in the database. And
so it only returns the three lines. Few Prestashop users know this, but
product features in Prestashop can be activated in one or more
stores when you are in a multi-store configuration. That is, a feature
can exist in one store and not exist in another store. And that's up to you to
define. So in Prestashop, it's very complicated to do. On the other hand, in Merlin,
it's very easy. In fact, if I go to the features table here,
I'm going to make a little space. So in the bottom table and I pull the horizontal scroll bar on
the right, you see four columns appearing here representing little houses
1 2 3 4 simply because I am currently in a four-store configuration.
And so for each of these four stores, I have checkboxes here indicating that
such and such a property, such and such a feature is or is not defined in such and such a store. And there,
I can in a very very simple way, for example, height, width and weight, define that
these characteristics are no longer available in shop 2 and shop 4. There you go,
in one click, it's done. Also note that if you click on pre-filtering,
here, you have an option that allows you to pre-filter on the selected shops,
that is to say, to display in the tables at the bottom here only the characteristics that are
associated with the selected shop, in the shop tab of the control panel. So,
I disconnected Merlin and reconnected it to a version of Prestash Shop in 174 to show you
the concept of multiple characteristics. Indeed, from version 173, Prestashop has changed the
behavior of the characteristics management in order to allow associating several values
​​of the same characteristic with the same product, which was not the case until now. in the
exercises we saw just before, you can go back and see each time we added
a characteristic with the button associated with a product, if this product already had a value of
This same characteristic, at that time, there was a replacement. Well, from 173,
it's different. This notion of multiple characteristics that you see here detected by Merlin,
it indicates multiple allows you to associate several values. I'm going to show what that gives here. So
I'm going to display finally select my products, display the existing characteristics. So
I see that there is already one for product number 10. Just select that one. There you go,
I'm going to display the characteristics. So here, we have a characteristic called frame size. I
'm going to see what we have in it. And we have several. We have materials. Okay? Currently,
this product has a lineage value characteristic. Well, if I choose, for example,
several characteristic values ​​like cotton and wool that I associate with this product, you
see that these cotton and wool characteristics have been added to those that already existed. In fact,
we can have as many values ​​of the same characteristic associated with a product as we
want. So this behavior is present by default on pressop 173. I repeat, it seems to me that
it can be deactivated. It seems to me that it's a parameter. I should check. In any
case, parameters can be adjusted in the back office. And for versions before this version of 17,
in fact, there were modules, like the multiple characteristic module from the
Presta module company, but there are at least two others on the Presta Adon website that do
the same thing. And all these modules are known by Merlin, which detects them automatically.
So from the moment you install a multiple characteristic module, you
end up with this type of behavior where, I repeat, the values ​​are no longer replaced but
are added to the list of characteristics of a product. When we display the
characteristic columns in the top table, I will do it by refreshing. A priori,
excuse me, in this configuration, I don't have them. So I go back to product.
I'm going to take, as before, one column per characteristic. That's it, to add them.
So I was saying when we display them in this table and a product has several values ​​of the
same characteristic, so we saw that our product had two, well we have two columns,
one per value. So why this behavior? It's completely normal. In fact, it allows you
then when we import to be able to import these two values ​​while having only one
line per product. We'll see that in a moment when we see how to import
characteristic values. So, let's now see how to import characteristics, that is to say, both
create new characteristics, create new values ​​and associate them
or not with products via import, so via a CSV or Excel file.
So, I'm not going to give a complete course on importing, that's not the goal,
but just show the specific part of the characteristics. So, I'm going to go quite
quickly over certain parts. So, I launch the import tool, you already know that. I'm going
to immediately create a new source that I'm going to call demo characteristic. I'm going to take this.
Control C just to copy it, reuse it later. There, I do as usual,
I'm going to look for a file and I'm going to take here characteristic words that I prepared
and I open it. There, my file is selected. I tell it that it's about product. Okay, the rest
I don't touch. I'm just going to show you the contents of the file. So, I do edit here
which opens the internal Excel file editor. So, here is the contents of my file that I
prepared in advance. I put two lines, one for the one line for product 1, one line for
product 2 with their number simply and then two characteristics, a composition and a height.
So, I didn't choose at random. Composition, it's a characteristic that already exists. Cotton
already exists. Leather doesn't exist. Height doesn't exist at all. So what I expect from the program,
This is to create the new composition. Value to cook to create a new composition, sorry,
a new one, excuse me, I'll get there, a new characteristic named height with two
new values, Arthur and Étienne, and to associate these four values ​​with my products 1 and 2,
close that, so step 2, we do as usual. I'm going to create a new model. I give it
a name out of habit, the same name as my source. I validate. It reads my file with my
different columns. Look what it did. Composition, it recognized it all by itself. Merlin knows
that there is already a characteristic called composition. So it did the mapping. It tells me
that it is an ID, a characteristic value that it has directly associated with the correct
characteristic, composition. And it suggests to me, finally, it makes it as a choice, as
anticipation, that it is a value inside the column and to write it if it does not exist.
That corresponds exactly to what I want, so I check it. For height, however, he doesn't know what
it is. That's normal, it doesn't exist yet. So I'm going to help him a little. So I'm going to create my
page myself and I go to the very bottom of the list. So you don't see. So I'm going to shift that,
hoping that this time you can see. There you go. So at the very bottom
here, the penultimate line, you have ID or value of characteristics. So I'm going to choose that.
Minimize. There you go. So ID or value of characteristics. In the list here,
I have the list of characteristics that already exist, so composition, paper, etc.,
but my height characteristic doesn't exist. So Merlin offered to create a new one
from the name. Exactly what I want. So it will take the title of my height column
to create a new characteristic. And then third choice, you have to tell it what
my column contains. It could be identifiers, it could be values, with the recommendation
not to create them if it doesn't exist. So use only the one that already exists or,
on the contrary, create them if they don't exist. And then the third choice is that it can also create
custom values. So we've already seen what that is. So product-specific values ​​that cannot
be shared between multiple products. So here,
I'm going to ask it to create them if it doesn't exist and I check them. And finally, well, this is
my key. So, it didn't recognize it, I hadn't named it correctly. I'm going to help it a little
by indicating that it's the product ID and I check it. That's it, that's it for step 2. Step 3,
well, I just have to choose my key carefully here. Since I've just mapped a section containing
the product IDs, by default, that's what I'm going to choose. Identifier, I could have put
another column with the references, supplier reference or barcodes. As usual,
I click on display. He confirms to me that these two products 1 and 2 do indeed exist. And look
what he did. The composition characteristic here is in gray. That means it
already existed. On the other hand, this one is written in green. That means he just created it for me and he
gave it the number 6. The database gave the number 6 to this new characteristic. In
the columns here, I have the values. So, if they already exist, they are indicated in black with
their number. If they don't exist, they are indicated in red with a question mark.
So, a priori, he didn't find any. So, I admit that I expected him to
find the cotton characteristic. Probably in the database, it's not written exactly
like that and for him it's a new characteristic. So we'll let him do it,
we'll check later if he's actually right or not. So I select these two lines. I'm
going down to step 4. So in step 4, I'm not going to do much. I'm not going to ask it
to create the products. I don't have any imported images. So basically, I don't have to touch anything. If you want
For more information on all these options, I invite you to watch the import tutorial.
That's not the purpose of this one. And finally, step 5. All I have to do is click on either import
or schedule the import to do it later or to do it repeatedly
and schedule it for a given date. So I'm just going to import now.
So the program launches, it tells me that it has updated the two products 1 and 2. There you go.
So we're back in the main window. So we'll immediately see our two products
1 and 2. So here they are. So take a good look. Indeed, in my product 1, I have
a cotton composition, an author Arthur for the 2 leather and Étienne. And we can see that it
has created a new characteristic called height with two values ​​Étienne and Arthur. And
then in composition, I have leather which has been created and cotton as well. Indeed, I didn't have a
cotton composition. I thought that was the case. Quite simply, I had confused it, I think, with
frame size. There you go, which actually contained a cotton value. But in composition, I didn't have one
. So, it created my four values ​​as requested and it
associated them with my two products. So, if I quickly go back to the import with this little button here,
I'll remind you of the trick. We see here that in the import table, in addition to giving me the information
that it updated the products, in fact, we see that in the lines, it replaced the
values ​​in red with values ​​in green like cotton Arthur and the question marks with
the number of the characteristic values ​​that it created. So just a little other information.
If we go to step 4 here, you see here it's grayed out because it's only
informative and it's checked. It tells me that we are in operation, uh, how can I say
multiple characteristics because actually, I have just imported into my site which is
still in inversion in sorry in version 174, so configured in multiple characteristics.
So if I import several values ​​of the same characteristic, for example, several compositions
in the same product, well, these values ​​will be added. They will not be replaced,
they will not replace each other but will be added, accumulated. If I want to avoid this behavior,
I just have to check this option here, replace rather than add. There you go. So when it is checked
here, I will end up with the old operation typically of version 16
where the values ​​replace each other where a product can only have one value of the same composition.
If you want to import several values ​​of the same characteristic to a product,
you just have to multiply the columns. So for example, if you want to give two
different compositions to the same product, you put two columns with different values
​​of composition characteristics. But be careful, you really have to give them a
different name for your columns, eh. You can't have two columns called composition,
it won't understand. So in this case, you have to name one composition one and the other composition
2. And at your step 2, obviously since the name won't correspond to a
given characteristic value, it won't do the mapping automatically. You will have your
composition one and composition 2 and here it will probably mark something as new to create,
doesn't understand what it corresponds to. At this point you will have to help it simply tell it for the two
columns to map them to the composition section. There you go. So you do that twice in two
different columns again with different titles and you can thus import
multiple characteristic values. So either on condition of being in 73 at least or by
having installed a multiple characteristics module. So there you go importing
characteristics. It's not very complicated with Merlin. You just have to think about the fact that you have to
put each characteristic in a separate column, like here composition or height. If
I want to put two compositions and well it will need a third column with a different name and
map them to the last one finally the penultimate one, excuse me, uh here property in the list
which is called ID or characteristic value. Then, either ask it to create a new one
if it does not yet exist, or to use a characteristic already existing in the list and
then define whether or not it should create the new values. You can also update
product characteristics by having columns that contain only the numbers,
the characteristic identifiers, finally the values ​​of existing characteristics. In this
case, you will choose identifier here. If you make a mistake, if it contains identifiers and
instead you put value, in fact, it will not understand more exactly, it will execute what
you ask it. That is to say that it will create as value the numbers of the characteristics that
you put in your file. So it will not be the expected result of course. There you go,
this part on importing ends uh this training on characteristics.
I hope I've been thorough, otherwise I'll definitely add more sections. Thanks and see you soon.