SquidSupport
Product reference / Settings

Refund Hub Settings

In the app: Settings → Refund Hub

Needs the 'General Settings' permission.

Decides how refunds and customer photos are handled before any money moves: which stores use the Refund Hub, how much the AI may refund per kind of problem, whether a person must approve refunds and photos, and what the manual refund form offers. The refund policies apply to the whole organization; approval, limits and photo review are set per store. The queue where refunds and photos are reviewed is the Refund Hub itself, in the main menu.

Store rollout and automatic processing

This block at the top controls where the Refund Hub is in use.

The store list shows every store you can access, with an "Enabled" or "Disabled" label and an "Enable store" or "Disable store" button. A change is saved at once.

  • Enabled: the AI can submit refunds for the store. Whether they are paid automatically or wait for a person is decided by "Refund Approval Required" under "Per-store refund settings".
  • Disabled: the AI cannot submit a refund for the store, neither to the queue nor automatically. When it tries, the ticket is assigned to the human team instead. The automatic refund for a cancelled membership is not paid either.

Enabling the first store of an organization that did not use the Refund Hub yet also switches the Refund Hub on for the organization, which opens the Refund Hub page and the "Manual refund policies" section. The stores you did not enable stay disabled until you enable them one by one. Disabling a store does not remove its refund requests or history, and disabling every store does not close the Refund Hub page again.

"Pause automatic processing" stops every automatic refund in the whole organization, in every store. The label next to it reads "Automation running" or "Automation paused". While paused:

  • a refund the AI would have paid automatically is added to the Refund Hub queue and waits for a person;
  • an automatic refund for a cancelled membership is not paid; the ticket is assigned to the human team;
  • the queue and the history stay available, and people with the right permission can still approve and deny refunds by hand.

Pausing takes effect for the next refund. A refund that is being submitted at that moment is finished first, and a refund that was already paid is not undone.

"Resume automatic processing" asks you to confirm with "Confirm resume"; "Keep paused" cancels. From then on, a refund the AI submits follows the store settings as they are at that moment. Refund requests that went to the queue during the pause stay there; resuming does not approve them.

Refund log

"Save refund requests to Google Sheets" is off by default. When it is on, a row is added to a Google spreadsheet for every refund request that is approved or denied in the Refund Hub, every refund the AI pays automatically, and every manual refund once it is paid or rejected. It applies to every store in the organization. Rows are written by a background task, so they may arrive later. If the connection or write fails, a row can be missing even though the refund itself succeeded.

"Destination spreadsheet" appears when the switch is on or a spreadsheet is already selected. It is the spreadsheet to write to. Only spreadsheets Squid can edit are listed; "Manage Google Sheets" opens Settings → Google Sheets. Without an editable spreadsheet the switch cannot be turned on.

Squid creates one worksheet per month inside that spreadsheet, the first time a refund is logged that month. Months follow UTC, so a refund processed late on the last day of a month can land in the next month's worksheet. "This month:" shows the name of the current worksheet.

"Save refund log" saves the switch and the spreadsheet; nothing changes before that. The log cannot be switched on without a spreadsheet. When saving would stop the log or switch it to another spreadsheet, Squid asks you to confirm; rows already written stay in the earlier spreadsheet.

AI refund policies

One row per refund category, such as "Defective", "Poor quality" or "Doesn't fit". These are the limits on what the AI may refund, and they apply to every store unless a store sets its own limit.

  • "Max %": the largest share the AI may refund in that category, from 0 to 100, kept to two decimals. For a refund of specific items it is a percentage of what the customer paid for those items; for a refund of the whole order it is a percentage of the order total. The check allows a one-cent rounding margin above the calculated limit. Above that margin, the refund is refused and nothing is submitted. A limit of 0 therefore still permits a one-cent refund.
  • "Full order": whether the AI may submit a refund for the whole order in this category, without naming the items. When it is off, the AI must name the items it refunds.
  • "Active": whether the AI may use the category at all. A refund in an inactive category is refused.
  • "Updated": when the row was last changed.
  • "Save": each row is saved by itself and applies to the next refund the AI submits.

The percentage also limits the order as a whole. Everything already refunded or waiting for review on the order is added to the new refund, and when the total exceeds the category's percentage of the original order total by more than one cent, the refund is not submitted and the ticket is assigned to the human team.

A warning appears under the "Return automation refund" row when at least one store refunds once a return is verified: "Refund automation is on." "See affected stores" lists those stores and whether each one refunds immediately or submits for review. The warning says the percentage is the refund the AI submits; that is not what happens. When a return tracking number or a return-label photo is verified, the refund is for the full amount the customer paid for the returned items, less the return shipping fee when the store charges one. The row only limits it: when that amount is more than the row's percentage of what the customer paid for the items, which a percentage below 100 normally causes, the refund is not submitted and the ticket is handed to a person.

The list of categories is managed by Squid. "Request a category" emails Squid support. Opening this page adds every category that is missing for the organization, with Squid's built-in limit, so the message "No refund policies are set up for this organization" should not normally appear. Its note says the AI then applies no limit per category; that is not what happens. For a category the organization has no row for, the AI uses Squid's built-in limit, and it refuses a category it does not know.

These limits cap what the AI may propose. They do not decide whether a person must approve the refund; that is "Refund Approval Required" under "Per-store refund settings". They do not apply to refunds teammates make by hand.

Manual refund policies

This section sets up the manual refund form that teammates fill in from a ticket. Seeing it also needs the 'View Refund Hub' permission, and it is unavailable when the Refund Hub is not enabled for the organization.

"Offers" are the options in the form's "Offer chosen" menu. "Add offer" adds one. Each offer has:

  • "Offer": its label. Every offer needs a label and labels must be unique.
  • "Refund %": the percentage that is filled in as the refund when the offer is chosen, 0 to 100.
  • "Needs QA": the refund is held for a reviewer before any money moves.
  • "Return policies apply": the order is checked against the store's return window first.

Four lists fill the form's menus. Type a value to add it and use the cross to remove one.

  • "Refund reasons": logged to the refund sheet as the refund explanation. The AI picks its refund reason from this same list. The help text calls the two lists independent; that only holds for an organization that existed before this list, whose AI keeps its earlier reasons until the first time the reasons are changed here. From that save on, the AI uses this list too.
  • "Product types": the top-level product grouping.
  • "Product categories": the detailed category, shown after the product type. The AI is shown this list too.
  • "Payment methods": the form's payment method menu. The first one is preselected.

None of the four lists, nor the offers, can be saved empty: the form needs an answer from each of them.

"Allow submitting on behalf of another agent" unlocks the agent name field on the form. Off by default; the refund is then recorded under the name of the teammate who submits it.

"Allow agents to manually adjust the refund amount" unlocks the refund value on the form. Off by default; the server accepts at most a one-cent difference from what the offer gives. With it on, the offer still decides whether QA is needed, except that raising the amount by more than one cent above what the offer would refund sends the refund to QA.

"Allow repeated refunds on the same item" is off by default. It lets an item that was already partly refunded take another offer, as long as the total stays within what the customer paid for it. A new offer replaces the earlier one; it is not added to it. With 10% already refunded and a 30% offer chosen, the customer gets 30% in total, not 40%.

"Refund allowance" is the most a manual refund may be, as a percentage of the order total, 0 to 100. It starts at 50. Two other limits still apply, and the lowest of the three counts: what Shopify says can still be refunded on the order, and the order total less the refunds Squid already recorded for the order.

Nothing in this section is saved until you click "Save manual refund policies". Saving needs the 'General Settings' permission.

Per-store refund settings

One card per store; click a store to open it. "Save Settings" at the bottom of the card saves that store.

"Refund Approval Required" is on by default.

  • On: refunds the AI suggests are queued in the Refund Hub and are only processed in Shopify after a person approves them.
  • Off: refunds the AI suggests are processed in Shopify automatically, and Shopify sends the customer its refund notification.

Even with the switch off, a refund goes to the queue for a person in these cases: it reaches the amount under "Send large refunds for approval"; the order already had one automatic refund; the order is waiting for a return-policy review; automatic processing is paused; or Shopify did not accept the automatic refund, for example because it is more than Shopify can still refund on the order.

One kind of refund does not follow this switch: the refund for a verified return. Whether that one is paid immediately or submitted for review is the store's choice for verified returns in its AI settings, whatever this switch says. The amount under "Send large refunds for approval" and the other cases above still send it to the queue. Review is also required when the destination city does not match the warehouse, when the parcel was shared with another order already refunded using the same proof, or when a receipt proves shipment but the carrier has not yet reported the destination.

"Send large refunds for approval" is an amount of money. A refund the AI suggests of that amount or more always goes to the queue for a person, even when the store processes refunds automatically. A refund of exactly the amount is queued too.

  • It can only add approval, never skip it. On a store where "Refund Approval Required" is on, every refund is queued anyway and the amount changes nothing.
  • Blank means no limit, which is the default. The amount must be greater than zero. It is saved with "Save Settings".
  • The amount is in the store's own Shopify currency, shown next to the field. You cannot choose the currency. Until Shopify has reported the store's currency, the field shows EUR.
  • The refund is compared in the currency the customer paid in. Squid does not convert currencies. Once an amount is set, a refund in another currency than the store's is always sent for approval, and so is a refund whose currency cannot be established. A refund in another currency only happens on a store that sells in several currencies; the (i) says so for such a store.
  • It also holds back the automatic refund for a cancelled membership: at or above the amount, that refund is not paid automatically.
  • It applies per refund, not per order or per day, and it does not limit refunds that teammates make by hand.

"Allow refunds for non-products" is off by default. When it is on, the AI may refund Shopify line items that are not products, such as a shipping warranty or a gift card. Despite the on-screen claim that these are always refunded in full, their dedicated category pays its configured "Max %" of the selected items’ paid value. A limit below 100 can therefore produce a partial refund. Membership cancellation refunds are handled separately. A shipping warranty is not refunded once Shopify shows the order as delivered, when the order has a return-portal submission, or when a return was registered for the warranty item. When it is off, the AI leaves such items out of a refund and refunds the rest. When the AI should offer this is set in your AI instructions.

"Selling add-ons and non-physical products" is a list of products a customer pays for that never ship as a parcel and never come back, such as shipping protection, memberships or gift wrap. Use it for the ones Shopify still marks as shipping. A listed product is hidden from the return portal, the AI never accepts it as a return, and returns and cancellations do not count it as a parcel. Listing a product covers all its variants. Teammates can still refund it by hand with the manual refund form. Search the store's products to add one, or paste a product's ID or its Shopify admin address; the list holds up to 50 products. Searching needs the store to be connected to Shopify; without a connection only a product's numeric ID can be added. A product is matched by its ID, so the list cannot match an order item whose product ID Shopify no longer supplies. The page marks listed products it can no longer find in Shopify.

"Possible add-ons" is a list of suggestions inside the add-on card. It only appears when there is something to suggest.

  • Once a day Squid looks at the store's orders of the last 60 days, as synced from Shopify. Test orders and orders without synced item details are excluded. A store without order sync, or with fewer than 30 orders in that period, gets no suggestions.
  • A product is suggested when it is on at least 5 orders, is almost never the only product on its order, and costs little next to the store's usual products. A product whose name sounds like an add-on, such as shipping protection, is suggested a little sooner. Products already on the add-on list are not suggested.
  • At most 10 suggestions are open per store. Each one shows the product and the reason, such as the share of orders it is on.
  • "Add to list" puts the product on the add-on list above. Like every other change on the card, it only takes effect after "Save Settings".
  • "Not an add-on" removes the suggestion at once, without saving the card. The product is not suggested again. It moves under "Dismissed", where "Undo" brings the suggestion back.
  • A suggestion disappears by itself when the store's orders no longer support it. A dismissed one stays dismissed.

A suggestion changes nothing by itself: only the add-on list decides what is hidden and what the AI refuses. When new suggestions appear, teammates with the 'General Settings' permission and access to the store get a notification, at most once a day per store and to at most 50 teammates.

"Sealed-only products" is a list of products you take back only when the packaging is still sealed, such as swimwear or cosmetics. It works like the add-on list: search or paste a product ID, up to 50 products, all variants covered, saved with "Save Settings".

  • In the return portal a listed product is shown greyed out and cannot be selected. The customer reads that the product cannot be returned through the portal and is asked to contact support.
  • When the customer writes in, the AI records the return as waiting for review and asks for a photo of the sealed, unopened packaging. Until that photo is approved, the AI gives no return instructions and no compensation for the item.
  • The photo appears in the Refund Hub for a reviewer. Approving it makes the item returnable, and the AI continues the return. With several sealed-only items on one order, each item needs its own approved photo. A rejected photo leaves the return waiting; the customer can send better photos.
  • A product that is also on the add-on list is treated as an add-on: it cannot be returned at all.

"Category limits for this store" is folded by default. Every category follows the organization's limit from "AI refund policies" until you set one here. "Set for store" saves a "Max %" for this store only, from 0 to 100; "In force" then shows the store's value next to the organization's. From that moment the store also keeps the category's "Full order" and "Active" values as they were when you set it: later changes to those two in "AI refund policies" no longer reach this store for that category. "Use organization" removes the store's value, and the store follows all three again. These save at once, without "Save Settings".

Photo validation hub settings

One card per store, for what happens with the photos customers send as proof.

"Photo Review Required" is on by default.

  • On: customer photos are queued in the Refund Hub for a person to approve or reject.
  • Off: photos a customer uploads in the return portal are approved automatically, but the upload does not itself send the approval email. Photos a customer sends by email or chat, which the AI files for review, are still queued for a person; the text under the switch does not mention this.

"Photo review emails" are what the customer receives when their photos are approved or rejected. There is an "Email on photo approval" and an "Email on photo rejection" for each language. A text marked "Default" is Squid's built-in email; edit it to make it your own ("Customized"), and "Reset to default" goes back. An emptied text sends the built-in email. Each text can be up to 10,000 characters. The subject line cannot be changed here.

The email goes out in the store's language when the return portal has that language. The texts in the other languages are then not used. For a store whose language the return portal does not have, the email goes out in the language the customer chose in the return portal, and in English when that is not known.

Words in curly brackets are filled in for each email. The allowed ones are listed under "Placeholders", among them the customer's first name, the order number, the item's name and the store's name. A text with an unknown placeholder cannot be saved. A blank line starts a new paragraph.

"Offers the verdict emails show" tells the AI which offer the approval email and the rejection email make. It does not change the text of the emails: you write the offer in the email text yourself, and here you point to the matching step of the store's offers, so the two say the same.

  • "Offers in the approval email" and "Offers in the rejection email" each have a menu with the store's offer groups, from its AI configuration. After you pick a group, a second menu picks the step ("Step 1", "Step 2" and so on), and the options of that step are listed underneath.
  • When a reviewer approves or rejects a photo and Squid prepares the email, the chosen step is recorded as the offer made to the customer for that item. This happens before delivery, so the offer can remain recorded even if the email fails to send. In the ticket, the AI then continues from that step instead of starting at the first offer again, and it can carry out the option the customer picks.
  • Only the options the step really has can be carried out. If the email text promises something the step does not have, such as a return to the warehouse, the AI cannot carry that out.
  • "No offers recorded" is the default. The email is sent as usual, no new offer is recorded, and any earlier offer history still applies. With no earlier offer, the AI starts at the store's first offer.
  • Nothing is recorded when the order still has an unaccepted offer at a later step of the same group, when the group or step no longer exists, or when it is not known which item of the order the photos are for.
  • The email that asks for new photos makes no offer and has no setting here.

A store whose AI configuration has no offer groups shows a note instead of the menus.

"Save Settings" saves the store's photo settings. Which return reasons ask for a photo at all is set under Settings → Return Reasons.