Products

Read off the site you already maintain, so there is no second catalogue to keep in step.

Where it comes from

When Jabee reads your website it recognises product pages and pulls out what is on them: the name, the price, the pictures, and the attributes your own products carry. A car dealer gets year, make and mileage. A clothes shop gets size and colour. Nobody chose those fields in a settings screen; they are the ones your products already have.

Shopify and common store platforms are recognised directly, which gives cleaner results than reading the rendered page.

What a customer can ask

"Anything under 60,000 in white." "Do you have that in a medium." "What is the cheapest automatic you have."

Those become filters over your catalogue, so the answer is a real list rather than a paraphrase of a category page. Pictures come with it where you have them.

Keeping it current

The catalogue refreshes when your site is re-read. Something sold or repriced on your site is sold or repriced here, with no second place to update.

If your stock lives in a system rather than on the website, connect it as your own API and Jabee will ask it live instead. That is the right answer for anything that changes hourly.

Checking what it found

The Products screen lists what was read and what each item's attributes are. It is worth a look after the first crawl, because a site that hides prices behind a script will show up here as products with no price, and that is fixable.

Questions