Site Root

Wiki: Product Registry Supplier Portal

Anonymous — Thu, 10 May 2012 02:01:00 GMT

User documentation and FAQs for the Product Registry Supplier Portal.

Wiki Page: Authorizing recipients

cpayne — Wed, 09 May 2012 21:01:00 GMT

A recipient is any retailer, distributor, shopping engine or really anyone who wants your data. When Edgenet forms a relationship with a new recipient, this alert will display to let you know.

When you check the box of a recipient and click Continue that recipient will be added to your profile as authorized. Two things will happen:

Your existing products will be authorized for that recipient. Any products that have been previously certified (and pass current certification validations) will be certified and sent to this new recipient. Though there may be additional attributes required by the recipient before you can send the data
Each new product you create will be authorized for that recipient going forward. You can also set this at the product level. So, if you have one product you want to create without this recipient authorized, you can do that.

When you uncheck the box of a recipient and click Continue that recipient will NOT be authorized for any existing products. You can always set authorized recipients on each product individually, but doing it this way will save you time.

Some things to keep in mind:

Publish to GDSN recipients is handled in Supplier Portal Classic and not affected by selecting these recipients. However, authorizing GDSN Recipients is necessary in order to see the GDSN attributes and fill in the data.
You can click Remind me later for 30 days. After that the recipient will be authorized and #1 & #2 above will proceed.
Check edgenet.com for more information about our data recipients.

Click here to learn how to manage your authorized recipients.

Wiki Page: Edgenet Services Agreement needs to be updated (UI)

Mike Owens — Fri, 09 Mar 2012 20:42:00 GMT

Resolution: Agree to the latest services agreement.

Details:

At least one of your authorized recipients requires that you have agreed to a newer agreement then you have on file.

Back

Wiki Page: Edgenet Services Agreement needs to be updated

Mike Owens — Fri, 09 Mar 2012 20:42:00 GMT

Resolution: Agree to the latest services agreement.

Details:

At least one of your authorized recipients requires that you have agreed to a newer agreement then you have on file.

Back

Wiki Page: Variation missing (UI)

Mike Owens — Fri, 09 Mar 2012 20:38:00 GMT

Resolution: Create at least one variation for your product.

Details:

Your product has been linked to a category that requires at least one variation.

What are variations?
For apparel product lines, you likely have one or more styles. Each comes in various sizes and colors. Everything about the products within a particular style will be identical except for size and color. So, you create Variations. The base item contains all of the marketing information as well as most of the category data. You enter/select the sizes and colors for the product, and we create the variations.

Let's say you have a T-shirt in red, blue and green that comes in small, medium and large. you select those 6 elements and we create variations for red/small, red/medium, red/large, blue/small, etc. Now you will have a variation for each of the 9 unique combinations. The variation may allow you to add addtional (non-required) information such as an identifier or a color swatch.

In Single Item Edit, click the variations section. If you are working in Bulk Edit, click the Variations tab and select the category you want to work on. If you have not already done so, you may need to specify your variation attribute values (like red, blue, large, etc.)

If variations don't seem right for your product, check to see that it has been categorized properly.

Back

Wiki Page: Missing attributes (Variations) (UI)

Mike Owens — Fri, 09 Mar 2012 20:34:00 GMT

Resolution: Categories that need variations, have a minimum number of variable attributes to complete. In Supplier Portal, these attributes are marked in red with "Attribute must have value" in the Variations section.

Details:

There is a minimum set of attribute required to Certify & Send product information to any recipient. This is true of product variations as well. You are missing one or more of those attributes on at least one variation for this product. When viewing your product in Single Item Edit (Variations section) or Bulk Edit (Variations tab), required attributes are denoted with an asterisk(*). Each required attribute will also have an error bubble underneath that reads "Attribute must have value". In Bulk Edit, you can also use the DQ Details to see all required attributes.

Once all required attributes have a value, you can try to certify again.

Back

Wiki Page: What to do when your certification failed?

Mike Owens — Thu, 08 Mar 2012 15:48:00 GMT

When you click Certify & Send, Supplier Portal runs a number of validations on your product(s). If any of these validations fail, a message will be display. When you click the message in Supplier Portal, the errors will display along with the resolution.
Click each error message below to see more details:

Wiki Page: Missing attributes (UI)

Mike Owens — Thu, 08 Mar 2012 15:48:00 GMT

Resolution: Fill in all attributes that are listed as required in the schema. In Supplier Portal, these are marked in red with "Attribute must have value".

Details:

There is a minimum set of attribute required to Certify & Send product information to any recipient. These requirements are the same for everyone. You are missing one or more of those attributes. When viewing your product in Single Item Edit or Bulk Edit, required attributes are denoted with an asterisk(*). Each required attribute will also have an error bubble underneath that reads "Attribute must have value". In Bulk Edit, you can also use the DQ Details to see all required attributes.

Once all required attributes have a value, you can try to certify again.

Back

Wiki Page: The number of warnings has reduced your product score below 75 (UI)

Mike Owens — Thu, 08 Mar 2012 15:12:00 GMT

Holding

Wiki Page: UPC is required by one or more of the selected recipients (UI)

Mike Owens — Thu, 08 Mar 2012 15:12:00 GMT

Holding

Wiki Page: This product must have Ezeedata Commerce or Search Product Type . . .(UI)

Mike Owens — Thu, 08 Mar 2012 15:11:00 GMT

Holding

Wiki Page: This product must have Ezeedata Commerce Product Type . . .(UI)

Mike Owens — Thu, 08 Mar 2012 15:11:00 GMT

Holding

Wiki Page: These required attributes are not populated: attribute list (UI)

Mike Owens — Thu, 08 Mar 2012 15:09:00 GMT

Holding

Wiki Page: Your enrollment does not include one or more of the selected recipients (UI)

Mike Owens — Thu, 08 Mar 2012 15:07:00 GMT

Holding

Wiki Page: Certification issues exist (UI)

Mike Owens — Thu, 08 Mar 2012 15:04:00 GMT

Holding

Wiki Page: Certification errors for XML feed users

Mike Owens — Thu, 08 Mar 2012 14:55:00 GMT

When you submit your XML feed to Edgenet, Edgenet responds with an email telling you processing is complete. If there are issues for you to correct, the email will have an attachment with it. The email contains instructions to properly open the attachment. Once opened and viewed in Excel, the file displays the issues and resolutions.
This article deals with issues labeled as “Certification & Publish”. Click the issue below to see more details. Some can be fixed by adjusting the XML file, others you will have to login to Supplier Portal to resolve.

Wiki Page: Certification issues exist

Mike Owens — Wed, 07 Mar 2012 17:34:00 GMT

Resolution: Correct the issues of type Data Quality in the feedback attachment. In Supplier Portal, fix attributes marked in red.

Details:

A certification issue is a critical data quality issue. These are labeled in Data feed email attachment as Issue Type: Data Quality. Examples might involve issues with the Product Name. These are considered critical because that is such an important part of your product’s online presence. Another critical issue could be the use of inappropriate or offensive words. These must be corrected before your product data can be sent.

Correct these issues and you can resubmit this product for certification.

Back

Wiki Page: Missing attributes (Variations)

Mike Owens — Wed, 07 Mar 2012 17:29:00 GMT

Details:

There is a minimum set of attribute required to Certify & Send product information to any recipient. This is true of product variations as well. You are missing one or more of those attributes on at least one variation for this product. In order to determine which attributes, you can compare your XML file to the latest schema from Edgenet. Or you can check the Data feed email attachment. Missing attributes will be listed as Issue Type: Certification & Publish.

Once all required attributes have a value, you can resubmit this product for Certification.

Back

Wiki Page: Missing attributes

Mike Owens — Wed, 07 Mar 2012 17:23:00 GMT

Resolution: Fill in all attributes that are listed as required in the schema. In Supplier Portal, these are marked in red with "Attribute must have value".

Details:

There is a minimum set of attribute required to Certify & Send product information to any recipient. These requirements are the same for everyone. You are missing one or more of those attributes. In order to determine which attributes, you can compare your XML file to the latest schema from Edgenet. Or you can check the Data feed email attachment. Missing attributes will be listed as Issue Type: Certification & Publish.

Once all required attributes have a value, you can resubmit this product for Certification.

Back

Wiki Page: This product does not have a Location/Target Market defined.

Mike Owens — Wed, 07 Mar 2012 17:17:00 GMT

Resolution: Specify an Active Combination of Location/Target Market for this product.

Details:

This refers to a Global Location Number (GLN) and where the product is sold (Target Market). GLN is a 13 digit number that corresponds to your company or distribution center. New suppliers will be prompted to provide a GLN during first login. Existing suppliers, you can follow these guidelines to add a GLN to your account:

Login to Supplier Portal
Click you Company Name (upper right corner of application)
Add your GLN in lower left corner of this page

You can use Supplier Portal Classic version to ensure a Location/Target Market is assigned to a specific product. Go to Items and search for your product. Click the Manage button to the right of the product. Here you can add Location/Target Market combinations to the Active pane.

You may also be asked for Target Market. Target Market specifies the country, region or part of the world where the product is sold. If you are unsure what to use, enter or select United States (840) If this is a GDSN product, make sure that you have logged in and registered the catalog item. Catalog item consists of the GTIN, GLN and Target Market for a product. A product may have multiple catalog items.

Back