# Bottlebooks (https://eulabel.eu/docs/knowledge-base/switch-from/bottlebooks)

> 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.



Bottlebooks is a wine PIM where e-labels are one module. Many teams keep Bottlebooks (or another PIM) as the master data source and publish e-labels through EUlabel. Others move e-label hosting entirely while continuing to sync from Bottlebooks.

At a glance [#at-a-glance]

* **Option A**: Bottlebooks remains PIM → sync to EUlabel for resolution and passport pages.
* **Option B**: Full cutover of consumer-facing e-labels to EUlabel; export once from Bottlebooks.
* **Strength of Bottlebooks**: becomes the winery’s master data; GS1 Digital Link QR support using GTIN.

How they compare [#how-they-compare]

| Dimension       | Bottlebooks                | EUlabel                                                         |
| --------------- | -------------------------- | --------------------------------------------------------------- |
| Model           | Wine PIM + e-label module  | Identity, resolver, and passport publication API                |
| Strength        | Master data for the winery | Standards-based resolution, partner embed, multi-sector schemas |
| Typical pattern | Data lives in Bottlebooks  | Data lives in PIM/ERP; EUlabel publishes                        |

Why teams switch (or dual-run) [#why-teams-switch-or-dual-run]

* They want a dedicated GS1-conformant resolver and OpenAPI-first publication layer.
* A partner or marketplace needs e-labels via API, not only the Bottlebooks UI.
* The same stack must later cover battery or textile passports.

Migration steps [#migration-steps]

Decide dual-run vs cutover [#decide-dual-run-vs-cutover]

    If Bottlebooks stays as PIM, use the [PIM integration](https://eulabel.eu/docs/knowledge-base/guides/pim-integration) pattern (webhook or batch). If you cut over e-label hosting, export a full product dump first.
Map GTIN-based Digital Links [#map-gtin-based-digital-links]

    Bottlebooks can encode GTIN in GS1 Digital Link QR codes. Keep the same GTINs in EUlabel so identity stays continuous — see [GTIN validation](https://eulabel.eu/docs/knowledge-base/guides/gtin-validation).
Publish passports [#publish-passports]

    Create products and wine passports via API. See [wine e-label](https://eulabel.eu/docs/knowledge-base/guides/wine-e-label).
Point resolution at EUlabel [#point-resolution-at-eulabel]

    Update Digital Link destinations (or reprint QR codes) so scans open EUlabel-hosted compliance pages.
Next steps [#next-steps]

* [PIM integration](https://eulabel.eu/docs/knowledge-base/guides/pim-integration)
* [Overview](https://eulabel.eu/docs/knowledge-base/switch-from)
* [CSV](https://eulabel.eu/docs/knowledge-base/switch-from/csv)