What Happens to Your Product Data When You Switch Platforms
Key Takeaways
- QR codes printed on physical products encode a permanent URL — switching to a platform using proprietary URL schemes means every code in the field breaks, with no way to push an update to shipped packaging
- GS1 Digital Link resolves product codes through a routing layer you control; changing platforms means updating the resolver, not reprinting codes
- The highest-risk data categories for portability are scan event history, troubleshooting logs, and no-code experience content — often excluded from standard vendor exports
- Require bulk export in machine-readable formats (JSON/CSV) as a baseline contractual term, plus a minimum 90-day export window post-cancellation
Most manufacturers ask the right question too late: "What happens to our data if we leave?"
By then, a quarter-million QR codes are printed on products sitting in retail channels, distribution centres, and customer homes. Switching platforms at that point is not a software migration — it is a physical recall problem. Every scan on every printed code returns a dead page, a broken experience, or worse, a competitor's placeholder screen.
Software-as-a-service contracts rarely make this risk visible at signing. But for manufacturers of physical durable goods, the stakes of vendor lock-in are fundamentally different to any other software category. The code is already on the box. You cannot push an update to packaging that shipped two years ago.
Why Data Portability Hits Differently for Physical Products
Vendor lock-in is more severe for manufacturers of physical products than for any other software category because the URL encoded in a printed QR code cannot be changed after the product ships. When a marketing team switches email platforms, they export a CSV and redirect a domain — a weekend's task. When a connected product manufacturer switches platforms, they face a problem that no engineering effort fully resolves: every code already printed in the field is permanent. A mid-size appliance brand that ran its connected product programme through a platform encoding a proprietary domain into every QR code faced exactly this problem when the vendor raised prices by 60%. The migration team discovered 800,000 units in the field, all pointing to the vendor's domain. Leaving meant every warranty registration, parts lookup, and troubleshooting scan would fail. The vendor knew this when they wrote the contract. This scenario repeats across the industry. Manufacturers who avoid it understand one foundational principle: the URL structure of product codes is a strategic infrastructure decision, not a vendor implementation detail.
The GS1 Digital Link Standard: Your Best Defence
GS1 Digital Link (GS1 DL) is an open international standard that defines how product identity — including GTINs, serial numbers, and lot codes — is encoded into a URL. A GS1 DL URL takes the form https://resolve.brandedmark.com/01/09521234567890/21/000001. The critical mechanism is the resolver: a routing layer that maps the code to whichever destination experience the manufacturer chooses. Changing platforms means updating the resolver, not reprinting codes. It is architecturally equivalent to changing DNS — the address on the box stays constant while the destination is under the manufacturer's control. Platforms that encode their own proprietary domain into product codes make themselves structurally impossible to leave without reprinting all affected packaging. This is worth understanding clearly before any contract is signed. If a vendor is reluctant to confirm that the scan URL routes through a standard resolver the manufacturer can redirect, treat that as a hard stop. For more on GS1 DL in practice, see our manufacturer's guide to GS1 Digital Link.
What Data You Should Be Able to Export
A connected product programme generates several distinct data categories, each with different portability risk. Warranty registrations are structured and generally exportable as CSV or JSON, though custom field mappings may not transfer cleanly to a new system. Scan event history is higher risk: event logs are commonly siloed in vendor infrastructure and excluded from standard exports. Product configuration and no-code experience content is frequently stored in proprietary formats with no published export specification. Support interactions and troubleshooting logs are often absent from export tooling entirely, despite being among the highest-value operational data a programme generates. EU Digital Product Passport records are the most critical category: ESPR regulation requires this data to be portable and accessible throughout the product lifecycle, meaning any platform handling regulated categories must support compliant export. The categories most commonly excluded from standard exports are precisely the highest-value ones. Request a sample export of every data category before signing. If the vendor cannot produce one on request, the data is unlikely to be exportable at exit.
| Data Type | Export Format | Portability Risk |
|---|---|---|
| Warranty registrations (name, address, purchase date) | CSV / JSON | Medium — structured data, but custom fields may not map cleanly to new systems |
| Scan history (time, location, serial, scan count) | JSON / CSV | High — event logs are often siloed in vendor infrastructure and excluded from standard exports |
| Product configurations and experience content | JSON / Markdown | High — no-code builder content is frequently stored in proprietary formats with no export spec |
| Spare parts orders and transaction history | CSV | Low-Medium — order data is usually structured, but linked product associations may break |
| Customer support interactions and troubleshooting logs | CSV / JSON | High — often not included in export tooling at all |
| EU Digital Product Passport records | JSON-LD / GS1 DPP schema | Critical — regulatory data must be portable; verify compliance with ESPR requirements |
| Anti-counterfeiting and serialisation records | CSV | Medium — GTIN + serial pairings are structured but vendor systems may not export full verification history |
The categories most likely to be missing from a standard export — scan history, troubleshooting logs, product configuration content — are often the highest-value data your program generates. The EU's ESPR regulation reinforces this: DPP data must be portable and accessible throughout the product lifecycle, meaning any platform handling regulated data must support compliant export. Ask for a sample export before you sign. If the vendor cannot produce one, the data is probably not exportable.
Red Flags to Find Before You Sign
Most vendor lock-in is not deliberate — it is a structural side effect of proprietary systems built without considering exit. Proprietary URL schemes with no resolver layer are the clearest risk signal: if the platform encodes its own domain into product codes, the manufacturer is physically locked in with no software workaround. Ask directly whether the scan URL resolves through a standard resolver the manufacturer can redirect. Absence of bulk data export in the base contract is the second risk to check: some platforms gate export as an enterprise-only feature, effectively holding operational data for ransom at renewal time. Require bulk export in machine-readable formats as a baseline contractual term, not an upgrade. Short post-cancellation retention windows of thirty or sixty days are particularly dangerous for manufacturers with products in the field for ten to fifteen years. Require a minimum ninety-day export window in writing. Experience content stored in proprietary no-code tools with no export specification means rebuilding from scratch on exit. Contract language restricting post-exit use of exported data requires legal review before signing. For a full analysis, see The Hidden Cost of Build vs. Buy for Product Experience.
How the Major Platforms Approach Portability
Three platforms serve the connected product market at scale, and their portability postures follow a consistent pattern. Registria is one of the most established warranty and registration platforms; its architecture predates the GS1 Digital Link standard and URL structures are largely proprietary, creating resolver dependency risk. Export tooling exists for registration data, but scan-level event history and experience content portability are less documented — manufacturers on multi-year agreements should negotiate export terms across all data categories before signing. Brij is a newer entrant oriented toward QR-linked experiences for consumer brands; its URL structure is platform-hosted, and its portability posture reflects a marketing campaign use case rather than long-lifecycle durable goods programmes where multi-generational data continuity is essential. Layerise has a stronger orientation toward durable goods, with custom domain support on some plans partially addressing URL lock-in; export capabilities vary by tier and manufacturers should verify that scan history and serialisation data are included, not just registration records. Across all three, the pattern is consistent: registration data exports are accessible; event logs, configurations, and experience content are harder to obtain. Manufacturers who negotiate export terms in writing avoid discovering the gap at the worst possible moment.
How BrandedMark Handles Portability
BrandedMark was designed with manufacturer autonomy as a foundational principle, not a premium feature. Every product code resolves through a standard GS1 Digital Link resolver encoding the manufacturer's own GTIN and serial number — not BrandedMark's domain. If a manufacturer switches platforms, the resolver is updated to point to the new destination; printed codes never break. All data categories — warranty registrations, scan history, ownership records, spare parts orders, support interactions, and product configurations — are exportable in JSON and CSV at any time on any plan, with no enterprise-only gate on a manufacturer's own data. If an account is closed, data remains accessible for ninety days. On exit, BrandedMark configures the resolver to redirect GS1 DL URLs to any specified destination — a new platform, the manufacturer's own server, or a static page — for a minimum of twelve months, so products in the field continue to work without interruption. The underlying principle is straightforward: data that cannot be taken is not truly owned. Portability is the default, not a negotiated concession. For more on platform selection, see Questions Manufacturers Ask Before Buying Product Software.
Frequently Asked Questions
Can I bring my own domain for product scan URLs?
Yes — in BrandedMark, you can configure a custom domain (for example, scan.yourbrand.com) as the resolver entry point. All GS1 Digital Link codes route through your domain, so even the resolver address is yours. This means the scan URL printed on your products is not tied to any vendor infrastructure at all.
What happens to registered customers if I switch platforms?
With a GS1 DL-based resolver, the scan URL keeps working regardless of which platform processes the scan on the back end. Customer-facing experiences remain live during any transition period. Your customer registration data exports as a structured JSON or CSV file that can be imported into your new platform or CRM. The relationship survives the platform change.
How do I verify a vendor's portability claims before signing?
Request a live demonstration of the export process, not a screenshot or a slide. Ask the vendor to export a sample of each data category — registration records, scan history, experience configurations — in the format they claim to support. Review the contract for data deletion clauses, export restrictions, and any language limiting your use of exported data. If a vendor is reluctant to demonstrate export before you sign, treat that as a strong signal about what exit will look like.
Data portability is rarely the most exciting topic in a platform evaluation. It tends to lose out to feature demonstrations and pricing discussions. But for manufacturers with physical products in the field, it is the question that matters most when the relationship goes wrong — and eventually, with any vendor, something goes wrong.
The manufacturers who sleep well are the ones who asked the hard questions before a single code was printed. Make portability a contractual requirement, not an afterthought.