SquidSupport
Product reference / Refund Hub

Photo review

In the app: Refund Hub → Photos

Needs the 'View Refund Hub' permission.

Customers send photos as proof of a problem, such as a defect or damaged packaging. This tab shows the submissions that wait for a person, one at a time, and lets a reviewer approve, reject, ask for new photos or discard them.

Photo Review

Photos reach Squid in two ways, and "Photo Review Required" under Settings → Refund Hub only decides about one of them:

  • Photos uploaded in the return portal. With "Photo Review Required" on for the store, they land here and wait for a verdict. With it off, they are approved automatically the moment the customer submits the return and never appear on this tab; they are listed on the "Photo History" tab as "Approved".
  • Photos a customer sends in a conversation, which the AI files. New submissions filed this way wait here for a verdict, also when "Photo Review Required" is off for the store. If the return portal already filed a pending submission for the item, the AI keeps that card instead of creating another.

Which return reasons ask for a photo at all is set under Settings → Return Reasons.

A card covers an item of an order, or a particular unit of that item when a unit number is shown. An order with three items that each need photos gives three cards, and each gets its own verdict. One verdict covers all photos on the card.

  • The cards are in the order they came in, oldest first.
  • "3 of 12" shows your place in the queue. The arrows on either side go to the previous and the next card. Going past the last card returns to the first, and going back from the first card goes to the last.
  • The "?" button lists the keyboard shortcuts: left and right arrow to navigate, A to approve, R to reject. A approves at once; R opens the reject dialog. The shortcuts do not work while you type in a field or review a photo you opened from the search.
  • The round arrow next to the title reloads the queue from the first card. The queue also reloads every 30 seconds and keeps your place, and a card disappears when a teammate reviews it.

This tab has no store filter of its own. A store chosen in the filter on another Refund Hub tab stays in force here. A teammate whose access is limited to certain stores only sees those stores' photos.

When nothing is waiting the page says why:

  • "All caught up!": no photos are waiting.
  • "No store has returns enabled": shown when nothing is waiting and none of your stores has its return portal switched on. "Open return portal settings" opens Settings → Return Portal.
  • "Photo review is off for every store": shown when nothing is waiting and none of the stores with its return portal enabled has "Photo Review Required" on. Photos from the return portal are then approved automatically. Photos the AI files from a conversation still land here, so this tab can hold cards even with review off for every store. "Open Refund Hub settings" opens Settings → Refund Hub.

Both settings buttons are greyed out for someone without the 'General Settings' permission.

Seeing the photos needs the 'View Refund Hub' permission. Every verdict, and "Generate customer message", needs the 'Review Photos' permission; without it the buttons are still shown, but a click is refused.

Search pending photos

"Search pending photos by order number or item..." searches as you type and lists up to 10 waiting submissions whose order number or item name contains the text, oldest first. A leading # is ignored and capitals do not matter. A store chosen in the store filter also limits the search. Click a result to review that submission by itself; "Back to queue" returns to the normal order. The search field is only shown while at least one photo is waiting.

The search only covers photos that still wait for review. Reviewed photos are on the "Photo History" tab.

What a photo card shows

On the left is the photo. Click it to zoom in and click again to zoom out; the button in its corner opens it full screen. A video plays with its own controls and cannot be zoomed. When the customer sent more than one file, small previews under it switch between them.

On the right:

  • "Order" with the order number, and "Shopify", which opens the order in the Shopify admin in a new tab.
  • "Conversation" or "Return Portal": where the photos came from: a ticket in which the AI filed them, or the return portal. "View conversation" opens that ticket.
  • The shop and the store.
  • "Item": the item the photos are for. "(unit 2)" means the second piece of an item that was ordered more than once, and "×3" means the submission covers three pieces, rather than necessarily the whole quantity ordered.
  • "Original Price" and "Paid Price": the recorded original and paid prices. For photos the AI files, these come from the order's unit price before and after discounts. Return-portal submissions currently show the same submitted price in both fields.
  • "Reason": the return reason the customer gave.
  • "Submitted": when the photos came in, in your own timezone.
  • "Customer Notes": what the customer wrote with the photos, when they wrote something.

Approve

Needs the 'Review Photos' permission.

"Approve", or the A key, approves the photos at once. There is no confirmation step.

  • The card leaves the queue and is recorded on the "Photo History" tab as "Approved" with your email address.
  • Squid queues the approval email in a new ticket of its own, which is created closed and tagged "photo-verdict", so a reply from the customer is about this item only. The email is recorded in that ticket as sent by you. It normally uses the store's current language, falling back to the submission language and then English when unsupported. If the source ticket uses a shared mailbox for this store, the new ticket sends from that mailbox and uses its current language, or English when unsupported. The store still supplies the email text and branding.
  • The text of the email is the store's own approval text from Settings → Refund Hub, "Photo validation hub settings", when the store has one for that language. A missing or blank store text, or one that fails to produce a usable message, falls back to the built-in text, which confirms the problem with the item and offers a replacement.
  • The email goes to the address the customer gave in the return portal; without one, to the customer of the ticket the photos came from, and otherwise to the email address on the order in Shopify.
  • When an offer is linked to the approval email under Settings → Refund Hub, Squid tries to record that offer for the item so the AI can continue from it when the customer replies. It skips a missing offer group or step, an unidentified item, or an order that already has a later unaccepted offer in that group. Units already holding their final offer keep it. Accepted offers are also left alone. Recording can update other unaccepted items on this order that already have an offer in the same group. For a card about a particular piece, linked-offer recording currently starts at the first piece of the item, even when the card shows a later unit number. Without a linked offer nothing is recorded.
  • For a product on the "Sealed-only products" list, approving the photo of the sealed packaging is what allows the return to go ahead. A return registered for a particular piece is released after the sealed-packaging photo for that piece and its current reason is approved. Older returns registered for several items wait until every required item has approved sealed-packaging photos. An older return without a recorded list of required items stays waiting for review.

Approving a photo does not refund anything by itself.

If the email could not be prepared, because no email address was found for the customer or the store has no verified sending address, you see an error message that asks you to open a new ticket and contact the customer yourself. The approval still stands. A delivery failure after that is not reported on this tab.

An approval is refused with "The item's return reason changed" when the return reason of that piece was changed after these photos were filed. Review the photos for the current reason instead.

Reject

Needs the 'Review Photos' permission.

"Reject", or the R key, opens "Reject Photo".

  • "Internal reason (required — not sent to the customer)": why you reject it, up to 5,000 characters. It is kept in the review history and shown to the AI as background. It is never emailed.
  • "Message to the customer (editable)": an optional paragraph for the rejection email, up to 2,000 characters. Leave it empty to send the rejection email without an extra note. When the store uses its own rejection text, your message only appears if that text has a place for the reviewer's message.
  • "Generate customer message" turns your internal reason into a short, polite message in the store's current language, falling back to the submission language and then English when unsupported, and puts it in the field for you to edit. It needs an internal reason first. Nothing is sent until you click "Reject Photo". For a shared-mailbox ticket, the generated note still follows the store language even when the surrounding email uses the mailbox language; check the draft before sending. "Written in …" names the language. If the AI is busy, the dialog says "AI is unavailable — write the message yourself or retry".

"Reject Photo" records the verdict, removes the card from the queue and sends the rejection email in a new, closed ticket, the same way as an approval. Without a store text of its own, the built-in rejection email says the photos do not show the problem and offers two options: a partial refund with a voucher, or returning the item for a refund. An offer linked to the rejection email under Settings → Refund Hub is recorded subject to the same checks as an approval's linked offer.

Request New

Needs the 'Review Photos' permission.

"Request New" opens "Request New Photos". Use it when the photos are unusable, for example too dark or of the wrong item, and the customer should try again.

  • "Add a note for the customer (optional)": what is wrong with the current photos, up to 2,000 characters. "Generate customer message" rewrites your words into a customer-ready note in the store's language.
  • "Send request" emails the customer a request for new photos, in a new, closed ticket, and removes the card from the queue. This email always uses the built-in text: it asks the customer to reply with new, clear photos. The store's own email texts and linked offers do not apply to it.

On the "Photo History" tab a request for new photos is shown as "Rejected". New photos arrive as a new card once the AI files them from the customer's reply. A new return-portal submission also creates a card, but it is approved automatically if "Photo Review Required" is off for that store.

Discard

Needs the 'Review Photos' permission.

"Discard" opens "Discard Photo". Use it for a submission that is not valid at all, such as an empty or unrelated upload.

  • The card is removed from the queue and recorded on the "Photo History" tab as "Discarded".
  • No email is sent to the customer.
  • The AI treats a discarded photo the same as a rejected one.
  • "Optional internal note" is kept with the review, up to 5,000 characters.

None of the four verdicts can be changed afterwards. Only one person can review a card: if a teammate was first you see "This photo has already been reviewed by another agent", and if the customer sent better photos in the meantime you are told the submission was replaced and to review the new card.