Skip to content
Hypamoon

For teams that run on Omniva

Omniva return parcels from your customers

Customers return goods with a six-digit Omniva return code or a return created for their parcel. The return travels as its own parcel, and when it does not arrive the customer asks the shop for the refund. Following each return means looking up its code in tracking.

How it goes today

  1. Ask the customer for the Omniva return code.
  2. Look the return up in Omniva tracking.
  3. Check the warehouse before you refund the customer.

How it can go

Know which Omniva returns are on the way, so the refund goes out on time.

Each morning you see the customer returns linked to your own Omniva parcels: handed in, on the way and arrived, with the order number and the last scan. Returns that have not moved for longer than you set are marked, so you can follow them up. When a customer asks, a return for their delivered parcel can be created, and it goes to Omniva only after you approve it. The refund itself stays in your shop.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. Omniva first switches on access for your company when you ask them, which can take a few business days. After that you get the key, or create it yourself, and paste it in the portal, never in the chat.

Your request

With Hypamoon, each morning, list the customer returns of our Omniva parcels that were handed in, are on the way or have arrived, with the order number and the last scan. Mark returns with no new scan for five working days. When I name an order, create an Omniva return for the delivered parcel, and only after I approve it. Email me the list.

Omniva gives API access to business customers with a contract: you ask Omniva business customer service for data exchange, and your account manager sends a user name and password with your customer code. They stay yours.