Who this is for
Operations or purchasing owner at a distributor or shop whose supplier files arrive every day or week and whose imports break in small ways nobody owns.
Someone checks each import by eye, a bad file has reached live prices before, or nobody knows who to ask when a supplier changes a column, an encoding or a delivery time.
The result
The named supplier feeds keep importing correctly. Each failed or suspicious file is investigated and ends in a proposed fix, an explanation of what your supplier must change, or a written recommendation to hold the file; each month you see what arrived, what we recommended holding and how each case ended.
What is included
- Watching the import results of up to three named supplier feeds, from run results and reject lists that you share
- Investigation of each failed or held file, with a proposed fix on a copy of your import code or an explanation with evidence
- A change report between each new file you share and the previous one, with moves over your thresholds flagged, and a written verdict on whether the file looks fine to import
- A written monthly summary of files seen, held, fixed and still open
You receive
- A proposed fix, with its test, for each failure we can fix within the agreed monthly number
- An explanation of what your supplier or your host must change, when the cause is outside your code
- A change report for each new file, and a written monthly summary
What is not included
- Applying changes to your live importer, store or database, which stays with your team
- Holding supplier credentials, keys or logins
- Correcting the supplier's data or negotiating with the supplier
- Out-of-hours cover or any guaranteed response time
- Personal data of any kind
What we need from you first
- The names of the supplier feeds you want kept correct, and how each is delivered and how often
- How often imports fail or need hand fixes today, as best you know
- Who reviews and applies changes. No credentials, supplier files or private code in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- For each proposed fix, the failure is reproduced on a copy and passes after the change using the same synthetic file.
- Every new file you share from a named feed has a change report and a written verdict, and the report reconciles distinct keys with the previous file (old keys minus absent plus added equals new keys), with the extra rows that repeat a key counted separately for each file.
- Each month's summary lists every file seen, held or failed on the named feeds and how each ended.
You review each proposal and the monthly summary. A proposal counts as delivered when you accept it.
When we would stop or decline
- Most failures are caused by something outside your control that nobody will raise with the supplier
- Safe checking would need supplier credentials or live production access that we would have to hold
- Failures regularly exceed the agreed monthly number, so we agree a different scope
Questions
How is this different from buying one fix?
A one-off job repairs one fault once. This watches the feeds you name and takes each failed or suspicious file through to a proposal, an explanation or a hold, month after month.
Do you change my live importer?
No. We propose changes on a copy. Your team applies them.
Do you need my supplier logins?
No. We work from run results, reject lists and copies of files that hold no personal data.
Price and terms
£395/month · untested offer price. Billing is monthly under the written terms we agree with you. Nothing is charged until you have agreed them.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.