Shopify, NetSuite and Salesforce: what a recent client discovery call revealed

They came to us with a simple goal. They wanted customers to buy low-value, non-commissionable items like replacement parts and accessories online, without tying up a sales rep. What they found instead was a stack that couldn’t tell them who was buying¹. Here’s what they’re up against, what it costs and what it looks like when the store runs inside Salesforce instead.

You can’t see who’s buying, so you can’t plan for it

The client’s Shopify checkout doesn’t identify which account a buyer belongs to. When orders pass to NetSuite, every purchase lands under one generic “Shopify customer” record. That isn’t a NetSuite failing; it’s what happens when the system upstream has no idea who the buyer is.

The result is a revenue line with no names attached. The client can see that buying spikes at the start of each sports season, but not which accounts drive it or at what volume. Their logistics team can’t prepare for demand it can’t see, and production contracts get planned on guesswork. They told us they’d rather have steady, predictable buying patterns that keep revenue flowing year round.

Poor data has a measurable price. Gartner estimates that poor data quality costs organizations an average of $12.9 million every year². That’s a cross-industry figure, but the mechanism is the same here: decisions made on data that can’t be trusted.

How StoreConnect solves this

When the storefront runs inside Salesforce, the buyer logs in and every order is saved against their account and contact automatically. Purchase history by account becomes something you report on, not something you reconstruct.

Your sales reps are still babysitting orders they don’t earn on

The whole point of the online store was to free reps from quoting and haggling over small items they aren’t paid commission on. But to get any customer detail into Shopify, the client’s workaround asks a rep to build a custom URL for each customer. The customer then has to use that exact URL every time they order, or the data is lost. Our contact called it a hack, and said it would break consistently and cost too much overhead to maintain.

Rep time is already scarce. Salesforce’s own research found that reps spend just 28% of their week actually selling³. Meanwhile buyers have moved on: 67% of B2B buyers say they prefer a rep-free buying experience, according to Gartner⁴. A workaround that keeps reps in the loop for every reorder works against both.

How StoreConnect solves this

The fix is simpler than the hack. A rep sends a login link once, the customer signs in, and from then on they can review past orders and reorder on their own. Reps get their time back, and the client can finally say yes to the inbound leads it currently turns away because no one has time to serve them.

Four regions, four stores, four copies of the same catalog

To match inventory to where it ships from, the client runs four separate Shopify stores: one for Australia, one for the EU through a third-party logistics provider, one for a US warehouse and one for Asia through another 3PL. Their catalog already lives in Salesforce, with about 1,800 active products sitting inside roughly 200 bundles.

Every one of those stores needs its own copy of that catalog. Each price change, bundle update or new product has to be made four times, and a customer who buys in two regions shows up as two strangers. During our call, one of the stores was redirecting visitors to the wrong regional site, and our contact described the setup as a nightmare to manage.

How StoreConnect solves this

Running the stores from Salesforce flips this around. You can still have a storefront per region, each tied to its own warehouse or 3PL, but they all draw on one set of product and customer data. A single account can buy from the US store and the Australian store, and both orders land on the same record.

Currency gets converted on the platform’s schedule, not your finance team’s

Selling in several currencies through one payment setup means every foreign-currency order gets converted at the moment of the transaction. Shopify’s own Help Center explains that conversion happens when a payment is captured, refunded or charged back⁵, and that Shopify Payments adds a currency conversion fee of 1.5% or 2%, depending on the store’s location⁶.

For a company with revenue across four regions, that fee applies order after order, and finance has no say in when the money changes currency. There’s no option to hold revenue locally and convert it later in larger, planned transfers.

How StoreConnect solves this

The alternative we walked through on the call is to let each regional store use a payment provider based in that country, such as Stripe into a US account or eWAY into an Australian one. Revenue stays in local currency until finance decides to move it.

Your data has to move twice, and someone has to keep the pipes working

Even if the customer workaround held up, the client’s data would still be only halfway home. Orders go from Shopify to NetSuite, and then they have to be moved again from NetSuite into Salesforce. Our contact said the worst part was that second hop. Their team is building and maintaining all of it in-house.

That’s a common pattern, and it’s expensive. Salesforce’s 2026 Connectivity Benchmark found the average organization now runs 957 applications, with only 27% of them integrated⁷. The same research found IT teams spend an average of 36% of their time designing, building and testing custom integrations⁸. Every connector between Shopify, NetSuite and Salesforce is another piece of that time, and another thing that can break when any one vendor ships an update.

The license fee is only the visible part of the cost. Apps and plugins added to fill gaps each bring their own subscription, update cycle and support path.

How StoreConnect solves this

When the store runs inside Salesforce, order data lands there directly through built-in sync, with no middle step to build or babysit. Your Salesforce admin manages commerce data with the tools they already know.

For a closer look at where those integration and app costs show up, see our StoreConnect vs Shopify comparison⁹.

Patching the stack can cost more than replacing it

Our recommendation to this client was direct: the work needed to fix four Shopify stores and two integrations is likely more than the work to move them onto one platform inside Salesforce. Because their product data is already in Salesforce, the move is close to a clean-slate build. We proposed a partner-led migration on a timeline of about six weeks, and the client is weighing it now.

There’s a growth angle too. The client expects to widen its customer base beyond enterprise accounts over time. Once the B2B store is live on Salesforce, adding direct-to-consumer sales is a configuration change rather than a new platform, and both run on the same customer data.

For a feature-by-feature view, see how StoreConnect compares with Shopify and other commerce platforms¹⁰.

If your team is running Shopify, NetSuite and Salesforce side by side, you’re likely paying for the same gaps.

Book a demo to see your own buying journey run inside Salesforce, from customer login to order record.

References