Interview with Lena Eriksson: Navigating Customer Data Platforms for Long-Term Supply Chain Success in Nordic Fine-Dining

Q: Lena, you manage supply chain operations for a prestigious Nordic restaurant group. How does integrating a customer data platform (CDP) fit into a multi-year supply chain strategy?

A: The first thing I tell peers is that CDP integration isn’t just a tech upgrade; it’s a strategic transformation of how we plan inventory, forecast demand, and connect with diners across our venues. In the Nordics, where seasonal ingredients and local sourcing dominate, knowing customer preferences at a granular level helps us avoid overstocking expensive produce or missing trends that suddenly spike demand.

For example, one of our venues noticed a 30% uptick in demand for heritage varieties of apples during a certain harvest season, thanks to aggregated guest preference data. Without the CDP feeding this into procurement in real time, we would have missed that window, either overbuying standard apples or understocking the specialty kind.

The key is that a CDP should evolve alongside your supply chain roadmap. Don’t rush the integration as a standalone project; embed it in your 3- to 5-year operational plan and link it directly to sourcing decisions, menu cycles, and waste reduction targets.

Q: What are critical early technical steps to ensure the CDP doesn’t become a siloed mess?

A: One common pitfall is focusing only on guest-facing data from reservations or loyalty apps. For supply chains, the value spikes when you unify this with backend purchase data, supplier lead times, and even weather forecasts.

Start with a data audit. Map every data source: Do you have real-time inputs from POS systems, supplier delivery times, and kitchen waste tracking? For instance, several fine-dining chains in Stockholm underinvest in kitchen waste data, which undercuts forecasting accuracy.

The integration process must also consider Nordic-specific data rules and privacy laws—GDPR enforcements here are strict. You have to design your data flows to anonymize or pseudonymize where necessary, especially if you’re combining CRM data with supplier contracts.

A practical gotcha: integrations often break during peak season planning due to data latency. If your CDP synchronizes customer trends weekly but procurement needs daily updates, you must design incremental syncs or event-driven APIs rather than batch uploads.

Q: Many companies aim for a single source of truth with CDPs. How realistic is this, and what’s the best way to approach it?

A: In theory, having a single source of truth sounds great; in practice, it’s almost never that simple. Different departments—supply chain, marketing, kitchen staff—all have varied data needs and formats.

From my experience, especially in Nordic fine-dining where artisanal suppliers and bespoke menus add complexity, it’s better to aim for a “federated” model. That means your CDP acts as a hub but respects the native data formats and update cycles from each system.

For example, our wine procurement team tracks bottle aging data in a cellar management system, which doesn’t sync neatly with guest reservation preferences. We built connectors to push relevant consumption data from CDP into cellar reports quarterly, instead of forcing daily syncs that created more errors than insights.

This approach reduces integration friction and lets teams trust the data they receive because it’s relevant and timely—not just dumped en masse.

Q: How do you align multi-year CDP development with seasonal menu planning and supplier contracts in fine dining?

A: Seasonal menu planning is the heartbeat of fine dining supply chains; it dictates procurement volumes and timing. A CDP should feed insights that shape these menus at least one cycle ahead.

We structured our roadmap to build quarterly feedback loops into the CDP—integration with supplier lead times, seasonal ingredient availability, and customer sentiment from Zigpoll surveys.

For example, last year, Zigpoll responses indicated a growing interest in wild mushrooms, which informed a new fall menu. Our CDP aggregated this demand signal and cross-referenced with supplier stock levels and delivery schedules. So we adjusted supply contracts early, securing better pricing and fresher produce.

The downside is that full integration with suppliers’ ERP systems takes time and often requires negotiation—some artisanal Nordic suppliers still manage orders manually, so digital syncing isn’t straightforward.

Patience is key; the roadmap must include milestones for gradual supplier onboarding and fallback manual processes during this phase.

Q: Are there unique challenges or advantages to CDP integration in Nordic markets compared to other regions?

A: Absolutely. Nordic consumers have a strong preference for transparency and sustainability, which feeds into how supply chains operate.

One challenge is incorporating provenance data into the CDP—not just what customers order, but where ingredients come from, their carbon footprint, and ethical sourcing certifications. This data isn’t standard in global CDPs.

A Nordic fine-dining chain we work with developed custom fields to integrate supplier sustainability scores directly into customer profiles, enabling personalized marketing that highlights the restaurant’s green sourcing. This integration took nearly 18 months because it required supplier cooperation, auditing, and careful data structuring.

On the plus side, Nordics have high digital literacy and infrastructure, so linking POS, CRM, and kitchen systems is often technically smooth once you negotiate data sharing agreements.

Q: What role does cross-functional collaboration play in long-term CDP integration success?

A: It’s everything. I’ve seen CDP projects stall because IT teams treated it as a pure tech rollout, ignoring supply chain nuances or guest experience priorities.

In our group, we insisted on a steering committee that includes supply chain directors, menu planners, sommeliers, marketing leads, and IT architects. Even finance gets involved because ROI tracking on reduced waste or improved supplier terms is crucial.

Regular workshops—sometimes monthly during initial phases—help align expectations. For instance, marketing wanted to push personalized offers to guests, but supply chain flagged risks of overpromising bespoke items without supplier confirmation. The CDP roadmap adjusted to include “availability flags” from procurement systems before offers go live.

This collaboration prevents disconnects that typically arise between front-of-house excitement and back-of-house realities.

Q: Regarding optimization and edge cases, how do you handle data quality issues given the heterogeneity of sources?

A: Data hygiene is a long-term challenge. Nordic fine dining relies on a mix of digital and manual inputs: handwritten supplier notes, legacy ERP entries, plus new app data from reservations.

We built automated validation scripts that flag anomalies—like a sudden surge in lobster orders when the season is closed or mismatches between supplier deliveries and kitchen usage.

But automation only goes so far. Regular audit cycles are essential, where supply chain analysts manually review flagged data monthly. One gotcha: suppliers sometimes update product codes mid-season, causing misaligned stock entries that skew demand forecasts.

Additionally, cultural nuances matter. Nordic customers might use nicknames or regional dialect terms in feedback surveys, which standard NLP models might misclassify. We customized text processing pipelines and included human reviews for critical customer sentiment.

Q: Can you share a concrete example where CDP integration led to measurable supply chain improvement?

A: Sure. One of our Copenhagen restaurants struggled with overbuying fresh herbs, leading to 22% waste monthly. By integrating reservation data, menu selections, and supplier deliveries through our CDP, we implemented dynamic procurement adjustments.

Within six months, herb waste dropped to 8%. This wasn’t just tech magic—it required syncing data daily, retraining staff to trust CDP-driven alerts, and building flexibility into supplier contracts to accommodate last-minute changes.

The financial savings covered CDP integration costs within the first year and created a foundation for further supply chain agility.

Q: What about limitations? When might a CDP integration not be worth the effort for Nordic fine-dining supply chains?

A: If your operation is very small—say, a single venue with minimal variability in menu or sourcing—a full-scale CDP might be overkill. The integration overhead and maintenance can outweigh benefits.

Also, if your supply chain is locked into rigid, manual contracts with suppliers who resist digital integration, the CDP’s potential is capped. You might get partial benefits from CRM improvements but miss the supply-side synergy.

Finally, be wary if your team lacks data skills or if IT infrastructure isn’t solid—integrations stall without continuous support.

Q: How should supply chain leaders prioritize CDP features in a long-term roadmap?

A: Start with data foundation—ensure comprehensive, clean inputs from your POS, reservation systems, and supplier data. Next, focus on real-time or near-real-time syncing with procurement and kitchen inventory systems to enable agile ordering.

Then layer in customer preference analytics tied to menu cycles to support predictive purchasing and menu development.

Later roadmap phases might include sustainability metrics, advanced personalization, and integration of external data like weather or local event calendars, which impact footfall.

Throughout, build feedback mechanisms using tools like Zigpoll and Hotjar to collect frontline staff input and diner sentiment, closing the loop on insights.

Q: Any advice for senior supply chain professionals embarking on this journey?

A: Start with a clear vision but break it into achievable increments. For example, year one might focus on integrating reservation and POS data with supply forecasts, year two on supplier digital onboarding, and year three on sustainability metrics.

Communicate constantly across teams. Celebrate small wins like a 5% reduction in waste or improved supplier lead times.

Lastly, don’t underestimate change management. Your kitchens, procurement teams, and suppliers need training and trust-building to fully adopt CDP-driven processes.

Remember, a CDP isn’t just software—it’s a long play on smarter, more responsive sourcing that supports the Nordic fine-dining promise of quality and sustainability.

Summary Table: CDP Integration Priorities for Nordic Fine-Dining Supply Chains

This multi-year approach, tailored for the unique blend of precision, seasonality, and sustainability that defines Nordic fine dining, helps supply chain leaders build resilient, data-driven operations.