Another spreadsheet from a department store
A department store wants to stock your knitwear. Before they will, they send a supplier questionnaire: every factory used, its address, the tier 2 suppliers for yarn, fibre origin by style, copies of any certificates, and a signed code of conduct. A marketplace sent something similar last month, in a different format. A boutique chain wants the same things in a web portal.
The information exists, mostly. It is spread across emails from your agent, certificate PDFs in someone's downloads folder and knowledge in your production manager's head. Each questionnaire is answered from scratch, and each answer is a little different.
Why every questionnaire starts from zero
- Factory and supplier details are not held in one place.
- Fibre origin and certificates are recorded per order, if at all, not per style.
- Certificates expire and nobody tracks the dates.
- Each retailer's template asks the same questions in different words.
- Previous answers are in sent emails, hard to find and reuse.
What it costs to answer this way
| Problem | Consequence |
|---|---|
| Answering from scratch | Days of your production manager's time |
| Inconsistent answers | Questions from retailers who compare notes |
| Expired certificates sent | Awkward corrections and lost trust |
| Slow responses | Listings and wholesale deals delayed |
There is also the risk of saying something you cannot back up. Claims about materials and sourcing need evidence, and the questionnaire is where retailers start to check.
How we hold supply chain data once
- A supplier register holds each factory, mill and trim supplier: address, contacts, what they make for you and any audits or certificates, each with its expiry date.
- Each style is linked to the suppliers that made it and the fibres used, with the certificate that supports any claim like 'organic' or 'recycled'.
- Certificate files are stored against their supplier or style, with reminders before they expire so you can request renewals.
- When a questionnaire arrives, as a spreadsheet, a PDF or a list of questions, a language model maps each question to the matching data and drafts an answer, citing the record it came from.
- Questions it cannot answer from the data are left blank and flagged for your team, never guessed.
- Your team reviews, edits and approves each answer. The approved answers are saved so the next similar question starts from them.
The drafting speeds up the typing. The facts come only from your records, and a person signs off every answer.
The next questionnaire
A new retailer sends a sixty-question spreadsheet. It goes into the tool, which drafts most of the answers from the register, attaches the current certificates and lists the questions it cannot answer: two about a new trim supplier you have not recorded yet. Your production manager checks the drafts and fills the gaps instead of rebuilding everything from scratch. The retailer gets consistent answers, backed by documents that are in date.
Keeping it honest
The value of the register is that it only says what you can show. If a style has no certificate for a claim, the tool flags it rather than filling it in, and if a factory's audit has lapsed, the draft says so. Which claims you can make and what evidence they need is a question for you and your advisers. The register just makes sure your answers match your records every time.
Many brands find the register useful beyond questionnaires. Product pages that mention materials can draw on it, and your team can see at a glance which styles have a full set of supplier information and which still have gaps to close before the next retailer asks.
Signs you need a supply chain register
- Every retailer questionnaire is answered from scratch.
- Factory and mill details are spread across emails.
- Certificates live in downloads folders with no expiry tracking.
- Answers to similar questions differ between retailers.
- Answering questionnaires falls on one overloaded person.