Skip to main content
Stuut provides a dedicated S3 bucket for file integration customers. While you can upload files manually during onboarding, Stuut recommends an automated upload from your ERP, data warehouse, or ETL workflow so files arrive on a consistent schedule. Use this page with the Data Contract. The data contract describes which files and fields to provide; this page describes how to deliver those files to Stuut.

What Stuut provides

During onboarding, Stuut will provide the connection details for your dedicated bucket.
1

Confirm your source files

Prepare the extracts listed in the Data Contract. Confirm which files are required for your implementation and which optional files your team can provide.
2

Configure an automated export

Schedule your ERP, data warehouse, or ETL tool to generate the files at the same time each day. Files should represent a complete snapshot or agreed lookback window for each data set.
3

Upload to the Stuut bucket

Use the bucket name, region, and credentials provided by Stuut to upload the generated files. Most teams use the AWS CLI, an AWS SDK, or an existing ETL connector.
4

Send a first test upload

Upload one complete test set so Stuut can confirm connectivity and validate file structure.
5

Move to a recurring schedule

After validation, keep the upload job running on the agreed schedule. Notify Stuut before changing file names, columns, formats, or delivery timing.

File naming

Name each data file with the file date and entity name:
Examples:
For corrections or multiple uploads on the same day, append a sequence number or timestamp:
If your source system already produces stable names, Stuut can usually map them during onboarding. Share the naming pattern before your first test upload.

Delivery schedule

Upload files at least daily unless Stuut confirms a different cadence for your implementation.

Changes to coordinate with Stuut

Tell your Stuut contact before you change:
  • Upload time or cadence
  • File names or folder prefixes