A manufacturer of industrial components had NetSuite. His company also had a 3PL, a Shopify B2B store, and a CRM. What they didn’t have was any of those systems talking to each other. This is the story of what that silence was costing them – and what happened when they finally made the introduction.
Quick Answer: NetSuite is a powerful ERP solution, but the NetSuite ERP doesn’t operate in isolation. Most manufacturers run it alongside a CRM, an e-commerce platform, a 3PL, and payment systems – each holding a piece of the operational picture. NetSuite API integration connects those pieces in real time, replacing the manual CSV exports and day-old data that cause orders to slip and customers to leave. This article follows Calloway Precision Engineering, a UK-based manufacturer of industrial components, through an integration project that changed how their entire business moved.
The Spreadsheet That Left at 5 PM
Lily Williams ran operations at Calloway Precision Engineering. She’d describe her job, half-jokingly, as “making sure the spreadsheets don’t lie.” She’d been saying that for three years. She didn’t find it funny anymore.
Calloway manufactured industrial valve components and fluid control fittings. Their customers were engineering firms, and increasingly, a segment of B2B buyers who placed repeat orders through Calloway’s Shopify storefront. Annual revenue was £47 million. They had 180 employees, a third-party logistics partner managing their dispatch and freight, and a Salesforce CRM the sales team used to track customer relationships.
They also had NetSuite – had for two years, actually – handling finance, inventory, and production planning. By every measure, NetSuite was working. The financial close that used to take three weeks now took six days. Inventory accuracy had climbed from 71% to 93%. The implementation, run eighteen months before Lily joined, had been a genuine success.
The problem wasn’t NetSuite. The problem was what happened at the borders.
Every morning at 8 AM, Lily’s team ran a report out of NetSuite, cleaned it into a CSV file, and uploaded it to their 3PL’s web portal. This told the 3PL what inventory Calloway had on hand and what orders needed to go out. Every evening at 5 PM, the 3PL’s warehouse management system generated its own export – shipment confirmations, tracking numbers, delivery exceptions – and emailed it as an attachment. Someone on Lily’s team then manually entered those updates back into NetSuite.
The Shopify situation was a variation on the same theme. Orders placed on the B2B storefront accumulated throughout the day and were pulled into NetSuite each evening via a manual export. Inventory levels on Shopify were updated once daily – the morning upload – which meant a customer could spend twenty minutes configuring a large order on the storefront, submit it, and receive a call the next day explaining that three of the items were out of stock.
The CRM disconnect was the quietest problem and the most damaging. Calloway’s sales team logged calls, tracked opportunities, and managed account notes in Salesforce. NetSuite held order history, credit status, and outstanding invoices. Neither system knew what the other contained. When a sales rep called a customer to discuss a renewal contract, they had no visibility into whether that customer had a £12,000 invoice that was 45 days overdue. Finance knew. The rep didn’t. These were conversations that went badly when they didn’t need to.
In one quarter, Calloway tracked four lost renewal discussions that later revealed disputed invoice histories the sales team had walked into blind. The combined value of those four accounts: £380,000.
The Integration Audit That Reframed Everything
Lily requested a NetSuite integration audit eight months into her role. She knew enough to know the problem wasn’t any single system – it was the gaps between them. EcobSoft’s integration team spent two weeks mapping every data flow in and out of NetSuite. What we found wasn’t unusual for a manufacturer at Calloway’s stage. It was, however, more expensive than anyone had quantified.
The manual CSV process between NetSuite and the 3PL required approximately 3.5 hours of staff time per day. Across a year, that was over 900 hours. The error rate – data entered incorrectly during the evening 3PL upload – ran at roughly 4%, which sounds small until you calculate it against the 180 shipments Calloway processed daily.
The Shopify inventory lag was generating an average of 23 failed orders per month. Each failed order triggered a customer service interaction, a manual correction, and a reprocessed transaction. Lily’s team had normalized it. It had stopped feeling like a problem and started feeling like just how B2B e-commerce worked.
It wasn’t.
The audit report landed on Calloway’s leadership team on a Thursday afternoon. The headline finding: Calloway’s disconnected systems were costing an estimated £190,000 per year in staff time, order errors, and lost revenue from failed Shopify transactions. The integration project they were about to commission had a fixed scope and a defined budget. The math wasn’t complicated.
The Big Bang vs. Phased Integration Debate
Before a single line of code was written, there was a conversation that almost derailed the project. It happens on nearly every integration engagement EcobSoft runs, and it’s worth naming directly: the Big Bang versus phased integration debate.
The Big Bang argument is intuitive. You have three integration problems – 3PL, Shopify, CRM. Build them all simultaneously, go live on a single date, and the entire system transforms overnight. Clean. Decisive. One go-live weekend instead of three.
Calloway’s head of IT, Stuart Brennan, pushed for this approach. He’d managed a Big Bang ERP rollout at a previous company and believed in the clean break. Lily pushed back. She’d also been at that previous company.
The phased argument comes down to risk surface area. Three simultaneous integrations mean three simultaneous failure points. When something breaks – and something always breaks in the first week after go-live – you’re debugging in a system where the variables have all changed at once. Isolating the cause becomes an investigation rather than a diagnosis.
There’s also a sequencing logic to phased integration that matters operationally. For Calloway, the 3PL connection was the most urgent and the most contained. Fixing the 3PL data flow would eliminate the daily manual upload process, reduce shipment errors, and give Lily’s team back time they could redirect toward the second phase. Starting there made the second phase easier, not harder.
We recommended phased. Three workstreams across four months: 3PL integration first, then Shopify, then the CRM. Stuart eventually agreed, with one condition: the phases had to run on a firm schedule. No indefinite gaps between go-lives. The project plan reflected that.
Phase One: NetSuite and the 3PL, Finally Speaking the Same Language
The 3PL integration was built on a RESTlet-based API connection using NetSuite’s SuiteTalk framework. SuiteTalk is NetSuite’s native web services layer – it allows external systems to read from and write to NetSuite in real time using SOAP or REST protocols, depending on what the external system can handle.
Calloway’s 3PL used a modern warehouse management system with REST API support. This made the connection cleaner than many 3PL integrations, which often involve older EDI-based protocols and require a translation layer. EcobSoft has built both – EDI integrations for logistics partners running legacy WMS platforms and direct REST connections for more modern infrastructure. Calloway fell into the latter category.
The integration we built did four things automatically: pushed inventory updates from NetSuite to the 3PL every fifteen minutes, pulled shipment confirmations and tracking numbers from the 3PL back into NetSuite in real time as shipments were processed, flagged delivery exceptions directly into NetSuite against the relevant sales order, and triggered customer dispatch notifications from NetSuite the moment the 3PL confirmed an outbound scan.
The manual CSV process disappeared. So did the 4% error rate it had been carrying. Lily’s team reclaimed 3.5 hours per day and redirected it toward customer onboarding – a backlog they’d been unable to touch for months.
Phase Two: NetSuite Integration with Shopify – The B2B Storefront, Synchronized
The Shopify integration addressed Calloway’s most customer-visible problem. Connecting NetSuite to Shopify for a B2B manufacturer involves more complexity than a standard D2C retail connection – you’re dealing with customer-specific pricing, order minimums, account credit terms, and inventory that needs to reflect warehouse reality, not yesterday’s count.
EcobSoft used a middleware layer to handle the bi-directional sync between NetSuite and Shopify. Inventory levels in NetSuite pushed to Shopify every ten minutes. Orders placed on Shopify created sales orders in NetSuite automatically, with customer tier pricing and payment terms applied from the customer record. Order status updates – confirmed, picking, dispatched, delivered – flowed back to Shopify from NetSuite as each stage progressed, surfacing in the customer’s order history without anyone manually updating anything.
The failed order rate dropped from 23 per month to under 2. The two that did occur in the first month after go-live were edge cases – a product discontinued mid-day while a customer’s session was still active – and prompted a real-time discontinuation sync that eliminated even that scenario.
Calloway’s Shopify revenue grew 31% in the six months following the integration. Not entirely attributable to the integration – they also ran a product catalogue expansion during that period. But Lily is clear about the causality on the failed order side: “We were turning away customers and not fully realizing it. The storefront looked like it worked. It just kept quietly failing.”
Phase Three: CRM Integration – The Conversation Sales Should Have Been Having
The Salesforce integration was the most architecturally complex of the three. CRM integration is bi-directional by nature: NetSuite needs to push financial data to Salesforce (order history, invoice status, credit utilization), and Salesforce needs to push relationship data to NetSuite (account ownership, pipeline stage, contract renewal dates).
Getting this wrong in either direction creates a different problem. Push too aggressively from NetSuite to Salesforce and you clutter the sales team’s view with financial detail they don’t need during prospecting conversations. Push too little and you recreate the blind spots that cost Calloway the four renewal accounts.
We built a field-level sync that gave the sales team a curated NetSuite panel inside Salesforce – account balance, last order date, open invoice total, and a 90-day order trend – without exposing every line-item detail. The sync ran every thirty minutes in both directions. When a contract stage in Salesforce moved to “Renewal Discussion,” a workflow triggered a NetSuite check of the account’s credit and invoice status, and surfaced any flags to the account manager before the call was scheduled.
Three months after go-live, Calloway’s sales team had not walked into a single customer conversation with mismatched financial information. The metric they track: renewal conversion rate improved from 71% to 84% in the subsequent two quarters.
What the Quote-to-Cash Cycle Looks Like Now
Before integration, Calloway’s quote-to-cash cycle – from a customer’s initial enquiry to cash received against an invoice – averaged 34 days. The delays weren’t in manufacturing or even in logistics. They were in the handoffs. A quote generated in Salesforce that had to be manually re-entered into NetSuite as a sales order. An invoice raised in NetSuite that the account manager in Salesforce didn’t know had been sent. A payment received that neither the sales team nor the 3PL could see until the next morning’s export ran.
Post-integration, the average quote-to-cash cycle runs 21 days. Thirteen days recovered from a process that hadn’t changed in three years – not through operational heroics, but through systems that finally passed information to each other without a human carrying it.
| Metric | Before Integration | After Integration |
| Daily manual data transfer time | 3.5 hours | 0 hours |
| Shopify failed orders per month | 23 | Under 2 |
| Shipment update lag (3PL to NetSuite) | 12–24 hours | Real-time |
| Renewal conversion rate | 71% | 84% |
| Quote-to-cash cycle | 34 days | 21 days |
| CRM-NetSuite financial blind spots | Routine | Eliminated |
The Handshake That Changes Everything
Calloway Precision Engineering didn’t have a NetSuite problem. They had a connectivity problem – a set of systems that held different pieces of the same operational truth and had no way to share it. NetSuite knew the inventory. Shopify was guessing. The 3PL was working from yesterday’s numbers. The sales team was walking into conversations without the full picture.
Integration didn’t change what any of those systems did. It changed what they knew about each other. And in the gap between those two states – between isolated and connected – was 13 days off the quote-to-cash cycle, a failed order rate that dropped by 91%, and renewal conversations that the sales team now walks into with the same information finance has. The missing handshake, once made, turns out to be the one that holds everything else together.
