Make the percentage a complete question
A quotation that says “high efficiency” may sound precise while leaving the actual comparison unresolved. Even a numerical percentage needs a defined measurement context. Your first response should ask for the particle-size field, method identifier and tested reference together, rather than asking whether the headline number can be increased.
Give the supplier the offered SKU and application information in the same message. A useful reply connects the claim to a specific report and identifies what was tested. If the evidence instead covers another model or an unspecified media sample, record that scope explicitly. A shared filter family name does not establish that the offered assembly has the same result.
Keep the original claim beside the clarified wording. This makes it possible to see whether a later percentage answers the original question or describes a different condition. It also prevents a purchasing spreadsheet from silently turning an incomplete marketing statement into a verified specification.
Identify which filter and claim are being offered
Before evaluating the number, connect the claim to the quotation's exact reference. Record the supplier code, original reference, variant and revision where available. Similar titles or a shared family code can identify a discussion topic while leaving the tested item unresolved.
Physical dimensions belong in the identification record. They cannot establish particle-removal efficiency, media specification or test applicability. Ask for the performance document instead of calculating an efficiency from diameter or height. A catalog that omits the result leaves a question open rather than proving that no further documentation exists.
Where a report names a material sample, ask how its result applies to the complete offered filter. Keep the original sample description visible. A drawing, photograph or matching package label does not supply that explanation. The next useful reply connects the evidence to the candidate rather than merely repeating the percentage.
Read particle size and efficiency together
Donaldson's explanation of liquid-filter beta ratings makes the essential pairing clear: an efficiency or beta result needs the particle size to which it applies. It describes beta as the ratio of upstream to downstream particle counts at the relevant size. This explains reporting terminology; it provides no rating for a MAKEXCAR SKU.
When transcribing a report, retain the particle-size notation exactly, including units and any qualification or symbol used by the laboratory. Ask what that notation means within the cited method. Do not remove a qualifier simply to make the comparison table shorter. A shortened cell can conceal the information needed to determine whether two results are comparable.
A purchasing table should therefore have separate columns for particle-size wording, efficiency wording and source location. Treat these as a linked record. If a percentage is supplied without its particle-size field, mark the row incomplete instead of filling the gap with the size used by another supplier.
A hypothetical count example, with explicit limits
The following arithmetic illustrates a count ratio only. Imagine a defined particle-size reporting category with 10,000 upstream counts and 100 downstream counts on a consistent comparison basis. The ratio is 10,000 ÷ 100 = 100. The associated removal percentage is (1 − 1/100) × 100 = 99%.
Now keep the hypothetical upstream count at 10,000 and change the downstream count to 50. The ratio becomes 200 and the associated percentage becomes 99.5%. This calculation does not specify a micron value, test fluid, actual product or engine application. It is not a proposed test procedure and cannot be used as a catalog rating. These invented count rows are not results from ISO 4548-12 and do not demonstrate that a proposed method applies to a filter.
| Hypothetical row | Upstream / downstream counts | Ratio | Calculated removal |
|---|---|---|---|
| A | 10,000 / 100 | 100 | 99% |
| B | 10,000 / 50 | 200 | 99.5% |
Rows A and B differ by 0.5 percentage points. Under the stated arithmetic, their downstream counts differ by half. That observation explains why rounding deserves attention, but it says nothing about engine wear, service life or value for money. Keep those additional conclusions out of an efficiency comparison unless separately supported.
Ask which test method and edition apply
The official ISO 4548-12:2017 summary describes a multipass test using continuous contaminant injection and online particle counting for full-flow engine lubricating-oil filters. Its published scope is steady-state and excludes flow-rate fluctuations. The abstract is a scope reference, not the full procedure or evidence that an offered filter was tested.
Ask the supplier to identify the report's actual method and edition. Do not treat a method named in an article as mandatory for every filter, and do not substitute a hydraulic-filter method for an engine-oil report merely because both use particle terminology. Where a report claims a standard, request confirmation that the method's scope applies to the tested item and stated conditions.
Read deviations and remarks rather than stopping at the cover page. If the supplier cannot explain a changed procedure or an omitted reporting field, keep the comparison unresolved. A standard number printed in a brochure does not answer which sample was tested, what conditions applied or which page supports the percentage.
Make each missing field lead to a specific request
Use one evidence row per offered reference and keep each result with its own source. Preserve differences between suppliers rather than rewriting the fields until they look equivalent. The purpose is to identify what can be compared and what still needs clarification.
| Field to preserve | Why the comparison needs it | Next request if absent |
|---|---|---|
| Offered and tested reference | Connects the percentage to the purchase | Request documented sample applicability |
| Particle-size wording and units | Defines the size associated with the result | Ask for the exact notation and its method definition |
| Efficiency or beta value and calculation basis | Identifies what the number expresses | Obtain the result page and basis; do not round away a distinction |
| Method, edition and stated conditions | Shows whether the reports support comparison | Request scope confirmation and explanation of deviations |
| Report number, revision and page | Lets another buyer recover the evidence | Ask for an identifiable complete source rather than an isolated chart |
If one supplier provides a percentage at a specified size and another gives a bare micron label, the second row remains incomplete. Do not fill it with the first supplier's efficiency. Ask the second supplier to provide the missing pairing and keep the initial description for comparison with the reply.
Where conditions or reporting conventions differ, describe those differences explicitly. Request an explanation of comparability or appropriate matching evidence before ranking the values. A finding that the supplied documents do not establish a common basis is useful because it identifies the next procurement action.
Keep efficiency apart from other filter requirements
A particle-removal result answers a narrower question than overall replacement suitability. It does not establish thread fit, seal geometry, installed clearance, vehicle coverage, bypass-valve behavior or pressure strength. Keep those requirements in their own evidence fields and avoid allowing one impressive percentage to close the entire sourcing decision.
Conversely, physical identification does not establish filtration efficiency. Diameter and height help describe an item, but there is no mathematical route from those dimensions to a particle-removal percentage. Keep the applicable performance record as a separate requirement.
When the intended application changes, reopen the requirements rather than assuming that the highest quoted number remains the appropriate choice. Identify the applicable vehicle or equipment information and ask the responsible supplier or technical reviewer which documented requirements govern the replacement. This article does not recommend an efficiency target or an oil-change interval.
Control the wording used after sourcing
Once a report has been reviewed, write the product claim so that a reader can recover its source. Retain the tested model, particle-size context and method qualification. Avoid upgrading “result reported for this sample” into “guaranteed for all applications” or turning an efficiency percentage into a claim about engine protection.
If supporting documents remain incomplete, use an inquiry-oriented description and leave the number unpublished. This is preferable to copying another brand's result into an empty field. An accessible audit trail also helps later staff check whether a supplier's revised report still supports the wording in the product listing.
For an unresolved quotation, assign the missing evidence request to a named contact and retain the original attachment. When a replacement file arrives, compare its sample reference and reported conditions with the earlier version. A newer date alone does not establish that the document covers the same filter or supports the same claim. Keep the earlier wording visible until that relationship is clear.
Resolve three incomplete efficiency replies
A micron label arrives without its efficiency
Ask for the associated percentage or beta result and the exact size notation used in the report. Do not treat the micron label as a 100% removal statement. The follow-up should identify the paired result and source page, rather than request a smaller micron figure without context.
Two percentages refer to different particle sizes
Retain both size fields and leave the direct ranking unresolved. Ask which evidence provides a common comparison basis. Changing the heading of the spreadsheet to the same size would alter the claims instead of comparing them.
The report revision changes the sample designation
Compare the new reference with the quotation and earlier report. Ask whether the change reflects a different test object, a corrected designation or another documented relationship. Keep the existing claim under review until that relationship is explained; a later date alone is not applicability evidence.
Request the paired result and applicable report
Use the following fields to make an efficiency inquiry specific. Include the original claim or existing report so the supplier can address the actual missing information.
Candidate: Offered SKU, original reference, application information, revision and quantity.
Claim: Exact percentage or beta wording and its associated particle-size notation. Preserve units, qualifications and the original statement.
Tested object: Sample reference and whether the document covers material, an element or the offered assembly. Explain applicability to the candidate.
Method and conditions: Reported method edition, relevant conditions and deviations. Identify how the size and result fields are defined.
Source: Report identifier, revision and result page. List unanswered questions, including differences that prevent direct comparison.
Browse the current Oil Filters category and send the inquiry through MAKEXCAR's contact page. Confirm the particle-size/result pairing and report applicability before using an efficiency number in a purchasing comparison or product description.
