Solutions · By process
Supplier product files turned into reviewed master data, ready for upload.
New articles arrive as supplier spreadsheets and manufacturer exports with their own codes and attributes. StencilFlow finds the table in each file, combines them per article, applies your rules and produces a reviewed file for upload to your PIM, shop or ERP. A person confirms the column mapping, and gaps go to a person, never a guess.
What lands in the inbox
- Supplier product sheet
- Manufacturer attribute export
- Price conditions
Read, checked against your data and handed off, with people deciding the exceptions.
The flow
From inbox to system, step by step
Every case follows the same visible path. Where a rule cannot decide, a person does.
- Mailbox
- Find table
- Confirm mapping
- Combine
- Review gaps
- Upload file
Step by step
How it runs, step by step
A worked example with made-up names. Rules do the checking; people decide what the rules cannot.
- 1
Product data in several files
Each vendor sends sheets, attribute exports and price conditions in its own shape.
XLSXCobalt Crafts productsCSVAcme Toys attributesXLSXBirchwood price conditions - 2
Find the table
The engine reads layout and column meaning, not a fixed template; the header can sit a few rows down.
Cobalt Crafts products
Catalogue 2026 · all prices excl. VAT
BarcodeOmschrijvingKleurMateriaal8712345000036Clay setBLK-MClay8712345000043Paint kitREDPage footer, left out
- 3
One record per article
Files about the same article are combined by EAN, then SKU.
XLSXProduct sheetCSVAttribute exportXLSXPrice conditionsArticle 8712345000036
- Product sheet
- Attribute export
- Price conditions
- 4
Check against your structure
Rules for mandatory attributes, classification codes, prices and duplicates run on every row.
- EAN valid and not a duplicatePass
- Mandatory attributes presentReview
- Colour code in your classificationReview
- Purchase price and conditions consistentPass
Human review - 5
Gaps go to a person
Missing or unknown values are listed with the reason, never guessed. Fix them at the source.
Source
XLSXCobalt Crafts productsRead
- ColourBLK-M
- Material(empty)
- EAN8712345000036
Not in your classificationConfirm mapping - 6
Remembered for next time
Confirmed names are stored per vendor, so their next file maps itself.
Remembered: Cobalt Crafts
- BarcodeEAN
- OmschrijvingDescription
- KleurColour
Maps itselfXLSXCobalt Crafts, new range - 7
Ready-to-import files
A person imports the file; every row keeps its source file, sheet and row.
- Product file for uploadReady rows only
- Review fileGaps and new products with reasons
- Summary emailTo the product team
Before and after
Product data onboarding, with and without StencilFlow
Today
- Product data assembled from several files by hand
- Attribute codes translated with lookup sheets
- New articles wait weeks to be sellable
- Errors propagate into purchasing and webshop
With StencilFlow
- Columns found by pattern recognition and confirmed once per vendor, then remembered
- Missing or inconsistent attributes listed in a review file
- A product file for upload, ready rows only
- Every record traceable to its source file
Rules
Checks that run on every case
Your rules and reference data, applied the same way every time. Each outcome records which check passed or failed.
- Mandatory attributes present
- Codes map to your classification
- Purchase price and conditions consistent
- No duplicate articles
Connects to
Hands off to the systems you run
- PIM import file
- Shop bulk upload file
- ERP import file
Through an API, an import file or a mailbox. About actions and integrations
In practice
Supplier product data checked against your rules and prepared for your ERP before an article goes live.
Ready to look at your inbox?
Bring one process and a handful of real documents. We show you the path from inbox to decision, on your own data.