1. Overview

The Fulfil Data Warehouse is a managed analytics layer powered by Google BigQuery. It gives your team direct access to your operational data for reporting, analysis, and business intelligence — without affecting your live production systems in any way.

Fulfil automatically and continuously syncs your operational data into BigQuery in the background. There is no manual data-transfer step, no staging area to set up, and no dataset to configure or name on your end. The dataset already exists and is maintained entirely by Fulfil. Once access is granted, it simply becomes visible to your authorized accounts.

After access is set up, users can query the dataset directly using SQL, or connect any compatible BI tool of their choice — including Looker, Power BI, Tableau, Metabase, Redash, and Google Sheets via Connected Sheets. All connections are fully read-only, meaning queries will never affect production performance, alter data, or interfere with day-to-day operations.

What This Guide Covers

This document is intended for Saras Analytics implementation teams and client stakeholders who need to set up external SQL or BI tool access, referred to as Mode B. It covers the complete end-to-end process from prerequisites through to a live connection, including:

• What needs to be in place before raising a Fulfil Support ticket
• How to open a support ticket and what information to include
• The Designated Contact (DC) approval process and what to expect
• Technical configuration settings for BigQuery and supported BI tools
• Saras Analytics Pulse service account setup for pipeline ingestion
• Common errors and how to resolve them quickly

If your team requires reporting within the Fulfil UI rather than external access, that is covered under Mode A — Built-in Reporting. Refer to docs.fulfil.io/developers/custom-reporting/ for that setup. This guide covers Mode B only.

Key Things to Know Before You Start

Before walking through the steps, keep the following points in mind. They address the most common questions and mistakes that cause delays during setup.

Access is always read-only. Queries run against the data warehouse never write back to production. There is no risk of altering or deleting operational data through this connection.

Only Google accounts are supported. Every email address submitted for BigQuery access must be a valid Google account. Microsoft 365 addresses, custom SMTP addresses, or any non-Google email will not work and will need to be replaced before the request can be processed.

The Pulse account must be added to the Fulfil UI first. Fulfil grants access at the Google-account level and verifies each address against the users already registered inside the Fulfil instance. If the Saras Pulse service account — or any user email requiring access — has not been added to the client's Fulfil user list beforehand, the support ticket will stall. This is the single most common cause of delay, and it must be completed before a ticket is opened.

You do not need to supply a dataset name. There is no need to initiate a data transfer or prepare anything on the BigQuery side. Fulfil handles all of that automatically. The dataset is already there — it just needs to be made visible to the right accounts.

Set Data Location to US. When configuring your BigQuery client or BI tool, always set the data location explicitly to US. The Fulfil-managed dataset is stored in US regions. If the location is left as the EU default, you will encounter access errors that appear to be permission issues but are not. This setting is one of the most frequently overlooked configuration steps.

How Access Works — At a Glance

Once a support ticket is submitted with the required information, Fulfil Support will route it to the Designated Contact on the account for approval. The DC is a named individual with authority to approve data access requests. Because the data warehouse provides read access to all tables in the instance, this approval step is mandatory and cannot be bypassed.

After the DC approves, Fulfil Support will grant BigQuery access to each listed Google account and deliver a credentials JSON file. This file is used to authenticate your BI tool or SQL client. The typical turnaround from DC approval to credentials delivery is one to two business days.

For Saras Analytics engagements, the Pulse service account must be included in the access request so that the ingestion pipeline can read data from the Fulfil-managed BigQuery project. Fulfil Support is responsible for allowlisting this account — Saras does not have the ability to grant access to a project it does not own.

Official Documentation

For further technical reference, Fulfil's official documentation is available at:
docs.fulfil.io/developers/data-warehouse/overview

Here attaching SOP doc: FulFil_SOP_Doc