Compare the original product copy with the draft before you publish anything. Squadexa AI stores both versions when you regenerate a live product, shows them side by side, and lets you push one field at a time. Use that view even when the new paragraph sounds better. A cleaner sentence can still drop the size, the material, or a warning you wrote by hand.

Regenerate-existing is listed on the Basic plan card, at $9 a month, together with CSV bulk of up to 10 products per job. The compare view is described as part of that regenerate flow. Free is $0 and single-generation only. Confirm on your plan screen that compare is included before you promise this workflow to a free user. The catalog does not publish a word cap, and it does not include an Enterprise plan.

What the compare view shows

You start by picking a real Shopify product with the resource picker. The app snapshots the product’s current SEO fields, generates replacement content, and keeps the original and the new version. The comparison is the place where those two copies sit together. Read the description, the SEO title, the meta description, and the tags as separate decisions. A good meta description does not require you to replace a handmade body.

The original side is the text that is live, or that was live when the snapshot was taken. The draft side is the generation. Nothing in that layout publishes by itself. Publishing is a button you choose after the read. Save for later is the other button: it keeps your edits in the app library and does not touch Shopify. Use save when you want a colleague to see the draft before any field changes in the admin.

  • Original: the pre-generation copy the app stored for comparison.
  • Draft: the new description, SEO title, meta description, features, and tags.
  • Your edit: changes you make in the rich-text description or the other fields before you publish.

Update one field

The comparison view can push a single field: title, description, meta title, meta description, or tags. That is the control to use when you are afraid of a full overwrite. If the handmade description is the one you want to keep, leave it. Push the meta description only, or the tags only, after you have deleted any tag that does not match how you organize the catalog.

A fuller product update sends title, description, tags, SEO fields, and status, and it can follow with a variant price update. Price is an edit-view field. It is not something this article treats as generated marketing copy. If the price in the record is wrong, fix it or avoid the full update. Status matters for the same reason. Read it so a copy review does not change whether the product is available.

Field-by-field update is also how you test the tool. Publish the meta description on one product, check the storefront and the product admin, and only then decide whether the body should move. One field is reversible in practice because the rest of the listing stayed put, and because revert can restore the snapshot if you did push the wrong field.

Save the draft

Save for later is the pause. The record stays in the product library with a status badge: created, updated, not created, or not updated. Search and pagination in that library are there so a growing set of drafts is findable. You can edit the title, the rich-text description, the price, the SEO fields, the status, the product type, the vendor, and the tag chips while the record is still local to the app.

Treat “not updated” as the safe state. It means the live product has not received this draft. Move it to updated only after the comparison is done. If two people share the store’s app access, agree that one person generates and the other publishes. The catalog does not document a formal approval status or a separate permission role. The handoff is the saved draft and the compare view, used as a habit.

Revert to the snapshot

Revert restores the pre-regeneration snapshot onto the live Shopify product. Use it when a field you published is wrong and you want the stored original back. The snapshot is the copy taken at regeneration, described in the catalog as the product’s current SEO fields at that moment, kept beside the new draft. The page does not say how long that snapshot is retained. Do not assume it is permanent, and do not assume Shopify keeps an unlimited archive of older descriptions outside this app.

Revert is a recovery step, not a reason to skip the comparison. If you publish five fields and then revert, you are depending on the snapshot still being available. The calmer path is the single-field push, checked on the storefront, with revert in reserve.

A field you should rarely overwrite blindly

The body description is the field to protect. It is often the only place a sizing note, an allergen line, or a compatibility warning exists. Generated copy is keyword-aware and editable. The catalog does not say the model verifies facts. A draft that adds “organic,” “medical grade,” or a measurement you did not supply should lose that phrase in the editor, or the original description should stay.

The SEO title and the meta description are safer candidates for a first publish, and only after you confirm they do not invent a claim. Tags are organizational. Replacing them blindly can pull the product out of collections that depend on a tag. Read the tag chips against the tags you already use. Delete the ones that do not match.

  • Keep the handmade description when it holds a warning, a size, or a material.
  • Replace a slogan-only description when the draft keeps those facts and adds the missing use.
  • Push meta title or meta description alone when the body is already right.
  • Edit tags down to the set your collections and filters already understand.

Questions about comparing product copy

Can I keep the handmade description and replace only the meta?

Yes. Use the single-field push for the meta description or the meta title. Leave the description field unselected so the handmade body stays on the product.

Is revert on the free plan?

Revert belongs to the regenerate flow, and the Squadexa page lists regenerate-existing on Basic. Free is single-generation only. Confirm the plan screen before you rely on compare or revert. The page does not state a time limit for the snapshot.

Does compare publish by itself?

No. The view is for reading. Shopify changes when you update a field or run the fuller publish. Save for later writes nothing to the product.

Read the original and the draft side by side, publish one field when that is all you trust, and use revert to restore the pre-regeneration snapshot if the live text is wrong. The workflow is described on Squadexa AI.