When an MLS returns virtually staged images, identify the rejection reason before editing anything: missing disclosure, unreadable disclosure, or disclosure placed where that MLS will not accept it. Each requires a different correction, and treating all three as “fix the label” can send the same photo set back for another return.
At 2:15 p.m., Lena is at her kitchen counter in Phoenix, one hand on a cooling mug of coffee and the other scrolling through an MLS return notice. Her seller expects the listing to go live before the evening, and the living-room image is the lead photo in the set. The notice says the altered-image disclosure does not meet policy, but does not say why.
If she guesses wrong, the listing may miss that launch window. Her seller has already approved the staged images, the description is ready, and a revised upload could still come back if Lena only enlarges a disclosure that was actually missing from one export. The clock does not reward broad edits.
Read the return notice as a sorting task
Start by separating the return into one of three buckets. Do not adjust color, furniture, crop, or video assets until you know which bucket applies.
A missing disclosure means the required statement never made it into the file or accompanying listing media. Check every altered image, including alternates and any version exported for a different channel. One compliant hero image does not correct six unmarked room photos.
An unreadable disclosure means the statement exists but cannot be reasonably read in the uploaded file. The cause may be small type, low contrast, compression, a crop, or a platform preview that reduces the image more than your local file viewer did. Open the actual exported image at the dimensions submitted to the MLS. Then check the disclosure at the size a reviewer is likely to see.
A placement issue means the disclosure is present and legible, yet it appears in a location the local rule does not permit or does not keep with the image. A disclosure in a caption, photo remark, or separate document may not satisfy a board that expects the disclosure on the image itself. The disclosure that must stay with every AI-altered listing image covers why the image and its disclosure need to travel together.
The national Code of Ethics Article 12 requires a true picture in listing media. Individual MLS policies add their own operational requirements. Read the return notice alongside your current MLS rule and your state association’s guidance. Disclosure-assisted software can support the work; the listing agent still needs to confirm what the local rule requires.
Check the exported files, not the source folder
Lena finds the disclosure on the source image. It sits in the lower edge, clear enough when she opens the full-resolution file on her laptop. But the image in the MLS upload queue has been cropped for a display format, taking part of the disclosure with it.
That makes this a placement problem caused during export, not an absent disclosure. If she had added a second label without checking the submitted file, she could have created a cluttered image and still missed the board’s requirement.
Build the check around the final files:
- Compare the returned image filename against the source and final export.
- View the final export at normal listing-view size, not only at 100 percent zoom.
- Confirm the disclosure remains visible after any crop, resize, or platform formatting.
- Check that each virtually staged image carries the appropriate disclosure, rather than assuming a note on the first image covers the set.
This is also where a public provenance page can help you keep a record of how an image was produced. It does not replace the disclosure required by an MLS policy, but it gives the agent and broker a clear reference when someone later asks what changed.
Correct the smallest thing that resolves the return
Once you know the bucket, make a narrow correction. For a missing disclosure, regenerate or re-export the affected image with the required disclosure burned in. For an unreadable one, increase legibility in the final file and inspect the compressed result. For placement, move the disclosure to the permitted location, then export again without changing the property image unnecessarily.
Avoid rebuilding the whole kit because one image was returned. That introduces fresh variables at the worst moment: a changed crop, an older draft uploaded by mistake, or an image whose disclosure differs from the others.
NestPath Listing Studio is designed around that practical workflow. It turns an agent’s own listing photos into a kit that includes virtually staged images with a burned-in, per-state AI disclosure and a public provenance page, alongside a narrated tour video and MLS-ready text pack with a fair-housing check. The disclosure support is useful only when the final export and local MLS rule are checked together.
Make the resubmission easy to defend
Before Lena reuploads, she saves the return notice with the final files and writes down the correction: the disclosure was cropped in the submitted version, then moved and verified in the replacement export. If her broker asks what changed, she has an answer tied to the file rather than a vague recollection of a rushed afternoon.
The photo set goes back with the disclosure intact at the image level. The living room remains staged, the seller’s launch plan remains possible, and Lena has a repeatable sequence for the next return notice: classify first, inspect the submitted file, correct only the failure, then document the resubmission.
Comments
No comments yet.