All case studies

Enterprise-Level Agentic Frameworks

Product Pages at Catalog Scale

A reseller’s catalog grown from 10K to over 1M products, every listing built by agents: a product image, a real title, key features, a description, and an FAQ.

BEFORERK-15U-WLBManufacturer—Part numberRK-15U-WLBBrand—DESCRIPTIONNo description.FAQNo questions and answers.part-number title · empty fields · no descriptionAGENTSper productAFTER15U Wall-Mount Rack CabinetLockable, Vented, Black• Holds 200 lb of 19-in. equipment• Swings out for rear access• Vented panels keep gear coolDESCRIPTIONA low-profile wall-mount cabinet for network closets, shops,and classrooms short on floor space. Heavy-duty steel witha powder-coat finish, a locking door, and removable sidepanels keep equipment secure while the vents keep it cool.FAQIs assembly required? No, it ships fully assembled.What is the weight capacity? 225 lb static load.Can I mount it on any wall? Yes, on studs or masonry.image · title · key features · description · FAQ
A product page before and after the agents
What stood in the way

The problem.

A large catalog is mostly empty text fields. A product lands with a manufacturer part number where its title should be, blank specification rows, no description, and no answers to the questions buyers actually ask. Every gap is a page that does not rank and a customer who leaves.

For a reseller the gap grows every day. Supplier feeds bring tens of thousands of new products at a time, and no team writes that many pages by hand.

What we built

The system.

Agents read what the product already carries (images, part numbers, scattered specifications) and build the page out: a product image, a full title, key features, a long-form description, and an FAQ covering assembly, capacity, compatibility, and returns. Every page is structured for search, from its title to its FAQ.

Around the pages, the same system categorizes every product, tracks competitor prices and suggests prices, flags opportunity products, and catches anomalies in a feed before they reach the store. It also keeps stock and orders in sync with the Shopify store, and customer-facing chatbots answer the stock and order questions buyers ask.

How it works

In operation.

A script runs every day and turns tens of thousands of new products into finished pages in under an hour. It runs on Kubernetes, sized for that throughput.

People stay in the loop. Changes go through human approval, and managers get a daily brief by email reporting what the system did. On the customer side, the chatbots collect feedback, let customers report errors, and open a support ticket when a person needs to step in.

The catalog grew from 10K to over 1M products on this system. It costs about a third of one product engineer’s salary, at thousands of times that engineer’s output. Development is complete, and every part of it runs in production today.

Beyond AI hype. Into execution.

Ready to build your AI capability?

We accept a limited number of research partnerships per quarter to ensure high-fidelity delivery.

Book a Discovery Call

Not ready for a call? contact@whitehand.ai