Bulk Injector Test Reports Show Only “PASS” and Cannot Support Batch Comparison: An Eswatini Fleet Parts Buyer Rebuilds Acceptance Criteria Around Test Programme IDs, Operating-Point Data and Unit-Level Traceability
“PASS” Was Not Enough to Compare Two Deliveries
A fleet-parts buyer in Eswatini purchased diesel injectors in batches for commercial vehicles operating across regional transport routes.
The supplier provided a test sheet with each shipment, but the document contained little more than the injector reference and the word “PASS.”
The first delivery operated without a clear common complaint. When a later batch generated several technical questions, the buyer discovered that the two shipments could not be compared objectively.
There was no record of which test programme had been used, which operating points were checked or which individual injector corresponded to a specific test record.
The purchasing issue became a technical acceptance-data problem, not simply a supplier-price comparison.
The Buyer Defined What a Test Report Needed to Explain
The Eswatini team did not demand a longer report for appearance alone.
It wanted answers to three practical questions:
What Was Tested?
The document should identify the complete injector reference and the applicable test programme or programme ID.
Under Which Conditions?
Relevant operating points should identify controlled parameters such as test pressure, pulse width or other programme-specific conditions.
Which Physical Unit Does the Record Represent?
Where individual traceability is available, serial or unit identification should connect the report to the actual injector.
These three questions formed the basis of the revised acceptance process.
Operating-Point Data Replaced the Generic Pass Label
Depending on injector design, a useful bench test may include several functional regions.
For example:
- Starting or low-delivery condition;
- Idle delivery;
- Medium-load quantity;
- Higher-load delivery;
- Internal return flow;
- Nozzle sealing;
- Electrical response where applicable.
The buyer did not assume that every injector technology needed exactly the same test points. The important requirement was that the supplier identify what was actually evaluated.
A result without its permitted range or test condition was considered difficult to compare across batches.
Batch Comparison Became Possible
For later Eswatini deliveries, incoming staff linked the purchase order, batch identity and available unit references to test documentation.
When an injector generated a field question, the buyer could determine which shipment it came from and what acceptance data had been recorded before installation.
This allowed technical staff to compare patterns instead of relying on memory or general supplier statements.
Field Feedback Was Added to the Acceptance Loop
The fleet parts department also classified returns by application error, installation issue, fuel contamination, confirmed injector test failure or no fault reproduced.
This prevented every returned unit from being counted automatically as a supplier-quality defect.
Over time, the acceptance record and field record could be reviewed together.
Why This Mattered in Eswatini Fleet Supply
Regional commercial fleets may operate vehicles of different ages and engine configurations while procurement is centralised.
A parts buyer therefore needs documentation that remains useful after the injector leaves the warehouse.
The test report becomes part of the technical traceability chain between supplier, inventory and workshop.
Technical Lesson
The independent core of this case is test-report comparability.
“PASS” is a conclusion, not a measurement record.
For an Eswatini B2B injector buyer, programme identification, operating-point results and unit-level traceability created a stronger basis for comparing deliveries and investigating later claims.
The objective was not to create unnecessary paperwork. It was to ensure that when two batches were described as tested, the buyer could understand whether they had actually been evaluated under comparable technical conditions.
