Loading...
Loading...
Sync. Complete. Review. Publish.
Then show it on your storefront.
One workflow. One registry. Human approval where it matters. Not a toy — a control surface.
Product rules in the EU are shifting from "declare once" to "prove anytime." What you put on the market today may need to be proven years later. Passports are not brochures — they are data objects that have to resolve, stay consistent, and hold up when someone checks.
From authorities
Structured, machine-readable data. Proof that can be re-checked later. No overwriting the past.
From the market
QR and link that work. Same truth for consumers, recyclers, and auditors. One source, not three versions.
Scattered data. Manual mapping. No single place that freezes and proves what was declared.
Mapping in tabs
Evidence elsewhere
Overwrote the past
Years later
You need one place that seals the record and keeps it verifiable.
The engine
Seal, version, verify. One registry. Immutable records. QR and link resolve to what was actually published. That core does not live inside your store — it lives in a system built for regulatory latency and proof.
The bridge
You stay in your catalog. Sync, map, review, publish from the admin. The app is the bridge: same rules, same registry, same proof — but the workflow lives where you already work. No rebuild, no second system to maintain.
You run commerce where you run it — Shopify today, another platform tomorrow. We run the regulatory layer. Same registry, same rules. You plug in where your products live; we keep the system updated as regulations and Delegated Acts evolve.
Schema updates, new product categories, timeline changes — we keep the engine in line so you can focus on your catalog.
One workflow inside your store: sync catalog, complete and map fields, review suggestions, publish once. Registry seals it; storefront shows it. No exit, no duplicate data entry.
See the workflowClick a step. The flow is clear.
The flow
Not a feature list. The modules that make the workflow real.
Your Shopify catalog is the source. The app syncs products and supports re-sync as you change data. Filter by vendor, tag, collection, or product category so large catalogs stay manageable.
Define how Shopify fields map to passport attributes. Save templates and reuse them; field ordering and required attributes can follow product type so apparel and electronics are handled appropriately.
The app fills gaps using deterministic rules first, then optional AI for unresolved fields. Every suggestion shows confidence and evidence; you accept or reject per field. No silent overwrites.
Before
Gaps. Manual mapping. No single source.
After
Mapped. Reviewed. One publish.
Publish from the product context. The record is sealed in the UCVreg registry, versioned, and verifiable. You can unpublish or update via a new version; the history remains auditable.
Put passport access where customers see it. Theme App Extension adds entry points on product pages; QR export and print-ready views are available; published passport URLs can be written to Shopify metafields.
Store-level view of passport readiness: scores, missing fields, and trends. Export reporting for ops and compliance. Audit and activity views so you can see what changed and when.
What becomes easier
Start with the catalog you already have.
No rebuild. Products and variants flow in. You work where your team already works.
Fill gaps without losing control.
Mapping and AI suggest; you approve. Nothing goes live without you.
Publish with review, not guesswork.
Preview what goes live. One action to seal. No silent promotion.
Show the same passport on the storefront.
Same URL, same QR, same truth — for customers and regulators.
One approval model. Four mechanisms around it.
No automatic promotion
Source of truth is the registry. QR and proof resolve to what was actually published.
AI suggests; you approve. No silent overwrites of publish-critical data.
Draft stays draft until you publish. No automatic promotion.
Version history and activity. Show what was declared and when.
UCVreg is a UnicodeVision brand. We are a UK-based software company with twenty years of building production systems. Indemnity insurance and enterprise readiness in place. We bet on compliance infrastructure for the long term.
Multi-vendor cloud
AWS, Google Cloud, Microsoft Azure, Cloudflare
99% uptime
Built for compliance seriousness
ESPR-aligned
Legal team keeps infra updated
20-year company
Not a side project
One sentence each. A small diagram. Expand when you need the depth.
Shopify catalog is the source; the app syncs and maps; published records live in the registry; the storefront reads the same truth.
Catalog and variants flow into the app; filters (vendor, tag, collection, category) let you work in slices. Mapping templates define how Shopify fields become passport attributes. Re-sync when you change data; no manual rebuild.
One place to edit, one place where the truth is stored.
Deterministic rules run first; AI suggests only for gaps. You see confidence and evidence; you accept or reject. No silent overwrites.
Deterministic rules (title, vendor, tags, variants) run first. AI suggests only for unresolved fields; output is structured and bounded. Each suggestion shows confidence and evidence. Publish-critical data is not written until you approve.
Anything publish-critical stays reviewable before it becomes public.
Nothing goes live without an explicit publish. You preview the exact record, version history, and evidence before you commit.
Draft stays draft until you choose to publish. AI suggestions are not written to publish-critical fields until you approve. Publish is one action; the record is then sealed in the registry.
No silent overwrites; you stay in control of what is public.
Published records are versioned and immutable. New version on change; old one remains. Stable URL, verification, history and evidence visible.
Each published passport has a stable URL and can be verified by third parties. Version history and activity views show what changed and when. Evidence and expiry are visible.
You can prove what was declared and when — for audits and customers.
The same record you publish resolves from QR or product link. App writes passport URL to metafields; theme or extension shows it. Publish/unpublish updates storefront.
Theme App Extension adds passport entry points on product pages. QR export and print-ready views use the same registry URL. When you publish or unpublish, the storefront sees the updated state.
Customers and regulators see the same truth you published.
Publishing seals the payload with a deterministic hash; the record is immutable. Versioning preserves history; lifecycle events are append-only. Separate encryption keys per tenant; RBAC at the API layer. Data retained in the registry for at least 10 years. AI uses multiple providers with schema-bound output; no raw prompt logging.
One workflow in Shopify. Secure registry. Human review. Storefront-ready. Your next step is clear.