Elemica’s trillion-dollar translation business

Consider the unit of measure. It is a tiny piece of a purchase order, the sort of thing a person notices only when it is wrong. In an Elemica customer case study, one specialty-chemicals business describes needing 60-70 custom unit conversions for a single customer. The document arrived. The difficulty was deciding what it meant. That small distinction helps explain a company whose network now carries, by its own account, about a trillion dollars of annual commerce.

Why rivals agreed on the plumbing

In 2000, leaders from companies including BASF, Dow, DuPont, Rohm & Haas and Shell helped create Elemica. These were businesses with plenty of reasons to compete. Yet the mechanism for exchanging an order was a problem they could sensibly solve together. An efficient factory still had to communicate with somebody else’s efficient factory, and their systems did not necessarily speak the same language.

Elemica’s anniversary account identifies fragmented, point-to-point connections as the limitation its founders saw. Every relationship could become another integration to construct and maintain. A supplier’s technological habits became the buyer’s administrative burden. The shared network offered a different arrangement: connect through common infrastructure, then use it to reach business partners.

There is a pleasing industrial practicality to that origin. Nobody needed to agree on the price of a chemical to agree that retyping its order was a waste of time. Elemica’s expertise grew around the handoffs operators already understood: procurement, customer service, logistics and manufacturing. The chemistry remained proprietary. The plumbing could be shared.

The work between send and receive

Today the company sells cloud software and services for supply chains that extend beyond a manufacturer’s enterprise resource planning system, or ERP. Customers include process manufacturers and their trading partners; public examples range from chemicals businesses such as BASF and LANXESS to tire companies such as Michelin and Goodyear. The relevant users sit at desks in procurement, customer operations, shipping, quality and finance.

Elemica accepts orders through electronic data interchange, APIs, portals and less orderly channels such as emails and attachments. Its order-management applications normalize and validate incoming information, apply business rules and pass transactions into enterprise systems. Forecast collaboration and vendor-managed inventory extend the relationship beyond a single purchase. Exceptions can be routed to people who need to resolve them.

A second set of applications follows the goods. Transportation management covers planning and execution; dock scheduling coordinates arrivals; freight audit checks charges. ProcessWeaver adds multi-carrier shipping execution, including cloud and SAP offerings. An invoice workflow can capture, validate and archive the bill. These functions are modular, which makes the first useful deployment a more manageable decision than buying an entire grand vision.

Then there is quality assurance, a revealing part of Elemica’s process-industry specialization. An electronic certificate of analysis can be checked against material specifications before a shipment arrives. Missing supplier certifications and nonconforming material become managed workflows. The operational question reaches beyond whether a truck is coming: can its contents be received and used?

This places Elemica among business networks and supply chain execution platforms. SAP Business Network and e2open offer alternatives for cross-company collaboration; a manufacturer can also maintain its own connections or buy tools for narrower tasks. Elemica’s case rests on the combination of an existing industrial partner network and applications attuned to process manufacturing. Which one fits depends on the transactions, partners and workflows a buyer actually needs.

Sixty conversions for one customer

The specialty-chemicals case study makes the integration problem concrete. Before its 2009 selection of Elemica, the unnamed company had many partners using different protocols, formats and manual methods. Adding relationships or services required time and money. The initial work connected more than 100 trading partners.

The detail about dozens of unit conversions matters because the hard work survives a successful file transfer. Someone must reconcile business meaning. The case describes subsequent expansion across orders, transport, invoicing and supplier processes. Its reported benefits include less manual entry and more staff attention available for customer service. It is a vendor-published account, so it offers an example rather than a controlled comparison. Still, it identifies a useful buying question: which awkward rules can the platform actually handle?

What the connections were worth

The ownership history puts a price on the business, though not on a subscription. Thoma Bravo completed its acquisition in July 2016. Eurazeo completed a subsequent acquisition in September 2019, announcing approximately $390 million in enterprise value. About $240 million of equity came from Eurazeo and its affiliates for 95% ownership. Those are different financial measures, and both belong to that historical transaction.

Elemica’s commercial model is B2B SaaS supported by implementation and ongoing services. A buyer has to price the actual scope: applications, partner onboarding, integrations and support. Its services pages describe stakeholder alignment and work across external partners as well as internal teams. That is a reminder that installing software and establishing a working business relationship are separate jobs, even when the software helps with both.

For a prospective customer, the defensible calculation starts with its own workload. How many orders need rekeying? How long does an exception sit unresolved? How much effort goes into keeping each connection alive? A quoted fee becomes meaningful beside those costs. The acquisition price tells us what an investor paid for control; it offers no shortcut to a customer’s return on investment.

AI enters through the order desk

In March 2026, Elemica announced expanded AI-assisted onboarding through Launchpad and self-service tools, alongside conversational access to its Insights analytics. The focus was the recurring problem of getting varied customer order formats into executable workflows. In the announcement, OXEA’s supply chain vice president Bret L. Bement described digitizing and onboarding 30 customers in a short period.

Elemica reported reductions in onboarding time of up to 80% and throughput increases of up to three times among organizations using the capabilities. Those are attributed upper-end claims, not a forecast for every buyer. The useful distinction is the job assigned to the AI: help configure and validate incoming orders within an operational process. Reading a PDF is an intermediate step. The order still has to survive fulfillment and invoicing.

“Visibility tells you something happened.”

Cindi Perdue Hane · Chief Product Officer · September 2026

Partnerships push in the same operational direction. An April 2025 alliance with Shippeo adds transportation tracking to execution. A September 2025 offering with Agilis connects chemical product discovery and digital buying with fulfillment. In September 2026, Elemica announced Leader placement in the Nucleus Research Control Tower Technology Value Matrix. Across these moves, the company’s proposition is to connect a signal with a practical response.

Start with one troublesome handoff

The method a reader can borrow is modest. Choose a repeated exchange that absorbs attention: an order, a quality certificate, a freight bill. Define the information required for it to be valid. Agree who owns exceptions. Measure manual effort and elapsed time before expanding to another workflow. That is an editorial lesson from Elemica’s approach, rather than a promise that every integration will pay for itself.

The same reasoning supplies the limits. A business with few repeat transactions has less work over which to spread implementation effort. A manufacturer whose partner data remains inconsistent will still need validation rules. A perfectly timed alert is of limited use when nobody has responsibility for acting on it. Network membership helps only when the relevant partners and processes are connected.

Elemica’s story is amusingly resistant to glamour. It begins with competitors agreeing to improve paperwork and keeps returning to units, confirmations and certificates. Yet these details decide whether a business can turn an intention to buy into a delivered, usable, paid-for product. The company has spent twenty-six years working in that gap. For anyone designing industrial automation, it is an excellent place to look.