Spike - Our Thinking

Is your NetSuite implementation partner's testing enough before go-live?

Written by Luke Foster | 19 November 2026

No. A NetSuite implementation partner tests the NetSuite build against the requirements they were given. Before go-live, retailers also need someone to test the end-to-end flows across every system NetSuite connects to, such as the storefront, 3PLs, payments and finance, plus UAT run by trained business users and go-live criteria the whole business has agreed.

Your partner’s testing is one layer. On its own, it can leave gaps between NetSuite and the systems around it. Testing those gaps before go-live means any issues are fixed long before they reach shoppers or your finance team.

NetSuite rarely works alone in a retail business. Orders arrive from Shopify, Magento or Salesforce Commerce Cloud. They pass through integration platforms to warehouses and 3PLs. Payments, tax and intercompany transfers all end up in the ledger. Each of those connections is often built or run by a different supplier.

We’ve tested NetSuite programmes from both sides: Lovehoney’s move onto a single NetSuite instance, and Ooni’s move to NetSuite, where we tested orders from Shopify through to their 3PL partners. Here’s what we’ve learned about where partner testing stops, and what to put alongside it.

What does an implementation partner’s testing usually cover?

The NetSuite build itself. A partner configures NetSuite, adds customisations and builds the integrations in their scope, then tests that work against the agreed requirements. That typically means orders arriving from the storefront, moving through the order flows, and stock processes such as purchase orders working inside NetSuite.

What often falls outside it is everything NetSuite plugs into.

Usually covered by the partnerOften left out
NetSuite configuration and customisationsSystems upstream and downstream of NetSuite
Integrations the partner builtIntegrations built or run by other suppliers
Features tested ticket by ticketRegression of what already worked
Scenarios written in the requirementsScenarios nobody wrote down, edge cases and timing issues
Test data set up for each featureMigrated data, and finance data at every stage of the period

 

Why does the gap exist?

In our experience, four things cause it:

1. The partner tests up to their boundary

A partner sees NetSuite as the system they’re accountable for. Many retailers have several storefronts, more than one order management system, entities in different countries and an integration platform run by someone else. All of that routes into NetSuite through different rules. Unless the contract says otherwise, testing the whole route gets missed.

2. Requirements are open to interpretation

A partner builds and tests to the requirements. When those are high level, with little acceptance criteria, each team reads them differently. On one programme we tested, the requirements were so broad that the same one could pass or fail depending on who read it.

3. Other suppliers deliver late

NetSuite can be configured and tested on its own. The end-to-end flows can’t be tested until every integration is in place. We’ve seen a programme where the integration platform supplier fell behind, and the end-to-end testing window was squeezed because of it. The partner’s testing was complete but the retailer’s was not.

4. Nobody joins the suppliers together

Many retailers run several third-party teams, each working on its own piece with nobody tying them together. The technical integrations get plenty of attention. The human ones, between teams and suppliers, often get none. That’s where one team’s change breaks another team’s flow without anyone noticing.

It’s also why independent testing matters. We’ve written about the wider issue in Marking their own homework.

 

 

Where do problems show up after go-live?

Mostly in the data as it travels between systems. Between the storefront and the finance system there are often three or four systems, each making API calls and transforming data so the next one can accept it. Each step is a chance for something to change.

The issues we see most often:

  • Rounding and price differences. On one programme we saw order values arrive in finance a penny out. Although a penny sounds small, when it’s repeated across thousands of orders and carried through the ledger, it adds up.
  • Tax. Different tax rules by region and country are a regular source of defects. Lovehoney trades across US states, Canada and Europe, and its regression pack includes a lot of tax tests for exactly that reason.
  • Payment types and subsidiaries. Gift cards, PayPal and other payment methods, across every subsidiary, each take a slightly different route.
  • Finance processes over time. Finance needs data in every status, across different periods, to test end of day, end of week and end of month. Someone has to create that data or migrate it.
  • Features cut to hit the date. Anything taken out of scope before go-live still has to be built and tested later. Until it arrives, people fill the gap by hand. If an integration is cut, for example, finance may have to key invoices manually.

If NetSuite will sit in the middle of these journeys for you, Raisa Lupascu’s article on how to test end-to-end retail journeys shows how to plan them.

“Our partner already tests. Why pay for more testing?”

Start by asking what they test, and how. The answer is different for every partner and every contract. Some run a single testing phase. Few test beyond the edge of NetSuite.

Then map every system involved, and mark where the partner’s testing stops. Look at:

  • each storefront, including those for other countries
  • every order management system and integration platform
  • each entity, and the intercompany transfers between them
  • every downstream process, especially finance.

Anything outside the partner’s boundary needs an owner. Agree roles, responsibilities and accountability for each part before testing starts.

What should you ask your NetSuite implementation partner about testing?

A partner’s work can feel like a black box: requirements go in, a build comes out. What matters is evidence that what comes out is on time, accurate and good enough to trade on. These questions help:

  1. Where does your testing stop? Which systems, integrations, entities and processes are in scope, and which belong to someone else?
  2. How do you manage requirements? How do you check they’re accurate and unambiguous, and has the business signed them off?
  3. How do you work? Agile or waterfall, and how do defects found in one sprint get fixed before you move on to the next feature?
  4. Who tests, and what do they cover on each ticket? For NetSuite, that should include every subsidiary, every payment type and any integration the feature touches.
  5. Can you show us the evidence? Ask to see test results, coverage and defect reports.
  6. What’s in each release? Ask for build notes that explain what changed, why the business needed it, and which issues each release fixes.
  7. What’s your SLA for fixing defects? A delivery date means little if fixes take three months after it.
  8. How will you work with our other suppliers? Who talks to the integration and SIT teams, where are defects raised, and how are they shared?

The last one is as much a question for you as for your partner. Set the ways of working when you bring each supplier on board: one process, one place to log defects, and regular conversations between teams. Bringing SIT testers into ticket refinement early is one of the simplest ways to spot when one team’s change will affect another’s.

If you’re further along and planning upgrades, Dan Vipond’s article on what needs testing when NetSuite releases an upgrade picks up from here.

What results can you expect when independent testing works alongside your partner?

Fewer surprises at go-live, a clear view of risk while you still have time to act on it, and a reusable test pack that keeps paying back after launch. Here’s what that looked like on two NetSuite programmes.

Ooni: SAP to NetSuite

We tested the joins around the partner's build, from Shopify through NetSuite to 3PLs in three continents.

55 critical defects found before go-live

569 end-to-end scenarios, signed off by the business

8 months from discovery to go-live

Read the case study

Lovehoney: implementation

We tested everything upstream and downstream of the partner's build, across more than 50 integration points.

12 weeks to 12 hours for a full regression cycle

1,200+ automated end-to-end tests

10,500 testing days saved

Read the case study

Lovehoney: after go-live

The test pack from the implementation became an ongoing service, covering every upgrade since.

Under 6 hours for a full upgrade regression, against 37 days by hand

Zero live incidents from NetSuite upgrades

75% faster releases

See how the service runs

 

Want to see the numbers for your own estate? Try our NetSuite regression calculator.

Where Spike fits in

We provide independent NetSuite testing for retailers, alongside your implementation partner. We test the flows that run between NetSuite and everything around it, support your UAT team, and help you define what go-live ready means for your business.

We’ve done this for retailers moving to NetSuite, like Ooni, and for those already running on it, like Lovehoney, where the same regression pack has tested every upgrade since go-live.

If you’re planning a NetSuite go-live and aren’t sure where your partner’s testing stops, now is the time to find out, while there’s still room in the plan. Our Land Big Change page covers how we support large programmes.

See how independent NetSuite testing works

Frequently asked questions