A seller went quiet with twelve open orders

Monday morning, twelve orders

A composite, but a common one. Your support lead flags it first: three buyers have written over the weekend asking where their orders are. All three bought from the same seller, a small ceramics studio that's been on the marketplace for a year and usually ships within two days.

You look. Twelve open orders. None has tracking. The seller last logged in on Tuesday. Your two messages since have gone unanswered, and the phone number on their account goes to voicemail.

Maybe the owner is ill. Maybe there was a family emergency, a kiln fire, a holiday they forgot to mention. You'll find out eventually. The buyers can't wait for eventually. The buyer doesn't care why the seller went quiet. They care whether anyone on your side noticed.

One quick check before anything else: make sure the silence isn't yours. Has your order notification email to this seller started bouncing? Did a payout fail, or did your own fraud rules restrict the account, so they can't see or ship orders? It happens more often than anyone likes to admit, and it changes the conversation completely.

If your side looks fine, don't spend the morning trying to reach the seller. Sort the orders.

Pile one: refund now

Some orders are already past anything you could honestly promise. They were placed ten days ago with a two-day handling time, or the buyer said it was a gift for a date that's now gone.

Refund these today, in full, and say so plainly. Don't wait for the seller to surface and argue. Holding a buyer's money while you investigate someone else's silence is how a delay becomes a complaint about your marketplace instead of about one shop. Tell the buyer, in the same message, what to do if a parcel turns up anyway: keep it, or send it back with a label you provide. Pick one in your terms so support isn't improvising.

How the refund is funded between you and the seller is a separate question, and your seller terms should already answer it. If they don't, that's a gap to close later, not a reason to keep the buyer waiting now.

Pile two: reroute

Some items aren't unique. If another seller on your marketplace sells the same thing, or close enough that the buyer might accept it, you can offer a swap: same item from a different seller, shipped now, or a refund. Let the buyer choose. Never switch the seller without asking; a handmade mug from one studio isn't the same mug from another. If the replacement costs more, decide in advance whether the marketplace covers the difference. Asking the buyer to pay extra for someone else's silence rarely ends well.

Rerouting works only if your catalog knows which listings are equivalent and your systems can move an order between sellers without someone re-keying it. If you can't do that today, you'll do it by hand this time, and you'll know what to build.

Pile three: hold with a deadline

The rest are recent enough that the seller could still ship if they reappear in the next day or two. For these, write to the buyer now, not after they write to you: "The seller hasn't confirmed your order yet. We're contacting them. If it hasn't shipped by Thursday, we'll refund you automatically."

Then honor it. Put the date in your system, not in someone's memory, so Thursday's refunds happen even if the person who wrote the message is out.

One trap to avoid: the seller reappears on Friday, sees twelve orders, and ships all of them, including the ones you already refunded. Mark refunded and rerouted orders as cancelled in the seller's own view, and tell them in the same message that those are closed. Otherwise you pay twice and a buyer gets a parcel they no longer expect.

Meanwhile, pause the seller's listings so new orders stop arriving. A seller who is unreachable shouldn't be collecting more promises.

Build what would have caught it sooner

Once the morning is over, look at why you found out from buyers.

Give sellers an away mode. A simple switch that pauses listings, or extends handling times and shows a return date to buyers, lets a seller who knows they'll be gone say so. Most sellers would rather use it than let orders pile up.

Watch for quiet sellers. You already have the signals: open orders without tracking past the handling time, messages unanswered for a day, no logins. Put them together into an alert that reaches your operations team before it reaches your support inbox.

Decide who decides. Write down who on your team may pause a seller, who approves refunds, and how long you wait before acting. A small rule written in advance beats a debate on Monday.

Keep a second contact. Ask sellers for a backup contact at onboarding: a partner, an employee, an email they check. Make clear it's only used when orders are at risk.

When the seller does come back, have a calm conversation. Show them which orders were refunded, which were rerouted and which they can still ship. Most quiet sellers aren't bad sellers. They just ran out of ways to tell you.

Keep a few dates. You don't need a dashboard for this, but you do need a few dates. When was the first order past its handling time? When did your systems notice? When did a person act? When did each buyer hear from you?

The gap between the first late order and the first message to a buyer is the number worth shrinking. It tells you whether the marketplace is looking after its promises or waiting to be told.

Put this into practice

Look at your open orders right now and filter for any seller with orders past handling time and no activity in the last two days. If that filter doesn't exist, start there. Then check whether your sellers have any way to tell you they'll be away.

We build marketplaces and the operating tools that keep both sides' promises visible. If your team finds out about quiet sellers from buyers, talk to us.

Related work: Paddle8.