Topic summary

Documenting a supplier's response to a discrepancy

Sourcing › Vendor reports third-party testing documentation quality batch & lot numbers Solved

This is a generated summary. It shows the 7 most-liked posts from a topic of 50, in their original order, with the accepted answer included where one exists. It is a reading aid and it will miss nuance — the full topic is the record.

o.nybergTL219 May 2026#1

On the subject in the title: Documenting a supplier's response to a discrepancy Working notes rather than a conclusion.

A question about how a record should be read rather than about a supplier.

We have results from VendorInvestigate and from Medutest on the same product line, months apart, agreeing closely. My question is what that agreement actually establishes, given that neither saw the other's sample.

I suspect the honest answer is narrower than it feels, and I would like it stated precisely.

36 likes 2mo

f.chowdhuryTL229 May 2026#5

v.okonkwo, post #3: Photograph the vial and the label before opening. It costs ten seconds and it is what turns a report into something checkable. Not the answer, but possibly the question that gets there. Go to post

Right, and stated more narrowly than I would have dared to state it.

26 likes in reply to #3 2mo

ThibodeauTL3Regular Solution31 May 2026#6

Where I part company with post #4, and it is a narrow parting.

Dosing and purity: a vial that is 99% pure might contain 80% of its label claim if the other mass is water, counter-ion, and excipient. Purity and content are different. Both matter for different reasons.

It is a small point and it changes the answer, which is an awkward combination.

7 likes 2mo

t.abubakarTL219 Jun 2026#18

Adding the measurement that post #15 says would settle it.

The cost of a submission is worth stating. It is the main reason people do not do this and knowing the figure helps somebody else decide.

29 likes 1mo

s.achebeTL21 Jul 2026#27

The arithmetic in post #24 is right; the assumption feeding it is the part to check.

Pattern across lots: a single result is a data point. Three or four results from the same supplier showing a consistent pattern becomes a record worth discussing. Two results that disagree might just be measurement variation.

25 likes 27d

t.lindqvistTL27 Jul 2026#32

t.abubakar, post #18: Adding the measurement that post #15 says would settle it. The cost of a submission is worth stating. It is the main reason people do not do this and knowing the figure helps somebody else decide. Go to post

Photograph the vial and the label before opening. It costs ten seconds and it is what turns a report into something checkable.

The conclusion is tentative; the arithmetic underneath it is not.

33 likes in reply to #18 21d

l.trevinoTL225 Jul 2026#48

a.sorensen, post #42: I had written a reply contradicting post #40 and deleted it. Here is what survived. The cost of a submission is worth stating. It is the main reason people do not do this and knowing the figure helps somebody else decide. Go to post

Following, with nothing to contribute beyond having asked the same thing elsewhere.

32 likes in reply to #42 3d

Read the full topic (50 posts)

This topic was referenced in

One lot is one lot: when a report becomes a patternSourcing › Vendor reports · 2 replies

Suggested topics

Topic	Participants	Replies	Views	Activity
Revisiting: Filing a first vendor report: a worked example Sourcing › Vendor reports batch & lot numbers documentation quality third-party testing disputed On the subject in the title: Revisiting: Filing a first vendor report: a worked example Working notes rather than a conclusion. A question about Filing a first vendor that I think has a definite answer,…		2	60k	11mo
Coming back to: Why our vendor pages link the storefront and mark it sponsored Sourcing › Vendor reports third-party testing batch & lot numbers certificate of analysis documentation quality Why our vendor pages link the storefront and mark it sponsored I have a specific reason for asking rather than idle curiosity, and the context is below. Reading back through what has been written here about…		2	22k	8h
The report format the maintainers ask for, and why each field is there — what changed since Sourcing › Vendor reports third-party testing disputed Janoshik Analytical The report format the maintainers ask for, and why each field is there — what changed since Writing it up because I had to work it out twice and would rather nobody else did. Structured report rather than an…	+29	35	6.6k	13mo
Reporting a good result: why nobody bothers and why they should Sourcing › Vendor reports third-party testing Janoshik Analytical certificate of analysis batch & lot numbers Reporting a good result: why nobody bothers and why they should — setting out what I have, and where I think it stops being reliable. Reporting a good result: setting out the arithmetic in full, because I…		2	3.5k	17h
Reporting a good result: why nobody bothers and why they should — one year on Sourcing › Vendor reports batch & lot numbers certificate of analysis documentation quality disputed Wiki Posting this under the heading it deserves: Reporting a good result: why nobody bothers and why they should — one year on Everything below is what sits behind that. The question about Reporting a good result…	+19	27	4.7k	18mo

Related topics — sharing the tags third-party testing, documentation quality, batch & lot numbers

Topic	Participants	Replies	Views	Activity
A payment that went through twice: how it was resolved Sourcing › Payments payments research use only documentation quality Solved Closed A payment that went through twice: how it was resolved Writing it up because I had to work it out twice and would rather nobody else did. A payments question, with the mechanics separated from the money. What…	+20	24	55k	3mo
About the Vendor reports category Sourcing › Vendor reports certificate of analysis batch & lot numbers third-party testing Pinned Wiki Structured reports on named suppliers. Batch, date, method and document, or it stays in the unverified column. This post is a community wiki: any member at trust level 3 or above can edit it, and every edit…		4	65k	18mo
Revisiting: Aggregate verification data across the directory, with caveats Sourcing › Independent verification PeptideMeter third-party testing blind sampling Medutest Closed Revisiting: Aggregate verification data across the directory, with caveats — setting out what I have, and where I think it stops being reliable. I have spent a fortnight trying to pin Aggregate verification…	+22	26	23k	17mo
Reporting a good result: why nobody bothers and why they should Sourcing › Vendor reports third-party testing Janoshik Analytical certificate of analysis batch & lot numbers Reporting a good result: why nobody bothers and why they should — setting out what I have, and where I think it stops being reliable. Reporting a good result: setting out the arithmetic in full, because I…		2	3.5k	17h
A supplier who responds to a discrepancy with silence Sourcing › Red flags underdosing documentation quality moderation mislabelling Closed On the subject in the title: A supplier who responds to a discrepancy with silence Working notes rather than a conclusion. Two things I would like separated before anyone answers on supplier, because they get…		2	6.1k	16mo