Step 3 — Approvals

After the Fix Sprint processes your catalog, every proposed change is staged in the Approvals queue. Nothing has touched your live store yet — this step is your opportunity to review each change and decide what gets published.

What you’ll see

For each change, the Approvals dashboard shows:

• What’s changing — the type of change (description, attribute mapping, schema, etc.)
• Original value — exactly what’s in your store today
• Proposed value — what Agentic Prep generated
• Why — a plain-language explanation of what gap this fixes

Your options for each change

Approve — marks the change as ready to publish. It won’t go live until you run Step 4.

Edit inline — if you want to modify the proposed value before approving. Useful if the generated description doesn’t quite match your voice, or if an attribute mapping needs adjustment.

Reject — removes the change from the publish queue. The original value stays as-is.

Batch approval

If you have a large catalog, reviewing every change individually can take time. Batch approval lets you approve all changes of a given type at once (e.g., “approve all attribute mappings for the Apparel category”). You can still reject individual items after batch-approving.

Tips for reviewing descriptions

The generated descriptions are factual and structured for AI readability, but they may not match your brand’s exact voice out of the box. Things to check:

• Tone — does it sound like your brand?
• Facts — are all product details accurate? (The generation is based on your existing data, but verify anything that matters)
• Audience — does the opening sentence correctly describe who the product is for?

The inline editor lets you make changes directly without leaving the approval queue.

What happens to rejected changes

Rejected changes are logged but not applied. If you change your mind later, contact support — rejected changes can be re-staged within the 30-day window.