Return File Processing for Commissions Adjustments
Client guide for sending LoudCrowd returns data to avoid paying commissions on returned products.
For brands on a custom eComm, we recommend the following process for adjusting commission payments based on returns.
File Transfer Process
- LoudCrowd will host an SFTP server
- Client will provide an SSH Public key for authenticating to server
- Client will drop return files on a monthly, weekly, or daily cadence to be agreed upon between LoudCrowd and client (to ensure timing will match payouts).
- LoudCrowd will process returns on that cadence. LoudCrowd will deduct commissions for any returns before the active commissions payment window is closed.
File Requirements
Standard Fields
| LoudCrowd Required | Client to complete mapped field name |
|---|---|
| Original order number | |
| Date purchased on web | |
| Date returned to store or web | |
| SKU returned | |
| Qty returned | |
| Amount returned | |
| Currency | |
| Return Transaction number (unique) |
- Recommended file type: The file is a SKU-level file. It is a tab-delimited txt file, and the file name will be something like &brand_name._W2S_Loudcrowd_20240327.txt.
- For clients with physical stores: We recommend an additional field to avoid duplicate returns (between online and physical stores).
Security Requirements
- Encryption: FTP Protocol tunneled over an SSH Connection (SFTP). SFTP Server hosted by AWS Transfer family.
- Authentication: we accept SSH Public keys in the form RSA, ECDSA, and ED25519
- File level encryption: Your brand's encryption requirements will determine this. This is an optional level of security on top of the out-of-the-box encryption standards SFTP provides.
Updated 6 months ago