Currently there is no consistent way to pull the delivery address from the order.

Comments

jdelaune’s picture

jdelaune commented

I'm surprised there isn't a 'delivery address' customer profile which gets created by the shipping module or similar. Then we could have a setting where users get choose which customer profile the delivery address is pulled from (Billing Information by default).

I can't even see where you add new customer profiles...

ikos’s picture

ikos commented

Whilst it's easy to set up a new address field for the customer profile, what I am not sure about yet is the "right way" to do it.

You're right in that it could be included in the shipping module.

I'll seek some guidance from CommerceGuys on this one.

jdelaune’s picture

jdelaune commented

I think the commerce shipping module now has a standard place to find this. We should try and use this and fall back to the billing address otherwise.

ikos’s picture

ikos commented

I am not sure that Commerce Shipping has actually stabilised on this yet.

RIght now, I have been adding a new customer profile type as a patch to Commerce Shipping on my projects - I think it's the right way to go and it seems to work well.

I'll have a word with @googletorp to see if there's agreement.

jdelaune’s picture

jdelaune commented

The latest dev of shipping does have a shipping address field as standard. But feel free to talk with @googletorp

fonant’s picture

fonant commented

Agree that delivery/shipping address, if required, should come from commerce_shipping, which now provides this. Pleased to see that this module defaults to the billing address otherwise, as my site has non-shippable items for purchase :)

ikos’s picture

ikos commented

Now Commerce shipping 2.0 is out and in use, we will be implementing shipping address support as discussed in this thread.

Stay tuned!

ikos’s picture

ikos commented
Status: Active » Fixed

Latest Dev version will have support for shipping address when using Commerce Shipping 2.x

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.