What are the integration requirements for Cylindo?
Apart from the technology requirement, you will also need to know the SKU codes, Features and Feature codes for each of your SKUs in order to be able to implement them on your live website. It is very important that these codes are an exact match between your system and ours, otherwise the Viewer will not work. You can find the SKU and feature codes for each SKU in the Cylindo CMS, or you can export them as .csv files from the CMS on a per-SKU basis, or export .csv’s for multiple SKUs together. If you, at any point, make any changes on your end that affect the SKU and feature codes, you should make sure to inform Cylindo about this so we can match those changes on our side to prevent the Viewer from breaking.
Can we pass unique SKU codes per variant?
At Cylindo we strive to make a process that is easy for our clients and works across all ecommerce platforms. We do not maintain one SKU code per variant because for a number of our more complex SKUs, you would be maintaining potentially millions of codes. To simplify the process, we stick with one SKU code and apply the feature codes that you will provide to us for each SKU. The feature array that is constructed like this is a unique “identifier” when it comes to a specific configuration that is called. If you, however, would like to map individual SKU configurations into separate SKU codes, you can do that mapping on your end, even though we envision it to be a difficult process and we do not recommend it.
Can I change my SKU Codes & Feature Codes on my end?
We are currently working on a process where this can be managed within Cylindo’s CMS platform but until then you can make changes by contacting your Project Manager or firstname.lastname@example.org. Here, for SKUs that are already live, it is important that this is aligned on your end and on Cylindo’s end so that the update in codes happens almost simultaneously, in order to avoid breaking the live Viewer.
Can I see an example of how feature codes are passed to Cylindo?
Do the SKU and Feature Codes need to be an exact match to what the customer/end user sees on the webpage?
In terms of exact match, it is important that your system and our system are an exact match when it comes to the SKU and feature codes. They do not necessarily need to be the same codes that you would display on the front end of your website/product pages, but they do need to exist somewhere behind in the website code (even if not visible) so they can be used in the initialization and configuration changes that occur on the product page.
Can we use the same code for different features on the same SKU and across SKUs?
On one SKU, you can have the same feature code if it’s associated with different feature types. E.g. for the feature type “Upholstery” you can have a code “blue” which can also be used for another feature type, e.g. “Pillows”. However, within the same feature type, you cannot have the same code. E.g. “Upholstery” as a feature type, cannot have two exact same codes “blue”, because in those cases, the Viewer has no way of recognizing which one you are calling.
The same applies across SKUs - “blue” can be the feature code for multiple different feature types across multiple SKUs.
Can we have non-graphical features on a SKU?
Non-graphical features can represent anything that’s not visual or represents a dependency between other features, which might be needed for integration purposes but would not affect the function or appearance of the Viewer. You can ask your Project Manager for help if you would like Cylindo to setup some non-graphical features for your SKUs.
Where can I get an overview of the Feature Types & Codes we use?
You can find these in our CMS platform. When you preview a SKU in the CMS and you look through the options available for that SKU, you can see the feature code for each option just below the option name on the right-hand side panel. An alternative would be to download a CSV file with all the SKU options and features, which you can also do from the SKU page.
What if the SKU does not have any options or variants, do we need to use feature codes?
Yes, you will still need to have the default feature codes available in the initialization object. Otherwise, the Viewer will not know which parameters the SKU is comprised of, and will not be able to send the correct content to be displayed.
Can we set a default set of features for a SKU?
This is currently not available, but Cylindo is working on the development of this functionality which is expected to be released with the next Viewer version, within Q4 of 2019.