This guide explains how to request DataSource SKU creation from 1WorldSync (now Syndigo) for configure-to-order (CTO), build-to-order (BTO), and refurbished products. These product types don't always carry a standard manufacturer part number, so we use a consistent naming convention to identify them in our system.
Preferred naming convention
When requesting SKU creation, build the Part Number using the prefix for the product type, followed by the customer part number and the OEM manufacturer part number:
REF_CustPN_OEMMPN
CTO_CustPN_OEMMPN
BTO_CustPN_OEMMPN
| Prefix |
Product type |
| REF_ |
Refurbished |
| CTO_ |
Configure To Order |
| BTO_ |
Build To Order |
- CustPN — the customer's internal part number for the SKU
- OEMMPN — the OEM (original manufacturer) part number
The 40-character limit
Part Numbers are limited to 40 Characters in our system.
If the full PREFIX_CustPN_OEMMPN string exceeds 40 characters, there are two options:
| Option |
What to do |
Notes |
| 1. Drop the CustPN |
Use PREFIX_OEMMPN only. |
Makes no difference on our side. |
| 2. Drop the OEMMPN from the Part Number |
Use PREFIX_CustPN and move the OEM part number into the product description instead. |
Keeps the OEM reference available, just in a different field. |
Recommended approach for refurbished products
Most customers opt for just:
REF_OEMPN
It's easy to identify the product and immediately clear that it is refurbished. This shortening is normally only needed for refurbished products — CTOs and BTOs usually have a specific part number from the manufacturer, so the full convention fits.
Sharing your data with us
You often don't need to send full product specifications. The right level of detail depends on your needs, and we can agree on a streamlined format that works for both sides. If you'd like, we can walk you through an example of how this is set up with another customer as a reference.
You also don't have to use the SPAF feed to send us the configuration. We can accept the data in other document formats too — what matters is the data itself, structured wherever possible. If you don't have a format of your own, simply fill in the SPAF Excel file and send that.
Submitting a claim for product data
Instead of (or alongside) a feed, you can submit a claim to request product data or a correction for a SKU. Submit claims through the DataSource submission form (sign-in required):
https://datasource.cs.1worldsync.com/qasubmission.aspx
One claim can cover multiple SKUs
You do not need a separate claim for every SKU. When several products share the same request — for example a batch of refurbished (REF), CTO, or BTO items — a single claim is enough. Attach the list of SKU numbers to that one claim rather than filing one per SKU.
For the full claims workflow (submitting, tracking, and claim statuses), see the DataSource Claims System guide:
DataSource Claims System
Prefer to watch it? See the walkthrough video:
Video – DataSource Claims
Reference documentation
For full feed structure, field definitions, and format requirements, see the 1WSCS Standardized SPAF Feed Guideline (v1.8). Key related resources:
- SPAF Feed Guideline (PDF) — full field reference and integration examples
- XML feed sample —
SPAF_xml-format.xml
- XLS feed samples — DataSource, Inline Content, and combined DataSource & Inline Content
- XML feed schema —
1WSCS_SPAF.xsd
Note: An AlternativePartnumbers section (for the ICB portal) has been added to the schema in test mode.
