Hey everyone, My company does a lot of drop s...
# suitecommerce
m
Hey everyone, My company does a lot of drop ships. Each order is going through a CSR prior to being sent to shipping to be fulfilled. We'd like to automate the ordering process so it doesn't have to go to a CSR first. Our issue is that Netsuite doesn't seem to differentiate between Billing and Shipping addresses. We'd like the billing address to be the default customer record address and the shipping to be where ever it's being sent to. I've been doing a lot of research and this seems to be an issue with Netsuite. Every time someone places a drop ship the address they enter changes the address in the customer record. Does anyone happen to know of a workaround or maybe a 3rd party extension that can add this to Netsuite or override the default behavior?
s
I believe the workaround people use for this is to write a script that tracks the billing address throughout the checkout wizard (eg with scriptable cart) and resets it once the user submits the order
m
Wouldn't this be pretty taxing on the system if multiple orders are coming in all at once?
s
I've not written it before but I don't see why. Why do you think it would?
m
The script would be be running constantly if a lot of orders are coming in all at once. That would seem to me that it might cause some slowing having the script running multiple times at different points.
s
OK, I'm inclined to disagree, assuming we're only talking about web orders here. I think you would write it so that it when a shopper starts checkout, the script stores the current billing address as a session object. Then it goes idle. It's then set up to listen for address changes -- if it was a specific billing address change, then let that go through and update your session object. Otherwise, do nothing. Then onsubmit, compare the two -- if it's 'wrong' change it
You could probably even do the address change after submit, so let the order go through and then change it asynchronously
We're talking about a small number of triggers, and even then only PUTing a single address object on one record, right? I think that's a pretty low performance cost.
But, like I said, I've not written one before so I don't know for sure
a
fully agree on this, implemented correctly this should not be a performance concern
m
I think you might be right. I can always try it and test in sandbox. I should also note that when I say "billing address" I'm talking about the default address in the customer record. That seems to change each time with a drop ship. We want the customer default address to never change when a drop ship is placed.
s
OK, workflows might be able to cover that as well
m
Do you have any think I can see for that? I didn't think workflows could be used on sales orders or addresses like that?
m
Thanks!
n
@Steve Goldberg is a recording of the webinar still available?
s
If it's not there then I'm guessing not