ThreadCloud SOPs

For the ThreadCloud team only

◐ ThreadCloud SOPs

Enrich

The tier-2 pass. After Build Order’s quick parse, Enrich fills in everything else: descriptions, fit notes, fabric details, country of origin, occasion tags, and 60+ Shopify metafields.

When to use
On every order after parse, before push. Usually auto-runs in the background — you only intervene if a row gets flagged for review.

When Enrich runs

Three triggers:

  1. Automatically after parse — fires on background worker once Submit for Review happens
  2. Manually — click Enrich on the order’s Enrich tab
  3. Per-style — click any style tile → drawer → “Re-enrich this style” button

You shouldn’t need to manually fire it for normal orders. The auto-trigger handles 95% of cases.

What Enrich actually does

For every style on the order, AI fills in:

Customer-facing

  • Web description (the long product description on the storefront)
  • Fit notes — how the garment runs (slim / regular / relaxed) and sizing advice
  • Occasion — when to wear it (Business / Casual / Resort / Formal)

Structured metafields (smart filters read these)

  • Category + Subcategory — the canonical TC taxonomy
  • Colour Group — the canonical colour bucket (Black, Navy, Brown, etc.) for filter facets
  • Pattern — Solid / Stripe / Check / etc.
  • Fabric content — primary fibre + composition
  • Country of origin — Italy, Japan, Portugal, etc.
  • Fit type — Slim, Regular, Classic, Relaxed
  • Construction attributes (for tailoring) — lapel, button stance, lining, vents, canvas type, etc.

Identity

  • Vendor Ref — supplier’s internal style code (separate from the Shopify SKU)
  • Brand Code — short brand prefix (e.g. “LRD” for Lardini)

Working the Enrich page

Open the order → click the Enrich tab.

You’ll see a grid of style cards. Each card shows:

  • Image
  • Editorial preview of the description
  • Tier-1 fields (category, colour, etc.)
  • Tier-2 fields (fit, fabric, occasion)
  • An Apply Edit button per card
  • A green checkmark if the style is complete, yellow flag if needs review

Reviewing a style card

Click the card to expand the field grid. Walk down the fields top-to-bottom:

FieldWhat to check
Web DescriptionReads well? No “elevate your wardrobe” cliches? Correct fabric mentioned?
Fit TypeMatches what you know about the brand’s fit
OccasionAt least one selected, more if applicable
Fabric contentMatches the linesheet (this is the most-common AI miss)
Country of OriginOnly “prestige” origins get mentioned in description (Italy, Japan, etc.)
Category/SubcategoryShould be correct from parse — verify

Edit any field inline. Click Apply Edit to save and re-generate dependent fields (e.g. changing the fabric will re-generate the description).

Speed tip
Cards with no flags can usually be approved in one click. Reserve attention for the ones with yellow review flags.

Bulk approve

Once all cards look good:

  1. Click Batch Approve at the top of the Enrich tab
  2. Confirms how many styles will flip to READY
  3. Click Approve

Only styles that pass completeness checks get approved — anything with empty critical fields stays in review.

Editing the description specifically

The AI description follows brand-voice rules set in Settings → AI & Models. To customize per-style:

  1. Click the style card → description field
  2. Edit the text directly
  3. Click Apply Edit

Or click Regenerate next to the description field — runs the AI again with the current brand voice.

Heads up
If you edit a description manually and then change the fabric or COO later, the description does not auto-update. It’s locked to your manual edit. To re-link it: click Regenerate.

Per-subcategory attribute fields

Some fields only appear when the style’s subcategory makes them relevant:

FieldShows for
Lapel StyleSuits, Blazers, Sport Jackets, dressy outerwear
Button StanceSuits, Blazers, Sport Jackets
VentsTailored jackets
Construction (canvas type)Tailored jackets
LiningTailored jackets, structured outerwear
Collar StyleDress shirts
Cuff StyleDress shirts
Sole TypeFootwear
Toe ShapeFootwear
FasteningFootwear
PlyKnitwear
RisePants, Shorts

If a field doesn’t appear, that means the gating rules decided it’s not relevant for this subcategory. You can’t force it visible from the UI.

Brand Recipes

Some brands have a “recipe” — a set of pre-filled defaults that override AI for known fields. E.g. Lubiam’s MTM recipe pre-fills construction, lapel, button stance, lining for every Lubiam MTM order.

Recipes are managed by the Owner under Settings → Brands & Suppliers. The team doesn’t need to touch them.

When AI flags a style for review

A row gets NEEDS REVIEW when:

  • Category confidence < 70% (AI not sure what kind of garment it is)
  • Colour confidence < 70%
  • One of the critical fields (fabric, COO) was extracted with low confidence
  • The vendor ref couldn’t be matched to a known supplier ref pattern

To clear the flag:

  1. Open the card
  2. Fix any empty or wrong field
  3. Click Apply Edit
  4. The flag clears automatically once all critical fields are filled

If the AI got it right and you just want to confirm:

  • Click Confirm as-is in the card footer (it’s a separate button from Apply Edit). Flips the row to READY without changing any values.

Common mistakes

Approving cards with empty fabric
If fabric is empty when you approve, the product pushes to Shopify with no fabric metafield. Smart filter “shop by fabric” misses these products. Always fill fabric before approving.

Wrong COO going public
Country of origin shows on the storefront for prestige origins (Italy, Japan, etc.). If parse extracted “Tunisia” but the linesheet actually says “Italy” — fix it before approving. Hard to undo after products are live.

Editing the description after push
If you push to Shopify and then edit the description in Enrich, you need to push again to see the change on the storefront. The metafield update doesn’t propagate without a push.

Next steps