We are currently looking to update our site with new product data but it’s a proving a bit tricky!
We sell kitchens online and have a range of kitchens available to purchase in a number of styles and finishes. Where we offer a cabinet product, for example a base unit we offer the appropriate door in the size and quantity required and have done this through associating the cabinet product with the appropriate fascia located in another section of the store.
The downside of offering the product in this manner is we have to add an instance of the cabinet data for every range of doors we sell in order to make an association with a specific door product. We have over 1000 individual cabinets and over 60 door ranges so this makes for a lot of data inside actinic and as you would expect performance of the application has suffered as a result.
This entire section of our website over 50k product lines was created through hierarchical file import right down to picture paths by parsing 2 different suppliers data to provide an import file which was 28mb alone! Understanding how this file has been generated is beyond our capability and it seems many of the developers we have spoken to.
Our website is in desperate need of an update in order to maintain a competitive edge and to make things a little more difficult the company that created the import file for us is no longer in business. I do want to stay with the Actinic especially as v9.03 is on the horizon which hopefully will cure some of our other woes but it seems we are being faced with a commercial decision to make on the platform on which we base our future ecommerce activity.
I’m hoping this post will prompt a little advice from some of the more experienced members of the actinic community there may be a more efficient way of offering the product which will do away with the hierarchical file method but offer the same functionality.
Apologies for the length of this post and any advice greatly appreciated.
We sell kitchens online and have a range of kitchens available to purchase in a number of styles and finishes. Where we offer a cabinet product, for example a base unit we offer the appropriate door in the size and quantity required and have done this through associating the cabinet product with the appropriate fascia located in another section of the store.
The downside of offering the product in this manner is we have to add an instance of the cabinet data for every range of doors we sell in order to make an association with a specific door product. We have over 1000 individual cabinets and over 60 door ranges so this makes for a lot of data inside actinic and as you would expect performance of the application has suffered as a result.
This entire section of our website over 50k product lines was created through hierarchical file import right down to picture paths by parsing 2 different suppliers data to provide an import file which was 28mb alone! Understanding how this file has been generated is beyond our capability and it seems many of the developers we have spoken to.
Our website is in desperate need of an update in order to maintain a competitive edge and to make things a little more difficult the company that created the import file for us is no longer in business. I do want to stay with the Actinic especially as v9.03 is on the horizon which hopefully will cure some of our other woes but it seems we are being faced with a commercial decision to make on the platform on which we base our future ecommerce activity.
I’m hoping this post will prompt a little advice from some of the more experienced members of the actinic community there may be a more efficient way of offering the product which will do away with the hierarchical file method but offer the same functionality.
Apologies for the length of this post and any advice greatly appreciated.
Comment