Delivering Registration Forms Across 20+ Nestlé Markets

Nestlé
Nestle.com homepage
Nestlé Brands web page. Image credit: Nestlé S.A.
SAP Customer Data Cloud platform
SAP Customer Data Cloud platform. Image credit: SAP

As Frontend Engineer on Nestlé’s global CIAM program, 2021 to 2023, I delivered 300+ multilingual registration and consent forms. They shipped across 20+ markets for Nespresso, Maggi, and Purina. Form drop-off fell by about 18%.

  • 300+Multilingualforms
  • 20+Marketscovered
  • 3+Globalbrands
  • 18%Fewerdrop-offs

The Challenge

Nestlé needed to roll out consistent registration and consent flows for global brands across 20+ markets in EMEA and Asia, but faced fragmented implementations, inconsistent UX, and varying GDPR compliance levels. Each market was building forms independently on SAP Customer Data Cloud, often with different Drupal sites, Qualifio campaign flows, and Screen-Set configurations, leading to duplicated effort, integration issues, and compliance risks.

My Role

As Frontend Engineer in Nestlé Business Services (NBS) in Lisbon, Portugal, I worked in the CRM and customer-identity stream: turning brand, legal, and data requirements into Screen-Sets and frontend patterns other markets could reuse.

Registration forms are where a brand collects its own customer data and consent for CRM and email marketing. Every extra field or unclear consent step costs sign-ups, which is why drop-off was the number that mattered.

I built and refined registration forms and consent flows for markets across EMEA and Asia, with GDPR-compliant data flows and consent logic in the frontend Screen-Sets. Delivery ran with CRM, data, brand, and engineering partners on requirements and timelines.

What I Did

  • Created reusable Vanilla JS/CSS UI patterns for SAP Screen-Sets to improve consistency across Nespresso, Maggi, Purina, and other brand sites.
  • Clarified consent-flow behaviour with technical, legal, and brand partners before market rollouts.
  • Improved localisation workflows, reducing translation errors across multilingual forms.
  • Introduced clearer API, testing, and delivery guidelines for agency partners (Postman, Jira).
  • Shared checklists and templates with agencies to keep Screen-Set work consistent across markets.
  • Resolved integration issues early across Drupal CMS, Qualifio, Screen-Sets, and backend systems.
  • Wrote technical specs in Confluence, reviewed implementations, and kept documentation current.

How a registration reaches CRM

  1. Brand site: A Drupal page or a Qualifio campaign shows the registration form.
  2. Screen-Set: The shared form pattern collects the fields each market needs.
  3. Consent: Consent text and checkboxes match the market and its legal sign-off.
  4. SAP Customer Data Cloud: The profile and consent records are stored once, per brand.
  5. CRM: Marketing can email only the people who opted in.
Where a registration goes, from the brand site to CRM. One reusable pattern served 20+ markets.
SAP Customer Data Cloud Screen-Sets user interface screenshot
SAP Customer Data Cloud Screen-Sets interface. Image credit: SAP.
SAP Customer Data Cloud Screen-Sets registration flow screenshot
Registration flow using SAP Customer Data Cloud. Image credit: SAP.

Results

  • Registration and consent UX became consistent across brands and markets, and markets stopped rebuilding the same forms.
  • Form drop-off fell by approximately 18% while UX and data-capture patterns were standardised.
  • Unified consent and data-handling processes raised GDPR compliance across the estate.
  • Integration issues decreased across Drupal, Qualifio, Screen-Sets, and backend systems.
  • New markets went live about 25% faster on reusable Screen-Sets and shared Confluence guidelines.

What I Learned

Reusable SAP CDC Screen-Set and clear shared guidelines matter at scale. They helped forms stay consistent across markets while legal and brand partners could still sign off per locale, with GDPR requirements kept in view throughout. Every marketing site has the same layer: demo, sign-up, and newsletter forms with consent. I later rebuilt that layer on HubSpot and WordPress for parcelLab's demo booking.