ChatGPT KI Guide: Compare Old Kurta Screenshots With Current Notes

By TryBuy Editorial

ChatGPT can organise the differences between an old kurta screenshot and a current record you supply. Ask for a dated change report that separates confirmed changes, unchanged fields and missing context. The model should not treat an old screenshot as live information or pretend it has refreshed a product page when you have only pasted saved text.

Assemble two clearly dated records

For each saved screenshot, provide the product URL, style identifier, selected variant context and capture date where known. Add the exact wording or your own transcribed observations relevant to the comparison. Keep a missing date or unclear selection marked unknown. Do not infer the size from the model in the photo or from a cropped interface element.

Create a second record from the live information you have personally checked or obtained from an appropriate current source. Include its check date and the selected option. Keep price, availability, description, measurement labels and inclusions in separate fields. The task does not require the model to browse; this guide uses only the records supplied to it.

Copy the dated-change prompt

Compare my saved and refreshed kurta records. Return field, old value and date, current supplied value and date, source pointer, whether the comparison is valid, and effect on my stated buying requirements. Do not infer missing variant context, treat a changed image as a confirmed product change or invent reasons for a difference. Flag unresolved conflicts and draft a specific clarification question. Keep preference notes separate from changeable purchase information, and do not claim you checked a live page unless that check is explicitly part of the supplied record.

Ask for a visible not comparable state. Two screenshots may concern different variants or lack enough context to establish that a field changed at all.

Filled fictional example

Suppose a fictional saved note contains a size option and price from several weeks earlier, while the refreshed record identifies another selected size. The report should flag the variant mismatch before declaring a price change. If the exact current candidate no longer has the required size according to the supplied check, that can be marked as a decision-relevant availability issue rather than an invitation to assume another size is equivalent.

A new photograph may make a border easier to see without proving that the design changed. The model should preserve that distinction and ask for clarification only if the difference affects your requirement. This is a record-comparison example, not a statement about current prices or inventory of any named kurta.

Revise the report by field

• “Show every claimed change where the two records do not identify the same variant.”
• “Move image-based interpretations into observations rather than confirmed product changes.”
• “Update the decision-effect column using my clarified requirement, leaving the source records unchanged.”

Avoid asking for a confident recommendation when the missing context still prevents a valid comparison. The useful next output may be a short question rather than a ranked shortlist.

Check the current record again before purchase

Verify the product and selected option yourself at the point you intend to act. Check arithmetic and copied figures in the report. Keep the model’s summary separate from a seller’s answer and retain the source dates. A polished comparison cannot secure availability, explain an undocumented change or establish whether a garment will fit you.

Keep any second-hand transcription labelled as such; if a digit or selected option is unclear, resolve it from the actual record before treating the comparison as complete.

Use the original practical guide for versioning the practical shortlist and the men’s kurtas collection for current individual listings. Save the report with the old and refreshed records. Its purpose is to preserve useful research while preventing stale information from quietly becoming the basis for today’s decision.

For general instructions and follow-up techniques, see official OpenKI prompting guidance.