How LingoVae thinks about styling

LingoVae has a small number of load-bearing concepts. If you internalise these, everything else in the app falls into place. They are also the source of most of the trust contract you have with us, so they’re worth reading once.

1. The catalog vs your library

LingoVae ships a catalog of pre-built styles (“Professional,” “Friendly,” “Holiday Warmth,” and so on). The catalog is global — everyone using LingoVae sees the same starting set, and we add new styles over time.

When you decide you want to use one of these styles, you install it into your library. From that moment on, the version in your library is yours: edits you make to length, must-mention terms, training examples, and so on don’t affect anyone else. If we later update the catalog version, your installed copy doesn’t change either.

You can think of the catalog as a bookstore and your library as your bookshelf. Once you take a book home, it’s yours.

Your library has a cap of 10 styles. If you hit the cap, installing a new style asks you to replace one. The one you replace doesn’t get deleted — it gets archived, and any products already styled with it stay published.

2. Originals are sacred

This is the single most important sentence in this document: LingoVae never overwrites your original product description without your permission, and even after you’ve published a styled version, the original is always recoverable.

When LingoVae styles a product, it writes the styled version into a separate place — a Shopify metafield that the storefront reads. Your original body_html field stays exactly as you wrote it. When you click Revert, we point the storefront back at your original; the styled version moves out of the way but is not destroyed.

This is true whether you styled the product once or two hundred times. Every version is stored. You can roll back to any of them.

(The full audit trail of every version is a Pro feature called version history. On Free, Starter, and Grow you can revert to the original; on Pro you can revert to any prior styled version.)

3. Drafts and review

When LingoVae generates a styled description, the output is a draft — not a published change to your storefront. Drafts have to be published by you before they go live.

A draft has structure: it’s not a single blob of text. It contains the title, the body HTML, the SEO title, the SEO description, and (on some plans) variants and metafields. You can publish some of those fields and leave others untouched. So if the styled title is great but you want to keep your existing body copy, you can publish only the title.

Drafts live in two places:

  • Per-product review. Open a product and you’ll see every draft generated for it, ready to compare and publish.
  • Review queue (Grow plan and higher). When you’ve generated drafts for many products at once (a bulk job), they all flow into the review queue grouped by batch.

Drafts don’t expire, but they can become stale — if you edit the underlying product description in Shopify between when the draft was generated and when you go to publish it, LingoVae will tell you the source has changed and let you choose to regenerate, overwrite anyway, or skip.

4. Background jobs

The everyday flow (“pick one product, style it, publish”) happens in the foreground — you click a button and the result appears in seconds.

The bulk flow (“restyle every product in this collection”) doesn’t fit in seconds, so LingoVae runs it as a background job. Once you start a job:

  • You can leave the page. The job keeps running.
  • You can pause it. The job stops at the next product boundary, with no duplicate work when you resume.
  • You can cancel it. Anything generated so far stays in your review queue; the rest stops.

Only one job runs at a time per store. Additional jobs queue up behind it. This is a deliberate design choice — it keeps your AI usage predictable and prevents one runaway job from consuming everything.

Jobs have a style lock while they’re running: the style they’re using gets frozen so the job’s output stays consistent. If you need to edit a style that’s locked, you have three options: cancel the job, duplicate the style and edit the copy, or wait for the job to finish.

5. Auto-quality scoring

Every draft LingoVae generates gets scored on a 0–100 scale for how well it matches the style you picked and stayed within your guardrails.

  • Drafts above your auto-approve threshold (default 80) get a green “Auto-quality” badge — you can fast-track them.
  • Drafts below your review threshold (default 60) get a yellow flag and a one-line reason (“might have introduced a claim not in the original,” “shorter than your style’s minimum length,” and so on).
  • You can change both thresholds in Settings → Quality controls, or turn scoring off entirely.

Scoring is informational. Nothing happens automatically because of a score — you still publish every draft. The score just tells you which ones probably deserve more attention.

The trust contract

These five concepts add up to a contract:

  • Your original product copy is safe. Always.
  • You decide what gets published. No draft is ever applied to your storefront without you publishing it.
  • Nothing destructive happens silently. If you downgrade your plan, your work pauses — it doesn’t get deleted. If you uninstall, you have a choice: keep your styled descriptions published or strip them off and revert to originals.
  • You can always look back. The activity feed shows everything that’s happened, with the actor and timestamp.
  • You can always roll back. Revert any styled product to its original, at any time, on any plan.

The rest of LingoVae is just tools. The trust contract is what makes those tools safe to use.