Difference between revisions of "Talk:Sponsored Development: Shipping Integration"

Latest revision as of 06:31, 4 July 2007

Suggestions

We have implemented this feature (on the webstore) using the following logic :

Based on delivery address (Zip code and Country) and order weight

• find Delivery Mode records matching the country
• find Delivery Mode records matching the city
• calculate cost for each delivery mode based on weight
• display option for "Express delivery" with lost "Sort" (if available)
• display option of "Normal delivery" with lost "Sort"
• if no price is found, display "manual price option"

Structure of Window :

Let me know if this is of any interest --ALP 14:09, 3 July 2007 (EDT)

Questions

Hello Alain, and nice to have you on board!

I am wondering about the source of your data for this model:

Is this a table structure to be built in ADempiere? Or a model to collect data from webservices?

Either way, where does the source data come from?

jsSolutions 20:16, 3 July 2007 (EDT)

Hello, happy to be on board ! This table structure has been implemented in Compiere. We use it to set the price schedule for delivery options. The actual implementation has been done in the Webstore where delivery price is automatically calculated according to this schedule. In fact the price of the Article 'delivery' is automatically adjusted depending of qty / weight / destination / delivery option. It was a bit easier to implement in the webstore than in Java Client because the "check-out" process is linear. To implement this logic in the java client, we need to recalculate delivery price everytime one of the following events happen : - delivery address is modified - a line is modified (qty or product) - the delivery option is changed

In the java client we could have the delivery cost managed either (in order of my preference): - in a new tab - in the order header - as a line

--ALP 09:31, 4 July 2007 (EDT)