Twelve listings, one afternoon, and the “still available” queue
A seller I know runs his Facebook marketing almost entirely through Facebook Marketplace listings rather than a page, across two dozen accounts for outdoor gear, mostly second-hand and clearance stock. Second-hand ecommerce looks simple and turns out to be all detail work.
His day looks like this. Two hours in the morning loading the day’s stock: twelve or thirteen items, each needing a title, description, price, condition and pickup method, plus three images. Halfway through, the phone starts. Yesterday’s listings are drawing messages.
He cannot answer while listing and cannot list while answering. By two in the afternoon the listings are up and forty-something messages are waiting, half of them asking the same thing and the rest asking for a discount.
“I don’t mind listing,” he said. “What I mind is going back afterwards. Which of yesterday’s sold, which ones need reposting. I always forget.”
Marketplace is not a page post
Many people treat Marketplace as another Facebook publishing channel. The cost structure is completely different.
A page post costs content production: what to say today, how to make the image, how to write it. Once it is out, it needs no attention.
Marketplace costs running two lines at once. Listing is one. Answering messages is the other. Goods go up and people start asking, always the same three things. Both lines have to run simultaneously, because a buyer’s patience is measured in hours.
That is where his throughput gets stuck. Not one slow task, but two tasks interrupting each other.
Staging bulk listings
Bulk listing splits into prep and upload. The cost of a product page sits in getting the assets right, not in the taps.
Prep happens the evening before. Product name, description, price, condition, pickup location and three images, all into one sheet. This is faster on a computer than a phone, and the next day involves no hunting for assets.
Upload happens in the morning. Twenty-odd accounts do not all carry the same batch. Within one city, one account is enough; multiple accounts only pay off across regions. So the right move is grouping accounts by region, each listing its own area.
After grouping, upload becomes “dispatch this batch to this group”. Which group went wrong and which device stalled become visible at a glance.
One step is worth keeping: run two or three accounts first. He went straight to twenty the first time and discovered one account had the wrong pickup location, putting twenty listings in the neighbouring city. Test two or three, confirm the flow, then widen. Multi-account operations punish that kind of mistake with twenty identical copies of it.
Triaging enquiries
He counted: over half his messages are still available, can you go lower, and can you ship it.
What those share is that the answer is fixed and needs no judgement. Still available is yes or already sold. Can you ship is yes with a shipping figure, or pickup only. A machine handles those more consistently than a person, because a person answering for the twentieth time gets tired and starts making mistakes.
The remaining minority is where the real talking happens: negotiating, asking for details, arranging a time. That part needs a human watching the list, sending a prepared line for standard questions and taking the rest personally.
Sold, expired, who clears up
This is the part he forgets most often, and the one most worth automating.
An unsold item left unmarked draws enquiries again the next day. An expired listing that never gets reposted is wasted, and Marketplace listings do expire.
The fix is simple: a scheduled sweep at a fixed hour, say ten at night, working through the accounts due that day. Mark sold items, repost expired ones, and take down anything under negotiation.
That third step is easily missed and saves the most. An item stays visible while you negotiate, keeps drawing enquiries, and you explain the same thing repeatedly. Pull it down, handle it when the deal closes.
Where iEasyRun fits
Everything above is daily work with a fixed flow, which is what an iOS cluster control setup is for.
He then ran into a different category: a quarterly clearance audit. Exporting live listings from two dozen accounts and reconciling them against physical stock, looking for items listed with none left and items in stock with no listing. It happens once a quarter, and writing iOS automation scripts for it does not pay.
That work went to iEasyRun. No script: describe the job and it works from the screen. One-off work with a shifting flow is far cheaper to describe.
The split now is: daily listings, enquiry replies and the evening sweep run on iOS cluster control; the quarterly audit, or a sudden urge to see what competitors charge, becomes a sentence to iEasyRun. Facebook automation of this kind runs fine over the no-jailbreak USB HID route, with both tools on the same phones.
Lines worth keeping
Do not relist the same batch repeatedly on one account. Stock that will not move, posted again and again, looks like spam. Delist it, reshoot from a different angle, rewrite the description.
Do not use fixed inquiry replies to chase customers. A machine answers repeated questions. It is not for pestering people who already stopped replying.
Negotiation and after-sales stay human. Both need judgement, and forcing them onto a script pushes buyers away.
Write the description honestly. Condition, flaws, pickup limits, all of it. Marketplace reputation is built on not having to handle returns, and one return gives back the time you saved.
To close
Back to his line about going back afterwards. He now spends twenty minutes in the evening reviewing the sweep: marking sold items, reposting expired ones, confirming tomorrow’s assets. Twenty minutes against the ninety he used to lose.
The time he got back went into regrouping the accounts by region, because he had been listing city-wide from every account and only discovering the distance when a buyer asked. For the wider multi-account picture, see building a Facebook matrix with Apple cluster control; for putting many screens on one display, see iOS no-jailbreak screen mirroring.
About EasyClick: A phone automation AI-agent platform covering Android no-root, iOS no-jailbreak (proxy / Bluetooth HID / OTG HID) and HarmonyOS Next, offering script development, Apple cluster control, local central control & mirroring, and cloud control systems. → Explore all products
Ready to build it for real?
Every approach in this article can be built on the EasyClick phone automation platform — full documentation, developer tools and cluster/cloud-control products, free to try.