Adhith SundaramSenior product designer

Albertsons Merchandising · Shipped 2025

Rebuilt the image asset collection that vendors kept skipping

92%

Vendor motivation to finish the image step

+20%

Increase in engagement after launch

2

Teams served by one repository

The collapsed Digital Assets section header in the item record. The Digital Assets section open: image requirements, a drag and drop area or import from URL for each hierarchy, and a table of five records with image category, image type, alt text and image source per row.

Role

Senior Product Designer

Timeline

2 months

Team

Merchandising & marketing partners, engineering

The merchandising item team briefed me about a feature vendors had abandoned, creating a break in the user experience. During item onboarding, the image asset collection supports the merchandising team, since every product at Albertsons requires images and data from vendors.

I designed the MVP scope of this flow, which served as the item onboarding channel for capturing item images. This experience improved engagement and benefited two different teams through a cost efficient design approach.

Beyond the final engagement outcome numbers, the split-card and scalable-table pattern that I designed became a reference for other merchant pods during the item onboarding redesign project, and the shared backend repository gateway removed a recurring source of vendor-to-marketing friction.

I observed that one card per image across four packing levels of an item (Each, Pack, Case, Pallet) caused endless scrolling and cluttered metadata that led vendors to abandon it. Vendors were sharing data offline with merchants, bypassing this step.

As a result, the merchandising team couldn't collect item images, with vendor motivation as low as 10%.

More images meant more scrolling... Metadata on one card made content type unclear

The Digital Assets card with the metadata for one image: product title, product details, the image requirements and the image rows, all on the same card.

Project constraints

This was two months into the 11-month long item onboarding redesign project, so the redesign had to fit into ongoing sprints.

Emerging opportunity

Through vendor conversations, I discovered that vendors shared the same data with the Marketing team. This prompted me to build a dual-purpose model serving Merchandising and Marketing within supply chain rules.

Despite high dev effort, I successfully advocated for an image ETL pipeline to prioritize long-term UX and efficiency by placing user experience above technical effort.

I followed three principles on this redesign: scalability across channels, glanceability through a modular pattern, and progressive reduction, by breaking one heavy component into smaller pieces.

My first iteration focused on reducing scroll with a compact carousel image capture.

One card: the product title and details, the image requirements, the upload area, and the seven added images as a row of thumbnails with the selected image's fields underneath.
The product detail card on its own: digital product title, product details, and whether the title is the same for a consumer-sellable pack. The image section as a grid: e-commerce images laid out by type, with empty drop areas for the ones still missing. The image section as a table: five records, each row carrying its thumbnail, image category, image type, alt text and image source.

Component Segmentation

Through user testing I found scalable tables helped vendors to categorize assets and record the image types. It also improved visibility and accountability when glancing at large sets of image data.

The product detail card: digital product title, product details, and whether the title is the same for a consumer-sellable pack. The image requirements and upload area, repeated per hierarchy: drag and drop or import from a URL, for each and for pack hierarchy 1. The image asset table filled in: seven records, each with its thumbnail, image category, image type, alt text, image source, source URL and availability dates. The Digital Assets section: the upload area above an empty four-record table waiting for image category, type and alt text. The image viewer modal: the enlarged product shot beside its image category, type, alt text, source and availability fields.

Final design

I explored an AI title-and-description generator: a rich-text editor that suggested product copy. Low LLM trust led vendors to reject the AI copy generator, favoring official manufacturer specifications.

AI title & description generator.

The Digital Product Details form: an empty product title field with a Generate AI Title link under it, and an empty rich-text product details field with a Generate AI Product Details link under it.

Product design extends into operational strategy

Multiple cross-functional conversations challenged me to look beyond the immediate product perspective. Finding ways to bridge new operational possibilities ended up being one of my biggest takeaways from this project.

Pushing technical boundaries creates scalable patterns

If I had stretched the team's capabilities to build AI-assisted content generation, the impact would have compounded. It would have created a blueprint for future merchandising tools.

Check out more of my work ↓