UnshiplyRequest access

Refund rules, written as sentences.

A rule says when to refund, how much, and what has to have happened first. One sentence each, the way you would say it at the packing table.

The three days a rule lives in.

Every rule fires on one of them.

  1. Day 0

    Request

    The customer picks the item and the reason.

  2. Day 1

    Label

    The carrier gives back a label and it goes to the customer.

  3. Day 3

    Scan and refund

    The carrier takes the parcel. Most rules fire here.

Twelve rules, as you would say them.

These are examples. You write your own in the same shape.

  1. 01Refund on carrier scan under €80.Fires: Day 3
  2. 02Refund on warehouse check above €80.Fires: Day 4
  3. 03Give store credit instead of money when the customer asks for it.Fires: Day 3
  4. 04No label for a request that arrives after 30 days.Fires: Day 0
  5. 05Free label when the reason is faulty; the customer pays otherwise.Fires: Day 1
  6. 06Take the €4.90 label off the refund unless the item came faulty.Fires: Day 3
  7. 07Hold the refund when the parcel weighs less than the order.Fires: Day 4
  8. 08Refund the outbound shipping when the whole order comes back.Fires: Day 3
  9. 09Send anything over €300 to a person before the label goes out.Fires: Day 0
  10. 10Never refund a clearance item on the scan; open it as a question.Fires: Day 0
  11. 11Refund on the scan for a returning customer, on the check for a first order.Fires: Day 3
  12. 12Close a request when no parcel has arrived after 14 days.Fires: Day 14

When two rules collide.

The stricter one wins. “Refund on carrier scan under €80” and “never refund a clearance item on the scan” meet on the same return, and the hold wins: the money waits for a person. Unshiply names the rule that fired on every return, so you can go and read the sentence that did it.

Try a rule against the last 30 days.

Write the sentence and Unshiply replays your last thirty days of returns through it before it is live: which ones would have refunded on the scan, which would have waited for the warehouse, which would have gone to a person. Then you turn it on, or you rewrite it.

The events a rule can hang on.

Seven of them. A rule names one, and everything else is a condition.

The events a rule can hang on. Seven of them. A rule names one, and everything else is a condition.
EventWhenWhat it means
request.createdDay 0The customer picked an item and a reason.
label.issuedDay 1The carrier gave a label; it is in their inbox.
parcel.scannedDay 3The carrier has it. Most rules fire here.
warehouse.checkedDay 4Someone scanned it on your shelf.
refund.issuedDay 3 or 4The money left, in Shopify or WooCommerce.
credit.issuedDay 3 or 4Store credit instead of money.
request.expiredDay 14No parcel arrived; the request is closed.

What Unshiply does not do.

  • It does not decide the reason. The customer picks from your list, and you write the list.
  • It does not shorten the 14-day right of withdrawal in the EU. Write a rule that tries and Unshiply refuses to save it.
  • It does not touch stock without a scan. Nothing goes back on sale because a sentence said so.

Tell us the first rule you would write.

Request access with your platform and your volume, and send us the sentence. Nothing here is live yet.

No inbox in the loop.

Waitlist. One email when it is your turn.