Good morning, I work for a construction company where we use Transfer Orders all the time to transfer inventory to work site. Before my time here, they always created a new location per new work site which last until the construction is completed. Which means an ongoing list of new locations. I don't see this as a sustainable approach. Since these are just temporary places, I was thinking in having one location and create Bins specific for each work site. • Do see any potential issues with this approach? • Have any of you come across a similar situation? • Any suggestions? Thank you

Thank you for the info. I will definitely look at I, however, I need to setup either Locations or Bins within a generic location for now to keep moving. I was wondering if anyone had any suggestions or see potential issues with that approach for now.

You definitely will run into location limitations with NetSuite over time with the approach you mentioned. You could recycle the locations once jobs are complete and keep it as is or certainly bins would work - with far more options. Maybe even create each location with a job year nomenclature or something to readily identify it

I'm not sure mine is a great idea either, but I'd think about 1 location ("Construction Sites") + a custom segment before I'd do Bins. But kind of creates the same issue. Though there are limits on Locations and not really on custom segments. I'd worry about using Bins more for future-proofing. I'm assuming you're not using Bins currently, but if you do in the future for their real purpose, you might be stuck if you're already using Bins for faux locations. e: I should clarify I think the Bins idea would work fine now and long-term too if you're 100% sure you're never going to use Bins in the future. If you do though, trying to accommodate bins as both a location and a bin could be painful.

Thanks a lot for the Info.