Looking for ideas on how to implement a solution in Actinic.
I have around 300 base products i.e
FT1001
FT1002
FT1003
.....
And these are ordered differently i.e.
FordFT1001
FordFT1002
HondaFT1001
HondaFT1002
HondaFT1003
This produces around 1500 products which can be ordered.
The products have attributes: Name, Length, Width, colour and a customer might not know all the attributes.
My thoughts are to build a front end search application with backend mysql tables which will narrow the product selection down and then do an external add to the Actinic Cart.
I am not sure what is the best way to hold the information in Actinic. Have the base products and then have duplicates. I would also want to automate the process of building the Actinic tables as I do not want to type hundreds of duplicates if at all possible. I also want to see Fordxxx not just the base product on the invoice.
Any help appreciated.
I have around 300 base products i.e
FT1001
FT1002
FT1003
.....
And these are ordered differently i.e.
FordFT1001
FordFT1002
HondaFT1001
HondaFT1002
HondaFT1003
This produces around 1500 products which can be ordered.
The products have attributes: Name, Length, Width, colour and a customer might not know all the attributes.
My thoughts are to build a front end search application with backend mysql tables which will narrow the product selection down and then do an external add to the Actinic Cart.
I am not sure what is the best way to hold the information in Actinic. Have the base products and then have duplicates. I would also want to automate the process of building the Actinic tables as I do not want to type hundreds of duplicates if at all possible. I also want to see Fordxxx not just the base product on the invoice.
Any help appreciated.
Comment