---
title: "Translation Workflow: TMS, PIM and Component Schema"
canonical_url: "https://www.laioutr.com/es/blog/translation-workflow-tms-pim-component-schema-2026"
locale: es
meta:
description: "A translation workflow breaks when TMS, PIM and component schema disagree on what is translatable. Here is how to wire them together the right way."
"og:description": "A translation workflow breaks when TMS, PIM and component schema disagree on what is translatable. Here is how to wire them together the right way."
"og:title": "Translation Workflow: TMS, PIM and Component Schema"
---
# Translation Workflow in the Frontend: How TMS, PIM and Component Schema Connect
Índice
1. [1.What actually breaks (it is rarely the translation itself)](#what-actually-breaks-it-is-rarely-the-translation-itself)
2. [2.Three systems, three different jobs](#three-systems-three-different-jobs)
3. [3.Declare translatable fields at the schema level, not in a spreadsheet](#declare-translatable-fields-at-the-schema-level-not-in-a-spreadsheet)
4. [4.Preventing layout breakage from text expansion](#preventing-layout-breakage-from-text-expansion)
5. [5.How locale routing ties back to the same schema decision](#how-locale-routing-ties-back-to-the-same-schema-decision)
6. [6.A five-step way to wire it together](#a-five-step-way-to-wire-it-together)
7. [7.Where this fits into a broader frontend architecture](#where-this-fits-into-a-broader-frontend-architecture)
8. [8.Frequently asked questions](#frequently-asked-questions)
9. [9.Next steps](#next-steps)
10. [10.More from the Laioutr platform](#more-from-the-laioutr-platform)
1. [1.What actually breaks (it is rarely the translation itself)](#what-actually-breaks-it-is-rarely-the-translation-itself)
2. [2.Three systems, three different jobs](#three-systems-three-different-jobs)
3. [3.Declare translatable fields at the schema level, not in a spreadsheet](#declare-translatable-fields-at-the-schema-level-not-in-a-spreadsheet)
4. [4.Preventing layout breakage from text expansion](#preventing-layout-breakage-from-text-expansion)
5. [5.How locale routing ties back to the same schema decision](#how-locale-routing-ties-back-to-the-same-schema-decision)
6. [6.A five-step way to wire it together](#a-five-step-way-to-wire-it-together)
7. [7.Where this fits into a broader frontend architecture](#where-this-fits-into-a-broader-frontend-architecture)
8. [8.Frequently asked questions](#frequently-asked-questions)
9. [9.Next steps](#next-steps)
10. [10.More from the Laioutr platform](#more-from-the-laioutr-platform)
Most translation failures are not translation failures. They are handoff failures between three systems that never agreed on who owns what. The translation management system, or TMS, moves strings from a source language to a target language. The product information management system, or PIM, owns product data. The frontend component schema decides what actually gets rendered on the page, and how. When these three disagree about which fields are translatable, where locale-specific content actually lives, and how much space a translated string is allowed to take, the failure rarely shows up inside the TMS itself. It shows up in the browser: a German button label wrapping onto three lines, a French product description sitting inside a layout built for English word counts, a locale switch that quietly points at the wrong page. This is a practical guide to wiring the three systems together so translation stops breaking at the frontend.
## What actually breaks (it is rarely the translation itself)
Ask a team where their last localization bug came from and the answer is almost never a bad translation. It is one of four repeat offenders. First, text expansion: translated strings, especially into German, tend to run noticeably longer than their English source, and a component built for a fixed-width button or a single-line label breaks the moment a longer string lands in it. Second, PIM attributes that were never meant to be free text get treated as translatable copy anyway, so a structured field designed for a SKU or a spec value ends up carrying marketing sentences nobody modeled for. Third, locale routing and content locale drift apart: a page renders correctly in the CMS preview but resolves to the wrong locale once it hits production routing, because nobody connected the two systems at the schema level. Fourth, and most common, is scope creep in the component schema itself: a status label mapped to a design token, for example, slowly becomes something an editor tries to translate anyway, because nothing in the schema stopped them. None of these four are translation quality problems. They are handoff problems, and they get fixed once, at the schema layer, not once per locale.
## Three systems, three different jobs
Once the handoff problem is visible, the fix is mostly a matter of ownership. The PIM's job is canonical product data: SKUs, dimensions, pricing rules, category codes, values that stay identical everywhere. Most of that should never enter a translation workflow, because it is not language-dependent. The exception is a field that is really marketing copy wearing a PIM attribute's name, a long-form product description, for instance, which needs to be treated as content and routed through translation, even though it lives next to the SKU. The content layer's job, whether a CMS or a component-driven page builder, is editorial content: landing pages, campaign copy, blog posts, authored per market with a full localization workflow behind it. The frontend component schema's job is to define the contract: which props accept translated rich text, which accept a fixed value that must never vary by locale, and how much length a translatable prop can hold before the layout breaks. The TMS's job is orchestration only, not ownership. It picks up flagged, keyed strings from the source locale, routes them through a translation job, and writes the result back to the same key in the target locale. The moment a TMS becomes a second place where content actually lives, locale drift has already started.
## Declare translatable fields at the schema level, not in a spreadsheet
The fix for most of the ownership confusion above is boring on purpose: every field in a content model should carry an explicit localization flag, translatable or fixed, decided once when the field is created, not re-negotiated ad hoc by whoever happens to be running a translation job that quarter. That decision belongs to whoever owns component management and content modeling, not to a spreadsheet maintained separately by the localization team. Two practical rules follow. First, every translatable string needs a single, stable source key, referenced identically by the content layer and the TMS, so a round trip through translation never quietly creates a second, drifting copy of the content. Second, localizations should reference the same underlying content node across locales rather than forking a new node per locale, because a forked node is a promise to keep two documents in sync by hand, and that promise gets broken within a quarter.
## Preventing layout breakage from text expansion
Text expansion is not a translation defect, it is a design assumption that was never tested against anything but the English source. German UI strings routinely run meaningfully longer than their English equivalent, sometimes long enough to break a layout only ever proven with English word counts. Three habits prevent most of this. First, give every component prop that accepts translated text an explicit character budget as part of its schema definition, not just a data type. Second, test new components against a worst-case-length placeholder, sometimes called pseudo-localization, during component review, before any real translation exists, because waiting for the German translation to discover a layout bug is the most expensive way to find it. Third, prefer flexible containers with a defined wrap or line-clamp behavior over fixed-height boxes for translatable text, and never bake translatable text into an image asset, or a simple copy change turns into a design ticket.
## How locale routing ties back to the same schema decision
Routing is usually built once, early, by whoever set up the frontend, and then forgotten by everyone who did not build it. That is exactly the problem: a URL should resolve to the locale that matches the actual localized content behind it, not to whichever market the frontend happened to be built for first. If the schema already says which fields are translatable, the routing layer needs to resolve that locale variant without duplicating the entire page tree per market. That is the practical argument for treating [Multi-Brand and Multi-Market](https://www.laioutr.com/en/product/multi-brand-multi-market) as a platform property rather than a per-project build: one component tree, with locale-specific data resolved at render time, instead of a forked frontend per market that someone has to keep in sync by hand. Get the schema, the content layer, and the routing layer agreeing on the same source of truth, and hreflang correctness mostly follows on its own. Keep them separate, and hreflang becomes a manually maintained mapping table that goes stale the first time someone adds a locale.
## A five-step way to wire it together
None of the above requires a rebuild. It requires a short, deliberate sequence, usually completed one content model at a time rather than as a single migration project.
1. Audit your content model and mark every field translatable or fixed at the schema level, not in a wiki page or a spreadsheet someone maintains separately.
2. Move marketing copy that currently lives inside PIM attribute fields into a proper content layer with localization support, and keep the PIM itself limited to canonical, mostly non-translatable data.
3. Give every translatable string a stable key that both the content layer and the TMS reference, so a translation round trip never creates a second, competing record of the same content.
4. Set a character budget and a wrap or truncation strategy for every component prop that accepts translated text, and review new components against a worst-case-length string before any real translation exists.
5. Wire locale routing directly to the content locale, so switching locale resolves the same component tree with different data, rather than a separate page tree that drifts out of sync over time.
Do these five in order and most of what looks like a translation problem on the ticket board turns out to have been a schema problem all along.
## Where this fits into a broader frontend architecture
We are not trying to replace a TMS or a PIM, and teams that expect us to are looking in the wrong place. What we build under the [Agentic Frontend Management Platform](https://www.laioutr.com/en/agentic-frontend-management-platform) is the layer where the outputs of both actually meet the rendered page: a [component schema](https://www.laioutr.com/en/composable-headless-frontend) that knows which props are translatable before a translated string ever arrives, and a [content management](https://www.laioutr.com/en/product/content-management) layer built for exactly the kind of localization workflow described above, instead of a general-purpose CMS bolted onto a rigid frontend that was never designed with locales in mind. For teams still running content through a [headless CMS](https://www.laioutr.com/en/headless-cms) layered on top of a monolithic frontend, this is usually the fastest place to start: not a new TMS, not a new PIM, but a schema layer that finally tells both of them what they need to know.
## Frequently asked questions
**Does Laioutr replace our PIM or TMS?** No. Laioutr sits at the frontend and component layer, where the outputs of both are actually rendered. Your PIM stays the source of canonical product data, and your TMS stays the orchestration layer that moves strings through a translation job.
**Where should marketing copy live, in the PIM or the content layer?** In the content layer, in almost every case. Keep the PIM limited to structured, mostly non-translatable data. A long-form product description is content, not an attribute, even if it currently lives next to the SKU.
**How do we test for text-expansion problems before a translation even exists?** Review new components against a worst-case-length placeholder string during design and development, not against the English default. This is often called pseudo-localization, and it catches layout breaks weeks before a real translation would.
**Does fixing this also fix locale-specific SEO issues?** Indirectly, yes. Once the schema, the content layer, and the routing layer agree on the same source of truth, hreflang correctness mostly follows automatically. It is a downstream benefit, not the primary reason to do this work.
## Next steps
If your team is untangling a translation workflow that keeps breaking at the frontend, [book a 30-minute demo](https://www.laioutr.com/en/pricing). We will look at your current content model, your PIM setup, and where the schema layer between them needs to catch up.
## More from the Laioutr platform
- [Multi-Brand and Multi-Market](https://www.laioutr.com/en/product/multi-brand-multi-market)
- [Content Management](https://www.laioutr.com/en/product/content-management)
- [Composable Headless Frontend](https://www.laioutr.com/en/composable-headless-frontend)
- [Headless CMS](https://www.laioutr.com/en/headless-cms)
- [For Content Managers](https://www.laioutr.com/en/role/content-manager)
**About the author:** Marcel Thiesies is Co-Founder of Laioutr and works on how translation, product data, and frontend schema actually connect in production storefronts.
---
Compartir este artículo
[Compartir en Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.laioutr.com%2Fes%2Fblog%2Ftranslation-workflow-tms-pim-component-schema-2026) [Compartir en X](https://x.com/intent/post?url=https%3A%2F%2Fwww.laioutr.com%2Fes%2Fblog%2Ftranslation-workflow-tms-pim-component-schema-2026&text=) [Compartir en LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.laioutr.com%2Fes%2Fblog%2Ftranslation-workflow-tms-pim-component-schema-2026) [Compartir en Pinterest](https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fwww.laioutr.com%2Fes%2Fblog%2Ftranslation-workflow-tms-pim-component-schema-2026&description=) [Compartir por correo electrónico](mailto:?subject=&body=%0A%0Ahttps%3A%2F%2Fwww.laioutr.com%2Fes%2Fblog%2Ftranslation-workflow-tms-pim-component-schema-2026)
## Más artículos interesantes
Conocimiento práctico sobre desarrollo frontend, agentes inteligentes y headless
[Al blog](https://www.laioutr.com/es/blogs)
[iPhone Duo and Ecommerce: What Merchants Need to Know Now
iPhone Duo goes on sale on October 23, 2026. Online stores don't need a dedicated app or a custo…](https://www.laioutr.com/es/blog/iphone-duo-ecommerce-foldable-storefront)
[Datos de producto estructurados: cómo se notan en tu storefront
Datos de producto estructurados significa que cada dato del producto vive en un atributo tipado, con…](https://www.laioutr.com/es/blog/structured-product-data-pim-frontend-2026)
[El 44 % decide con prueba o PoC: el PoC de storefront para DACH
En la región DACH, las decisiones de software se toman cada vez más con las manos en la masa: en el …](https://www.laioutr.com/es/blog/storefront-proof-of-concept-dach-buyers-2026)
[Comparativa FMP: cómo elegir la Frontend Management Platform adecuada
Elegir una Frontend Management Platform (FMP) no consiste en comparar listas de funciones, sino en s…](https://www.laioutr.com/es/blog/frontend-management-platform-comparison-how-to-choose-2026)
[DAM, PIM y CMS convergen: qué significa para el frontend de tu tienda
Los proveedores de DAM, PIM y CMS están entrando en el terreno de los demás, y cada vez más equipos …](https://www.laioutr.com/es/blog/dam-pim-cms-convergence-content-hub-storefront-2026)
[Contentful Live Preview: lo que tu frontend tiene que resolver
Con Contentful Live Preview, los editores ven un borrador junto al editor de la entrada y siguen los…](https://www.laioutr.com/es/blog/contentful-live-preview-frontend-perspective-2026)
[Gobernanza de contenido a gran escala: contenido de producto y assets
Gobernanza de contenido a gran escala significa definir una sola vez roles, aprobaciones, reglas de …](https://www.laioutr.com/es/blog/content-governance-product-content-brand-assets-frontend-2026)
[Agentes de IA como operadores del frontend: arquitectura y control
Un agente de IA se convierte en operador del frontend cuando vigila el storefront en producción, det…](https://www.laioutr.com/es/blog/ai-agents-as-frontend-operators-2026)
[Los agentes de compra leen tu feed: qué cambia el Agentic Commerce
El Agentic Commerce añade un nuevo lector a tus datos de producto: los agentes de compra de ChatGPT,…](https://www.laioutr.com/es/blog/shopping-agents-product-feeds-agentic-data-distribution-2026)
[Server-side tracking en e-commerce: la medición vuelve a ser completa
El server-side tracking traslada el envío de eventos de analítica y conversión desde el navegador de…](https://www.laioutr.com/es/blog/server-side-tracking-ecommerce-complete-measurement-2026)
[Imágenes de producto por deeplink, no por ZIP: assets siempre al día
Si todavía envías las imágenes de producto a distribuidores, marketplaces y prensa en archivos ZIP, …](https://www.laioutr.com/es/blog/product-image-deeplinks-asset-distribution-2026)
[De PrestaShop 8 a 9 sin replatforming: desacopla primero el frontend
Puedes quitar la mayor parte del riesgo de la actualización de PrestaShop 8 a 9 si separas la storef…](https://www.laioutr.com/es/blog/prestashop-8-to-9-upgrade-without-replatforming-2026)
[Order management con un OMS como fulfillmenttools: la vista frontend
Un order management system eficiente decide qué ubicación prepara un pedido, cuánto stock hay realme…](https://www.laioutr.com/es/blog/order-management-fulfillmenttools-oms-frontend-2026)
[¿Sin presupuesto para replatforming en 2026? El frontend sí se aprueba
Si en tu presupuesto de 2026 no hay sitio para un replatforming, no eres el único, y no tienes por q…](https://www.laioutr.com/es/blog/no-replatforming-budget-frontend-project-approval-2026)
[Gestión de pedidos en jardinería: lo que tu storefront debe mostrar
En el retail de jardín y bricolaje, un mismo carrito puede contener un artículo que va en paquete, u…](https://www.laioutr.com/es/blog/garden-retail-order-management-seasonal-frontend-2026)
[](https://www.laioutr.com/es/apps/shopify)
Laioutr
[Shopify](https://www.laioutr.com/es/apps/shopify)
Shopify es una plataforma de comercio para vender online y en tienda física.
[](https://www.laioutr.com/es/apps/shopware)
Laioutr
[Shopware](https://www.laioutr.com/es/apps/shopware)
Shopware es una plataforma de e-commerce flexible de origen europeo para catálogos de productos y comercio omnicanal.
[](https://www.laioutr.com/es/apps/adobe-commerce)
Laioutr
[Adobe Commerce](https://www.laioutr.com/es/apps/adobe-commerce)
Adobe Commerce es una plataforma de comercio empresarial para escenarios B2C y B2B complejos y globales.
Planned
[](https://www.laioutr.com/es/apps/b2b-sellers)
Laioutr
[B2Bsellers](https://www.laioutr.com/es/apps/b2b-sellers)
Suite B2B para Shopware que convierte la tienda online en una plataforma profesional de comercio B2B.
Planned
[](https://www.laioutr.com/es/apps/commerce-layer)
Laioutr
[Commerce Layer](https://www.laioutr.com/es/apps/commerce-layer)
Commerce Layer es una plataforma de headless commerce para que inventarios y catálogos estén disponibles online.
[](https://www.laioutr.com/es/apps/commercetools)
Laioutr
[Commercetools](https://www.laioutr.com/es/apps/commercetools)
Commercetools es una plataforma de e-commerce headless basada en SaaS y utilizada en todo el mundo.
[](https://www.laioutr.com/es/apps/emporix)
Laioutr
[Emporix](https://www.laioutr.com/es/apps/emporix)
Emporix es una plataforma de composable commerce API-first para escenarios B2B y B2C escalables.
Planned
[](https://www.laioutr.com/es/apps/hcl-software)
Laioutr
[HCL Software](https://www.laioutr.com/es/apps/hcl-software)
Suite empresarial de comercio y experiencia digital con un alto grado de configurabilidad.
Planned
[](https://www.laioutr.com/es/apps/intershop)
Laioutr
[Intershop](https://www.laioutr.com/es/apps/intershop)
Plataforma de comercio empresarial para modelos de negocio B2B y B2C complejos.
Planned
[](https://www.laioutr.com/es/apps/magento-2)
Laioutr
[Magento 2](https://www.laioutr.com/es/apps/magento-2)
Plataforma de comercio ampliable y muy extendida para escenarios B2C y B2B.
[](https://www.laioutr.com/es/apps/oxid-eshop)
Laioutr
[OXID eShop](https://www.laioutr.com/es/apps/oxid-eshop)
OXID eShop es una plataforma de comercio ampliable para requisitos B2B y B2C complejos.
Planned
[](https://www.laioutr.com/es/apps/patchworks)
Laioutr
[Patchworks](https://www.laioutr.com/es/apps/patchworks)
Patchworks es un iPaaS low-code que conecta e-commerce, ERP, WMS, 3PL y marketplaces.
Planned
[](https://www.laioutr.com/es/apps/PrestaShop)
Laioutr
[Prestashop](https://www.laioutr.com/es/apps/PrestaShop)
Plataforma de comercio open source para pequeños y medianos comerciantes en Europa y más allá.
Planned
[](https://www.laioutr.com/es/apps/saleor)
Laioutr
[Saleor](https://www.laioutr.com/es/apps/saleor)
Plataforma de comercio open source y API-first basada en GraphQL para storefronts a medida.
Planned
[](https://www.laioutr.com/es/apps/salesforce-commerce-cloud)
Laioutr
[Salesforce Commerce Cloud](https://www.laioutr.com/es/apps/salesforce-commerce-cloud)
Salesforce Commerce Cloud es una plataforma de comercio empresarial en la nube para empresas de cualquier tamaño.
Planned
[](https://www.laioutr.com/es/apps/sap-commerce-cloud)
Laioutr
[SAP Commerce Cloud](https://www.laioutr.com/es/apps/sap-commerce-cloud)
Plataforma de comercio empresarial para catálogos complejos, modelos de precios y recorridos omnicanal.
Planned
[](https://www.laioutr.com/es/apps/scayle)
Laioutr
[Scayle](https://www.laioutr.com/es/apps/scayle)
SCAYLE es un motor de comercio con el que marcas y comerciantes escalan su negocio.
Planned
[](https://www.laioutr.com/es/apps/spryker)
Laioutr
[Spryker](https://www.laioutr.com/es/apps/spryker)
Plataforma de composable commerce para modelos de negocio B2B y B2C exigentes.
[](https://www.laioutr.com/es/apps/sylius)
Laioutr
[Sylius](https://www.laioutr.com/es/apps/sylius)
Sylius es un framework de e-commerce pensado para desarrolladores y para experiencias de compra B2C y B2B.
Planned
[](https://www.laioutr.com/es/apps/vendure)
Laioutr
[Vendure](https://www.laioutr.com/es/apps/vendure)
Vendure es una plataforma de headless commerce para empresas con requisitos complejos.
Coming Soon
[](https://www.laioutr.com/es/apps/vtex)
Laioutr
[VTEX](https://www.laioutr.com/es/apps/vtex)
Plataforma de composable commerce cloud native para B2B y B2C a gran escala.
Planned
[](https://www.laioutr.com/es/apps/websale)
Laioutr
[Websale](https://www.laioutr.com/es/apps/websale)
Backend de comercio estable y apto para grandes empresas en entornos comerciales complejos.
Llamada estratégica
## ¿Listos para convertir su frontend en una capa de control?
Muéstranos tu stack, tu roadmap, tu escenario de replatforming, y te mostraremos cómo encaja Laioutr, cuánto cuesta y qué tan rápido puedes estar en producción.
*"Después de 30 minutos supimos que Laioutr hace viable nuestro replatforming." - Daniel B., CEO,* [*hygibox.de*](https://hygibox.de)
[Reserva una demo](https://www.laioutr.com/es/contact)
## Structured Data
```json
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://www.laioutr.com/#identity",
"name": "Laioutr",
"legalName": "Laioutr GmbH",
"url": "https://www.laioutr.com/",
"logo": {
"@type": "ImageObject",
"url": "https://www.laioutr.com/laioutr-logo.png",
"width": 400,
"height": 400
},
"email": "info@laioutr.com",
"telephone": "+49 30 75435715",
"address": {
"@type": "PostalAddress",
"streetAddress": "Münchweilersteig 5",
"postalCode": "12559",
"addressLocality": "Berlin",
"addressCountry": "DE"
},
"vatID": "DE450905846",
"sameAs": [
"https://www.linkedin.com/company/laioutr",
"https://www.youtube.com/@Laioutr",
"https://x.com/laioutr"
]
},
{
"@type": "WebSite",
"@id": "https://www.laioutr.com/es/#website",
"url": "https://www.laioutr.com/es/",
"name": "Laioutr",
"inLanguage": "es",
"publisher": {
"@id": "https://www.laioutr.com/#identity"
}
},
{
"@type": "BlogPosting",
"@id": "https://www.laioutr.com/es/blog/translation-workflow-tms-pim-component-schema-2026#article",
"headline": "Translation Workflow in the Frontend: How TMS, PIM and Component Schema Connect",
"description": "A translation workflow breaks when TMS, PIM and component schema disagree on what is translatable. Here is how to wire them together the right way.",
"image": [
"https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmtckpajh5xbs06mmio9ok7jz"
],
"datePublished": "2026-08-28T06:32:03.712128+00:00",
"dateModified": "2026-08-28T06:32:03.712128+00:00",
"inLanguage": "es",
"articleSection": "Insights",
"keywords": "Localization, Content modeling, Information architecture, Frontend Management",
"author": {
"@type": "Person",
"name": "Marcel Thiesies",
"jobTitle": "Cofundador y CEO, Laioutr",
"image": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmj01b962364n07lb0iguvts5"
},
"publisher": {
"@id": "https://www.laioutr.com/#identity"
},
"mainEntityOfPage": {
"@id": "https://www.laioutr.com/es/blog/translation-workflow-tms-pim-component-schema-2026#webpage"
},
"isPartOf": {
"@id": "https://www.laioutr.com/es/#website"
}
},
{
"@type": "WebPage",
"@id": "https://www.laioutr.com/es/blog/translation-workflow-tms-pim-component-schema-2026#webpage",
"url": "https://www.laioutr.com/es/blog/translation-workflow-tms-pim-component-schema-2026",
"name": "Translation Workflow in the Frontend: How TMS, PIM and Component Schema Connect",
"description": "A translation workflow breaks when TMS, PIM and component schema disagree on what is translatable. Here is how to wire them together the right way.",
"inLanguage": "es",
"isPartOf": {
"@id": "https://www.laioutr.com/es/#website"
},
"breadcrumb": {
"@id": "https://www.laioutr.com/es/blog/translation-workflow-tms-pim-component-schema-2026#breadcrumb"
},
"primaryImageOfPage": {
"@type": "ImageObject",
"url": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmtckpajh5xbs06mmio9ok7jz"
},
"datePublished": "2026-08-28T06:32:03.712128+00:00",
"mainEntity": {
"@id": "https://www.laioutr.com/es/blog/translation-workflow-tms-pim-component-schema-2026#article"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://www.laioutr.com/es/blog/translation-workflow-tms-pim-component-schema-2026#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Laioutr",
"item": "https://www.laioutr.com/es/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Insights",
"item": "https://www.laioutr.com/es/blogs/insights"
},
{
"@type": "ListItem",
"position": 3,
"name": "Translation Workflow in the Frontend: How TMS, PIM and Component Schema Connect"
}
]
}
]
}
```