Frequently asked questions

A digital product passport (DPP) is a set of data about a product — materials, origin, carbon footprint, recycling route — reachable through an identifier carried on the product itself. The EU is phasing it in by category: batteries from February 2027, further groups in the years after.

If you make batteries, textiles, electronics or furniture, the obligation either already applies to you or will within a few years. Itemoo ships the passport block as standard so you can fill it in before the deadline becomes a problem.

The passport applies to every product in scope that is placed on the EU market, wherever it was made. It has to be ready before the goods enter the market — not after the first shipment.

An operator in the EU — the importer or an authorised representative — is responsible for keeping it available. In Itemoo you fill in the passport and the responsible-entity details before the goods leave your warehouse, and the code on the label works from the very first unit.

No. The canonical Itemoo code works independently of GS1 and suits short production runs, prototypes and products never sold at retail.

If you do have a GTIN, we attach GS1 Digital Link as a second address for the same product — so one code serves both the retail checkout and the product page, in line with the Sunrise 2027 direction.

Two routes, usually in parallel. Import from source material takes manuals, safety data sheets and label photos and builds finished pages — a typical product means minutes of review instead of hours of writing.

CSV import takes an ERP or PIM export and proposes a column mapping that you approve by hand. The model creates no content here, it only matches column names to fields — a deliberately narrow and safe role.

The data contract does not allow it. Every fragment written by the model must cite a source document and a quotation — missing evidence means the fragment is rejected at validation, rather than turning into a more cautiously worded sentence on the page.

On top of that, safety data sheets, product passports and legal documents run in cite-only mode: the model does not paraphrase, translate or generate file addresses for them. A control test suite must pass in full before every release.

You announce the recall for a specific batch or a LOT range. From that moment every scan of a code from that batch shows a red banner with the reason and what to do — before the user sees anything else.

In parallel a push notification goes to installed brand apps, with email as the fallback. A counter shows in real time how many holders have seen the notice — that is your proof of reach for the regulator. Recalls are never subject to plan quotas.

No, and that is the heart of the idea. The code on the label points at the product, and the product page points at the document by reference rather than by a copied file URL. Uploading a new version changes the documentation across the whole catalogue at once.

A version can carry a future effective date and the system switches to it on the right day by itself. Batches produced earlier keep the version that was in force on their production date, because that is the evidence for that specific production run.

From the data we already collect on every scan: the code, the time and the country. The same serial number cannot be in Gdańsk and Guangzhou at once, and a genuine item is not scanned four hundred times.

The system surfaces signals — multiple countries, an impossible journey, unusual volume — always next to the legitimate explanation that could account for them. We do not issue a verdict, because you are the one who knows your distribution channel. No new technology, no change to production.

You enter responsible-entity data once when registering the brand, and it appears with every published product. Gaps in critical data block the publication of your first product — the system will not let a non-compliant page go out.

We split responsibility plainly: Itemoo is answerable for making sure content unsupported by your material never reaches the page. The manufacturer is answerable for what is in the material, and for the decision to publish.

No. A scan records the code, the time and the country — not a precise location, and with no personal identifier. A shipping address typed before purchase stays on the customer's device and reaches us only when they place the order, with consent.

Customer accounts are passwordless: sign-in by a code sent to email. The risk of a password leak disappears because there is nothing to steal. Accounts belong to the brand, not to Itemoo, and contact data lives in a separate table so it can be permanently erased on request.

Yes. Every application query is scoped to your company and its brands — another manufacturer's data cannot be reached from your account, and yours cannot be reached from theirs.

Only what you publish is public: product pages and files marked as public. Source material, drafts and order data stay in the panel.

No. A product enters the brand shop automatically once it is published and priced — you do not maintain a second catalogue alongside the one you already have.

Customers buy without creating an account, because forced sign-up is one of the most common reasons for abandoned purchases (Baymard Institute). We offer the account after payment, and a guest order can be found using its number and email address.

You do not need IT to reach your first working code: register the brand, import the material for your first product, print a sheet of codes on an ordinary printer. That fits into a single afternoon.

IT gets involved only for the integrations you want anyway: serial numbers from MES, the catalogue from ERP, Zebra printers on the line, pointing your own domain at the pages. Each of these runs through a ready import or export, with no code to write on your side.

No. No plan counts scans or product page views. Any customer, service technician or inspector can scan the code as often as they like.

Each product above the limit is charged from the overage price list, measured at the month’s peak. Serialised unit, team, brand and file limits work the same way. Serialised units are never deleted, so with steady production their count grows year by year. Without an overage cap nothing is blocked.

If you set a monthly overage cap in the panel, the cost has an upper bound: once it is reached, new products, brands and invitations above the limit wait until the month ends or the cap is raised. Existing codes, pages and recalls always keep working.

When the extra charges start to grow, a higher plan is usually cheaper — compare it in the calculator.

Like a progressive tax: each turnover band has its own rate, and crossing a threshold raises the rate only on the excess, not on the whole amount. Tiers follow your billing period: month by month when paying monthly, cumulative over the paid year when paying yearly.

Turnover is the net value of goods after discounts, without shipping, minus cancellations and returns, from orders handled through Itemoo (your brand shop and connected marketplaces). Turnover of all brands in a company is added up; sales outside Itemoo don’t count.

No. Every manufacturer works with its own payment gateway account, and sales revenue goes straight to them. We settle commission with you separately.

Yes, up or down, yourself in the company panel. A new plan applies at once, the subscription is prorated by day, and new commission tiers apply from the next billing period.

When paying yearly, you can upgrade at once with a top-up until the end of the paid year, while a downgrade starts when that year ends.

After your contract ends, codes and product pages keep working for 30 days while you download a full data export.

You can then prepay Code Maintenance Mode: codes lead to your own address or to a read-only page in its last version, and you can still publish batch recalls. Without it, brand data is deleted and the codes show a notice that the product is no longer supported.

You buy the mode for whole years, at least for the period during which the law requires your products’ passports to stay available (e.g. 10 years for batteries). You pay a fixed company fee and a decreasing per-product rate, so a large catalogue costs less per product. Serial numbers of individual units are included up to your last plan’s limit. Prices are below the overage price list.

Yes, on every plan. The CSV import takes an export from your ERP or PIM and suggests a column mapping that you approve. From a file you can load products, serial numbers of individual units, SKUs with EAN codes and stock levels.

Ongoing data exchange with your ERP (the /v1 API, webhooks and order export) comes with the integrations module from the Pro plan.

From the Start plan, your brand website runs on your own domain. Codes on products always lead to the Itemoo domain: we keep it running after your contract ends, so a printed code does not die with your DNS record and can keep working in Code Maintenance Mode for years.

The product page after a scan, the order page, the app and emails without Itemoo branding come with the Enterprise plan.

You choose a paid plan and keep working on the same data. If you do not, the account becomes read-only and the company is deleted a couple of weeks later — we send reminders before that. That is why codes are not public and cannot be printed during the trial: nothing from the trial ends up on your goods.

No. All prices on this page are net — VAT is added at the rate that applies to your company.

We handle tickets Monday to Friday, 9:00–17:00 Polish time (CET/CEST), excluding Polish public holidays. The “working h” response times in the table count only within those hours — a ticket sent on Friday evening counts from Monday morning.

On the Enterprise plan, critical tickets (an outage, e.g. the product page does not open after a scan) get a 24/7 response: the clock keeps running at night, at weekends and on holidays, and the ticket goes straight to the person on call.

Write to us. For a large catalogue, many brands or particular SLA requirements we prepare an individual plan under a signed agreement.

For LMT, EV and industrial batteries above 2 kWh — from 18 February 2027. For further product groups the obligation will come through ESPR delegated acts. Today GPSR already requires manufacturer details and safety information for every consumer product.

Yes. Itemoo bases every passport on GS1 Digital Link — an identifier scheme accepted by EN 18219:2026 that also scans at the till. You need a GTIN for the product (issued by your national GS1 organisation) and a company identifier such as a GLN. The code and product page without a passport work without a GTIN.

We build the passport to these standards: the API per EN 18222:2026, the data format per EN 18223:2026, GS1 Digital Link identifiers (EN 18219:2026) and the QR code per EN 18220:2026. We do not yet claim full conformity with the whole package: prEN 18239 and prEN 18246 are still being prepared, and the archive after the contract ends will be switched on once retention periods are settled.

Under ESPR, registry obligations sit with the manufacturer or the operator placing the product on the market. Itemoo makes the data available in machine-readable formats but does not register passports on your behalf.

No. The rules set out how the sheet is provided to recipients — the code is an extra, always-current way to reach it, including for people who never got the paper copy.

Each language version is a separate file from your SDS provider. The page shows the one matching the phone’s language and keeps the others available next to it.

Your ERP catalogue comes in as a CSV with suggested column mapping, and sheets and manuals from PDFs through an import that tells you exactly what was missing.

No. EUDAMED registration and Basic UDI-DI assignment stay with the manufacturer. Itemoo provides the UDI carrier and the product page with documents.

Only in the cases and under the conditions of Regulation 2021/2226 — among others for devices intended for professional users, with a risk assessment and a paper copy on request. Itemoo provides a stable address and version history; the decision and assessment stay with the manufacturer.

You announce the action for a batch or a serial range. Every scan shows a banner with instructions, holders with notifications on get a message, and a counter shows how many people have seen it.

Light means of transport (LMT) batteries, electric vehicle batteries and industrial batteries with a capacity above 2 kWh — from 18 February 2027.

No. We make the data available in machine-readable formats (JSON-LD, API); obligations towards registries stay with the manufacturer.

The regulation separates public data from data available to persons with a legitimate interest; the details are set by an implementing act. We publish the public data today; access levels are being prepared.

Yes — the manufacturer’s obligations follow the product, not the sales channel. A code on the product gives you a direct channel to the user that distribution does not.

A product placed on the EU market needs an economic operator established in the Union responsible for the tasks in Article 4 of Regulation 2019/1020 — their details go into the block next to the manufacturer’s.

No. The Itemoo code works without a GTIN, at model, batch or unit level. If you have a GTIN, the same code also serves GS1 Digital Link.

No. Individuals and businesses can both create a partner account. For payouts you add billing details, and we check them before the first transfer.

From your link or from the code entered at sign-up. With the visitor’s consent the code is remembered for 90 days. The panel shows clicks, sign-ups and companies for each link.

A reward waits until the client has paid a few subscription periods — this protects against refunds. Then you request a payout in the panel. The client’s trial does not count.

No. A client with a partner code gets a starting discount, and Itemoo covers the partner’s reward.