Vendor Concept

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.


Order and Payment Flow

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.

Vendor Integration

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.


Product Feed

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:

  • Product ID (SKU): A unique identifier of the product
  • Product name 
  • Short description: A one-line description about the product
  • Long description: A multi-line description about the product, with more details
  • Thumbnail image: At least one image that can be used as a thumbnail
  • Recommended seller price: A recommended price for the product
  • Shipping price: Cost to ship the item
  • Return price: Additional costs in case the item is returned (does not include return shipping prices)
  • Purchase price: The price 35up pays the vendor
  • Availability: Is your product currently on stock

To enable 35up to recommend your products to larger enterprises running SAP, in addition, following information should be provided:

  • GTIN/EAN: A global unique identifier of the product
  • Width: Width of the product (with and without packaging)
  • Height: Height of the product (with and without packaging)
  • Length: Length of the product (with and without packaging)
  • Weight: Weight of the product (with and without packaging)
  • Materials: List of materials of the products
  • Color: The main color of the product

Any additional information is welcomed and used internally.


Delivery and Returns

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.


Order Interface

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:

  • Customer’s first and last name
  • Additional address field
  • Shipping street
  • Shipping zip code
  • Shipping city
  • Shipping state and country
  • Order number
  • Customer's email address
  • SKU of product ordered
  • Quantity of product ordered

Moreover, 35up requires a reference order number and a process to receive order status updates from the vendor.


Return Flow

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.

Confirm Returns

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:

  • 35up order ID
  • Vendor reference ID (if passed on via order interface)

To ease the process, 35up provides the seller a return label barcode with both sets of information.

Create Returns

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:

  • 35up order ID
  • Vendor reference ID (if passed on via order interface)

Product Feed

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.

  • Product ID (SKU): A unique identifier of the product
  • Product name 
  • Short description: A one-line description about the product
  • Long description: A multi-line description about the product, with more details
  • Thumbnail image: At least one image that can be used as a thumbnail
  • Recommended seller price: A recommended price for the product
  • Shipping price: Cost to ship the item
  • Return price: Additional costs in case the item is returned (does not include return shipping prices)
  • Purchase price: The price 35up pays the vendor
  • Availability: Is your product currently on stock

To enable 35up to recommend your products to larger enterprises running SAP, in addition, following information should be provided:

  • GTIN/EAN: A global unique identifier of the product
  • Width: Width of the product (with and without packaging)
  • Height: Height of the product (with and without packaging)
  • Length: Length of the product (with and without packaging)
  • Weight: Weight of the product (with and without packaging)
  • Materials: List of materials of the products
  • Color: The main color of the product

Any additional information is welcomed and used internally.


Order File

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:

  • order_id: The 35up internal identifier of the order. This one has to be passed throughout all communication
  • item_id: The 35up internal identifier of the order item. This one has to be passed throughout all communication
  • item_sku: The vendor SKU for the item bought
  • item_qty: The qty of the item bought
  • shipping_first_name: First name of the shipping address of the end customer
  • shipping_last_name: Last name of the shipping address of the end customer
  • shipping_company: (optional) Company name of the shipping address of the end customer
  • shipping_extra: Additional line of the shipping address of the end customer
  • shipping_street_name: (optional - either street name and number or line) Street name of the shipping address of the end customer
  • shipping_street_number: (optional - either street name and number or line) Street number of the shipping address of the end customer
  • shipping_street_line: (optional - either street name and number or line) Street name and number of the shipping address of the end customer
  • shipping_city: City of the shipping address of the end customer
  • shipping_state: (optional) 2 digit (ISO 3166-1 alpha-2) state code of the shipping address of the end customer
  • shipping_country_code: 2 digit (ISO 3166-1 alpha-2) country code of the shipping address of the end customer
  • shipping_postcode: Post code of the shipping address of the end customer

In case a customer orders more than one different item, multiple lines will be generated within the file.

Example file download

Shipment 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:

  • shipment_id: Id of the shipment to clarify if an shipment included more than one item
  • order_id: 35up order id from the orders.csv
  • item_id: 35up item id from the orders.csv
  • item_sku: Vendor SKU
  • shipped_qty: Quantity shipped of that item
  • shipped_at: Date and time the shipment was made in UNIX timestamp
  • shipping_provider: (optional) Which shipping provider is used
  • shipping_method: (optional) Which shipping method is used
  • tracking_code: (optional) Tracking code of shipment
  • tracking_url (optional) Tracking url of shipment

The csv file should provide one line per item_id and order_id

Example file download

Return File

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:

  • order_id: 35up order id from the orders.csv
  • item_id: 35up item id from the orders.csv
  • item_sku: Vendor SKU
  • returned_qty: Quantity shipped of that item
  • received_at: Date and time the return was received in UNIX timestamp
  • status: (optional) Either "vendor_received" to mark that return was received or "confirmed" to mark that return was received and accepted. Default is "confirmed"
  • message (optional) Message with more details on the return

The csv file should provide one line per item_id and order_id

Example file download

Cancellation File

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:

  • order_id: 35up order id from the orders.csv
  • item_id: 35up item id from the orders.csv
  • item_sku: Vendor SKU
  • cancelled_qty: Quantity cancelled of that item
  • message: (optional) a message explaining the reason for the cancellation

The csv file should provide one line per item_id and order_id

Example file download