Beyond NSPOS and SCIS: What NetSuite Retailers Should Consider
Support runs through 2029, so there's time to plan. Use it to compare not just POS features, but the architecture behind them: integrated with NetSuite, or built around it.
Jump to a section9 sections
Retailers using NetSuite Point of Sale (NSPOS) or SuiteCommerce InStore (SCIS) are facing an important technology decision.
According to Lightspeed, Oracle announced in 2026 that NSPOS and SCIS are moving toward end-of-life, with support expected to continue through 2029 depending on the customer's specific environment and agreement.
That does not mean businesses need to replace their POS immediately.
But it does mean now is the right time to start planning.
A point-of-sale system touches much more than the checkout screen. It can affect inventory, customer records, pricing, payments, returns, fulfillment, accounting, and reporting. For businesses that have spent years building their operations around NetSuite, replacing the POS can quickly become a much larger project than simply choosing a new register application.
The important question is no longer just:
It is:
What options do NetSuite retailers have?
There are several paths retailers can take.
One option is moving to a standalone POS platform such as Lightspeed.
Lightspeed provides a modern retail environment with its own point-of-sale, inventory, payments, reporting, and commerce capabilities. NetSuite can remain the ERP while information is exchanged between the two platforms.
Another common option is Shopify POS.
For companies already heavily invested in Shopify ecommerce, extending Shopify into physical stores can be a natural choice. Shopify can connect with NetSuite through integrations that synchronize products, pricing, inventory, sales orders, and fulfillment.
There are also industry-specific POS platforms that may be a strong fit for businesses with specialized requirements.
All of these approaches can work well.
But they share one important architectural characteristic:
That means information must move between them.
The integration question
With a traditional external POS, the architecture often looks something like:
The sale happens in the POS, and relevant information is then synchronized into NetSuite.
At the same time, information such as products, inventory, customers, and pricing may need to move from NetSuite back into the POS.
Modern integrations can do this very effectively.
But integration still introduces another layer that needs to be configured, monitored, and maintained.
Retailers should understand how that layer works.
How quickly does inventory update?
Which system owns the customer record?
Where is pricing calculated?
What happens if the integration fails?
How are refunds handled?
How are custom NetSuite fields supported?
What happens when a NetSuite workflow changes?
For simple retail operations, these questions may be easy to answer.
For complex NetSuite environments, they can become much more important.
What if the POS worked directly around NetSuite?
There is another approach.
Instead of adding a separate retail platform and connecting it back to NetSuite, retailers can use a POS designed to operate natively around NetSuite.
This is the approach behind SphericalBRM POS.
Rather than treating NetSuite as a downstream ERP that receives data from another system, SphericalBRM keeps NetSuite at the center of the retail operation.
The architecture becomes closer to:
The cashier still gets a modern point-of-sale experience.
But the underlying business environment remains NetSuite.
This can allow retailers to continue working with the NetSuite structures they already use, including:
- customers
- items
- inventory
- locations
- subsidiaries
- pricing
- transactions
- permissions
- custom fields
- workflows
The goal is not to turn the NetSuite ERP interface into a cash register.
The goal is to give store employees a simple retail experience while allowing NetSuite to continue doing what it already does well behind the scenes.
Why this matters for NetSuite-first businesses
Many NetSuite customers have spent years customizing their environment.
They may have unique pricing rules, customer classifications, manager approvals, special-order workflows, multiple subsidiaries, location-specific inventory rules, or custom transaction fields.
When an external POS is introduced, businesses need to determine how much of that logic needs to be recreated or synchronized.
For example, a retailer may already have customer-specific pricing configured in NetSuite.
With an external POS, the business needs to decide whether that pricing should be copied into the POS, calculated through an integration, or managed independently.
The same applies to inventory.
If NetSuite is already the inventory authority, the retailer needs to determine how inventory is synchronized with the POS and how quickly changes become visible at the store.
Returns, customer deposits, special orders, and partial fulfillment can make the architecture even more important because those workflows may involve several related NetSuite transactions.
A native approach can reduce the amount of business logic that must exist in two places.
Native does not mean every technology lives inside NetSuite
It is important to be realistic about the term "native."
Retail environments still use external technologies.
Payment processors may be external.
Hardware is external.
Ecommerce platforms may be external.
Shipping, tax, and other specialized systems may also connect with the business.
The difference is where the core retail transaction lives.
In a native NetSuite approach, NetSuite remains the central operational environment rather than receiving a second version of the transaction from another POS platform.
That can reduce duplicate data models and simplify the relationship between the store and the ERP.
Is a native POS right for everyone?
No.
A retailer whose entire commerce strategy revolves around Shopify may prefer Shopify POS.
A business looking for a broader standalone retail ecosystem may find Lightspeed to be the right choice.
An industry-specific platform may offer specialized capabilities that are essential for another retailer.
Those are all valid approaches.
The key is understanding which system you want at the center of your retail operation.
If the answer is Shopify, Shopify POS may make sense.
If the answer is a standalone retail platform, Lightspeed may make sense.
If the answer is NetSuite, then a NetSuite-native POS deserves serious consideration.
Questions to ask before choosing your next POS
As retailers evaluate replacements for NSPOS or SCIS, the conversation should go beyond features like barcode scanning or receipt printing.
Ask:
Where is the actual transaction created?
How is inventory updated?
How are NetSuite custom fields handled?
What happens to your existing pricing rules?
How are customer deposits and special orders represented?
How do returns work?
What happens when the integration is unavailable?
How much reconciliation will finance need to perform?
And perhaps most importantly:
The migration is also an opportunity
The retirement of NSPOS and SCIS should not only be viewed as a forced migration.
It is also an opportunity to rethink the retail architecture.
Some businesses may decide that moving to another standalone POS is the right strategy.
Others may decide that they want fewer systems between the store and NetSuite.
There is no universal answer.
But retailers should use the transition period to compare not only POS features, but also the architecture behind them.
For NetSuite-first organizations, that distinction can be significant.
SphericalBRM POS is designed for the second.
It provides a modern point-of-sale experience for retailers that want to keep NetSuite at the center of their customers, inventory, transactions, and retail workflows.
If your organization is beginning to evaluate alternatives to NSPOS or SCIS, now is the right time to start asking not only which POS should come next, but what you want your retail technology architecture to look like for the years ahead.
Explore SphericalBRM POS
See how SphericalBRM keeps NetSuite at the center of your retail operation — customers, inventory, transactions, pricing, and workflows — while giving store teams a fast, modern point-of-sale experience.
