Jushuitan (JST) Stockout & Inventory Reports, Exported Daily
Export the stockout and inventory reports for every shop in your Jushuitan ERP each morning, confirmed on disk and filed by shop and date.
- Jushuitan ENT (Requires Enterprise Operator Build)
- ERP
- Multi-shop
Business Pain Point
What slows your team down today
Every shop is a separate export
The stockout report is exported shop by shop. Operations staff repeat the same filter, click and save for each store before the morning meeting.
Nested iframes throw clicks off target
ERP screens sit several iframes deep. A click aimed by a resolver that forgets a frame’s padding lands a few pixels away, often on the wrong control.
Slow networks leave half-finished files
Over a proxy or a busy office line a report can stall mid-download. Without a check, a partial file is merged as if it were complete.
Operun Advantage
Why the Operun kernel gets it right
Frame offsets measured, not guessed
physical_click adds every frame’s outer edge, its border (clientLeft) and its computed padding, so the click lands at the control’s true centre.
Background-window clicks
Before a click the tab is selected in its own window and verified active; the window is not raised, so the operator keeps working in front.
Native download guard
wait_download_finish succeeds only when chrome.downloads reports complete. An interrupted or timed-out file fails the step and is never filed.
- 01
Load the shop list
Upload the shop list, pick the report types and the output folder.
- 02
Open the report screen
Operun opens the Jushuitan report page in your signed-in browser and reads the report frame with a snapshot.
- 03
Click export inside the frame
A physical click, aimed through every iframe offset, starts the export while the window stays in the background.
- 04
Confirm and file
wait_download_finish confirms the file is complete; it is filed by shop and date and merged into the daily summary.
Run It Yourself
The Operun commands behind this playbook
Runs on: Enterprise Operator Edition.
# Operator Edition required for physical_click
operun browser snapshot --tab 14 --frame "iframe#report-frame"
operun browser act --action physical_click --tab 14 \
--selector "iframe#report-frame >>> button.export"
operun browser act --action wait_download_finish --timeout 90000 [
{ "action": "physical_click",
"selector": "iframe#report-frame >>> button.export" },
{ "action": "wait_download_finish",
"file_pattern": "*.xlsx", "timeout": 90000 }
] Run this only on Jushuitan accounts you own or are authorized to operate. Operun drives your own signed-in browser; credentials stay in local memory.
Input / Output Artifacts
What goes in, what comes out
Inputs
-
Shop list
CSV — shop name, Jushuitan shop code
-
Report types
Stockout, inventory, or both
-
Output folder
Local folder or NAS path, one sub-folder per day
Deliverables
-
Per-shop reports
XLSX exactly as Jushuitan exports them
-
Daily stockout summary
XLSX — SKU, shop, shortfall, merged across shops
-
Run log
CSV — shop, report, file name, download time, status
ROI Impact
Measured in hours, not promises
0
manual exports before the morning meeting
100%
of files confirmed complete before merge
< 15 min
from first shop to daily summary
Typical results from production engagements; your outcome depends on store count and workflow scope.
See this playbook run on your stack
Book a live demo and watch Operun execute jushuitan (jst) stockout & inventory reports, exported daily inside your real workflow.
Book a Demo Get Pro with Operator EditionRequires Enterprise Operator Edition.