Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Create attribute view groups to define product parameters relating to a common concept. For example "Audio" view group defined for "Laptop" product type can consist of "Audio system", "Built-in microphone", "Number of built-in speakers" which would give a complete view on the audio capabilities of a particular laptop.
  • Create searchable attributes. Most manufacturer provide very detailed product information, which works very well when there is a limited set of products. Once we get into thousands of products much of the information starts to overlap and introduce a lot of "noise", which makes searching for specific products difficult. This is especially true for attributes such as product descriptions. For example consider a phrase "this will look nice with our red hand bag" for a "dress" specified in products's description, which would make this "dress" a part of "hand bag" phrase search or "red" colour. This is not necessary wrong (in some use cases) but in general can leave customers puzzled or even annoyed to see dresses in their searches for hand bags or a dress in a different colour. This is is why YC allows to specify exactly, which attributes should contribute to search thus providing only clean and relevant keywords.
  • Create navigatable attributes. Some parameters are very important to customers purchase decision making process and thus we put emphasis by configuring them to be part of the navigation menu. For example "CPU speed" or "laptop screen diagonal" could be much more influential factors than "number of USB ports" for a "Notebook" product. In order to place those into attribute navigation all is needed is to select a checkbox in product type attribute configuration.
  • Provide comparable views 
    Label
    BodyYCE
    Colourinfo
    . Once the product type views are configured it is trivial to present information to the user showing key differences by listsing comparable parameters side by side.

...

Once the product types are configured in the system, admin users can simply import product data or manage it via editors within Admin app.

...

  • SKU has to have inventory record in fulfilment centre available to the shop (i.e. this shop has this item in its inventory)
  • SKU has to have at least one price record defined for the shop (i.e. this shop offers this product at a given price)
  • Product has to be available in a shop category (i.e. this shop can display this product from its category menu)
  • If all of the above holds true after product index is build the products will appear in frontend.

...

Full text search index holds all this data combined together is scope of a shop and makes it available the customer to see.

Detailed documentation

 

  It

Tip
It is highly recommended to start with product type configuration overview to gain understanding into how product information in made available to the storefront and which part thereof affect specific functional areas.

 

Children Display