Messages

Konakart supports various forms of merchandising:

Display what other customers have ordered with the current product shown.
AND
For every product you may define a list of products for:

• Up-selling


• Cross-selling


• Accessories


• Dependent products (e.g. Service Plans or Extended Warranties)

Go to http://www.konakart.com/konakart/SelectProd.do?prodId=9 for an example of cross-selling in the "Products Similar to this one" tile.

Yes. The category tree is cached. The refresh interval is set in the Admin App, Configuration>>Cache. The default is set to 600 seconds (10 minutes ) .

It looks like the problem is that it doesn't detect the SKUs as being the same. Therefore instead of doing an update it tries to do an insert which fails because there isn't enough compulsory data.

We have a "Global" product master that has all of our products in it (all invisible) and then a specific product master for all of our customers that has their model number and pricing.  In the customer specific import we only have a few fields (but SKU is one of them).  The idea was to have the import just update these particular fields, but it's not doing that.  Any ideas?

I don't understand what you are attempting to do. Does it follow the logic I posted earlier regarding the matching of the id, sku etc. ?

Well, if it used to work and now doesn't work, I'd try and figure out what has changed.

You could merge the files before doing the import. That way you have full control over the merge.

Yes the SKU lookup could be failing if it doesn't match precisely. i.e. If there is an extra space character somewhere.

The logic is as follows:

• If you have an id, this is guaranteed to be unique so it searches for a product with the same id and if it finds it, it does an edit.
  


• If you don't have an id, it searches for an SKU and edits the product if it finds only one with a matching SKU. If it finds more than one, it throws an exception.


• If it can't find a matching SKU or matching id it does an insert.

You should try debugging SetLocaleAction.java to get some clues.

This isn't possible using the import / export tool. The way to do it would be to write your own loader for the options using the Admin API.

Yes, you can do this by editing the ActionClasses and the StrutsConfig file. Many of the Action classes already check for being logged in and forward you to the login page if you aren't:

           custId = this.loggedIn(kkAppEng, "CheckoutDelivery");

            // Check to see whether the user is logged in
            if (custId < 0)
            {
                return mapping.findForward(loginForward);
            }

You will have to implement this in all of the action classes and ensure that in StrutsConfig.xml you have defined the forwards.

Just export into a text file and import that into Excel.

Hi,

You could use a custom field on the product object to define this type of product. Once you've done this, you will have to modify the relevant action classes / JSPs to stop a customer adding these products to the cart and to display a "Call Us" message etc.

Hi,

Take a look at com.konakart.bl.OrderIntegrationMgr.java which is where the digital downloads are added:

              for (int i = 0; i < order.getOrderProducts().length; i++)
                {
                    OrderProductIf op = order.getOrderProducts();
                    if (op.getType() == ProductMgr.DIGITAL_DOWNLOAD)
                    {
                        if (productMgr == null)
                        {
                            productMgr = new ProductMgr();
                        }
                        productMgr.insertDigitalDownload(order.getCustomerId(), op.getProductId());
                        numDownloadsCreated++;
                    }
                }

Since you have the source code for it, you could add other products that are related to the one in the order. i.e. You could have a bunch of products in a category which you never display and add these to the digital download list based on information that connects them to the product in the order.

The idea behind this is that you can store whatever structured data that you want so that you can compare it. e.g.

<?xml version="1.0" encoding="UTF-8"?>
<mobilephone>
   <radio>no</radio>
   <camera>yes</camera>
   <num-colors>65536</num-colors>
</mobilephone>