Designing an Enterprise Samples Portal

From a manual request process to a connected product.

The Samples Portal was a new enterprise application for authorized promotional partners and internal operational stakeholders. It digitized a largely manual promotional-samples request process, connecting product discovery and ordering with administration and operational management.

I personally owned the new application’s complete frontend UX/UI design and implementation from discovery through production. It occupied roughly a year or less of an approximately 2.5-year engagement that also included substantial new capabilities within two established enterprise platforms.

Understanding the work behind a sample request.

I conducted discovery meetings with primary client stakeholders, gathered requirements, and worked through the business processes behind the manual request experience.

Administrators maintained operational and regional configuration affecting requester choices, applicable policies, and how requests were processed. Discovery connected the requester journey with the administrator-managed business rules behind it.

Make the decisions tangible before building.

I designed high-fidelity, interactive Figma prototypes for both the ordering experience and substantial administrative interfaces. I presented them to stakeholders, gathered feedback, and iterated through multiple review cycles to work through complex requirements.

One request flow, different paths.

The request experience adapted to rules influenced by sales center, co-op arrangement, sales channel, and fulfillment method. Depending on the applicable rules, fulfillment options became available or unavailable, and different fields or sections appeared.

The design challenge was to expose relevant questions and explain constraints while keeping the request understandable. Requester-facing behavior had to remain connected to the operational and regional information maintained by administrators.

A regional change reached beyond the form.

Expanding from U.S. operations to Canada introduced considerations around currency, regional fees and deposits, geographic qualifiers, and administrative reference data.

The ordering experience had to reflect the relevant regional context, with frontend behavior coordinated with backend calculations. Supporting that expansion also meant accounting for administrative complexity, not simply adding a country choice.

Ownership from prototype through production.

The frontend implementation covered both the ordering experience and administrative interfaces. I worked closely with a backend engineer responsible for backend functionality, calculations, and integrations.

I participated in extensive client UAT, resolved issues across request scenarios, and supported production delivery. The portal entered production with an initial U.S. scope and later expanded to Canada.

Designing geographic configuration.

I designed and implemented a country-management experience across the two established platforms. Previously limited geographic configuration became an administrative workflow in which authorized users could manage country records, currency information, effective dates, status, and platform visibility.

This work translated geographic expansion into configurable administrative decisions while keeping the relevant properties and availability understandable.

Making brand expansion configurable.

I designed and implemented an administrative experience for introducing and managing parent brands. It supported creating and configuring parent brands, uploading multiple logo formats and other assets, and previewing brand-specific presentation across different interface contexts.

Brand-specific colors and assets required careful attention to consistency. The experience supported an expanding brand portfolio through reusable configuration and preview patterns, rather than treating every addition as a separate design problem.