Flutterfrog
← Results
AI TransformationDistribution & retail · Every new supplier, every new product

Your sales catalogue builds itself from purchase entries

The workflow, running

Tally Prime showing a list of stock items written as shorthand, such as AAC GHEE 1 LTR*16 and Gopura Kalasam 200ml*60. The status bar reads 15 stock groups and 5,263 stock items.
01 Where it starts. 5,263 stock items in the accounting system, written for whoever typed them — pack counts and abbreviations jammed into the name.
The ERP connector listing raw products pulled from Tally, each with HSN code, GST percentage, selling rate, MRP and a status of either active or validation failed.
02 The connector pulls them across with HSN, GST and rates — and flags what fails validation rather than importing it quietly.
The Enrich Listing screen. The stockist's product name reads BOURBON 90G 80PK; the product name field reads Britannia Bourbon Biscuit, with a Suggest button beside it, plus fields for Tamil name, net quantity, category, brand, keywords, weight, a written description and product images.
03 BOURBON 90G 80PK becomes Britannia Bourbon Biscuit — with a Tamil name, description, keywords and images. Suggest proposes; a person confirms before it goes live.
The customer app cart showing Gopura Kalasam Instant Sambrani at thirteen rupees, reduced from twenty, with a product photograph.
04 The same product, in a customer's cart.

What you get

A product arrives in your billing software as shorthand and leaves as a listing — proper name, description, pack size, category, brand and photo. It happens on every new supplier and every new product, without anybody being assigned to it. Onboarding a new supplier stops being a week of somebody's life and becomes a session.

What it replaces

Someone sitting with a spreadsheet, working out that SOFT 100ML is a 100ml bottle of a particular dishwashing liquid, typing a description, finding a photo, and repeating that several hundred times per supplier. It is the least interesting work in the business, which is why it never gets done and the catalogue stays unsellable.

How it works

Each entry is read and a full listing proposed, field by field, with a confidence on each. A deterministic check requires the fields that matter before anything can go live; where the system cannot identify a product it leaves the field empty rather than guessing. A person confirms against the pack photo. The same pass keeps the brand list clean, which is where catalogues usually rot.

Measured so far

703

listings processed in a single pass

656

product names generated

870

Tamil-language corrections

242 → 81

brands, de-duplicated automatically

1,317

product photos placed, byte-verified

2

left blank rather than guessed

Recognise your own situation in this? That is usually the point to talk — gokul@theflutterfrog.com.

Have a system worth building?

Start a project