# Arianee (https://eulabel.eu/docs/knowledge-base/switch-from/arianee)

> Fetch the complete documentation index at: https://eulabel.eu/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> Full content: https://eulabel.eu/docs/llms-full.txt
> Append .md to any page URL for markdown, or send Accept: text/markdown.



Arianee is the closest architectural peer: API-first Digital Product Passport infrastructure with REST/GraphQL, SDKs, and enterprise trust signals. Teams evaluate EUlabel when they want EU-hosted GS1 Digital Link resolution, wine e-label beachhead workflows, or a lighter mid-market path without a full enterprise implementation.

At a glance [#at-a-glance]

* **Similar**: developer-facing APIs, passport publication, brand-controlled identity.
* **Different emphasis**: EUlabel leads with wine e-label compliance and GS1-conformant resolution; Arianee is broader DPP/NFT-heritage infrastructure at enterprise scale.
* **Honest fit**: if you need multi-tier supplier provenance or a large existing Arianee estate, evaluate carefully before switching.

How they compare [#how-they-compare]

| Dimension     | Arianee                               | EUlabel                                               |
| ------------- | ------------------------------------- | ----------------------------------------------------- |
| Focus         | API-first DPP infrastructure          | GS1 resolution + passport publication; wine available |
| Strength      | Scale, SDKs, SOC 2 (company-reported) | Open standards, wine compliance path, partner embed   |
| Typical buyer | Enterprise brands and platforms       | Software vendors and mid-market manufacturers         |

Company-reported scale and certifications change; verify current Arianee and EUlabel trust materials for procurement.

Why teams switch (or choose EUlabel instead) [#why-teams-switch-or-choose-eulabel-instead]

* They need wine Reg. 2021/2117 e-labels on the same stack as later DPP groups.
* A PIM/ERP/labelling vendor wants passport publication as a component, not a full suite.
* They prefer EU-hosted GS1 Digital Link semantics as the primary product surface.

Migration steps [#migration-steps]

Inventory passports and identifiers [#inventory-passports-and-identifiers]

    List GTINs (or other product IDs), passport payloads, and current Digital Link / redirect URLs from Arianee.
Map to EUlabel schemas [#map-to-eulabel-schemas]

    Align fields with [passport data format](https://eulabel.eu/docs/knowledge-base/guides/passport-data-format). For wine, use [wine e-label](https://eulabel.eu/docs/knowledge-base/guides/wine-e-label); for other groups, use sector guides (battery/textile preview).
Recreate via API [#recreate-via-api]

    Use the [REST API](https://eulabel.eu/docs/api-reference) and [quickstart](https://eulabel.eu/docs/documentation/get-started/quickstart). Prefer automated scripts over manual UI for large estates.
Cut over resolution [#cut-over-resolution]

    Point GS1 Digital Link or brand domains at EUlabel destinations. Coordinate QR reprint or soft redirects for codes already in market.
Next steps [#next-steps]

* [Overview](https://eulabel.eu/docs/knowledge-base/switch-from)
* [DPP concepts](https://eulabel.eu/docs/knowledge-base/concepts/digital-product-passports)
* [PIM integration](https://eulabel.eu/docs/knowledge-base/guides/pim-integration)