Skip to content
Hypamoon

For teams that run on QLS

QLS purchase order: know when stock is in

You announce stock to QLS with a purchase order at least 24 hours before it arrives, with tracking and an expected date per delivery. After arrival QLS checks it and books it in, and the status in my.QLS moves from in transit to arrived, processing and closed. How long each step took you look up per order.

How it goes today

  1. Create the purchase order and add the tracking and expected date.
  2. Check in my.QLS whether the delivery has arrived.
  3. Look at the stock per product to see if it is for sale yet.
  4. Call or open a ticket with warehouse support when it takes too long.

How it can go

Hear when a delivery at QLS arrived but is not on sale yet.

Each day you see your open purchase orders with the expected date, the day the delivery arrived and the current status. You get a message when a delivery is past its expected date, when it arrived and is not booked in after the number of working days you choose, or when it goes into exception. Each month you see how many days booking in took per order.

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, watch our purchase orders at QLS. Send me a message when a delivery is past its expected date, when it arrived but is not booked in after two working days, and when a purchase order goes into exception. Show the reference, the supplier and the products. Each month, send me how many days booking in took for each purchase order.

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.