Chemelex standardises procurement across eight markets

Chemelex has deployed Ivalua’s source-to-contract and supplier-performance systems across operations in eight markets, creating a shared procurement platform for sourcing, contracts, supplier governance, and risk screening.

The implementation covers the United States, United Kingdom, India, China, Australia, Singapore, Japan, and Germany. It includes Ivalua’s Supplier Relationship Performance Management capability and integrations with Chemelex’s enterprise resource planning and third-party screening systems.

Durvah IT Consulting led the deployment with Chemelex and Ivalua. The project has entered live operation rather than remaining a pilot, giving procurement teams a common system across regions with different suppliers, currencies, regulations, and operating practices.

Chemelex manufactures self-regulating electric heating cables and thermal sensors used in pipe-freeze protection, industrial temperature maintenance, snow melting, and leak detection. Its supply chain includes raw materials, fabricated components, electrical assemblies, logistics providers, and professional and operational services.

That supplier mix creates several layers of procurement control. Direct materials affect product availability and technical quality, while contractors and service providers introduce different commercial, safety, data, and compliance risks.

A central platform can standardise the process, but it still has to accommodate the difference between buying a production component and appointing a specialist service company. Excessive standardisation can make simple purchases cumbersome, while weak controls around strategic suppliers expose the business to inconsistent decisions.

Mahek Patel, global process excellence manager at Chemelex, described the implementation as one of the company’s most significant digital-transformation initiatives. She said it had established a procurement foundation that strengthens governance and provides greater visibility for data-driven decisions.

Source-to-contract systems generally cover supplier discovery and onboarding, sourcing events, evaluation, negotiation, contract creation, approval, and performance management. Connecting those functions can reduce fragmentation when supplier records, tenders, contracts, and risk checks are held in separate applications or local spreadsheets.

The third-party screening integration is an important part of the design. Supplier checks can include sanctions, ownership, financial stability, modern slavery, environmental performance, cybersecurity, and other risk factors.

When screening is disconnected from onboarding and contracting, a supplier may progress through the purchasing process before an adverse result reaches the responsible team. Automation can place those checks at defined gates, but it does not remove the need for judgement.

Screening services can produce false positives, incomplete records, and alerts requiring investigation. Procurement teams need clear ownership for resolving exceptions and documenting why a supplier was approved, restricted, or rejected.

The same principle applies to supplier performance. A platform can collect delivery, quality, cost, service, and compliance information, but the result depends on consistent definitions and reliable source data.

Comparing suppliers across eight markets is difficult when business units measure performance differently or record problems only after a relationship has deteriorated. A shared system gives Chemelex an opportunity to establish common scorecards and escalation rules.

It can also expose where local purchasing practices have developed around genuine operational requirements rather than resistance to standardisation. The strongest procurement programmes distinguish between necessary local variation and avoidable inconsistency.

ERP integration should reduce duplicate entry between sourcing decisions, supplier records, purchase transactions, and financial processes. It also increases the importance of master-data governance.

Incorrect supplier identifiers, banking details, tax records, or contract dates can move quickly between connected systems, making disciplined approval and change controls essential. An integrated platform can spread accurate information efficiently, but it can distribute poor data just as effectively.

Contract visibility offers another operational benefit. Procurement teams can use a central repository to track expiry dates, pricing provisions, service levels, insurance requirements, and other obligations.

The repository will be less useful if signed documents are stored without structured metadata or if business users continue placing orders outside negotiated terms. Contract management therefore depends on process adoption as much as software configuration.

Kishore Gajendra, director at Durvah IT Consulting, said the implementation depended on close collaboration between the three organisations rather than technology alone. That distinction is important in procurement digitalisation, where configuration is often simpler than persuading employees and suppliers to follow a new process consistently.

Supplier adoption can determine whether a platform improves collaboration or merely shifts administration outside the buying organisation. Registration, document submission, tender response, and performance-review workflows need to be proportionate to the relationship.

A major strategic supplier may support a detailed process, while a small specialist vendor can struggle with unnecessary complexity. The system needs enough structure to support governance without excluding capable suppliers through administrative burden.

Chemelex has not disclosed the number of users, suppliers, contracts, or sourcing events covered by the deployment, nor has it published savings or cycle-time results. The announcement therefore establishes geographical reach and system capability rather than measured commercial outcomes.

The next phase is operational: improving data completeness, moving more sourcing activity through the platform, monitoring supplier performance, and using contract information in day-to-day purchasing. A successful go-live creates the foundation; procurement value appears only when the system changes decisions and behaviour across the organisation.