Skip to content
Hypamoon

For teams that run on QLS

QLS orders: see the ones that did not start

Orders come into QLS through the link with your shop. An order with an address or product QLS cannot validate stays at a validation error or on hold until someone fixes it, and an address that looks right but is refused goes to IT support through a ticket.

How it goes today

  1. Check in my.QLS whether the orders of today came in.
  2. Open the ones with an error message and read why.
  3. Check the address on postcode.nl or ask the customer.
  4. Open a ticket with IT support when the address is right.

How it can go

See each morning which orders QLS could not start on, and why.

Each morning one list of orders at QLS with a validation error, still in concept or on hold, with the order number, the reason QLS gives and how long each has waited. You also see how many orders came in per shop compared with the same day last week, so a quiet day stands out before a customer writes.

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, list our orders at QLS that have a validation error, are still in concept or are on hold, with the order number, the reason and how long each has waited. Also show how many orders came in per shop compared with the same day last week, and flag a shop where far fewer came in.

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.