Task and feed questions
Name the treatment task first: landfill leachate, highly polluted industrial wastewater, or another task described plainly, because the task decides which membrane family deserves discussion. Then describe the feed in general terms: the water source, the main pollutants in plain language, and any extreme character, such as high solids or high salt content in general terms. A feed description does not need laboratory detail in the first message, but it should go beyond the word wastewater, or the reply can only be general.
If the feed varies widely, say so, because variability changes the discussion as much as average character does. If the feed is unknown, say that plainly and ask what feed information would help, rather than inventing feed detail that could misdirect the discussion. An honest gap in the first message can be filled in the reply round, while an invented detail can send the discussion toward the wrong family or the wrong scope.
Goal and scope questions
State the goal for the treated water in general terms: a purity goal, a reuse goal, or a discharge goal, together with any document the destination or the project requires. A goal stated plainly lets the company judge whether ultrafiltration, reverse osmosis, or a combination deserves discussion, while a goal left unstated leaves the family choice to guesswork. If the project expects a combination of families, name that expectation and the intermediate goal between stages, so the combination is discussed from the start.
State the scope wanted: membranes alone, components, or a wider system discussion. The showroom lists membranes and components, and it mentions system-level work in general terms, so the scope question changes the reply substantially. A component discussion needs the existing system context in general terms, while a system discussion needs the task, the feed, the goal, and the site context, and the inquiry should supply whichever set matches the stated scope.
Commercial and document questions
Please confirm the minimum order quantity, the lead time, and the payment terms in your inquiry before you place an order. Those three questions apply to every membrane inquiry, and this site states no figure for any of them, because the source pages publish no fixed commercial terms. Asking them together with the task, feed, goal, and scope, in the first message, lets the company reply with terms that match the specific membrane inquiry in question.
Add the document questions that apply: any certificate or test document the project or the destination requires, named exactly, and any trial or sample possibility the project team would value, described by what it should demonstrate. Documents and trials belong in the first message for membranes even more than for other lines, because a membrane decision without a document or a trial rests on a general description, while a decision with them rests on evidence for the specific feed and goal.
Sending the membrane checklist
Copy the answered questions into the inquiry form on the inquiry page, or into an email to [email protected], with the same content either way. Read the message once before sending, checking for the details that are easiest to forget: the task named plainly, the feed in general terms, the goal, the scope, and the commercial questions. A message that passes that read usually receives a complete reply, while one that fails it usually receives a round of clarifying questions about the task, the feed, or the scope.
Keep a copy of the sent checklist with the order record, and check the reply against it point by point when it arrives. Any checklist point the reply does not cover should be asked again before an order is placed, because an unasked point is an unagreed point. That habit is especially valuable for membrane orders, where the task, the feed, and the goal interact, and where an assumed point can lead to a membrane that fits the description but not the project.