01
Pipeline Dependency
Annual expiry forced recurring rework and downtime, not a one-time fix.
Get In Touch
Our customer support team is available for help.
NetSuite case study
Lighting Brand Eliminated Manual Effort With NetSuite–Azure Integration
A London-headquartered lighting brand ran NetSuite for financials, procurement and operations, with Azure SQL as its analytics and reporting warehouse behind it. The Azure Data Factory pipelines connecting the two expired every year, and each renewal meant downtime, manual reconfiguration and a real risk of delayed reporting.
Reported outcomes
From the client's own results after go-live
From the client's own results after go-live
Zero
Annual pipeline-renewal downtime
Eliminated since go-live
6
Custom, secure Azure APIs built for the sync
One per Azure SQL table
Real-time
Error visibility inside NetSuite
Every failed transmission logged with a code and message
Client context
A Lighting Brand Running NetSuite Financials Against an Azure SQL Reporting Layer
The client is a lighting solutions brand based in London, running NetSuite as its core ERP for financials, procurement and day-to-day operations. Azure SQL Database sits alongside it as the central repository for analytics and reporting, giving finance and operations teams a single place to build reports from.
The data exchange between the two platforms was originally built on Azure Data Factory pipelines — a workable but fragile arrangement, since those pipelines expired annually and needed manual renewal every time.
The challenge
The Pipeline Worked — Until It Expired, Every Single Year
The recurring pipeline expiry was the core problem: once a year, without warning built into the business calendar, the integration would stop and someone on the IT team would have to notice, diagnose and manually rebuild it. That created real operational risk, not a one-off inconvenience.
02
High Data Volumes
Large NetSuite datasets needed to move without data loss or partial transfers.
03
No Error Visibility
The old setup gave the IT team no way to see a failed transfer until its downstream effects showed up.
04
Real-Time Expectations
Business-critical reports needed timely synchronization the pipeline-based approach couldn't reliably guarantee.
The solution delivered
Replacing an Expiring Pipeline With a Framework Built Not to Expire
ERP Peers replaced the expiring-pipeline approach with a custom-built integration designed to remove the annual-renewal problem entirely, built around three deliverables.
Azure Custom APIs
Six secure APIs were developed, each mapped to a specific Azure SQL table, with authentication built in, pagination support for high-volume transfers, and error resilience.
NetSuite SuiteScripts
Custom scripts extract data directly from NetSuite saved searches and transmit it to the Azure APIs, with logic to prevent duplication — running in real time or on a schedule, depending on what the data needed.
Error-Handling Framework
A custom error log record inside NetSuite captures every failed transmission with a specific error code and message, so the client can track and resolve issues without waiting on external support.
Measurable impact
What Changed Once the Annual Renewal Problem Was Gone
These aren't projected figures — they reflect what changed operationally once the expiring-pipeline dependency was removed.
Annual pipeline-expiry downtime
Dedicated Azure APIs now running the sync
Error visibility and resolution, instead of downstream discovery
Built for what comes next: the framework supports both scheduled and real-time sync, so it doesn’t need to be rebuilt as reporting needs change.
Takeaway
A Framework Built Not to Need Rebuilding
ERP Peers remains the client’s NetSuite support partner in the UK for this integration, managing performance, handling exceptions and continuing to optimize synchronization between the two platforms. For any NetSuite environment leaning on a time-boxed or credential-expiring integration, the lesson here generalizes: a sync layer that depends on an annual renewal date is a recurring liability, not a one-time build — replacing the dependency itself, not just patching around it, is what actually removes the risk.
Facing a similar challenge?
Have a Similar Challenge in Your Business?
We can assess your current setup, the systems involved and where things are actually getting stuck before recommending an integration, workflow change or another route.
Discuss your situation
No solution assumed before discovery.