Looker Studio Reporting Connector

Most small and mid-size NetSuite teams do not have a reporting problem so much as a distribution problem. The numbers exist — there is a saved search for pipeline, one for aged receivables, one for inventory by location, and they are correct. What does not exist is a way to put them in front of people. The warehouse manager has no NetSuite login and would cost a user licence to give one. The board wants a single page, refreshed, not a PDF someone assembled on Sunday night. So a person exports three saved searches to CSV every Monday, pastes them into a spreadsheet, fixes the currency columns that came through as text, and re-links the charts. When that person is on holiday, reporting stops.

The obvious fix — a full BI platform — is priced for a different size of company. Per-seat licences for people who only ever look at one dashboard are hard to justify, and the implementation effort is disproportionate when the underlying question is simply how do we show ten saved searches on a shared page that refreshes itself. Meanwhile the free dashboarding tool most teams already have access to cannot talk to NetSuite, because NetSuite does not publish a data source it can read.

What ECOSIRE builds

Nothing here is pre-built or available for instant download. After scoping, ECOSIRE builds two halves and installs both: a curated data endpoint inside your NetSuite account, and a connector deployed into your own Google account that reads it. You own both, and there is no per-seat charge for anyone viewing the resulting dashboards.

The NetSuite side: a curated data endpoint

Rather than exposing the whole account, we publish only the datasets you nominate. Each one is a RESTlet backed either by an existing saved search or by a SuiteQL query executed through N/query — so the logic your finance team already trusts stays the source of truth instead of being re-implemented somewhere else. Alongside the rows, each endpoint returns a schema descriptor: field names, human labels, and types. That descriptor is what turns a wall of strings into properly typed dimensions and metrics on the reporting side, so currency aggregates as currency and dates group by month without anyone writing a calculated field.

Endpoints support paged fetch with continuation tokens, so a result set larger than a single response is assembled safely rather than truncated at an arbitrary row count. Repeated refreshes are served through N/cache with a TTL you set, which keeps a dashboard with a dozen tiles comfortably inside the 5,000-unit governance ceiling a RESTlet gets per call. Errors return a readable message that surfaces on the report canvas instead of leaving a blank chart, and the failure is written to a custom record so your administrator can see what happened without opening the script logs.

The reporting side: a connector you own

The second half is a connector project deployed into your own Google account, in the community-connector style — it is not published to any public gallery and it is not shared with other customers. It authenticates to your NetSuite endpoints, presents the schema Looker Studio needs, and hands over rows on request. Because it lives in your account, you control who can use it, and revoking access is something your administrator does rather than something you email a vendor about.

Filters, refresh and field typing

A connector that ignores the report's controls pulls everything, every time, and gets slow immediately. This one pushes down: the date range control becomes a filter on the underlying saved search or a where clause on the SuiteQL query, and report-level filters map to saved search filters for subsidiary, department, class, location, item type and status. Only the rows actually needed cross the wire. Field typing covers currency, percentage, date, datetime and boolean, including both transaction and base currency amounts so consolidated views do not silently mix units.

Security

Authentication uses token-based authentication against a dedicated integration record — never a named user's login and never a stored password. The token runs under a purpose-built Reporting Integration role restricted to the specific records, saved searches and permissions the published endpoints need, so a compromised token cannot read payroll or edit a transaction. Where your policy requires it, we apply role-level IP address restriction so the token is only usable from the connector's egress. Every endpoint is read-only by construction.

Who this is for

Small and mid-size companies on NetSuite that want shared, self-refreshing dashboards without adding a BI platform and its licences. Finance managers who currently maintain the weekly export-and-paste ritual and want it to stop. Operations and warehouse teams who need to see one operational board — open orders, backorders, stock by location — without consuming a NetSuite user licence each. It also suits companies that intend to build a proper warehouse eventually and want something honest and cheap working in the meantime.

How delivery works

We scope first: which saved searches and questions matter, roughly how many rows each returns, how often the dashboards need to refresh, who will view them, and what your security policy requires around tokens and IP restriction. That produces a fixed quote. We then build the endpoints and the connector and test them against realistic result sizes. Installation goes to your sandbox account first, where you point a test report at the endpoints and confirm the numbers match the saved searches you already run. After sign-off the same SDF project deploys to production, the integration record and role are created there, and the connector is pointed at production. We then build out the agreed dashboards with your team and hand over. A support window covers defect fixes and questions while the first reporting cycles run.

What this is not

It is not a data warehouse and will not pretend to be one. It is designed for curated datasets of moderate size refreshed on a dashboard cadence — if your reporting needs multi-year transaction-line analysis across millions of rows, the honest answer is a replication pipeline into a warehouse, and we will say so at scoping rather than sell you a connector that will disappoint. It is also not a NetSuite licence workaround for people who need to transact: viewers see published, read-only report data and nothing else. And it is not published in any public connector gallery — it is deployed privately to your account, which is precisely why you control it.