Job supplier-feed-change-triage-note-with-mapping-suggestion · revised 12 October 2026
When a supplier changes its file, tell me what changed and what to change in my import
For one changed supplier file you get a note that classifies each change, such as a rename, split, truncation or encoding shift, and suggests the matching change to your import mapping.
You might be seeing
- An import ran without an error and the data looked wrong
- The supplier says nothing changed but the file looks different
No passwords, keys, card details or admin invites needed to start.
What usually happened
Drift that passes validation is real: a renamed column, a split name field, a headers-only file, a changed date format. A line-by-line comparison buries it. The question is which kind of change it is and what the import mapping must do about it.
Who it’s for: Purchasing or e-commerce operator whose import broke or looked odd after a supplier changed its file.
Usually starts when: A supplier file arrived with different columns, and nobody can say what changed or what the import must do about it.
The result: For one changed supplier file, a note classifies each change (rename, split, merge, type change, headers-only, truncation, encoding, date format) and suggests the matching change to your import mapping, as text for your developer. A headers-only or truncated file is flagged as not importable. Nothing is applied.
Check whether this job fits
Answer these without sending files or logins. Nothing is submitted unless you choose to contact us.
What you get
- The change note
- The suggested mapping changes, as text
- The classification table for the 12 planted drifts and your 6 changes
- The script, run steps and stored decisions
Included
- Two versions of one supplier file, old and new, as redacted or synthetic copies
- Your current import mapping, as text: column names to fields
- A note that classifies each change and suggests the mapping change
- A smoke test on 12 drifts we plant, and a test on 6 changes you make and keep from us
- The script, run steps and stored decisions
Not included
- Applying any change to your import or store
- Deciding whether to import the new file
- Judging whether the supplier's values are true
- A standing watch on every new file
- Files with personal data
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
On 12 drifts that we plant (rename, split, merge, type change, headers-only, truncation, encoding change, date-format change, extra column, missing column, reordered columns, placeholder nulls), at least 10 are classified correctly with a right mapping suggestion. We plant these and know the answers, so this is a smoke test: 10 of 12 shows only that the true rate is at least 56% with 95% confidence. Then on 6 changes that you make to a copy of your own old file and do not tell us about (for example rename a column, split one, truncate the file, change a date format, add a column, swap two columns), at least 5 are classified correctly with a mapping suggestion your developer confirms. 5 of 6 is a small test: it shows only that the true rate is at least 41% with 95% confidence.
Evidence: The planted list, your 6 changes and the classification table.
A planted headers-only file and a planted truncated file are each flagged as not importable, never as 'no changes'.
Evidence: The two planted files and the note.
Comparing a file with itself reports no change.
Evidence: The note and its zero counts.
Your import mapping file is byte-identical before and after the job.
Evidence: File checksums.
Re-running the script reuses the stored model decisions and gives an identical note; the stored decisions are handed over.
Evidence: Both notes compared, and the stored decisions.
Sign-off. You inspect the planted-drift table and the note, and sign off in writing. Payment follows sign-off. Your developer applies any change.
If it fails. If a check above is not met, you do not pay for this fixed scope. You keep the results and the failures, and we agree whether to stop or re-quote. No surprise work.
When it fits, and when we stop
It fits when
- Two versions of one supplier file as redacted or synthetic copies
- Your current import mapping as text
- A developer or app owner who applies any change
- The files hold product, price and stock data, not personal data
- A developer on your side makes 6 changes to a copy of the old file and keeps them from us until the test run
We stop and tell you if
- There is no written import mapping and none can be written
- The files hold personal data that cannot be removed
- You want changes applied to a live import
- You want every future file watched, which is a different service
What could go wrong
The job reads copies you send and writes files. It changes nothing in your systems, so there is nothing to revert. Our copies of your files are deleted when the job ends.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A broken file is read as 'no changes'. | A headers-only or truncated file is flagged as not importable, and the planted drifts include both. |
| A suggested mapping is applied without checking. | Suggestions are text for your developer. Nothing is applied, and your mapping file is unchanged by us. |
| Your files go to a model provider outside your control. | Before any file is shared we name the provider, its country and its retention terms in writing. Entry jobs run on redacted, synthetic or public copies, or on your own provider account with a key you hold. |
A separate automated reviewer checks the classifications and the planted drifts before hand-over and does not see your 6 changes. A developer on your side makes the 6 changes, confirms the suggestions and signs off. No person on our side is included unless your agreement names one, and at launch the work is largely automated.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the files, the mapping format, the drift types and the severe errors
- Receive both file versions and your current mapping
- Make 6 changes to a copy of your old file; keep them from us
- Classify each change and propose the matching mapping change
- Run the 12 planted drifts, then your 6 unseen changes
- Independent review of the note, the classifications and the not-importable flags
- Hand over the note and script; delete our copies
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the price, a start window and a delivery date before you accept, and work starts only after inputs, a secure handoff route and permissions are in place. Model usage up to a cap agreed in writing is included, and an enquiry creates no charge or booking.
Need to keep it working?
Want every new supplier file checked the same way? The existing import-watching service covers that.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing managed lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Our supplier feed change report compares two versions product by product. This note explains what kind of change happened to the file's structure. syntheticindustry.ai
- A header-diff tool in your browser shows renamed columns for free.
Questions
How is this different from the file change report?
That job lists which products changed. This one says which kind of structural change happened to the file and what your import mapping should do about it.
Will it change my import?
No. It writes suggestions as text.
Can it watch every new file?
Not in this job. A standing service does that.
Send an enquiry
Send us
- The supplier's column names in each version, as text
- How the import maps columns today, in a sentence
- No real records, personal data or credentials in the first enquiry
Later, once you agree
- Redacted copies of both versions by an agreed secure route
- The current import mapping as text
- A developer who applies any change
- A written cap on model usage
You keep both files, your import and every decision. We work on copies you send by an agreed secure route, return a note and a script, and delete our copies when the job ends. We never touch your import or the supplier's system.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “supplier-feed-change-triage-note-with-mapping-suggestion” as the subject.