Standard
Get started
Three ways in, depending on what you do. None of them needs membership or a licence fee.
Brands and manufacturers
Your first record
No PIM system needed: a spreadsheet is enough to start.
-
Collect what you have
GTIN, manufacturer details, dimensions and weights, warnings in every language you sell in, and one main image. These are the fields every record needs.
Fields of the core -
Download the template for your category
One spreadsheet per category, with one column per field and a filled example row. Overwrite the example with your product and add one row per variant.
Spreadsheet templates -
Check it in the validator
Open the file in the validator. It shows missing fields, completeness per block and whether the information for online offers is there. Your data stays in your browser.
Open the validator -
Pass it on
Send the record to retailers and partners that accept it. Until they do, fill their templates from the same record – you maintain the data once either way.
Tell us what your retailers ask for
Retailers and marketplaces
Taking in records
A record arrives as JSON – one file per product variant – or as rows of the spreadsheet template. Map it once to your import, and every brand that supplies records fills your catalogue the same way.
Check incoming records with the validator or validate them in your own systems with the schemas. The compliance chapter shows which fields carry the information online offers have to show.
| Column in your template | Field in the record |
|---|---|
| GTIN / EAN | gtin |
| Brand | brand.name |
| Product title | title.<language> |
| Manufacturer name and address | manufacturer |
| EU responsible person | euResponsiblePerson |
| Weight (kg) | weight.netKg |
| Dimensions (cm) | dimensions.assembled |
| Main image | media.images (role hero) |
| Warnings | compliance.warnings[].text |
| Suitable from / to | childSuitability |
Solution providers
Validating records in your software
The JSON Schemas (draft 2020-12) are the normative part of the specification. Load all six, register the two formats for GS1 check digits, and validate against the core schema. The example uses Ajv in JavaScript; any validator for draft 2020-12 works.
Schemas: downloads · Field reference: core · Examples: three records
import Ajv2020 from 'ajv/dist/2020.js';
import addFormats from 'ajv-formats';
const base = 'https://openjuvenile.org/schemas/v0.2/';
const files = ['core', 'compliance', 'media', 'compatibility', 'profiles/stroller', 'profiles/car-seat'];
const schemas = await Promise.all(
files.map((file) => fetch(`${base}${file}.schema.json`).then((response) => response.json())),
);
// GS1 check digit for GTINs and GLNs.
const gs1 = (value) =>
[...value].reverse().reduce((sum, digit, i) => sum + Number(digit) * (i % 2 ? 3 : 1), 0) % 10 === 0;
const ajv = new Ajv2020({ allErrors: true, strict: false });
addFormats(ajv);
ajv.addFormat('gtin', (value) => /^(\d{8}|\d{12,14})$/.test(value) && gs1(value));
ajv.addFormat('gln', (value) => /^\d{13}$/.test(value) && gs1(value));
ajv.addSchema(schemas);
const validate = ajv.getSchema(`${base}core.schema.json`);
if (!validate(record)) console.log(validate.errors); Software that reads and writes valid records can be certified as “OpenJuvenile Ready” once the certification programme opens.