NetSuite Next is Oracle's next generation of NetSuite. If you sell online, it raises practical questions: will my storefront keep working, do my integrations need changes, and is this the moment to rethink ecommerce? This guide answers those questions in plain language and gives you a checklist to take to your partners.
What changes, and what does not
NetSuite Next changes how people work inside NetSuite. Your business data does not move anywhere: items, prices, inventory, customers, and orders remain NetSuite records. For ecommerce, what matters is how your storefront talks to NetSuite.
Oracle's documentation and release notes for your account are the authority on timing and specifics. Plan with your NetSuite account team and partners; this guide helps you ask the right questions.
Why the integration approach decides your risk
Storefronts connect to NetSuite in a few different ways, and they carry different levels of risk as NetSuite evolves:
| How the storefront connects | What to check |
|---|---|
| Hosted inside NetSuite with legacy web store templates | Ask Oracle or your partner how your release and templates are supported |
| SuiteCommerce or SCA with heavy custom SuiteScript | Review custom code for API versions and deprecated features |
| SOAP web services | Plan a move to REST, since Oracle is phasing SOAP down in favor of REST |
| Third-party connector or middleware | Ask the vendor for its NetSuite Next plan in writing |
| SuiteTalk REST, SuiteQL, RESTlets, OAuth 2.0, SuiteScript 2.1 | These are the interfaces Oracle carries forward |
A readiness checklist for your storefront
Take these questions to your ecommerce partner or vendor:
- Which NetSuite interfaces does the storefront use? Look for SuiteTalk REST, SuiteQL, RESTlets, and OAuth 2.0.
- Are there SOAP web services anywhere in the integration? If yes, what is the plan to replace them?
- Which SuiteScript version do custom scripts use? SuiteScript 2.1 is current; 1.0 scripts deserve a review.
- Where does the storefront run? Storefronts hosted outside NetSuite depend less on how NetSuite renders pages.
- Where do design and content live? If they live in a separate admin, they carry over unchanged.
- Is authentication OAuth 2.0? Older token methods may need attention.
- Who tests each NetSuite release? You want a named owner, not a hope.
If you run SuiteCommerce Advanced
SCA sites vary widely. A current release with light customization is in a different position from an older release with years of custom modules. Ask your partner to review:
- Your SCA release and its support status
- Custom SuiteScript and its API versions
- Extensions and their maintainers
- Any SOAP-based integrations around the store
If the review turns into a large project, compare its cost with a move to a storefront designed around current APIs. Many merchants find the NetSuite Next planning cycle is the right moment to do both at once. See the SuiteCommerce migration plan.
How AwaCommerce Next approaches NetSuite Next
AwaCommerce Next connects through SuiteTalk REST, SuiteQL, RESTlets, OAuth 2.0, and SuiteScript 2.1. The storefront and the cloud Admin run on AwaCommerce URLs outside NetSuite, and your design and content live in the Admin. Moving your account to NetSuite Next does not require a commerce rebuild. Read more on the NetSuite Next Ready page.
A simple plan
- Inventory every integration that touches NetSuite: storefront, payments, shipping, marketplaces, tax, and EDI.
- Classify each one by interface using the table above.
- Ask vendors for their NetSuite Next plan in writing.
- Prioritize anything on SOAP, legacy templates, or unmaintained custom code.
- Decide whether to remediate or replace, using a three-year cost view.