Apple cluster control means running many iPhones from one computer: screens viewed together, tasks dispatched by group, results collected in one place.
This one answers: Pinduoduo, Douyin, Tmall With Apple Cluster Control，How.
Zhou sells home and kitchen goods. One Pinduoduo store, two Douyin Shop stores, one Tmall store.
He said something I keep repeating: people assume listing is the hard part, but listing comes in waves. What grinds you down is the dashboards，orders in the morning, orders at noon, orders again at night. Four dashboards, twelve checks a day.
Twelve sounds like nothing. But each one means picking up a phone, unlocking it, switching to that app, opening the order list, reading the statuses, backing out. Two or three minutes a trip, half an hour a day. The half hour is not the problem. The problem is that it cuts your day into twelve pieces.
The four dashboards do the same things
I had him list what he does on each one. The structure came out nearly identical.
Open the app, go to orders, filter by status, look for anything waiting to ship or a refund request, handle it, back out. After-sales is the same idea on a different screen. Stock and price are weekly: delist what sold out, relist what arrived, follow a competitor down.
Different interfaces, same sequence. That is exactly why one set of scripts can cover all four，iOS automation scripts work off positions on the screen, not off the name of the dashboard.
What to hand over and what to keep
Order sweeps, after-sales queues, delisting sold-out items, relisting arrivals and rule-based price changes can all go to scripts.
Two things should not. One is judgement: whether to answer a bad review publicly, whether to follow a price down, whether to open another channel for this batch. The other is conversation. Maybe a fifth of buyer messages actually need thought，but you have to read through them to find that fifth.
My suggestion is to automate the reading first, the writing second. A sweep is read-only; the worst case is missing something. A change that goes wrong touches real orders.
Devices and connections
Four stores means four phones, sitting on a desk, not moving. A data cable is enough: console 10.7.0 or newer with phones on iOS 17 or newer, one cable each. No Bluetooth board, no OTG board, no jailbreak, no signing.
As stores multiply and the phones no longer fit on one desk, look at WiFi. To drop cables entirely, a Bluetooth board (ESP32C3) works; desks too far from the PC are the only real case for an OTG board (ESP32S3, iOS 17 and above only). The question is whether you have a distance problem, not which link is faster.
Past a handful of devices, two physical issues show up first: powered USB hubs, and spacing between phones rather than stacking. Neither is a software problem. Connection options has the detail.
Binding accounts to stores
One store, one device, physically bound.
Some sellers log two or three store accounts into one phone and rotate. At four stores that saves almost nothing, and when one store runs into trouble the others on that device get looked at together. Zhou now runs four phones for four stores, and a problem points straight at its source.
Name devices fully: platform, store, number，something like PDD-home-A-01. The slowest part of multi-dashboard work is not the tapping, it is remembering which phone belongs to which store.
Stagger the dashboards too. Four dashboards moving at the same minute looks like four phones doing one thing. Two in the morning, one at noon, one at night reads more like a shop being run.
How many stores before it pays off
One or two stores by hand is fine. The maths changes around four, when every store needs a look every day.
If you want to test it, run one read-only sweep on one dashboard for a week. That tells you the actual time saved and whether anything gets missed. Then add the other three. Zhou switched all four on at once, had two mis-taps in the first two days, rolled back and added them one at a time，which was faster overall.