Skip to content
Hypamoon

For teams that run on QLS

QLS cut-off: see the orders that missed it

QLS fulfilment works with a cut-off time: orders that come in before it go out the same day. Whether that happened you see per order in my.QLS. A late order often shows up first as a question from your customer or as a late shipment on a marketplace account.

How it goes today

  1. Filter the orders of the day in my.QLS.
  2. Check which ones are still open after the cut-off time.
  3. Find out whether a product was out of stock or the order was on hold.
  4. Open a ticket and tell the customer the order is late.

How it can go

Know each evening which orders came in before the cut-off and did not leave.

Each evening you get the orders that came in before your cut-off and were not sent that day, with the reason that shows in QLS: on hold, waiting for stock, an address that did not pass validation, or no reason given. Each week you see the share of orders sent on time per day, so you can bring it up with your account manager with the numbers at hand.

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 evening, list the orders at QLS that came in before our cut-off time, which I will give you, and were not sent that day. For each one show the order number, when it came in, its status and why it waits: on hold, waiting for stock, an address problem or no reason given. Once a week, send me the share of orders sent on time per day.

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.