Catalogue enrichment (batch)
Attributes pulled from supplier PDFs and images, TR/EN copy written; hundreds of SKUs ready in minutes.
Catalogue enrichment (batch) is an agent scenario in the Retail & E-commerce sector running on the batch, email channels. Trigger: Supplier catalogue files landing in the S3 drop folder. The Catalogue Supervisor coordinates 3 specialist agents (Document Agent, Normalisation Agent, Content Agent) across 4 systems (Document Store (S3), PIM / Catalogue, SAP ERP, Email (Exchange)); of 10 steps, 1 write to systems and 2 are checks or approvals. Outcome: SKUs publish-ready in the PIM, exceptions queued, catalogue team has the summary report. Approval rule: New category or supplier price deviation > 15% → category manager approval.
Catalogue enrichment (batch)
- Supplier drop: 340-product PDF catalogue + 1,120 images landed in S3
- Files read; 14 attributes per SKU extracted (material, dimensions, colour), confidence 96%
- Plan: taxonomy mapping → unit normalisation → dedupe → content → QC
- Existing 2,150 SKUs and the supplier price list pulled from SAP
- 340 SKUs → 312 new, 28 existing; sizes converted to cm, 3 colour codes unmapped
- TR/EN descriptions and SEO titles written for 312 products in brand tone
- QC: mandatory fields 99.1% complete; 9 SKUs missing dimensions → human queue
- New category or price deviation > 15% → category manager approved 12 SKUs
- 303 SKUs saved to the PIM as "ready to publish", 9 as "incomplete"
- Summary report and exception list emailed to the catalogue team
- ■completed
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Supplier catalogue files landing in the S3 drop folder
SKUs publish-ready in the PIM, exceptions queued, catalogue team has the summary report
Agents
Catalogue Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Document Agent
Extracts product attributes from PDFs and images
parse_supplier_pdfextract_attributesread_product_imageNormalisation Agent
Maps to the taxonomy, normalises units, dedupes SKUs
get_existing_skusmap_to_taxonomynormalise_unitsdedupe_skurun_qcContent Agent
Writes TR/EN descriptions and SEO titles in brand tone
write_descriptiongenerate_seo_titletranslatesave_to_pimsend_emailSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Catalogue Supervisor | Supplier drop: 340-product PDF catalogue + 1,120 images landed in S3 | — | 300 | — |
| 02 | retrieve | Document Agent | Files read; 14 attributes per SKU extracted (material, dimensions, colour), confidence 96% | Document Store (S3) | 1,800 | 3,400 |
| 03 | plan | Catalogue Supervisor | Plan: taxonomy mapping → unit normalisation → dedupe → content → QC | — | 260 | 190 |
| 04 | tool | Normalisation Agent | Existing 2,150 SKUs and the supplier price list pulled from SAP | SAP ERP | 520 | — |
| 05 | reason | Normalisation Agent | 340 SKUs → 312 new, 28 existing; sizes converted to cm, 3 colour codes unmapped | — | 740 | 680 |
| 06 | reason | Content Agent | TR/EN descriptions and SEO titles written for 312 products in brand tone | — | 2,400 | 5,200 |
| 07 | verify | Normalisation Agent | QC: mandatory fields 99.1% complete; 9 SKUs missing dimensions → human queue | — | 480 | 350 |
| 08 | approval | Catalogue Supervisor | New category or price deviation > 15% → category manager approved 12 SKUs | — | 3,200 | — |
| 09 | write | Content Agent | 303 SKUs saved to the PIM as "ready to publish", 9 as "incomplete" | PIM / Catalogue | 620 | — |
| 10 | notify | Content Agent | Summary report and exception list emailed to the catalogue team | Email (Exchange) | 240 | — |
Outfit stylist: a complete look by size, stock, budget and style
The customer sends a photo and a sentence; the agent builds three looks that are in stock, fit and within budget, and adds the chosen one to the cart.
Where is my order? (WISMO)
Customer asks, order and carrier events join instantly; on delay a new ETA is given and a trace opened.
Returns and refunds
Policy and history checked in seconds, label issued; the refund executes when the carrier scans the parcel.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis