As a platform, 35up connects distributors (vendors) to customers on third-party websites (sellers). The vendors provide the supply of cross-selling products that their customers demand.
Once a sellers' customer purchases a product, 35up will receive the order and pass it on to the vendor. The vendor will then drop-ship the products to the end customer.
We include only large-scale vendors with drop-shipping capabilities on our platform, to ensure a fast and high-quality delivery and product experience for the end customer.
There are two ways to get integrated. For large scale operations or those that require real time order placement, 35up build a proprietary vendor service. For all others, we offer dedicated SFTP servers and a csv integration.
To include the vendor's products, 35up will build a proprietary interface to load the vendor’s product feed onto the platform. The product feed can be based on an API, an XML, and EDI, or a CSV/TXT file.
Whatever the format, the feed needs to provide this basic information about each and every product:
To enable 35up to recommend your products to larger enterprises running SAP, in addition, following information should be provided:
Any additional information is welcomed and used internally.
To ensure a great customer experience, all vendors must ensure delivery within two to three business days via drop-ship to the end customer.
Our sellers provide our customers a 14-day return-without-a-reason policy. The vendor therefore must accept returns and fully refund the seller. However, they can charge a return fee.
Because 35up builds a proprietary interface for every vendor, we can work with every format available (API, XML, EDI, csv, txt).
However, the vendor’s order interface has to accept and process the following information, so that orders can be processed:
Moreover, 35up requires a reference order number and a process to receive order status updates from the vendor.
As it does for other interfaces, 35up builds a proprietary solution to connect to the vendor’s return services.
To process returns, it is necessary to follow interactions. In case a vendor cannot provide an automated interface, 35up will store respective information in an available space and in a structured way.
If a seller requests a return and the customer ships it back to the vendor, the vendor has to mark the item as arrived, and — if it was returned without reason — assess whether the product is damaged in any way. The confirmation can be done either through the 35up admin interface, or the vendor’s interface (if available), based on:
To ease the process, 35up provides the seller a return label barcode with both sets of information.
If the product never reaches the customer, or if the customer sends the item back without notifying 35up or the seller, the vendor has to create a return and assess any potential product damage.
The confirmation can be done either through the 35up admin interface, or the vendor’s interface (if available), based on:
To include the vendor's products, 35up will provide an SFTP server for the vendor. On this server, the vendor has to upload a product catalog csv file, including all product information availability quantities. The file has to be update regularly, to ensure no out of stock products are listed.
The structure of the csv file is flexible, however, following information need to be provided.
To enable 35up to recommend your products to larger enterprises running SAP, in addition, following information should be provided:
Any additional information is welcomed and used internally.
To transfer the orders back to the vendor, a daily orders.csv is generated and uploaded to the dedicated SFTP server. The vendor has to download and process the file, and move it to an archives folder. The order file includes the timestamp and is unique.
The file contains following columns, including header:
In case a customer orders more than one different item, multiple lines will be generated within the file.
To transfer the shipment status back to 35up, a daily shipments.csv needs to be generated and uploaded to the dedicated SFTP server by the vendor. The file name should include a timestamp and be unique.
The file must contain following columns, including header:
The csv file should provide one line per item_id and order_id
To transfer the return status back to 35up, a daily returns.csv needs to be generated and uploaded to the dedicated SFTP server by the vendor. The file name should include timestamp and be unique.
The file must contain following columns, including header:
The csv file should provide one line per item_id and order_id
To transfer the cancellation status back to 35up, a daily cancellations.csv needs to be generated and uploaded to the dedicated SFTP server by the vendor. The file name should include timestamp and be unique.
The file must contain following columns, including header:
The csv file should provide one line per item_id and order_id