What the data for this category looks like
The profit yield data for the cosmetics category is sourced primarily from internal brand sales ledgers, offline counter POS systems, and transaction backends of mainstream e-commerce platforms. Data updates occur once daily, with full aggregation of the previous day’s data completed in the early morning of the current day. The standard document structure is a two-dimensional table grouped by SKU, with nine fields: SKU code, product name, sales channel, shipment quantity, purchase cost, terminal selling price, return and exchange quantity, single-SKU revenue, and single-SKU total cost. Units for shipment quantity and return and exchange quantity are pieces. Units for purchase cost, terminal selling price, revenue, and total cost are yuan.
Constraints imposed on form and interaction workflows
Scattered data sources and diverse formats for the cosmetics category require the form to support uploading CSV, Excel and other multi-format files, while adapting to differences in field naming exported by different channels. The fixed daily update rhythm requires the form to be configured with scheduled trigger tasks to avoid repeated processing of historical data. Fields include numerical items with multiple unit types, so independent format verification rules must be configured for each field to block non-compliant inputs. The large number of SKUs requires the form to support batch data import instead of single-entry processes, and to provide fuzzy matching verification for SKU codes to avoid duplicate entries. Additionally, profit yield calculation needs to exclude return and exchange orders, so the form must include corresponding data filtering options.
How to configure the settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
UPLOAD_FILE_ALLOWED_EXT | csv, xlsx, xls | The mainstream export formats of cosmetics-related sales data are these three types, covering export files from most channels |
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | When batch SKU data volume is large, full parsing takes a long time. This duration covers parsing needs for most conventional data volumes |
FORM_FIELD_MAPPING_RULE | Auto-match source file header + manual correction | Differences exist in field naming exported by different channels. This configuration balances data import efficiency and field mapping accuracy |
SCHEDULED_TRIGGER_TIME | 02:00 | Cosmetics sales data is usually aggregated for the previous day in the early morning of the current day. Executing tasks at this time obtains complete and non-duplicate daily data |
DATA_FILTER_CONDITION | Only retain records with the status of "valid order" | Excludes interference from return, exchange and refund orders on profit yield calculation to ensure data calculation accuracy |
BATCH_IMPORT_MAX_RECORDS | 5000 rows | Single batch data volume should not be too large. This value avoids excessive system load while ensuring batch import efficiency |
The parameter values given on this page are all conventional recommendations used as a starting point for configuration. Actual values are affected by material form, data volume and business rules. Specific issues require specific analysis. It is recommended to test on your own samples before finalizing the configuration.
Three common mistakes
- Symptom: After uploading a cosmetics sales data file, the interaction form does not load on the conversation interface, and the system returns the error "No valid input fields found". Cause: The allowed file extensions are not configured in the system's "file input" module, or the uploaded file format does not meet the requirements.
- Symptom: The form input component configured in the workflow does not appear in the conversation, and data entry cannot be completed. Cause: The "display as form" switch is not enabled in the "user input" node, or the bound fields are not added to the form configuration.
- Symptom: In the batch imported SKU data, the single-SKU total cost field displays as empty. Cause:
FORM_FIELD_MAPPING_RULEis not configured, and the "purchase cost" field in the source file is not correctly mapped to the system's "single-SKU total cost" field, resulting in missing data.
How to confirm the configuration is complete
- Upload a cosmetics sales data test file that meets the allowed formats, and confirm that the corresponding form interaction controls load on the interface.
- Check the scheduled trigger task time setting to ensure it matches the daily aggregation rhythm of cosmetics sales data.
- Trigger a test run to check whether the parsed data fields are consistent with the configured mapping rules.
- View the system operation logs to confirm that there are no abnormal errors in the file upload, parsing, and form submission links.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.