The CMS is your yearly SKU consumption limit, as stated in your DataSource agreement. Only datasheets that have been shipped count towards the limit. The limit is reset at the beginning of each agreement renewal term. Consumption can be monitored in the “Consumption statistics” section of the Extranet (Production tab > Consumption statistics). Only CatalogBase accounts have a contractual CMS. SupplierBase accounts do not have a CMS.

The contractual bandwidth is the amount of datasheets that we can produce for you on a daily basis. This limit applies only to SKUs that need to be built; therefore, only CatalogBase accounts have a contractual bandwidth. All the SKUs that are automapped will not consume bandwidth.

Consumption can be monitored in the “Consumption statistics” section of the Extranet (Production tab > Consumption statistics). Your Customer Support representative will contact you when your consumption reaches 80%, then again when it reaches 100%.

The list of digital content media types that your account is set up to receive is provided in the table cds_digital_content_media_types (cds_DigContent_Media_Types if you use the ContentConnector).

It can also be checked in the Extranet. Click here.

UPC/EAN codes can be provided by request. Please contact the Customer Support Team.

Codes are delivered in two tables:

• cds_metamap
• cds_distivoc.

You will find additional information here.

You will find on this page the complete list of available components.

If you're interested in a Free component, please contact the Customer Support team.
If you're interested in a Fee based component, please contact your Sales representative.

In order to know the components to which you're subscribed, please follow this link.

Depending of the configuration of your solution, you may have different accounts with different settings. If this is the case, check the link above from each of your accounts.

The “market” is the country in which the products are intended to be sold.

The “language” is the language in which the different localized DataSource components will be displayed (e.g. the specifications or the marketing text). It is possible to receive several different languages for a same market.

For information on the Languages we support, please visit Markets and Languages

For information on the Markets we support, please visit Markets and Languages

Yes, it is possible to receive several languages for a single market. Please contact your sale representative if you need to add an additional language.

Please read the article below"What is the difference between a market and a language?" to understand the difference between market and language.

No. You can download all the images and host them yourself. Or, let 1WorldSync host the images, and use the links provided to access the images. The images links are stored in the digital content table.

In case you need to refresh your database with your complete catalog, you can request the delivery of a full dump.

Click on "Full Dowload.zip File Request" under the menu "Downloads". You can request a complete full dump, a related products full dump (if applicable) and a digital content full dump.

The full dump will be delivered during the next weekend. If you need it to be delivered earlier, please contact the Customer Support team.

In order to trigger delivery of a new download.zip file, you need to connect to the FTP server, go to the folder "ACK", then delete the file dataout.txt. A new file will then be delivered during the next distribution cycle. Please note that if you are using the DataSource ContentConnector, there's no need to take these actions. The ContentConnector automates the process.

In order to retrieve missing digital content (images, marketing texts, key selling points, etc.), you can request a full digital content data dump.
To do so, click on "Full Download.zip File Request" in the Extranet, under the menu "Downloads". Then select "Full Download.zip Digital Content Only".

The full dump will be delivered during the next weekend. If you need it to be delivered earlier, please contact the Customer Support team.

The character set used is Windows-1250 (Latin2).

The size of the download.zip file will depend on your account type, market and options. A full download.zip for a full market catalog may be up to 3Gb. Regular increments for a small catalog may be less than 1Mb. Please contact the Customer Support team if you need more details regarding download file size.

Compatibility Rules are limited to Accessory SKUs in your account with us. But Product Lines/Models are not limited to your catalog, and will include all possible Product Lines/Models which we could identify for the Accessory SKUs in your account.

Yes, there is an option to get partial data when a product has not yet been released, or if the product is rejected or on hold. A partial delivery includes a limited number of components. Please contact the Customer Support team for more details.

Go to the "Claims" tab, then "Add a claim". Be sure to enter all of the information requested into the fields provided. Please keep in mind that 1WorldSync builds product data sheets primarly from information provided on manufacturer web sites. So, in the description field, your providing link(s) to manufacturer web sites can be helpful towards a speedy resolution to your claim. Similar to links, manufacturer product documentation is used by our Production Team to create data sheets. If you would like to share documentation with us, use the "Attachments" field.

If you have a CatalogBase account, an "Upload content" button is provided under the "Claims" tab. You can also click here. Use this section to inform us of new product releases, and to submit general catalogs or product information to our data production staff. The files you upload MUST contain a product part number. This is the primary method of matching customer SKU requests to product files.

Please note: Submitting files here will not request additional products for your DataSource catalog or automatically resend an already reviewed product back into production.

Any SKU you request first goes through our automatic and, if needed, manual mapping process. Then, if applicable, through the production process. One or two days after the SKU request upload, you can view the SKU’s status code in the cds_Catalog_Info (or cds_Catalog) table.

Here are typical production turnaround times:

• If the requested SKU is mapped to an existing, released SKU from the DataSource worldwide catalog, expect delivery within one or two working days.
• If the requested SKU is mapped to an existing SKU ‘in production’, or if the SKU is not mapped to any existing SKU, the SKU will go through the production process. Expected delivery depends of your contractual terms.
• If the requested SKU is mapped to an existing ‘on hold’ SKU, the delivery time cannot be determined. This is because required information about the requested product has not yet been made available by the manufacturer
• If the requested SKU is mapped to an existing rejected SKU, expect delivery of this information within one or two working days

Note that these turnaround time estimates are not applicable if you have exceeded your daily bandwidth. For more details about bandwidth, please check the FAQ “What is the contractual bandwidth, and how does it work?” above.

PUSH, CategoryBase or SupplierBase accounts

Your SKUs will have one of these two statuses:

• Shipped: SKUs that have been delivered to the customer’s account FTP
• Ready for delivery: SKUs that have been produced or updated but not yet delivered

Note: ‘Partial SKUs’ (SKUs for which the specifications have not been completed yet) will have either ‘In data capture’ , ‘On hold’ , or ‘No data found’ statuses.

PULL or CatalogBase accounts

The SKUs will have one of the following statuses:

• Shipped: SKUs that have been delivered to the customer’s account FTP
• Ready for delivery: SKUs that have been produced or updated but not yet delivered
• Prelaunch: SKUs that have future release date provided by manufacturer

In-Production statuses:

• Buffered (Unmapped): SKUs that have not been mapped to CCS SKU ID yet
• Production (In data capture): SKUs that are currently in data capture
• On hold: In production SKUs that cannot be completed yet because the data is not available from the manufacturers

Rejection statuses:

• Invalid Manufacturer: SKUs that were requested with incorrect or unrecognized manufacturer
• Invalid Part Number: The requested manufacturer part number is invalid
• Out of scope: The type of the requested products is not covered by CCS Product Data Model
• No data found: SKUs that do not have enough information available from the manufacturers
• Restricted: Requested SKU type is not covered by current contract or forbidden for delivery by manufacturer

Note: ‘Partial SKUs’ (SKUs for which the specifications have not been completed yet) will have either ‘In data capture’ , ‘On hold’ , or ‘No data found’ statuses.

SKUs are set to 'On hold' status when some of the required information about the product has not been made available by the manufacturer. These SKUs are periodically reviewed by our Production Team. If the information becomes available, the SKUs will be completed and released/delivered to you. If, after a longer period of time, the manufacturer has still not published the product information, the SKUs will be rejected as 'No data found'. If you have access to original manufacturer information about such SKUs, don't hesitate to share them with us. As a distributor or reseller, you may have access to certain manufacturer's documents that are not available to us.

If you request numerous SKUs requiring manual mapping or production, you will exceed your daily bandwidth. You would then risk losing control over your requested SKUs, because production of the pending SKUs will then depend on regular prioritization. You may also risk exceeding your contractual yearly CMS.

Yes, there is an option to get partial data when a product has not yet been released, or if the product is rejected or on hold. A partial delivery includes a limited number of components. Please contact the Customer Support team for more details.

You can set the priority codes to the products that you are requesting.

There are 3 priority codes: 1 - first priority; 2.- second priority; 3 - lowest priority.

Note: The priority codes are only applicable to the products in the buffered (unmapped) or in production status. The products with no specified priority code are being automatically added to the production queue based on the request date and the bandwidth consumption.

There are two ways to set the priority codes:

1. Upload in the PRC file.

The priority tag, e.g. “<PRIORITY>1</PRIORITY>” should be added into the 6th column of the PRC file.

If you use this column also for specifying the products UPC/EAN code, just add this tag to the UPC/EAN tag, e.g.: “<PRIORITY>1</PRIORITY><UPCEAN>545698532569785</UPCEAN>”.

Note: The upper cases are required. The order of the tags does not matter. As soon as the product shows up on the Extranet (usually within a day), you can see its priority in the Search your SKUs section.

1. Extranet / Search your SKUs section.

In this section you may select the required products in the SKU Search Form on the right side and enter the priority code in “Set SKU Priority” and click “Update”.

Note: If the priority codes are set via the Extranet then there is a limitation of how many products can be set up with the Priority 1 and 2.

Priority 1 limitation equals your daily bandwidth limit times 5.

Priority 2 limitation equals your daily bandwidth limit times 15.

There is no limit if the Priority Codes are submitted in the PRC file.

The ContentConnector can generate the required MFC and PRC files to be uploaded to our FTP server. The ContentConnector will perform based upon your entries in the cds_sku_request table in the ContentConnector. More detail is available here.

The Extranet does not provide a real-time view of SKU production. There is a 24 hour delay. So, newly requested SKUs can usually be found in the Extranet's SKU search on the following day. It may happen from time to time that synchronization between Production and the Extranet takes a bit longer.

In order to optimize the mapping of your requested SKUs, you're invited to add the UPC/EAN code if available.

Tag it into the 6th column of the PRC file of the SKU request file (PRC): "<UPCEAN>[UPC-code]</UPCEAN>". If you use this column also for specifying the SKU's prioritization level, just add this tag, e.g.: "<PRIORITY>1</PRIORITY><UPCEAN>545698532569785</UPCEAN>". Note that upper cases are required. The order of the tags does not matter.

We highly recommend that you delete from your DataSource catalog all SKUs that you don't use (obsolete) or which have been rejected by our production team. Doing so will shrink the download files and makes the production statistics more meaningful. In the future, in case you need a SKU you've previously deleted, the SKU will be delivered back to you the day after your new request. This situation won't count a second time towards your yearly CMS (consumption limit).

If your account(s) configuration requires that you specify to 1WorldSync the products for which you would like to receive content, you'll first have to fill MFC and PRC files and upload them to your FTP account. The procedure is described here.

If your account(s) configuration doesn't require that you specify to 1WorldSync the products for which you would like to receive content (e.g. receiving all the products from a specific market or distributor), there's nothing you have to do.

Delivery process

5 times a week (Tuesday, Wednesday, Thursday, Friday and once during the weekend) a new download.zip file is generated and made available on your FTP account, as long as you requested a new file to be provided. To do that, connect to your FTP account and delete the file dataout.txt available in the folder ACK.
The download.zip file consists of a set of text files used to update your DataSource database.

The request and delivery processes can be managed by the DataSource ContentConnector. Please contact the Customer support team for more information.