Attribute Sets: pros & cons of using a few broad ones vs many specific ones?
Is it better to have a small number of very general Attribute Sets or a large number of very detailed Attribute Sets? Why?
Obviously it depends on a lot of factors (eg: the number of products, how much those products differ from each other, how we choose to use attributes, etc).
Say I had 10,000 SKUs and they were all t-shirts, maybe I would only need one Attribute Set. But if I had 10,000 SKUs and they included t-shirts, hats, headphones, skateboards, bed sheets, bicycles... would you just have one Attribute Set for each of those broad product types? Or would you, for example, have one Attribute Set for mountain bikes and another for road bikes and another for kid's bikes?
Any opinions welcome. Thanks!
attribute-set
New contributor
add a comment |
Is it better to have a small number of very general Attribute Sets or a large number of very detailed Attribute Sets? Why?
Obviously it depends on a lot of factors (eg: the number of products, how much those products differ from each other, how we choose to use attributes, etc).
Say I had 10,000 SKUs and they were all t-shirts, maybe I would only need one Attribute Set. But if I had 10,000 SKUs and they included t-shirts, hats, headphones, skateboards, bed sheets, bicycles... would you just have one Attribute Set for each of those broad product types? Or would you, for example, have one Attribute Set for mountain bikes and another for road bikes and another for kid's bikes?
Any opinions welcome. Thanks!
attribute-set
New contributor
add a comment |
Is it better to have a small number of very general Attribute Sets or a large number of very detailed Attribute Sets? Why?
Obviously it depends on a lot of factors (eg: the number of products, how much those products differ from each other, how we choose to use attributes, etc).
Say I had 10,000 SKUs and they were all t-shirts, maybe I would only need one Attribute Set. But if I had 10,000 SKUs and they included t-shirts, hats, headphones, skateboards, bed sheets, bicycles... would you just have one Attribute Set for each of those broad product types? Or would you, for example, have one Attribute Set for mountain bikes and another for road bikes and another for kid's bikes?
Any opinions welcome. Thanks!
attribute-set
New contributor
Is it better to have a small number of very general Attribute Sets or a large number of very detailed Attribute Sets? Why?
Obviously it depends on a lot of factors (eg: the number of products, how much those products differ from each other, how we choose to use attributes, etc).
Say I had 10,000 SKUs and they were all t-shirts, maybe I would only need one Attribute Set. But if I had 10,000 SKUs and they included t-shirts, hats, headphones, skateboards, bed sheets, bicycles... would you just have one Attribute Set for each of those broad product types? Or would you, for example, have one Attribute Set for mountain bikes and another for road bikes and another for kid's bikes?
Any opinions welcome. Thanks!
attribute-set
attribute-set
New contributor
New contributor
New contributor
asked 16 mins ago
deanosaurusdeanosaurus
1
1
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
deanosaurus is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f258298%2fattribute-sets-pros-cons-of-using-a-few-broad-ones-vs-many-specific-ones%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
deanosaurus is a new contributor. Be nice, and check out our Code of Conduct.
deanosaurus is a new contributor. Be nice, and check out our Code of Conduct.
deanosaurus is a new contributor. Be nice, and check out our Code of Conduct.
deanosaurus is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f258298%2fattribute-sets-pros-cons-of-using-a-few-broad-ones-vs-many-specific-ones%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown