Product data is arguably the single most important set of information you provide to NuORDER. This template holds all the information related to the items you are selling in NuORDER.
In the product data template you will be able to control availability, establish filtering of products, and indicators for reporting.
- For a single product, information must be the same in all columns with the exception of the Size column.
- Every SKU should have its own line in the product data.
- Sizes breakdowns for a product will display in the order you list them.
- Nearly all of the columns can be set as filters or as searchable content within NuORDER.
PRODUCT DATA FAQS
Q: What defines a product in NuORDER?
A: A unique product is created based on the combination of Style Number + Season + Color.
Note: For a single product, when there are multiple rows of data, information must be the same in all columns with the exception of Size.
Q: How will my products display in NuORDER?
A: Each color-way of a style will have its own instance in the product gallery. When a product is selected, the full details will become visible, showing the full breakdown of color options available for that style, delivery dates, pricing, etc.
Q: Do I have to fill out all of the columns in the template?
A: No, you only have to fill out the required fields. However, we recommend you provide more details for a better user experience for your reps and buyers.
Q: What are the required fields on the product data template?
A: Required fields are Style Number, Season, Color, Size, Name, & Wholesale Price – this information will need to be filled out for all of your products. Category is not a required field, but is strongly recommended.
Q: I have extra fields I do not see on this template - can I add this information to NuORDER?
A: Yes, you can create additional columns. We will build those into your portal for you. Examples: Collection, Divisions, Brand Names
Q: Is the order of the columns important?
A: No, NuORDER logic is based on the accuracy of the column header name.
Note: If you want to display your information in a certain order, please indicate this to the Onboarding team and they will set up portal to match.
Q: Can I use my SKUs as the Style Number?
A: NuORDER is built at the style-color level. Therefore you cannot use SKU’s as your Style Number. Best practice would be to use the parent style code, and remove the size and color reference.
Note: If storing the SKU in NuORDER is critical to your business needs, it can be added in as a custom field - simply create a new column called “SKU” in the template.
Q: What is considered a parent style code?
A: A parent style code is typically the portion of the SKU that does not reference the color or size. For example; Isadora Blouse in Forest, Small. The SKU is MK-409-FRT-S, the parent style would be MK-409.
Q: What if we don’t differentiate our products by season?
A: Season is a required field. We recommend using a placeholder like “Core” or “Year-round” if season is not applicable to your business. This information can be hidden from the portal so that it is not visible at all.
Q: We carry styles from season to season? What is the best way to reflect this in NuORDER?
A: If you offer a product as a part of a specific season (i.e. “Holiday”) you can later adjust the data to assign the product to a new season. We strongly recommend assigning these carry-over or replenishment styles to a season like “Core” so you do not have to constantly update.
Q: What if our products don’t have a color?
A: Color is a required field. If your products are not assigned a color, we recommend a place holder like “Multi” or “Assorted”.
Q: What if our products do not have a size?
A: Size is a required field. If your products do not come in different sizes – we recommend a place holder like ”One Size” or “Units.”
Q: We haven’t determined all of our prices yet – what do I do if I do not have a price?
A: Price is a required field. You can send us zero; by default these items will be disabled from reps and buyers (Admin users will usually have permission to view disabled items). If you want the item to be visible and orderable, you will need use a placeholder price like $0.01.
Q: We sell in multiple currencies – how do I set this up in the product data?
A: Create separate Wholesale Price and Retail columns for each of the currencies (e.g. Wholesale EUR, Retail EUR & Wholesale CAD, Retail CAD)
Q: We sell in multiple currencies, but I do not want all of my customers seeing all currencies. Can I designate what currency they see?
A: All customers need to be assigned to a currency in the Company Data template. When a buyer logs in, they will only see their own currency pricing. If an item is not offered in a particular currency, those customers will not see it.
Q: Some of my customers are offered a different price point, how do I handle this?
A: This is best supported by using price sheets or customer-level discounts, and will not impact how you fill out this template. Simply provide the standard wholesale/retail price in each currency for your product data.
Q: I have products where each size is a different price - is this supported?
A: Yes, we can turn on a setting for price per size. You will have to set up your product data accordingly for those products.
Q: How are Category and Subcategory related?
A: They are nested filters. They have an “all or nothing” rule – if you put data in some rows in either column, you should fill out all rows in that column in order for these to function properly.
Q: Are there any special characters that should be avoided?
A: Yes, characters that cause delineation should be avoided in all fields. We support special characters such as ©, ™, and & in the Description column.
Note: These characters can become corrupted if copied and pasted directly from the web into your data template. Our system is based on UTF-8 language encoding.
Q: Can we use HTML formatting?
A: No. The one exception would be the break line code <br> to create new lines or paragraphs in a large body of text in the Description column.
Note: We can set other custom fields to accept <br> tags like the Description field ("long string" field type). Let us know if you would like this applied to other long text fields.
Q: We have long product descriptions – is there a character limit for the Description field?
A: No. Be mindful that lengthy descriptions take up more room and will push other important information farther down in the product details - meaning more scrolling for you and your customers.
Q: We carry multiple brands - how do I fill out my data templates and what will that look like in NuORDER?
A: Ultimately, all of your products, regardless of brands belong on one set of templates. Best practice is to add a column header such as “Brand Name” which would then function as a filter to help differentiate the brands you carry.