The year before last, a friend who sells second-hand electronic accessories came to me. He had three eBay accounts, and the same batch of stock had to go on all three.
He prepared a batch first, about twenty items, shot the photos, and wrote the titles and descriptions. Then he opened the first account and listed them one by one. After those twenty, he switched to the second account and listed twenty more, then the third.
One batch took over two hours. Two batches a week, five hours.
I asked whether the three accounts listed exactly the same things. He said not quite. The dispatch location and the returns policy were different, and the prices differed a little, because he wanted to test different pricing.
The same batch of items has to go through each account once. The item and the account have to line up. That is a different job from running a single account.
Split the item from the account
If you only speed up the listing action, what you end up with is often still walking through each account by hand. Split the two sides first.
On the item side are the title, description, price, condition, and images: the properties of each item. On the account side are the shipping method, returns policy, payment method, and dispatch location. Those are basically fixed for one account.
That pile of account fields may not change for years on one account. Hard-code them into that account’s template, so you do not rethink them on every listing. What is left to manage is the item. Each item is different, so make those parameters.
| Field | Travels with | How to handle it |
|---|---|---|
| Shipping method | Account | Hard-coded in the template |
| Returns policy | Account | Hard-coded in the template |
| Payment method | Account | Hard-coded in the template |
| Dispatch location | Account | Hard-coded in the template |
| Title / description | Item | Parameter |
| Price | Item (may differ between accounts) | Parameter |
| Condition | Item | Parameter |
| Images | Item | Parameter |
One workflow per account. The parameters stay on the item side.
Expand the table as item times account
One row per item does not show which account still has not been listed. One row per item-and-account combination does.
| Account | Item | Title | Price | Condition | Image index | State |
|---|---|---|---|---|---|---|
| Account A | Bluetooth earbuds | … | 12.99 | Used, good | 001 | Listed |
| Account B | Bluetooth earbuds | … | 13.49 | Used, good | 001 | Listed |
| Account C | Bluetooth earbuds | … | 12.99 | Used, good | 001 | Pending |
Twenty items and three accounts is sixty rows in theory. If the table has only forty rows, twenty combinations are still undone.
If you only list one account today, filter to that account’s rows. You do not have to split the batch again in your head.
Repricing and restocking can hook on as well. Price is already split by account, so the later repricing flow takes this table as its input.
Images follow the item. One image works for all three accounts. You do not prepare it again for each account. Use the workstation’s file distribution to push the images in bulk into each phone’s photo library. Two limits: push in batches, not all at once; on an iPhone, turn on photo library permission first, or the files arrive and still cannot be saved into the library.
Do not write the titles and descriptions of the three accounts word for word the same. Reusing images is fine. Identical text looks like one seller bulk-listing, and the accounts can get linked. Change the wording a little and shift the order of the main details. That is enough.
How to describe the listing, then attach repricing and restocking
On the conversation page, select the phone for one account, switch to refinement, and describe the whole listing flow:
Open eBay, go to the selling entry, choose the images I specify from the photo library, set the title to the text I give you, set the price to the number I give you, set the condition to used good, set the description to the content I give you, set shipping to this account’s default, leave the returns policy as the default, and stop in front of the submit button. Do not submit yet.
Leave a person to confirm the first time. Listing is public. A wrong listing has to come down and be done again, which costs more than one extra tap.
Once it runs cleanly, save this bulk product publish as that account’s workflow. Copy it, change the fixed fields that belong to the account, and you have templates for the second and third accounts.
This friend later found that what took time every day was repricing and restocking. Listing only happens on the batch that has new products. Repricing and restocking have to be looked at every day: which prices got pushed down, and which stock is nearly gone.
Those two repeat more than listing, and the rules are clearer. Restocking: if a SKU is below a threshold, add quantity, and the amount added is fixed. Repricing: if the price falls below a line, move it back, and how far is a rule.
The same logic, run once a day instead of once a week, saves on the order of ten times as much time.
The data comes from that table. Write the threshold and the size of the adjustment as parameters. The flow does the work. You still set the prices. The tool repeats the rules you set.
Put a floor and a ceiling on repricing. It can only move inside a range, and if a step would go outside that range it stops and alerts you. Otherwise one bad rule can send a whole batch of prices off.
How far this approach goes
It covers consistency and coverage: the same batch reaches every account, fields are not filled in wrong, and prices follow the rules you set.
It does not cover choosing products or setting prices. Whether this stock is worth listing on three accounts, whether the three accounts should be priced differently, and when something should come down: those are business calls.
The friend who sells electronic accessories now runs three accounts from one table. Items are expanded by combination, and prices are filled in separate columns. Listing went from over two hours to half an hour, and most of that time is checking Execution History. He said it used to be that this batch still had to be listed twice more. Now it is filling in the rows for these accounts and tapping once.
Get one account running first, then copy it to the other two. The fields on the account side do not need changing every time. The install steps are on the install selection page.
Frequently asked questions
- What makes eBay listing harder than most platforms?
- The number of fields, and the way they cluster. Basics, shipping options, returns policy, payment methods, condition: several groups, fifteen to twenty fields in total. Domestic Chinese platforms usually need about half. More fields means a higher chance of a human error.
- What is the core difficulty with several accounts?
- One-to-many. The same batch has to be listed separately on each account, and shipping, returns and pricing policy can differ between them. So the problem is not making the listing action faster, it is keeping the item and account dimensions aligned.
- Which fields travel with the account and which with the item?
- Shipping method, returns policy, payment method and dispatch location travel with the account, and are fixed for months, so hard-code them into that account template. Title, description, price, condition and images travel with the item, and become parameters.
- How should the table be shaped?
- Expand it to item times account, one row per combination rather than one row per item. That way you can see at a glance which items have not gone to which account, and control the rhythm per account. One extra column saves a lot of reconciliation later.
- Reusing the same images across accounts, is that a problem?
- Reusing product images across accounts is normal. What to avoid is identical titles and descriptions, because that reads as one seller bulk-listing and invites account association. Rewording slightly costs almost nothing.
- What else is worth doing after listing?
- Repricing and restocking. Both repeat more often than listing, since listing only happens with new stock while those two are daily. Wiring them up after listing pays back more than listing itself.
- How should devices be arranged for several accounts?
- One account per phone, aliased with the account name, grouped by marketplace or category. At dispatch time, choosing a device means choosing an account, so one decision disappears.
- How do I confirm an item really reached every account?
- From the table, not from memory. Reconcile Execution History after each run and mark both successes and failures back into the table. Fixing the mismatched rows is much faster than opening each account in turn.
Hand over the repeats
Prepare the item once, let each account run its own flow
Software is completely free and runs on your own computer.