What is the output schema when sheets have different column sets?

The output schema is the union of all column names found across all sheets and workbooks. Rows from sheets lacking a given column receive empty (null-equivalent) cells for that column. The output always has a consistent schema regardless of per-sheet variation.

Is the output format compatible with Snowflake or BigQuery bulk load?

The output is a standard single-sheet .xlsx. Both Snowflake (via COPY INTO from stage) and BigQuery (via load job) support .xlsx as a source format. Alternatively, open the file with pandas and write to CSV or Parquet for your preferred ingest format.

When should I use Deliteful vs. handling this in my pipeline code?

Deliteful is best for ad-hoc or irregular Excel drops where writing and maintaining a flatten script isn't justified. For fully automated scheduled pipelines processing the same schema repeatedly, keep the flatten logic in your pipeline code for full control and observability.

Does the tool handle workbooks with merged cells or complex formatting?

Deliteful reads raw cell values from the first-row-header structure. Merged cells and complex formatting are not preserved or interpreted — the tool extracts the underlying values. If your source workbooks use merged headers or non-standard structures, the output may require cleanup.

Pre-Process Multi-Tab Excel Files Into a Single Flat Sheet for ETL Ingestion

Multi-tab Excel workbooks are one of the most common sources of friction at the start of an ETL pipeline. Most ingestion frameworks expect a single flat table, not a workbook with data distributed across 8 region tabs. Adding a pre-processing step to flatten the workbook before ingestion is necessary — Deliteful's Excel Combine Sheets tool handles that step without requiring a custom script.

Create free account

The typical approach to handling multi-tab Excel inputs in an ETL pipeline is a small pandas or openpyxl script that reads each sheet, concatenates the DataFrames, and writes a flat CSV or Excel file for the next stage. This works but adds a script to maintain, test, and update when source schemas change. For pipelines that process ad-hoc or infrequent Excel drops — stakeholder submissions, vendor reports, partner data shares — the maintenance overhead rarely justifies the script.

Deliteful covers the flatten step for the 80% case: first-row headers, multiple sheets, multiple workbooks, column union output, optional provenance columns. The output is a clean single-sheet .xlsx suitable for COPY INTO Snowflake, BigQuery load job, or any other flat-file ingestion step. For fully automated recurring pipelines, Deliteful's UI handles the manual drops; for scheduled automation, the pre-processing logic is simple enough to remain in the pipeline code.

How it works

1
Receive the multi-tab Excel input
Collect the workbook(s) from the upstream source — vendor, partner, or internal stakeholder — in .xlsx or .xls format.
2
Upload to Deliteful for pre-processing
Drop one or multiple workbooks; all sheets across all files are flattened in one job.
3
Add lineage columns for staging
Enable 'Include sheet name' and/or 'Include source file name' to preserve provenance for your staging layer or audit log.
4
Load the flat output into your pipeline
Feed the combined .xlsx into your ingestion step — COPY INTO, pandas read_excel, or a bulk load utility.

Frequently asked questions

What is the output schema when sheets have different column sets?: The output schema is the union of all column names found across all sheets and workbooks. Rows from sheets lacking a given column receive empty (null-equivalent) cells for that column. The output always has a consistent schema regardless of per-sheet variation.
Is the output format compatible with Snowflake or BigQuery bulk load?: The output is a standard single-sheet .xlsx. Both Snowflake (via COPY INTO from stage) and BigQuery (via load job) support .xlsx as a source format. Alternatively, open the file with pandas and write to CSV or Parquet for your preferred ingest format.
When should I use Deliteful vs. handling this in my pipeline code?: Deliteful is best for ad-hoc or irregular Excel drops where writing and maintaining a flatten script isn't justified. For fully automated scheduled pipelines processing the same schema repeatedly, keep the flatten logic in your pipeline code for full control and observability.
Does the tool handle workbooks with merged cells or complex formatting?: Deliteful reads raw cell values from the first-row-header structure. Merged cells and complex formatting are not preserved or interpreted — the tool extracts the underlying values. If your source workbooks use merged headers or non-standard structures, the output may require cleanup.

Create your free Deliteful account with Google and flatten your next multi-tab Excel input into a pipeline-ready sheet without writing a script.