Shipping information tickbox

Is it possible to have the shipping information automatically populated with the billing information on the checkout page rather than using the tickbox.

Then add a comment to amend the shipping information if necessary.

this would require hand coding of the checkout form. you would need to add an onblur event to each of the billing fields to update the corresponding shipping field using javascript.


for example, the first name would use this code:

<input type="text" name="firstname" id="firstname" value="" onBlur="document.ecart_checkout_form.shipping_firstname.value=this.value"/>

select lists are a little different, for example the state list would look like this:

<select name="state_province" id="state_province" onChange="document.ecart_checkout_form.shipping_state_province.selectedIndex = this.selectedIndex">

After checking with the client I tried the following method first.

Added spry validation to the shipping fields on the checkout page.

This prevents a customer moving to the confirm page until the shipping fields have been completed.

All was working well with a completed successful test purchase.

However during testing when submitting the checkout page and moving to the confirm page and then aborting the test I found that the order details were being stored in the orders table.

I've not noticed this orders table update happening before I added the spry validation to the shipping fields on the checkout page. This page doesn't have the "store summary in database" behaviour like the confirm page.

Should this be happening or is it as a result of the addition of the spry validation?

What gateway are you using?

this will happen with paypal standard as a result of the way paypal standard works.

Ok, its Worldpay.

Like paypal standard, worldpay is a remote payment gateway.

using a remote system the confirm page posts to the gateway server, so the order information is stored when the checkout posts to the confirm page instead.

Ok thanks, I presume there is no simple alternative to this.

Not sure how big a problem this is going to be for the client, it obviously depends on how many customers abort a payment after submitting the checkout page.

Is there a workaround or is it a case of this is the only way the system can function?

So that I can explain to the client can you give some more information about how different payment gateways operate with the extensions.

I'm also curious to know how the checkout page does the database update.

this is the way that remote checkout systems function. With a remote checkout system, the checkout page sends data to the confirm page, and the confirm page sends the data directly to the gateway for the customer to place the order.


In a local payment system, the customer never leaves your site, the checkout page post to the confirm page, when the confirm page submits, it runs code to process the transaction, then if it is successfull stores it in the database and sends a confirmation email, if it fails, it directs to the failure page instead.