Agree completely! Seeing that authorize.net will not process any transactions if the address entered doesn't match the card. Shipping address can route to shippo (or however routed) and billing can route to processor. The only option currently is to remove fraud detection and thats a really risky move with chargebacks and identity theft on the market currently. Seems like it could be an easy addition to the checkout page. Looking forward to it soon.

Agreed! And shipping should also have an option to be replaced or combined with "Pickup"

ASAP! I want HL to be my main CRM database, not a combination of HL and Quickbooks.

Yes, please! :) Thank you.

I'm talking to someone on Monday about just this thing. Currently, the shipping address on the ecommerce form overwrites the initial contact's info.

Anyone trying to take on a client who ships is ruined right out of the gate because of this obvious issue with the design. All they have to do is allow the contact to store the shipping information separately (within the contact) and it's a win.

Amazon will store several different shipping addresses within an account/contact, which can be pulled up for repeat delivery.

What gives High Level? As it is, I don't dare reach out to another client until this is resolved.

This is so critical! I wonder why it's taken so long for this to be requested to be included? Such an important differentiation, billing vs. shipping address...