By using this website, you agree to our Terms of Use (click here)
Hello,
We sell to a number of chain store companies, where the individual stores have their own Business Account in the system. These stores are set as child accounts of the parent account, the chain store HQ.
In Stock Items, Cross-Reference tab, you can set a Customer Part Number for a particular customer.
Is there a way for me to put the alternative type customer as the parent account, and then have this alternative number work for all of the child accounts?
I thought this was the default behavior to be honest. Does your customer selector only show the child accounts? If so, you need to create a master customer with locations in your system. The locations would be the children accounts. I do this with nested Vendors (we have buying agents we pay with multiple source locations i.e. "children").
Otherwise, you'd need a line for each unique entity, which is hard to control and maintain. I happen to have a series of customers who are NOT nested and should have been in my system. For these situations I use an Import Scenario, with all the stores baked in and then pivot off item ID and the new customer code.
I'm not too sure how your system is configured, so hopefully one of those solutions is correct for you. If not, please let us know!
Thanks a lot for letting us know as to the options here @michaelhansen.
I looked into the two options suggested.
Currently the child accounts are separate accounts, rather than locations. However, to have them as locations would make things quite complex. A number of these child accounts are fairly large and complex in their own right, and having them all as locations under the parent account would make a mess of the contacts and activities sections etc.
I had wondered about a line for every business account, but as you mention, maintaining this would be quite hard - to the point that it would be a lot more time consuming than the benefit would provide....
Just looking further into this - I think the easiest way to go about this is to add the cross-reference items as Global rather than Customer. I know that this makes it available for all customers, but I don't think this would be much of an issue.....
@daniel I always like going simpler myself whenever possible. Complicated relationship trees can get difficult to understand.
We've got the same need at our company. Our customer list is very complex and parent customers are used extensively. Its not feasible to use 'Global' cross references and is proving difficult to maintain the cross references by individual child customers. We have some Parents with 100 Child companies in our industry because each location is managed as a separate company. Anyone figure out a way to do this or do I add it to the idea list?
Online Members
