A sample request that appears to come from a competitor should be handled with the same written checklist you use for every other requester — not with a case-by-case judgment call. Decide two things separately: whether the material can be released at all, and what terms, documentation, and supporting information accompany it. A documented process protects proprietary know-how, keeps decisions consistent across sales staff and regions, and gives you a defensible answer whether you approve or decline.

This article is written mainly for the people who approve or refuse those requests — sales engineers, technical managers, and quality staff at water-treatment material suppliers. It also explains to genuine buyers why a well-run supplier asks for application details before sending a polyphosphate sample.

Why polyphosphate and siliphos crystal samples need their own review rules

A small quantity of polyphosphate glass carries an unusual amount of analyzable information. Phosphate content, chain-length distribution, bead geometry, bulk density, and dissolution behavior in a simple lab setup can all be measured from a few hundred grams by anyone with standard wet-chemistry equipment and a bit of patience. That does not make a competitor’s request improper, but it does mean the review should be deliberate rather than automatic.

Terminology matters here. “Siliphos” is a trade name associated with a slow-dissolving polyphosphate glass used for scale and corrosion control in potable and industrial water lines. Products sold as siliphos crystal, phosphate crystal, or polyphosphate media are not necessarily identical to one another, and their behavior depends on composition, form (bead, crystal, granular, or powder), and how they are dosed. Treating the whole category as one interchangeable material is the most common source of both bad sample decisions and bad technical conclusions.

Information to collect before approving any sample

Collect the same fields from every requester. A vague request is not proof of bad intent, but it is a legitimate reason to ask for clarification before releasing material.

Not every field is mandatory. Small evaluation quantities for a named end user with a clear application can often proceed with less paperwork than a request for a custom form or an unusually large quantity.

A three-tier model for consistent decisions

Tiering turns a subjective question into a repeatable one. Define the tiers, publish them internally, and record which tier each request falls into and why.

Note what the tiers deliberately do not include: “is a competitor.” Competitors buy products on the open market, and a blanket refusal rule is difficult to apply consistently, easy to apply unfairly, and often unnecessary. The decision should rest on what is being requested and what supporting information comes with it.

What a polyphosphate sample can and cannot demonstrate

Mixing up these two columns causes most disputes between suppliers and evaluators.

A bench dissolution test tells you how a material dissolves under bench conditions. It does not predict cartridge life in a real installation, because residence time, temperature, water chemistry, and contact geometry all shift the result. Where a sample is being used for qualification, pair the bench work with a pilot or side-stream trial in the actual system.

Confidentiality, competition, and consistency

Two separate protections are usually in play. The first is contractual: a confidentiality or limited-use agreement restricts what the recipient may do with the sample and any accompanying data. The second is physical: no agreement prevents a laboratory from analyzing a material it lawfully holds. Understanding that limit is what stops a review process from relying on paperwork alone.

Practical rules that hold up over time:

• Send only what the stated test needs. Extra quantity adds no technical value and expands exposure.
• Keep technical data sheets to published specifications. Formulation ratios, sintering or compaction parameters, raw-material sources, and process windows are not sample-support information.
• Apply the same tier criteria to a long-standing customer and to an unfamiliar requester. Exceptions should be recorded with a reason, not made quietly.
• Keep sample correspondence to the sample itself. Do not use a review conversation to exchange price, capacity, or market plans with a competing company.
• Do not treat “food grade” as evidence of drinking-water suitability. That determination depends on the exact product, the application conditions, and the destination market’s rules, and it must be verified rather than assumed.

Documentation that makes the process defensible

A sample log with consistent fields turns individual decisions into a reviewable record. At minimum, capture: request date, requester and company, stated application, tier assigned, reason code, grade and quantity released, production lot or batch code, shipping date and destination, terms signed, and outcome including any test results the requester later shares. Retain a reference sample from the same lot for as long as your quality records require, so that any later performance question can be traced back to the material that was actually sent. Regular review of the log — monthly or quarterly — quickly shows whether the criteria are being applied evenly or drifting.

Common mistakes

• Deciding requests individually with no written criteria, which produces inconsistency that is hard to explain later.
• Sending a sample from a non-representative or unlabeled lot, which undermines the evaluation before it starts.
• Treating a competitor’s request as inherently improper rather than evaluating what is actually being asked for.
• Releasing process or formulation information that the requester never needed for the stated test.
• Allowing urgency to bypass the tier criteria without recording the exception.

Frequently asked questions

Should we refuse all sample requests from competitors?

Not automatically. A blanket rule is difficult to apply consistently and may block legitimate business. Base the decision on the application, the requested quantity and form, and the information provided, and apply the same standard to everyone.

Can we ask what the requester intends to do with the sample?

Yes. Application, equipment type, and source-water conditions are normal technical questions, and the answers determine which grade is relevant. Requests that cannot answer them are usually not ready for a sample.

Does a confidentiality agreement prevent reverse engineering?

It limits use and disclosure contractually, which has real value in a commercial relationship. It does not physically prevent laboratory analysis of a material the recipient holds. That is why quantity control and documentation matter alongside the agreement.

Is a competitor’s sample request improper?

No. Purchasing and evaluating a product that is sold on the market is generally lawful. The concerns are confidential information, misleading claims about the requester’s identity, and inconsistent treatment of different requesters.

How large should an evaluation sample be?

Large enough for the stated test method and representative of production material. Since sample size depends on the equipment and the test plan, confirm the method first and calculate from there rather than working from a default figure.

Requesting a sample of siliphos crystal or polyphosphate media

If you are evaluating a polyphosphate material for a specific duty, a short, specific request moves much faster than a general one. Tell us the application (scale inhibition, corrosion inhibition, or another function), the equipment type and contact arrangement, the source-water conditions you expect, the form and grade you need, the quantity required for your test method, the destination market, and any compliance documentation your project requires. ENVO CHEMICAL can then confirm which grades are relevant to that duty and what supporting documentation is available for your evaluation.