For teams that run on Ongoing WMS
Ongoing WMS return reasons per product
When the warehouse processes a return in Ongoing WMS it can set a return cause per product, and Ongoing notes that this data can be used to evaluate products. The goods owner gets a daily email with returned goods, so the picture per product is put together in a spreadsheet.
How it goes today
- Collect the daily emails with returned goods.
- Copy the returns into a spreadsheet.
- Count per article and per return cause.
- Compare with how many of each article were shipped.
How it can go
Each month you see which products come back, and why.
On the first of the month you get a page per product: units shipped, units returned, the return rate next to last month, and the return causes from most to least common. Products whose return rate went up stand at the top.
Say this in ChatGPT, Claude or Copilot
Your chat gets connected to Hypamoon first, with this request filled in. You paste your Ongoing WMS key in the portal, never in the chat.
With Hypamoon, on the first of every month, take last month's shipped and returned products from Ongoing WMS. Per article, show units shipped, units returned, the return rate compared with the month before and the return causes from most to least common. Put the articles whose return rate went up at the top and email it to me.
If you run the warehouse, you create the Ongoing WMS API user yourself under Administration, API for goods owners. If a 3PL runs it, the 3PL creates it for you. It stays yours.
More for teams on Ongoing WMS
- The stock in my webshop does not match Ongoing WMS.
- I want a report the Ongoing WMS customer login does not have.
- I type B2B orders from email into Ongoing WMS by hand.
- I set the reorder point in Ongoing WMS article by article.
- I find out late that a supplier delivery was short.
- My team looks up orders in Ongoing WMS to answer where is my order.
- I want to know what fulfilment costs me per order.
- Everything for Ongoing WMS