Home/Product/Returns
● Returns and cases

Returns, cases and
cancellations, one queue.

A return on eBay, a case on Amazon and a cancellation on Shopify are three different things in three different portals. Here they are three rows in the same queue, each with the order, the buyer and the tracking already attached.

● Every channel, one queue● Labels and refunds in place● Portal-free handling
● Why it matters

Returns are where the metrics get lost.

Marketplaces measure how quickly you respond, and they measure it per channel. Anything handled by logging into a portal when somebody remembers is a metric waiting to slip.

Speed

Response time is a seller metric

Late responses on cases and returns damage seller standing on most marketplaces. A single queue with the context attached is the difference between answering in minutes and answering tomorrow.

Context

The order is already there

Whoever picks up a return can see the order, what shipped, which carrier carried it and where the parcel got to, without going to look for any of it.

Stock

Returned stock comes back

A return that is processed here puts the unit back into the right place, rather than leaving the stock figure wrong until somebody counts.

● What the module does

Handle it here, not in the portal.

Each marketplace models returns differently. Huup ingests them into one shape while keeping the actions each platform actually supports.

Returns Returns ingested per channel

Return requests arrive from each connected marketplace with reason, items and the original order attached.

Returns Return labels

Return labels are generated through the carrier integrations already connected, so the buyer gets one without a separate portal visit.

Cases Cases and disputes

Buyer cases land in the same queue as returns, so nothing sits in a channel inbox nobody has open.

Cancellations Cancellations as a real flow

Cancellation requests are handled against the marketplace API, so stock, the order and the ledger all end up consistent.

Refunds Refunds issued in place

Refunds are issued from the return record and pushed to the channel rather than being done in a portal and noted here afterwards.

Stock Restock on receipt

Receiving a return puts the unit back into the warehouse and location it belongs to, so the number on the shelf and the number in the system agree.

Accounting Credit documents posted

A refund posts to Xero, QuickBooks, Sage or Odoo as the matching credit document instead of being reconciled by hand.

Portal Buyer self-serve

The branded customer portal lets buyers start a return themselves, which takes the first message out of the queue entirely.

● Getting started

It turns on with the channels.

There is nothing separate to connect. Once a marketplace is connected, its returns, cases and cancellations arrive in the queue.

  1. 1 Connect the marketplaces you sell on.
  2. 2 Open Sales, then Returns, Cases or Cancellations.
  3. 3 Set who handles them and which warehouse receives stock back.
  4. 4 Answer from the queue instead of the seller portal.

Answer returns before the metric slips.

14-day trial, no card required. Every channel's returns in the queue your team already works from.