Publishing one product to a marketplace is not a complicated set of steps: open the publish entry, pick images, fill the title, fill the price, choose a category, and submit. The hard part is the number of phones.
In that case the customer had ten phones, each one an account or a category. Doing the bulk listing by hand ran into three things at once. You cannot remember which phone is in what state, which app is installed, or where the last run stopped. The task has to be tapped through one phone at a time, and by the eighth phone you have already forgotten whether the first one went out. When something goes wrong, you do not know which phone it was or which step it stuck on. You have to flip through the screens one by one.
So manage the devices first, then send the tasks, and only then worry about the content of the flow. What follows uses iEasyRun. It runs on your own computer, Android, iOS, and HarmonyOS all work, and many phones are managed in one place.
Four steps on the device page
Install the workstation and the phone-side program for each phone using the install selection page, then open the Devices page. Bulk listing starts here.
Do not reverse the order:
- Scan. Tap scan, or wait for the system to find them. Phones on USB and phones on WiFi show up in the results.
- Add them. Put the phones you will use into the list. Only a phone that has been added can be chosen reliably by conversation, workflows, and scheduled tasks.
- Set an alias. Give each phone a name you recognize at a glance, such as “electronics-01” or “apparel-02”.
- Group them. Group by category, use, or account type.
Most people do the first three. The alias is the one most often left blank. With five phones or fewer you can still rely on memory. Past five, ticking a column of random device numbers is easy to get wrong and easy to miss one. The alias is for the person looking at the list. It decides how fast you pick a device, and whether you pick the right one.
| Action on the device page | What it mainly solves | What happens if you skip it |
|---|---|---|
| Scan | Lets the workstation find the phone | The phone never appears in the list |
| Add | Lets the phone be chosen by a task | Conversation and workflows cannot select this device |
| Alias | Lets a person recognize which phone it is | With many phones it is easy to pick the wrong one or miss one |
| Group | Gives a batch task a clear set of targets | Every dispatch means ticking phones one by one again |
A group is the set of targets for a batch task. Once the phones are split into “electronics”, “apparel”, and “home”, an electronics listing selects the electronics group. You do not tick through a dozen phones, and you are less likely to leave one out.
Buy a new phone, add it, and put it in “electronics”. Later tasks sent to the electronics group cover it. You do not go back and change the task setup.
Grouping also decides what an external AI can look up. iEasyRun’s local MCP exposes the workstation to clients such as Cursor and WorkBuddy. The device query tools are list_devices (phones that have been added and synced), list_device_groups (the groups, including the ungrouped set), and list_devices_by_groups (phones by group). Those are queries. They show what the devices look like now. Taps and running a flow still happen in iEasyRun’s conversation or workflow. Details are in the local MCP docs.
Get one run working, then dispatch by group
Dispatch has two stages. Do not skip the first.
On the conversation page, pick one online phone and describe the full listing flow in plain language, and confirm the AI can do it correctly on a real phone. When the request is vague, switch to refinement, fill in the order, the boundaries, and what to do when something goes wrong, then switch to execute and send it. Once it runs, save that description on the prompts page.
Then create a template on the workflows page. Arrange the steps on the canvas, use validate to check connections and parameters, and use layout to tidy the canvas. When the steps are not enough, AI workflow collaboration can generate or change them. Leave the parts that change each time, such as title, price, and image index, as parameters.
Last, choose the target devices. Choose by group, cover every online phone in the group at once, and each phone runs the same template on its own. Test-run on one phone first. Once that is right, send it to the whole group.
| Stage | What you use | What it mainly does |
|---|---|---|
| Get the flow working | Conversation / refinement | Check that the AI can do it correctly on a real phone |
| Keep the description | Prompts | Save a task description you can reuse |
| Fix the template | Workflow canvas | Steps, parameters, validation, layout |
| Dispatch in bulk | Workflow plus device group | Cover several phones in the group at once |
| Check | Test run | The last check before you use it for real |
An offline device can be viewed and cannot be run. Conversation, workflows, and scheduled tasks will not execute on an offline phone. They do not queue and wait, and they do not retry on their own.
Offline usually comes down to these, in this order:
- On a cable, the USB connection is loose or the cable is bad
- On wireless, the phone and the computer are not on the same WiFi
- The program on the phone is not running
- The workstation is in a bad state, or it is not open
The list may show twenty phones at dispatch time while only fifteen are online. The other five never receive the task, and the screen does not report an error. Look at the online state on the device page before you send. That is less work than hunting through Execution History afterward.
Execution History and schedules
After the task goes out, you do not have to watch the screen. Check Execution History. Each record has the task source (a conversation, a scheduled task, a workflow test run, and so on), the status, the target device, and the error. With many devices, filter by target device. That shows which phone had the problem, which a batch-level status leaves out.
The words in an error line up with an action, roughly:
- “Automation environment” means go back to the install page and check the phone-side setup
- “Device offline” means go back to the device page and match the status, using the list above
- “Unauthorized” or “expired” means look at the template state in the workflow library
- An image-find or recognition failure means add an image template, capture the hard-to-recognize icon into the library, and write down how to use it
Once the flow is stable, fix it in place with Schedule. Bulk listing uses a workflow schedule: choose the template and the target group, set the time, and at that time it runs on the phones in the group that are online. Three conditions: the workstation on the computer stays open (scheduling is local, there is no cloud); the target phones are online, or can connect when the time comes; for a phone on USB, the cable is still there at that moment.
Scanning, adding, aliases, and groups on the device page are how you know which phones you have and which group they are in. Conversation and workflows are how the work gets done correctly and how it gets repeated. Execution History is how you see where this run failed.
Connect one phone and get one listing flow running, then add phones to the group one by one. The install steps are on the install selection page.
Frequently asked questions
- What is bulk e-commerce listing in this context?
- It means taking one product listing routine and running it across several phones in one dispatch, instead of opening each app by hand on each device. It is for listing your own catalog items.
- How many phones can one workstation manage?
- iEasyRun manages multiple devices together and supports Android, iOS and HarmonyOS. Start with one or two devices, confirm the workflow is stable, and add more once it runs cleanly.
- Why should I create device groups if I only have a few phones?
- Groups are the dispatch unit. Naming a group such as shop-a-android or test-run lets a batch task target exactly the right devices, and keeps a test phone out of a production run.
- Why will a batch task not start on one of my phones?
- The most common cause is an offline device. An offline device is visible in the list but cannot run tasks, so it will be skipped or fail. Bring it online before dispatching again.
- Does the workstation need a server or cloud account?
- No. The software runs locally on your own computer, with no server required. Device lists, workflows and execution records stay on that machine.
- How do I track progress across many devices at once?
- Use execution history. Each run records its result and any error per device, so you can see which phones finished and which stalled, instead of guessing from the screen.
- Can a batch task run on a schedule?
- Yes. Scheduled tasks are dispatched locally by your workstation, so the computer must stay on, and each target device must be online or able to reconnect at the scheduled time.
- Do I need to write a script for every phone?
- No. You build the listing routine once in conversation or on the workflow canvas, then dispatch it to a group. There is no per-device scripting.
Get Started
Run One Listing Routine Across Every Phone
Software is completely free and runs on your own computer. Onboard one device, then add the rest.