For brands on a custom eComm, we recommend the following process for adjusting commission payments based on returns.
1) 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.
2) File Requirements
Standard Fields
LoudCrowd required | Client to complete mapped field name |
Original order number |
|
Date purchased on web ISO 8601 |
|
Date returned to store or web ISO 8601 |
|
SKU returned |
|
Qty returned |
|
Amount returned |
|
Currency |
|
Return Transaction number (unique) |
|
Tax Return |
|
Recommended file type: The file is a SKU level file. It is a csv or tsv file and the file name will be something like “&brand_name._W2S_Loudcrowd_20240327.csv”.
For clients with physical stores: We recommend an additional field to avoid duplicate returns (between online and physical stores).
3) Dropping the file
In order to drop files to our SFTP server, the connection has the following requirements:
Your server host's public SSH key (in the form RSA, ECDSA, or ED25519) OR the password you received from LoudCrowd
The file will need to be dropped into a directory named
/refund_line_itemsFile should be a .csv or .tsv file
4) 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: To be determined by your brand's encryption requirements. This is an optional level of security on top of the out of the box encryption standards provided by SFTP.