Listing and Buyer Messages on Etsy, Run by One Person

Listing is work you batch up. Buyer messages are work that lands on you. Mixed together, the day disappears.

Running Etsy alone · 8 min read
On this page
  1. The two jobs run on opposite rhythms
  2. Turn bulk listing into a template
  3. Draw a line on buyer messages
  4. Several shops, and what this setup leaves alone

Two years ago a friend who makes custom gift cards ran one Etsy shop by herself.

Her day went roughly like this. In the morning she checked buyer messages and replied to the ones from overnight. Then she listed new items. A batch goes up every few days. Halfway through, two more messages came in, so she switched back to reply. When she returned to listing, she had lost the thread. The afternoon went to custom orders, checking what each buyer had written, one by one. In the evening she did another round of messages.

She said listing and replying were each manageable on their own. Doing both, she did neither well. Listing kept stopping halfway, and the replies were not prompt enough.

The two kinds of work were mixed into the same day.

The two jobs run on opposite rhythms

Bulk listing is work you save up and do in a batch. Items do not depend on each other, so working straight through is fastest. Interrupt it once and you have to get back into it.

Buyer messages land whenever they land. They interrupt whatever is in your hands, and they have a time limit. While a buyer is waiting for a reply, they may already be ordering somewhere else.

Mix them into one day and you keep switching. Switching costs more than either job on its own. One interruption during listing can cost ten minutes of getting back into it. Five interruptions in a day and an hour is gone.

So handle them apart. Give the batch work a solid block of time, and hand as much of it as you can to a computer. Look at messages at a few fixed times.

Turn bulk listing into a template

One item takes about ten steps: open Etsy, go to shop manager, tap add a listing, upload photos, fill the title, write the description, set the price, set stock, choose a shipping profile, add tags, publish.

There are not that many fields. The repetition is high and the judgement is low, so it suits a template.

The method is still the same: put the information in a table first, then configure the flow.

Table column In the flow
Title Parameter
Description Parameter
Price Parameter
Stock Parameter
Image index Parameter
Tags Parameter
Shipping profile Hard-coded in the template, per shop

Anything fixed per shop, such as the shipping profile, should stay out of the parameters. A shop can keep the same profile for months. Leaving it as a parameter only means filling it in again before every run.

Prepare the copy in the table in a batch. Writing copy needs a certain state of mind. Writing a whole batch in one sitting is faster than inventing it halfway through a listing.

Describe the flow once on the conversation page. The first time, leave publishing for a person to confirm. Once it runs cleanly, save it as a workflow. After that the job is edit the table and tap once.

Workflow canvas: the listing flow frozen into a template, item information passed in as parameters

Draw a line on buyer messages

These can be templates: where is my parcel, when does it ship, which size should I pick, what is the returns process. The answers are fixed, and a wrong reply is low risk. A message template can close them out directly.

These need a person: disputes, negative feedback, refund complaints, special requests. One wrong sentence in those replies costs more than the time saved.

Custom orders have to be pulled out on their own. When the buyer checks out they write a block of requirements: which font for the name, which colour, what date to engrave, what size. That block belongs to that one order. A person has to read it and check it.

The flow does the first half. It picks out the custom orders and gathers what the buyer wrote into a table. Then a person confirms and replies, line by line. The time spent opening each order goes away. The judgement stays with the person.

Execution History: the result of each run, checked before you go back to the shop and look at the actual state

Once they are split, a day can be arranged like this.

One solid block in the morning for the batch work: listing, restocking, repricing. The templates run it. You prepare the table, tap once, and check the results.

Messages sit in two or three fixed windows, such as once at midday, once in the early evening, and once before bed. Interruptions that used to scatter across the day collapse into a few checks.

Custom orders get their own block: check the requirements, reply to the buyer. Keep that block separate from everything else.

What this arrangement does is bring down the number of times you switch state.

Several shops, and what this setup leaves alone

With more than one shop, keep one shop per phone, set the alias to the shop name, and group by category.

The difference from a single shop is that dispatch location and shipping profile can differ between shops. Hard-code those fields in each shop’s own template. Keep the templates separate.

Device library: one shop bound to one phone, aliased with the shop name

This setup handles execution. It repeats the fixed actions of listing, restocking, and repricing, and it gathers the requirements from custom orders.

Judgement stays with a person: whether the description is appealing enough, how to calm this buyer, whether the custom request contradicts itself.

Hand over what can be a template. Use the time you get back on messages and on improving the listings.

The gift-card maker later turned both listing and restocking into templates. One hour in the morning went to preparing the table, running the tasks, and checking the results. Messages moved to two fixed times, midday and evening. Custom orders kept a whole block just for checking. She said the day used to be busy the whole time. Now the day has two clear sections: the morning does the batches, and the rest of the time deals with people.

If you run Etsy on your own, start from the install selection page, connect one phone, and begin with the listing flow. Once that holds, add restocking and repricing.

Frequently asked questions

Why treat listing and buyer messages as two different jobs?
Their rhythm is opposite. Listing works best in batches, one item after another without interruption. Messages arrive whenever they arrive and have to interrupt. Mixing them means constant switching, and both suffer.
Which one suits a computer better?
Bulk listing. The actions are fixed, nothing needs a live reaction, and it can wait until you have a batch. A good share of buyer messages must be written by a person, especially personalised orders and disputes, where the risk is too high.
How should Etsy personalised orders be handled?
Pull them out separately. Buyers write a block of specific requirements: a name, a colour, a size, a date. That block must be read and checked by a person. Let the flow collect the orders and gather the requirements into a table, but keep confirmation and replies manual.
Is any of the messaging automatable?
Yes, but only standard questions: where is my parcel, when does it ship, which size should I pick, what is the returns process. Fixed answers, low risk. Everything else gets routed to a person by category.
How many steps does one listing take?
Around ten or so: open Etsy, go to shop manager, tap add a listing, upload photos, fill the title, write the description, set the price, set stock, choose a shipping profile, add tags, publish. Not an unusual number of fields, but very repetitive.
How should sellers with several shops arrange it?
One shop per phone, aliased with the shop name, grouped by category. Choosing a device then means choosing a shop. Note that dispatch location and shipping profiles can differ between shops, so those must be hard-coded per template.
What about after listing?
Restocking and repricing. Both repeat more than listing and have clearer rules. Wire them up once the listing flow is stable and the return is larger than listing itself.
How do I know the automated part did not go wrong?
Reconcile Execution History after each run, then check the shop itself. Both agreeing is what counts. Price and stock especially, since a wrong number there leads directly to a complaint.

Move the batch work out first

Template the listing, spend the time saved on messages

Software is completely free and runs on your own computer.