FlagshipPimcore Administration & Integration

Pimcore for a medical device manufacturer

Two years running the PIM, DAM, CRM and translation stack behind a multilingual product catalogue

PimcorePIMDAMIntegrationsPlatform.sh

How the systems connect — drawn instead of screenshotted, so nothing client-specific leaves the room.

01 — The challenge

Product data in a regulated manufacturing environment has to be correct in every market at the same time. A single product carries technical attributes, marketing text, approved imagery, and documentation, and each of those exists in a set of languages that is never quite the same from one market to the next. Pimcore held the structured data. A separate DAM held the assets. Dynamics held the commercial relationships. memoQ ran the translation workflow. None of those four systems agrees on what a product is, so most of the day-to-day work sat in the seams between them: keeping identifiers stable, keeping the export shapes consistent, and catching the cases where an upstream change quietly broke something three systems downstream.

02 — What we built

  • Administered the production Pimcore instance: class and data-object definitions, field collections, object bricks, classification store groups, and the permission model behind them
  • Maintained the data model as requirements changed, which in practice means deciding which new attribute belongs on the class, which belongs in a brick, and which belongs in the classification store before it is added rather than after
  • Kept the integrations running: product and commercial data moving between Pimcore, Dynamics CRM, and the asset library, with the ERP-side export as the upstream source of record
  • Operated the translation workflow through memoQ: extracting source content, tracking what was in flight, and getting approved translations back into the right localized fields without overwriting newer edits
  • Ran the asset pipeline from the DAM into Pimcore so that the image or document attached to a product was the approved version, not a copy someone had downloaded months earlier
  • Managed the Platform.sh hosting environment: environment configuration, deployments, and the branch-per-environment workflow Pimcore changes went through before production
  • Planned and executed version upgrades, including the regression testing that a catalogue of this size needs before an upgrade is allowed anywhere near production

03 — The result

The instance stayed in service and stayed current through the period, with product data, assets, and translations reaching the downstream channels they were supposed to reach. More useful than any of that, though, is the operational knowledge: two years is long enough to see the same Pimcore failure modes arrive more than once, and to learn which ones are the data model coming due and which ones are an upstream system changing without telling anybody. That experience is the reason Aiki Labs now maintains Pimcore instances that other agencies built.

Operational impact

2 years

administering one production instance

Inside a four-year tenure at a DACH medical device manufacturer. Day-to-day operations, not a fixed-term implementation.

4 systems

kept in sync around Pimcore

PIM, DAM, CRM, and the translation workflow. Most of the recurring work lives in the boundaries between them, not inside any one of them.

Multi-market

multilingual product catalogue

Product data and documentation maintained across markets and languages, where the language set differs per market.

Platform.sh

hosting and deployment workflow

Environment configuration, branch-per-environment deployments, and upgrade rollouts handled as part of the same role.

  • Two years of continuous production administration, not a single implementation project
  • Four connected systems kept in sync: Pimcore, a DAM, Dynamics CRM, and a memoQ translation workflow
  • Upgrades planned and executed against a live multilingual catalogue rather than deferred
  • Hosting, deployments, and environments handled on Platform.sh alongside the application work

Under the hood

PIM
PimcoreClassification StoreData ObjectsObject Bricks
Connected systems
DAMDynamics CRMmemoQERP export
Infrastructure
Platform.shGit branch environmentsStaged upgrades

What's connected

Dynamics CRM
Commercial and product data shared between the PIM and the CRM, with identifier stability as the thing that actually has to hold.
DAM
Approved images and documents flowed into Pimcore and out to channels, so a product referenced the current asset rather than a stale copy.
memoQ
Translation jobs left Pimcore as source content and came back as approved target-language values written into localized fields.
ERP export
Upstream product data arrived as a scheduled export. When its shape changed without notice, everything downstream noticed.

Want something like this?

Book a free consultation — we'll map your workflows and tell you exactly what to build.

Book a callAll projects