Features
Approvals
Send listing copy, images and A+ designs to a manager or client for review over a shareable link, no login required, with an audit trail of every decision.
Approvals
Approvals lets you send proposed changes to a manager, client, or teammate for sign-off before they go live. The reviewer opens a shareable link, no Rufusly account needed, and approves, rejects, or suggests changes item by item.
It covers three kinds of work now: listing copy, product images, and A+ designs.
How it works
Sending for approval
From a listing project or the product editor, click Send for Approval. You can send:
- A full listing project (title, bullets, description, backend terms) comparing current against proposed content
- A custom set of items with any current and proposed field pairs
- Product images, shown as photos rather than as text diffs
- A+ modules, shown as a module preview with its text blocks
Add a title and an optional message for the reviewer, and choose how long the link stays open (7, 14, 30, or 90 days).
Reviewing
The reviewer opens the link in any browser. For each item they can:
- Approve the proposed change
- Reject it and leave a reason
- Suggest an alternative
Copy appears as a before-and-after diff, images as images, A+ modules as a preview with the copy that goes in them. No sign-up or password is required. Links are unguessable and scoped to a single approval request.
If something on the page is broken or an item will not load, the reviewer has a Report a problem link at the bottom that sends the message straight to you. They do not need to find your email address or work out who to tell.
Statuses
| Status | Meaning |
|---|---|
| Pending | Sent, not yet opened by the reviewer |
| In progress | Reviewer has opened the link and started deciding on items |
| Reviewed | Reviewer has submitted a decision on every item |
| Expired | The link's expiry date has passed and can no longer be opened |
A daily background job closes expired requests automatically. Individual item decisions carry their own status: pending, approved, rejected, or suggestion.
After the review
Regenerate and resend
Where a reviewer rejected something or left a suggestion, you can regenerate that copy with their feedback fed into the rewrite, then resend the same link. The reviewer sees the new version in the place the old one was, and does not need a second link.
Regenerating costs one listing credit per item regenerated, and a failed generation refunds its credit. Regeneration applies to listing copy. Rejected images and A+ modules link out to Image Studio or A+ Studio, where the feedback is acted on with the tool that made them.
Self-approve
If you regenerated the copy yourself and are happy with it, you do not have to send it back out for another round. Self-approve marks the remaining pending items approved and, once nothing is undecided, flips the request to reviewed so the apply actions become available.
Self-approve deliberately will not touch an item the reviewer explicitly rejected or left a suggestion on. Those have to be regenerated first, so a reviewer's decision cannot be quietly overridden.
Apply approved content back to the source
Once a request is reviewed, approved content can be written back to where it came from:
- Back to the listing project, so the approved copy is what the project holds
- Back to the source file, so the approved title, highlights, bullets, description and search terms land on the exact rows they came from in a bulk session, ready to export
Where a reviewer edited a value themselves rather than just approving it, their edit is what gets applied, not the original proposal.
Where to send from
- Product editor, the Send button in the product header
- Listing Studio, Step 3 (Optimised Listing), after a rewrite
- Approvals dashboard (
/approvals), view every request you have sent, filter by status, and open the reviewer's decisions
Brand memory
When a reviewer rejects a change or leaves a suggestion, Rufusly extracts the reason and feeds it into that brand's memory, so future AI rewrites for the same brand avoid repeating the same mistake automatically.
Frequently asked questions
What can I send for approval in Rufusly?
Listing copy (title, bullets, description, backend search terms and highlights), product images, and A+ modules. Copy is reviewed as a before-and-after diff, images as photos, and A+ modules as a preview with their text blocks.
Does the reviewer need a Rufusly account?
No. The reviewer opens an unguessable link in any browser and approves, rejects, or suggests an alternative for each item. No sign-up or password is required, and the link is scoped to that single approval request.
What does it cost to regenerate rejected content in Rufusly Approvals?
One listing credit per item regenerated, with the reviewer feedback fed into the rewrite. A failed generation refunds its credit. Sending, reviewing, self-approving and applying approved content cost nothing.
Can I approve my own changes without sending them back to the reviewer?
Yes. Self-approve marks the remaining pending items approved so the apply actions become available. It will not touch an item the reviewer explicitly rejected or left a suggestion on, so their decisions cannot be quietly overridden.
What happens to content after it is approved?
Approved listing copy can be applied back to the listing project it came from, or back to the exact rows of the source file in a bulk session so it can be exported. Where a reviewer edited a value rather than just approving it, their edit is what is applied.
What if the reviewer hits a problem on the review page?
There is a Report a problem link at the bottom of the public review page that sends the message straight to the person who created the request, so the reviewer does not need to work out who to contact.