One expected submission
Replace scattered attachments with a supplier-specific feed, clear expectations for every required file, and a visible effective period.
Supplier price list intake
Keep supplier price lists ready for the import that depends on them.
Give each supplier a clear submission path, verify identifiers, prices, currencies, and effective dates, and identify one accepted price list your team can use with confidence.
Incoming supplier feedSupplier price list
ActiveReceivedChecks passedCurrent accepted
Control the file before the import
A new price list should not create a new investigation.
When price lists arrive through email or shared folders, your team still has to determine whether the right supplier sent every required file, whether the submission is usable, and which version should be loaded.
Checks before handoff
Catch missing identifiers, invalid amounts, unexpected currencies, and duplicate item keys before acceptance.
History without overwrites
Keep each submitted file unchanged and identify the accepted list without erasing earlier failed or replaced attempts.
A concrete price-list workflow
Give every supplier the same clear route to a usable file.
Your team sets clear expectations once, while every supplier gets understandable status and a straightforward correction path.
Define the expected price list
Set the file format, filename matching, required or optional status, and the table rules your import expects.
Assign the supplier
Give the right supplier contacts a secure, focused place for their price-list submissions.
Set the effective period
Track the month, quarter, or ad hoc business period the submitted list belongs to.
Keep every submitted version
Keep each submitted price list connected to its supplier, effective period, and correction history.
Let the supplier correct issues
Show clear locations and examples so the supplier can correct the price list and submit a new version.
Release the accepted list
Make the current accepted price list available for authorized download by the purchasing, catalog, or import team that needs it.
Example price list
Validate the fields that make a list loadable.
Use transparent rules for one predictable table instead of relying on manual spot checks after the file arrives.
Supplier item IDDescriptionUnit priceCurrencyEffective dateUnit of measure
Identifiers and headers
Require the product and pricing fields your target import needs, including approved aliases.
Prices and dates
Check decimal price values and accepted effective-date formats before acceptance.
Currencies and units
Limit selected fields to reviewed currency codes, units, or other allowed values.
Duplicate item keys
Flag duplicate item identifiers within the submitted price list.
Operational status
Know which supplier list currently counts.
Keep due state, validation outcome, corrections, and accepted-file history around the same supplier feed.
- Missing price list
- Submitted late
- Processing
- Validation failed
- Accepted
- Replaced by a later acceptance
- Current accepted submission
- Complete submission history
Good fit
Control the complete supplier price-list package.
This workflow fits recurring or ad hoc price-list submissions that must be complete and ready before purchasing, catalog, import, or review processes continue.
- The supplier submits a price-list package by period or when prices change.
- Your team defines every expected file and what makes the submission complete.
- A complete price-list package can keep Excel or CSV tables together with approved supporting documents.
- Apply detailed checks to the important Excel or CSV data while every expected file stays connected in one complete package.
Questions your team may ask
Before moving supplier price lists into a portal.
Can a supplier send a price list in more than one file or format?
Yes. Define the complete package your team expects, then apply detailed checks to the structured Excel or CSV data while every supporting file stays connected to the same submission.
Can a supplier replace a failed list?
Yes. The corrected file is a new submission. Earlier attempts remain in history, and a later accepted submission becomes current.
How does an accepted price list reach our ERP or catalog process?
Authorized users can download the accepted price list, or an approved integration can retrieve it through the API for an ERP, catalog, or import process.
Which price-list rules can DTO Flow enforce?
Configure checks for required fields, data types, ranges, currencies, units, effective dates, allowed values, and duplicates. Your team keeps its established commercial approval process.
Explore the complete workflow
Connect supplier intake to clear file rules.
See the supplier experience, consistent validation, clear file expectations, and related partner-file workflows.
Start with one supplier
Make the next price list predictable before it reaches your import.
Define the expected price-list package and checks once, then give the supplier a clear path to submit, correct, and complete it.