Skip to content
Hypamoon

For teams that run on QLS

QLS returns: follow each one to the end

A return at QLS goes from a return label to arrival at the warehouse, a check, and then back into stock, rejected or into quarantine. The status changes in my.QLS, but a return that arrived and is still not processed a week later stands out when your customer asks for the refund.

How it goes today

  1. Look up the return label by the tracking number your customer sends.
  2. Check whether the carrier delivered it to QLS.
  3. Search the returns in my.QLS for that order.
  4. Open a ticket when it arrived but is not processed.

How it can go

Follow each return from the label to the moment QLS books it back in.

Each morning you see the returns on their way, the ones QLS received and the ones processed, with how many days each has waited. Returns delivered to QLS that are not processed after the number of days you choose, and returns that were rejected, incomplete or put in quarantine, are on a short list with the order number and the products, so you can answer your customer and open a ticket with the details.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your QLS key in the portal, never in the chat.

Your request

With Hypamoon, each morning, go through our returns at QLS. Show the ones on their way, received and processed, with the days each has waited. List the returns that were delivered to QLS but not processed after five working days, and the ones rejected, incomplete or put in quarantine, with the order number, the customer and the products. Draft a short ticket text for each one I mark.

You create a separate QLS user yourself: register it, add it in my.QLS under Settings, Users, and paste that login in the portal. It stays yours.