New Customer Location inherit Entity Usage type and Exemption from Default Location

​@kyle90 , it’s probably not the answer you’re looking for, but I don’t think you can accomplish what you are asking for, without a customization (either to how the location is created, or to the way the import from BigCommerce works). The easiest solution would be to disable Customer Locations sync altogether. Unless you must have customer locations stored in Acumatica, of course. In my experience, there aren’t too many reasons to have the locations synced. If you had the locations disabled, you would only keep the MAIN location, and since you set up Exemption Number and Usage Type on the customer level, all subsequent orders would use those settings.

That’s an interesting approach - I’ll need to test a bit and see if there are other downsides or issues from the rest of the team. But so I understand - if we disable syncing the Customer Locations entity and a customer places a new order online with an updated address (or even a slight difference in the formatting of their address) how does the commerce connector handle this?

 - Are the details of default address updated?

 - Does the system somehow know to override the address details (or is this configured somewhere in the commerce connector?)

Or does the order import and ignore the BigCommerce address and use the details from Acumatica? This would obviously be a no-go

Appreciate the thoughts! 

​@kyle90 , thanks for your questions!

1. If the client updates their default address in BC, it will be updated in Acumatica. But for all other locations - there will be no effect in Acumatica. If they update their second, third locations, etc., those changes won’t be imported into Acumatica, since there won’t be any second, third, etc. locations.
2. Address details on the order will be overwritten if the client placed an order with an address different from their default location address. So, your order will always have the correct ship to and bill to address.

Hope this helps. Feel free to follow up with more questions.

Hi ​@Yuri Karpenko  - 

We set aside some time last night to test this and quickly discovered that we’re unable to mark the Customer Locations entity as inactive. Is there a trick to disabling Customer Locations from the sync records? Are you using an import filter?

We did notice that when we added some bad code to the entity mappings of the customer location, the new location records failed but the orders imported as needed with the customer’s default location (including tax exemption records from Acumatica) and the proper address information with the override checkbox

​@kyle90 , could be a version of Acumatica issue… Here’s what I CAN do on the 24R1:

What Acumatica version are you on?

I understand that a bad code can cause the desired result, but I wouldn’t rely on that approach, maybe only for a very short time :)

We’re 23R1 (working to upgrade soon) - Customer Location is enabled and can’t be made inactive

Ah yes! 

It’s been a few years since we set up any of this that I had forgot. We’ll give it another whirl with your suggestions but this seems to be the best approach I can find

Thank you