A product value changes in inriver. Technically, the update is correct at the source. Commercially, it still has to reach technical data sheets, catalogues, product segments and every language variant — each following its own route through selection, layout, review and approval, so the source data is current well before the documents are.
Wolf Oil had structured product information and established layouts. What it lacked was a controlled route from an approved product update to every required document variant.
Wolf Oil now reports more than 75% less manual document-production work.
One update, many outputs
Lubricant companies rarely update one isolated PDF. A specification can appear in a technical data sheet, a catalogue section and a commercial product overview — sitting under several brands, in several languages, with different review paths.
That complexity doesn't come from the value itself. It comes from repetition: each output is prepared separately, so the same work returns in a slightly different form. Products are selected again, language content is checked again, a layout is found, adjusted and approved again.
Experienced teams keep this moving through accumulated knowledge and workarounds — which export to use, which file is current, which exception applies to a particular brand. Over time, that knowledge becomes part of the production system, without ever becoming a real system.
Why the process kept expanding
Wolf Oil's earlier setup relied on manual, ad hoc production. Updates could take weeks or longer, because every downstream document followed its own route.
A designer would start from an existing file. Marketing would check brand treatment. Product information travelled through handoffs, agency requests and correction rounds before a usable document came back.
There was no single dramatic failure. The burden accumulated quietly — another export, another correction list, another PDF to compare against the source.
Adding brands or languages made the process heavier. Translation was only one part of the work; content selection, template choice, structure and review could all change with it.
Connecting data to output
The answer wasn't to replace Wolf Oil's existing systems. Product information already lived in inriver — the missing layer sat between those data fields and the documents people needed to publish.
2imagine Pulse now connects Wolf Oil's product data with approved templates, language requirements and workflow rules. The repeatable production work is handled in one configured flow:
- product specialists remain responsible for technical correctness;
- marketing retains ownership of brand governance;
- regulatory or local review can remain part of the approval path;
- Pulse handles the repeatable assembly around those decisions.
inriver product data → configured template and language logic → controlled multilingual output
For the core product-sheet flow, Wolf Oil generates 14 language versions, with Arabic currently being implemented. Where a language requires a different document variant, a separate template can remain part of the workflow. The gain didn't come from creating more data — it came from no longer rebuilding the same work around that data every time it changed.
What changed at Wolf Oil
The strongest result is the one Wolf Oil reported itself: manual document-production work fell by more than 75%.
Product sheets are now generated in seconds, and full catalogues for defined product segments can be finalized within one day. Production is currently largely managed by one owner, with marketing involved where brand-guideline governance requires it.
The multilingual setup is also easier to extend. Product sheets are generated in 14 languages, with Arabic currently being implemented. Agency dependency and manual preparation have been reduced substantially — not eliminated, and not shifted wholesale to another internal team.
"I am happy because the migration reduced stress, timing and mistakes."
Wolf Oil also reported more accurate, up-to-date output. These results belong to Wolf Oil's configured environment — they're not a universal promise for every company or document type. Their value lies in what they demonstrate: recurring publication becomes easier to control when data, templates and ownership are connected instead of treated as separate production jobs.
The full Wolf Oil use case covers the customer context and implementation in more detail.
The right automation boundary
Automation doesn't decide whether a viscosity value is correct. It can't approve a regulatory statement or judge whether a local formulation is appropriate for a specific market — nor should it. Once approved information is available, the workflow can place it into the correct structure without asking people to repeat the same assembly work for every language and output. That's the useful boundary: human review stays where judgment is needed, routine production stops consuming that same attention, and exceptions become easier to see.
For lubricant and chemical companies, that distinction matters. Product data, technical ownership, brand presentation and language requirements all meet inside the same document, but they don't all belong to the same team. A controlled publication flow connects those responsibilities without pretending to replace them.
Not every document deserves automation. A one-off brochure can be handled perfectly well as a design project. The case changes when the same work keeps returning: the same assortment appears under several brands, local or language variants multiply, and teams end up rebuilding datasheets or catalogue sections from information that already exists elsewhere.
That's usually where workflow-driven automation starts to earn its place — and it doesn't have to start with the entire document landscape. One recurring TDS flow, one product family or one defined language set can expose the real bottlenecks quickly; from there, the setup can expand as data sources, templates and governance evolve.
2imagine Pulse is built for that role: not as a replacement for PIM, ERP, DAM or human review, but as the document-automation layer that connects them to repeatable output.
The oil, lubricants and chemicals market page explores that operating context across datasheets, catalogues and related product communication.
Review one recurring document flow
A useful first conversation starts with one document that consumes too much manual effort. We can start with the current source data, the template and the route from an approved update to the final PDF, then identify where the process still breaks into exports, corrections and repeated production.