Skip to main content

Get your SKU.io data into a spreadsheet or BI tool

Sometimes you want SKU.io numbers next to data from elsewhere, in a spreadsheet, a finance model, or a BI tool such as Power BI, Tableau, or Looker Studio. SKU.io gives you three ways to do that. Pick by how often you need the data and how much setup you're willing to do.

SKU.io doesn't offer a direct connection to its database, a read-only copy of it, or a ready-made data warehouse connector. Every route below goes through reports or the REST API, which keeps your data scoped to your account and to the permissions of the person or token pulling it.

Compare the options​

You need…UseSetup
The numbers once, for a one-off analysisExport on any reportNone
The same report as a file every day, week, or monthA scheduled custom reportA few minutes
Data that refreshes automatically in a BI tool or your own databaseThe REST API with a personal access tokenA developer, or a tool that can call an API

Export a report​

Most reports under Insights → Reports have an Export button that downloads CSV, and custom reports also export XLSX and PDF. Build a custom report with the exact fields and filters you want, then export it, and the file opens straight in Excel or Google Sheets.

Lists such as sales orders, products, and purchase orders also export from their own pages. A large export runs in the background and appears in your job tray when it's ready.

Schedule a file by email​

When you want the same numbers on a regular basis, save a custom report and schedule it. SKU.io runs it daily, weekly, or monthly and emails the result as a CSV, XLSX, or PDF file to the addresses you choose. See Share a custom report and email it on a schedule.

Many BI tools and spreadsheets can import a file from an email inbox or a shared folder, which turns a scheduled report into a simple, low-maintenance feed.

Pull data through the REST API​

For a feed that refreshes on its own, connect to the SKU.io REST API. Your BI tool, a script, or an integration platform calls the API with a personal access token and loads the results into your own database or warehouse on a schedule.

  1. Create a personal access token with read access to the data you need. Give it the narrowest scopes that cover the job.
  2. Point your tool at the API. What you can read, and the fields that come back, are documented at developer.sku.io.
  3. Schedule the pull in your tool, for example nightly.

To push changes out as they happen instead of pulling them on a timer, subscribe to webhooks. No-code platforms can do both without a developer; see Connect n8n or Make.

Next steps​

Last verified: