ZDHC Gateway: a chemical verification checklist for mills

01

Start with the exact product

To verify a chemical purchase using the ZDHC Gateway, match the exact product and formulator to the available conformance information, record when you checked it, and reconcile that identity with the incoming material. A supplier name or a familiar logo is not enough to identify which formulation you are buying.

ZDHC announced its Gateway relaunch on 20 August 2026, with navigation and workflows organised around user roles. This is an August platform update, not a new September purchasing deadline. The checklist below is Straits’ suggested procurement workflow; it is not an official ZDHC audit checklist or a guide to unverified screen controls.

02

Keep three kinds of evidence separate

ZDHC describes ChemCheck as product-level information about MRSL conformance, InCheck as inventory-level reporting, and ClearStream as wastewater reporting. MRSL means Manufacturing Restricted Substances List. Use the report that addresses your question: information about a facility’s wastewater cannot establish the identity of a particular drum.

The current Chemical Purchasing chapter covers a purchasing policy, conformant chemicals, commodity-chemical supplier due diligence, solvents and a chemical inventory list. This wider scope matters when a purchasing team concentrates on branded auxiliaries but overlooks other inputs. Consult the original programme guidance for the requirements applicable to your facility.

03

What the September transition update changes

In its 21 September 2026 message, ZDHC says some processes have changed, functionality is still being enhanced and occasional issues may occur. It directs users to its Knowledge Base or Zeddy assistant for navigation guidance before opening a support ticket. The message does not announce a new purchasing deadline or waive chemical requirements.

For a mill, a missing search result or a report that cannot be retrieved leaves a question open. Record the exact observation before drawing a conclusion about the product. A platform problem, an identity mismatch and a confirmed conformance issue require different follow-up; the observation alone does not identify which one applies.

As a separate, platform-specific example, Worldly’s BHive guidance warns that spelling and manufacturer-name differences can lead to the wrong database entry. It also explains that its “Unverified” label means compliance has not been verified in that system, not that hazardous substances have been demonstrated. Do not transfer that label’s meaning to a different platform without checking its own guidance.

04

Give unresolved records a clear owner and next step

Use the following suggested exception record when a purchasing check cannot be completed. This is Straits’ proposed working method, not a new ZDHC requirement or a substitute for the facility’s chemical approval procedure.

• Observation: save the exact trade name, formulator, available reference, check date and the result or error. Note whether the issue arose in Gateway or a connected inventory service.
• Identity check: compare the quotation, label and supporting documents. Ask the supplier to clarify name or code differences; do not select a similar-looking entry simply to complete a row.
• Navigation question: consult current official help for the task and user role. Keep the help-page reference with the record so another colleague can repeat the check.
• Unresolved technical issue: prepare a concise support description with the relevant product reference, steps attempted and a redacted screenshot if useful. Share only what the support channel needs.
• Purchasing decision: assign the chemical-management owner to review the evidence under the mill’s procedure. Set a follow-up date; a ticket number or an unanswered query is not a product approval.

Keep “verification unresolved” distinct from both “approved for purchase” and “confirmed non-conformant.”

05

Build a record before comparing offers

For a Bangladesh dyeing or finishing mill buying through an intermediary, make the identity trail explicit. Our suggested record is one row per proposed product, with supporting files kept together. It should let a colleague repeat your check without relying on a forwarded screenshot.

• Identity: quoted trade name, product code, formulator and selling company; explain any differences in writing.
• Evidence: product reference or available ChemCheck report, stated conformance information and the date checked. Resolve missing or ambiguous details with the seller or relevant evidence issuer.
• Use: intended process, substrate and current technical and safety documents. Keep suitability for the intended trial as a separate decision.
• Handoff: the employee responsible for resolving each discrepancy and the evidence needed before purchasing releases the order.

A similar product name is a question to resolve, not a reason to assume the same formulation.

06

Connect the order to the incoming batch

ZDHC’s Chemical Traceability chapter calls for an internal system tracking chemicals used in production, alongside stock rotation by expiry and/or purchase date. The practical purchasing question is whether the receiving team can connect the delivered material to the product that was reviewed.

Our suggested receiving check compares the order and delivery documents with the container label, records the available batch reference and flags unexplained substitutions. Keep the discrepancy visible to the purchasing and technical teams before release for use. A renamed product should trigger a documented identity check, not an informal edit to the inventory.

07

Use a short exception note

Consider an illustrative purchase: the quotation names Auxiliary A, while the supporting product report names Auxiliary A Plus. This does not establish that the offer is invalid, but it leaves identity unresolved. Ask the seller to explain the relationship and provide evidence for the exact proposed material.

A useful internal note can be brief: “Product identity unresolved; quotation and supporting record differ. Purchasing owner to obtain clarification. Technical suitability review remains separate.” This is a process example, not a finding about any named supplier.

08

Make verification lead to a better trial

After resolving the document trail, define what the mill needs the product to achieve and how the trial will measure it. Product conformance information alone does not demonstrate performance on your fabric, machine and process. Keep the evidence decision and the production decision connected, but record them separately.

For a discussion with Straits, bring the proposed product identity, the document gap and your intended application. That gives the enquiry a concrete starting point without assuming that any product or supplier has already been approved.