Case study · Commerce · Leiria

In development

From license plate to the right part, without portal-hopping

At an auto parts business in Leiria, identifying the right part is the biggest time sink of the day. We are building the copilot that walks that path: plate, request, part, price, and stock.

The context

An auto parts shop with a counter and deliveries, working with dozens of suppliers. Each supplier has its own B2B portal with its own login, and the same part exists in several brands, at different prices, scattered across those portals.

The problem

The customer arrives with a license plate and a rough description ("the front bearing", a photo, a noise). Getting to the right reference takes experience, time, and patience: identify the vehicle, navigate technical catalogs, then compare price and stock portal by portal. All while the customer waits.

What we are building

A copilot for the counter: it takes the plate and the request exactly as the customer says it, identifies the vehicle and the part, and returns a single table with brand variants, price, and stock across suppliers. The operator confirms and orders; the decision stays theirs.

01

From license plate to exact vehicle identification

02

The natural-language request is interpreted into a part category and reference

03

Technical catalogs and supplier portals queried in parallel

04

One table: brand, reference, price, and stock, ready to compare

05

First phase in development, with the main supplier integrated

The goal

  • Minutes per request instead of tens of minutes
  • Less dependence on a single person's experience
  • Price and stock comparison always complete, never sampled
  • A faster counter, customers waiting less
LaravelReactSupplier APIsClaude

Does your company's critical knowledge live in one person's head?

That is a good sign a tool can help. Let's talk about your case for 30 minutes.