E-Commerce Daily Report OSS Upload

Problem

Daily e-commerce reports are often stored in separate local folders, with different file formats and platform-specific rules. Manual uploads can miss nested folders, use the wrong business date, or submit Windows backslash paths that OSS cannot resolve. This skill turns the PDD, Douyin, JD, and Tmall daily report upload process into a repeatable workflow.

How It Works

For PDD, Douyin, and Tmall, the workflow first checks whether all files in the corresponding Desktop folder were modified today. If any file is stale, it stops and prompts the user to update the files. JD skips that date check, extracts ZIP files while preserving the original file names inside the archive, and overwrites existing XLSX outputs. Uploads are keyed by yesterday’s date and keep the original subdirectory structure, such as product, category, and store folders, without changing file formats. Credentials are loaded from the configured OSS_CREDENTIALS.py file. The implementation also needs to handle Windows path separators, converting backslash paths from os.path.relpath() into forward-slash paths for OSS.

Boundaries

This is intended for Windows workstations where daily reports are already saved in the expected local folders. It is not meant for pulling data from platform APIs, cleaning or transforming reports, or building cross-platform analytics. Trigger phrases should identify the platform clearly, such as “process JD data.”