Miinto: why was my order/transfer rejected?

About this article

This article describes Miinto's transfer system and the most common reasons behind transfer rejections.

Table of contents

Introduction

Troubleshooting

• Setting the threshold

Is there a manual transfer override?

Introduction

Miinto uses a system where individual merchants, known as boutiques, sell their own items. However, it is possible that multiple merchants sell the same items.

To prevent buyers from being disappointed by unnecessary out-of-stocks, Miinto implements a system where an order is first a 'transfer'. As the name suggests, it can be passed on to different merchants if the first merchant rejects it.

If the transfer matches certain specific scenarios, described below, ChannelEngine automatically rejects it and displays a notification accordingly.

Troubleshooting

There are four scenarios in which ChannelEngine checks if a transfer should be automatically rejected or not. If none apply, the transfer is accepted.

1. The Miinto item ID on the transfer is empty.

   This is the unique identifier for products on Miinto, also used to match the product on an order with an existing product on ChannelEngine. If this ID is not provided by Miinto, ChannelEngine automatically rejects the transfer.

2. The Miinto item ID is provided, but ChannelEngine cannot find the matching product.

   When exporting products to Miinto, ChannelEngine frequently requests the status of a product/offer on Miinto. If it is published, ChannelEngine gets the corresponding Miinto item ID and stores in ChannelEngine's database under Listed products. However, if the Miinto item ID is not found under the Listed products section for that Miinto channel, ChannelEngine cannot connect the transfer to the correct product – and the transfer is automatically rejected.

3. There is a Miinto item ID and a matching product was found, but there is no last exported price.

   While the transfer system Miinto uses is great for buyers, the downside is that transfers are not unique to each merchant. On other marketplaces, you set the price and discounts, and that is what the buyer pays and you receive from the marketplace – minus the related fees. However, on Miinto you can get a sale from a different boutique for a different, perhaps lower price. Without a reference price exported, ChannelEngine's system cannot verify if the price is acceptable. Hence the automatic rejection.

4. The selling price listed on the transfer is lower than the exported price, minus the threshold.

   
   This is the most common rejection reason. Due to Miinto's transfer system, the offered price on the transfer can be lower than the last exported selling price – minus a configurable threshold percentage, which by default is 0%. If this is the case, the transfer is also rejected.

Setting the threshold

It is possible to add a threshold percentage to indicate if the offered price on a transfer is lower than the last exported price. To do so, go to the Setup tab of the channel.

There you can see a field labelled Percentage threshold for transfers. By assigning a value to it, say 20%, you can lower the minimum price at which the transfer is accepted.

Is there a manual transfer override?

Miinto fines merchants who reject too many transfers, a plausible solution could be to not reject or accept any transfers automatically – letting merchants handle them manually. However, there is only a limited window during which a transfer can be accepted: 24 hours, after this period the transfer is automatically rejected.

This would mean that someone with access to your account would have to manually accept or reject transfers 24/7, 365 days/year.

Because ChannelEngine is all about automating as many tasks as possible, the above scenario is not desirable. If too many of your transfers are automatically rejected, please contact your customer success manager or the Support team.