What causes a duplicate key sale?
| Cause | How it happens |
|---|---|
| The key is in two places | It sits in a file and in a listing, or in two listings, and each one sells it. |
| A batch was loaded twice | The same file is added again a week later. |
| Two people, one file | Both copy the same unused key before either marks it. |
| The source sent it twice | The key was already a duplicate when you bought it. |
Why does a buyer say a key is invalid?
There are four usual reasons. The key was already redeemed before it reached you. The key is for a different region or platform than the listing says. The buyer typed it wrong or tried it on the wrong account. Or the key was revoked at its source after the sale.
Only the first and last are about the key itself. The middle two are about the listing and the buyer, and they are the quickest to settle.
What should I do when a complaint arrives?
Work in this order. First, open the order and read which key was sent, and when. In Keysender that is in the log for the order. Second, search for that key in your other orders. If it shows on two orders, it is a duplicate and one buyer needs a new key. Third, if it shows on one order only, check the listing's region and platform against the key, then ask your source whether the key was used or revoked.
Then answer through the marketplace's own complaint flow, inside the time it allows. Each marketplace has its own steps and deadlines, so follow its seller terms. Send what you found: the key, the delivery time and your supplier's reply.
What does one bad key cost?
More than the key. Here is an example with a key you bought for $18 and sold for $20.
The second delivery is one more dispatch, so it uses 1 credit. The marketplace's fee on the first sale is on top of that. See the marketplace's fee page.
How do I keep duplicates out of my stock?
Keep each key in one place. In Keysender your keys sit in one stock pool, and a key is taken from that one place when it is delivered. No listing holds its own copy.
Load every batch through bulk import. The import takes a CSV or XLSX file, removes duplicate rows and reports an error for each row it could not load. That check runs when you import, not when a key is delivered, so the import is where to catch a repeated key. If your source sent you a key that was used before you got it, no import can see that. Buy from sources that replace bad keys, and keep the invoice.
What record should I keep?
For every order: the key sent, the time, and the channel. For every batch: the source, the date and the cost. Keysender keeps the first part for you, with a log on each order, and bulk import has columns for cost and supplier. With both, a complaint takes minutes to answer.
Quick answers
What is a duplicate key?
One key delivered to two buyers. Only the first buyer to redeem it gets the product.
How do I prove which key I sent?
Open the order's log. It shows what was sent and when.
Does Keysender check my file for duplicates?
Bulk import removes duplicate rows and reports errors row by row. Duplicates can still reach you from a source, so keep your purchase records.
Who decides a complaint on a marketplace?
The marketplace, under its own rules. Answer inside its complaint flow with your record.