Required column missingExpected Product ID or accepted alias SKU
Controlled file intake for legacy imports
Excel/CSV Validation for Partner Imports
Check the columns, values, dates, numbers, and duplicates your process depends on, then give partners a clear path to submit a file that is ready to use.
Validation reportpricing_june.xlsx
Needs correctionArchiveSubmitted file kept unchanged
Value is not acceptedStatus must match the accepted-value list
Duplicate unique valueSKU repeats in example rows 62, 88, and 104
Before the next import
Turn recurring spreadsheets into import-ready files.
Give partners clear, useful guidance and give import owners one clearly accepted file before the next process begins.
Keep every submitted version
Keep every submitted Excel or CSV file connected to its partner, period, and submission history.
Apply the agreed checks
Check the selected table against the approved columns, value rules, formats, and duplicate safeguards.
Return actionable feedback
Give partners clear feedback with affected locations, counts, examples, and a practical next action.
Let the sender correct and resubmit
The partner uses the report to correct the export and submit a new attempt while the earlier file remains in history.
Move the accepted file forward
Make the accepted file available for authorized download or API retrieval when it is ready.
Validation coverage
Check the spreadsheet details that keep imports moving.
Capture the approved expectations for each recurring file so partners keep familiar exports and your team receives consistent, usable data.
Columns and aliases
Keep approved partner header names flexible while giving the receiving process one dependable set of fields.
- Require the columns the receiving import depends on
- Resolve approved aliases such as SKU to the standard Product ID column
- Detect the intended header and unexpected column changes
Types and accepted values
Make sure each accepted column contains values the receiving process can actually interpret.
- Validate text, integer, decimal, date, datetime, and boolean values
- Restrict fields to approved value lists
- Accept the date and time formats approved for the exchange
- Read numbers consistently and apply the approved ranges
Duplicate safeguards
Catch repeated identifiers in one table and flag an identical file that has already been received.
- Require values in selected columns to be unique within the submitted file
- Warn when the same file already appears in the relevant submission history
Friendly partner feedback
Exact enough for import owners, clear enough for senders.
Partners see what needs attention, where to look, and what to do next, while import owners retain the precision needed to approve the file confidently.
- File, sheet, column, and example row references where available
- Affected counts so teams understand the size of the problem
- A focused set of useful examples
- A clear correction or resend action for fixable problems
- Earlier attempts retained with the submission and period history
Consistent by design
A dependable quality check before import.
DTO Flow applies your reviewed requirements consistently to every submitted table, giving partners and import owners a result they can understand and trust.
Agreed file rules determine readiness.
The same file and the same approved expectations produce the same result, so every acceptance decision is clear and repeatable.
Best fit
Built for repeatable partner tables.
DTO Flow brings the most value to recurring partner exports whose columns and values need to stay dependable from one period to the next.
- Recurring CSV exports with one header row and a consistent table
- Excel sheets that contain one clear table selected for validation
- Partner submissions that feed the same import every week, month, or period
- Contracts that can express expected columns, types, values, and uniqueness
See the supplier upload and correction experience See how File Feed Contracts define these expectations See how validation fits inside the Partner File Gateway Compare manual spreadsheet checks with DTO Flow Use the CSV validation checklist Audit Trail for Partner File Exchanges Data Retention for Partner File History
Common questions
What teams want to know before strengthening spreadsheet intake.
Does validation change the submitted file?
The submitted file stays unchanged, while the validation result clearly records what passed and what needs attention.
What happens when validation fails?
The sender sees a safe, understandable report, corrects the file, and submits again. The earlier attempt remains attached to the period and submission history.
Which duplicate checks are supported?
DTO Flow can require unique values where your process needs them and highlight a file that has already appeared in the relevant submission history.
Which spreadsheet layouts are a good fit?
Choose the CSV table or Excel worksheet whose rows and columns drive the next process. The complete workbook can remain connected to the same submission while its business table receives detailed checks.
What decides whether a file passes?
The approved rules for that file determine the result. The report shows the affected locations, counts, and examples so the decision is easy to understand.
Protect the next import
Make spreadsheet intake predictable before it reaches your import.
Start with one recurring partner spreadsheet, define the checks that matter, and give senders a clear path to correct problems before handoff.