Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Myth or Fact: Performance Issues with many Locations?
If you search for number of locations + performance issues, you'll see posts and anecdotes how horrible the system performance is the more locations you have. I also hear this as a concern from people who have used Netsuite for a long time. However, I can't really see or measure the impact the number of locations have.
Currently, in 2024 its possible to have up to 1000 locations with "Advanced Item Location Configuration" enabled, which seems to optimise the way item/locations are handled with subrecord 'itemlocationconfiguration’.
Is there a clear Netsuite description on number of locations + impact on performance in 2024? Do 800 locations have a huge impact on performance in comparison to 400 locations?