Messages

PaymentInterface should be in konakart_custom.jar .

It only allows you to add customers who have or haven't made an order for a certain time period.

In the Enterprise version of KonaKart there are customer tags and an expression builder that allow you to finely tune which customers can use a promotion based on the values in the customer tags for each customer.

You can edit the promotion module to add the id to a custom field.

You have full control over the order statuses of a KonaKart order. They are stored in a database table and may be managed through the admin app under Localizations >> Order Statuses. Although during installation we populate the database with a typical set of statuses, it's normal for our customers to add others and modify them to match their specific workflow.

In our demo storefront application, an order when first saved is put into the Pending state or the Waiting for Payment state . You can see how these are set in CheckoutConfirmationSubmitAction.java. Then an order may enter the Payment Received or Payment Declined State (normally set by the payment gateway module). Once payment has been received it typically goes to the Partially Delivered or Delivered state. OTB there are also states for managing refunds.

The Order Integration Mgr ( http://www.konakart.com/docs/OrderStatusChangeActions.html  ) or AdminOrderIntegrationMgr are the classes where you can add your own code to interface with external systems whenever the state of an order changes or when it is saved .  Once the order management has moved outside of KonaKart (e.g. an ERP system) the external system should use the KK APIs to call back into KonaKart to keep the state updated so that the customer always sees the latest information after logging in to the storefront application. 

Yes, the tier prices only apply to the main price of the product and not to the option prices.

I would just follow the steps we take in the example code under KonaKart\java_api_examples\src\com\konakart\apiexamples . Look at InsertOrder.java .

You should check your shipping address and see if it lies within a tax zone.

All you need to do is to create an action class very similar to ShowProductDetailsAction.jsp where you pass it the SKU rather than the product id. The action class can use the getProductPerSku() API call to get the product.

I don't understand why you don't just follow the example all the way to where it gets the order totals for the order which is before it is saved.

Code Select Expand


       /*
         * Now that the order has been completed with all necessary information we can ask the
         * engine to calculate the order totals. We send it the order and receive back the same
         * order which includes order totals that the customer may check before confirming.
         */
        order = eng.getOrderTotals(order, DEFAULT_LANGUAGE);


You can get a product by SKU if that's what you're asking.

You should always use KKEngIf and not the individual managers.

Take a look at InsertOrder.java under java_api_examples\src\com\konakart\apiexamples which shows you how to create an order and get the order totals which include the promotion.

I couldn't reproduce either of these problems after a fresh install.

The full source code of the storefront application including the KonaKart client engine, the Struts action classes, the JSPs, the payment modules, order total (including promotion) modules and shipping modules are included in the Enterprise Edition of KonaKart.

The Community Edition includes all of the above except the source of the client engine.

Sort order is for sorting the categories so that they display in the order you want them to display.

If you are new to KonaKart, I would concentrate on understanding the APIs following some of the examples in the java_api_examples directory and by looking at the storefront action classes.

I'd say that a good approach is to maintain dev, pre-prod and production environments and to use database tools to easily move data between the databases and scripts to move the webapps.

• Use the installer to install KK with the demo database in a development env.


• Remove demo products and add your own. This may involve writing an importer against the KK APIs if you have 1000s of products and you want to automate the process.


• Customize KK to match your requirements and styling. e.g. Make your modifications to the storefront app, configure / add payment and shipping modules, modify eMail templates etc.


• Do some load tests and user acceptance tests before going into production.