Open adominguez85 opened 8 years ago
been there, done that, and solved thanks to... you guys.
How can you be having a problem when I solved it by seeing your guys pof file?? I'm sure I even told Phil how excited I was to see it was fixable. Nothing like shipping an express order to someones old address when they clearly entered the correct one.
Do you have more than one pof report? are you generating a different one based on full service/pro? Maybe you have it implemented in one and not the other?
They key is what Alex said - letting LW use the account address as the ship to address is really bad, any time someone moves you will ship to the old address on the first order - the 2nd order and any others will be correct, it is just the first one that is wrong.
No need to no the 'needsshippig'. In the pof report where the shipto fields are, you have to do logic to check if it is dropship or normal ship, and then populate them based on which it is. I bet for whatever customer type this happened to you only had dropship logic in there - it needs to be both. The shipto fields have to be populated no matter what if it is shipped.
I am almost postive one of your reports is correct, because I saw it in there when Phil sent a copy of your report to me.
I just found the emails I had with Phil, I had a problem initially with doing it the way we do now because anything in the shipto was triggering a dropship work order - so a normal ship order printed a drop ship order. This was fixed when LW added a Dropship: yes/no flag.
Check your pof file or with Alex and see if your system has the update that allows that attribute in the pof file. If it does, then you should be able to solve it.
Here are my notes: https://github.com/rdyar/LabWOES/issues/24
Hello Ron,
I was wondering if you could shed some light on an issue we've been having with some of our shipping orders getting sent to the wrong address.
Basically, when an existing customer orders through ROES as a NEWUSER, Labworks looks to see if that customer has an existing account, which in this case, he does. This particular customer selected a Ship To Billing Address option (Standard US Mail). When the order came through to Labworks, his account's billing address information was automatically updated because he specified a different address than what was on his account, it left the shipping address information set to the prior address, and the order shipped to the prior address, as opposed to the updated address.
Alex with Lablogics has said that this happens because the Ship To pof fields are not populated. I've found that the only way to populate these fields is to add a "needsaddress" attribute on the shipping option in ROES, exactly how we have it set up for our Ship To Alternate Address option. Now, this does not actually appear to update that shipping address information in the customer's account area, but rather just updates the shipping/delivery address information from which our Barcode Scanner pulls and generates a shipping label.
Phil wanted me to reach out to you and see if you have a solution for our issue; possibly something that I'm not aware of, as your system seems to be functioning similarly to ours. Thanks for your help on this! Let me know if you need additional clarification.
Amanda D. Digital Pro Lab