Audience: URBN suppliers

This page contains documents that are unique for suppliers connecting with URBN on the platform. The documents on this page have been customized for URBN suppliers and should be used during the onboarding process and when receiving live orders.

For questions related to the URBN drop-ship program, please reach out to your brand's URBN merchandising representative.

For onboarding support, please email Rithum's Onboarding team:

For production support, check out the supplier documentation or email the Software Support team

Onboarding with Rithum

To learn more about the onboarding process and your next steps, see:

The Rithum Onboarding team presented region-specific webinars about the overall onboarding process and how to prepare for the upcoming transition.

US Webinar for URBN - August 10, 2023 - (Recording)

 

EU Webinar for URBN - 23 May, 2023 - (Recording)

Onboarding webinar/supplier Q&A

The following document contains questions that were asked during the onboarding webinar that took place on January 24, 2023. Note that some questions will be answered more fully as URBN adds functionality.

URBN onboarding webinar/supplier Q&A

Using advanced catalog services to set up your products

As a supplier, you are required to use advanced catalog services to add all rich item data, including images, for any items you wish to sell on the URBN-owned brand websites. To learn more about advanced catalog services, go to Advanced Catalog Services for Suppliers.

Note: Advanced catalog services is different from the basic Catalog templates that are used to provide product data to your retail partner. For more information about uploading basic Catalog/Inventory templates using the Inventory page, see Creating or Updating Inventory.

Looking for more information on managing your content with advanced catalog services? View and enroll in the Managing Your Content training course in Rithum Learn, which provides interactive, on-demand business and system training.

Using shipping labels

URBN suppliers who are authorized to use UPS shipping labels can easily use the platform to generate these labels to fulfill orders.

Setup

If you would like to use UPS shipping labels, please contact your URBN brand associate to verify:

  • You have a UPS account.
  • Information has been shared with Rithum to authorize your account to use labels.

For additional setup and readiness related questions, you can email the Rithum Onboarding team at dscopartnersetup@rithum.com.

To see detailed steps for creating shipping labels, please see Creating shipping labels for your order.

For more details about using shipping labels, watch the short video below:

Orders Beta Demo

Please be aware, the steps to create a shipping label will effectively close the order. Customer information will be hidden on orders that are 90 days from creation date AND have been closed. If your product has a lead time longer than 90 days, please be sure to print the packing slip prior to creating the ship label so customer information is not hidden after 90 days.

Required fields by workflow

URBN requires certain fields for inventory, cancel, and shipment updates. You will need to ensure that you are sending all the required fields for this program. The document below outlines those required fields by workflow.

URBN - Required Fields by Workflow

Excel templates for each workflow

If you would like a description of the required fields listed in the document above, or if you plan on using Excel files for your feeds, the templates below are available for you to use.

URBN - Inventory Upload Template
URBN-  Cancel Upload Template
URBN- Shipment Upload Template

Partner SKU

A requirement of working with URBN is that each item in the platform must include a Partner SKU. A Partner SKU (also referred to as a Merchant SKU or Retailer SKU) is the identifier used by URBN when creating orders for a supplier's items. The Partner SKU is not the same thing as a Vendor SKU. The Vendor SKU is the supplier's own unique identifier for the item. The partner_SKU field in the platform should be used to include the URBN Retailer SKU.

The table below shows the difference between a Vendor SKU and Retailer SKU and how each of those SKUs should be used in the platform.

Rithum Field Item Identifier
sku Vendor SKU
partner_sku Retailer SKU

Submitting incoming inventory to URBN

URBN uses incoming inventory data to allow their suppliers to communicate inventory that is not yet ready to ship from their shipping facilities. Refer to the document below for more information on how to submit incoming inventory using the platform.

Submitting incoming inventory to URBN

Invoice policy

URBN urges you to make note of these requirements and best practices:

  • Include the invoice number in the shipment information. If the invoice number is not available, please use the purchase order (PO) number
  • Separate invoices are not required by URBN.

EDI documentation

If you are going to exchange EDI documents with Rithum for URBN, you will use the standard EDI specifications.

Note: In the standard EDI specifications, there are two versions for the 850 file: 4010 and 5010. For URBN, we recommend you use the 5010 version for 850 files. All other files (846, 856, 870, 810) will use the 4010 version.

API documentation

If you are going to exchange transactions via API, you will use the V3 API specifications

Packing slips

You are required to download packing slips and include them in your shipments. Packing slips can be downloaded in the platform.

If you prefer to create your own packing slips, this document provides instructions for replicating packing slips for URBN. Once you have created your packing slips, please submit samples to URBN for approval.

URBN - Packing Slip Guide

URBN Logos

Resources

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Articles in this section