OriginSpan DPP platform demonstration

Full video transcript

A beautiful product wins attention. The information behind it has to earn trust. Where did it come from? What is it made of? Which batch does that document cover? And can your team stand behind the answer? For brands and manufacturers, those questions cross purchasing, suppliers, quality, operations, and customer service. When the answers live in separate systems and inboxes, every request becomes another search. OriginSpan connects product identity, partner data, traceability, evidence, and Digital Product Passports in one controlled workflow.

So the story you tell your customer has a record behind it. Let's make that concrete. We'll use apparel and components, with demonstration records, to show how the platform works—and why these connections matter to your business. Start with the product. A garment, a component, a material: your team needs to know exactly what it is working with. In this example, a gold-tone buckle has a name, a business reference, a product type, and its own identity. OriginSpan supports GS1 identities alongside your operational references. The product record connects to batches, lots, individual serials, assets, and logistics records.

A model specification and an inspection of one lot stay attached to the right level. Here, the finishing lot is linked to the buckle. Its location, condition, and recorded history are available together. Similar-looking components no longer have to depend on similar-looking filenames. Teams can scan with a phone camera, use an image, enter a code, or use a compatible hardware scanner. The identity takes them into the relevant work.

That is the foundation for everything that follows. Your supply chain does not have one level of digital maturity. A small workshop may answer a form. A larger supplier may send a spreadsheet. A connected business may exchange data through an API. OriginSpan gives those paths a common destination: guided entry, structured CSV and JSON imports, scoped service connections, and supported EPCIS event exchange.

You can start with the data you have and connect more sources as the relationship develops. Mappings preserve the relationship between source information and platform fields. Import receipts show what was accepted, rejected, or held for attention. Original values and source references remain useful when something needs correction. Look at this apparel import: the outcome is visible at record level.

The point is accountability. Your team can see what arrived, what happened to it, and where to act. Getting a file into the system is the beginning of a controlled process. The hardest information often belongs to someone outside your company. A mill has the material details. A component supplier has the specification. A laboratory has the report. Your brand needs the pieces to work together.

OriginSpan gives partner collaboration a clear structure. Define the relationship, assign the request, identify the product or batch, and specify the required information. Partners contribute within the access you grant. Invited contributors do not need their own separate paid OriginSpan subscription. Sharing is deliberate. The source, the destination, and the permitted information matter.

A supplier working with more than one brand does not automatically expose one customer's information to another. Review keeps the brand in control. Receiving a response, processing its data, and accepting it are separate steps. Corrections retain their lineage. Confidential documents can stay restricted while an approved product statement is prepared for publication. That is how you build participation without surrendering control of your product story.

Now pull back and see the wider picture. This is Global Trace. Recorded lifecycle observations connect across approved locations, turning a list of events into a journey your team can explore. In this demonstration, the map brings together eight mapped observations across six countries. Select a location and the corresponding event becomes the focus. Filter by the records, event types, or time window that matter to the question.

At Rotterdam, an attention marker takes us to a recorded exception. We can inspect the timestamp and status, then open the operational record, its evidence, and the available correction workflow. The map represents recorded observations and their sequence. It gives the team a clear route into the detail. For operations and customer service, that connection matters: see where attention is needed, then get to the information behind it.

A supply chain also changes the product itself. Materials are combined. Lots are split. Components become finished goods. To answer a quality question, geography alone is not enough. OriginSpan's material genealogy connects recorded inputs and outputs through transformations, splits, and merges. Trace backward toward origins, or forward toward affected products. Keep quantities, units, source references, and supporting evidence with the relationship.

The operational timeline records receipts, inspections, custody transfers, conditions, and exceptions. When information needs correction, a new entry preserves what came before and why it changed. Imagine a concern about one component lot. Your team needs to investigate the connected records, understand the scope, and make a responsible decision. This is where identity, genealogy, and history become practical tools for the people doing the work.

A document is useful when you know what it supports. OriginSpan connects evidence to the relevant record and event, with file checks, a content fingerprint, and retained attribution. Here, a sample PDF is attached to an inspection observation. The observation and its supporting document can be reviewed in context. The reviewer does not have to reconstruct that relationship from an email chain.

Evidence controls distinguish a recorded assertion, available documentation, and independent review. Expiry and review queues help teams see where attention is needed. The scope of the evidence stays important: one batch report should not silently become a claim about every product. For quality teams and commercial teams, the benefit is a stronger answer. The product, the claim, the source, and the review can be understood together.

Before information reaches a customer, teams need to know what is missing. OriginSpan brings together required data, evidence, translations, and publication controls, with reasons that lead back to the underlying records. Readiness is shown in separate dimensions. Technical conformance, data completeness, evidence, language, Registry readiness, product-law requirements, and customer policy each have their own meaning.

Versioned requirements and evaluation records help explain why a result was reached. Customer requirements can add the controls your business needs. A reviewer can see a blocker and follow it to the work that needs attention. This supports a disciplined preparation and review process. Your team has a clearer basis for deciding what is ready to share, and what still needs an answer.

The Digital Product Passport is where that work becomes a clear customer experience. Start with a defined profile, prepare the content, assign approved imagery, and preview the result. Public and restricted information have different audiences. OriginSpan keeps those classifications visible in the workflow. Your internal evidence and working details do not have to become the public product page. Validation checks the draft.

Publication captures an exact version with its own fingerprint and retained history. Delivery controls determine which approved version the public link presents. Updates can move the story forward while earlier publications remain traceable. The same identity can support a QR code, a readable passport, and structured representations for connected systems. Branded public links and customer-domain onboarding help the experience fit your business.

You control the source, the review, and the publication. The passport becomes the visible result of a connected process. Let's look at the customer side through this separate apparel example: an everyday cotton tee. The published passport brings the product image, identity, and useful information together. For apparel, the detail matters. The body fabric, neck rib, and sewing thread can have different compositions.

Care instructions, construction, repair guidance, and information about keeping the item in use give the customer something practical to return to. Your brand controls the imagery, visual theme, contact details, and public sharing experience. Customers can open the QR destination and share the published link. When enabled, they can also submit an observation for review. Moderation keeps those contributions separate from authoritative product information until the appropriate decision is made.

The product story can continue beyond the transaction, with your team retaining control. A global product needs a global experience. OriginSpan separates your team's interface language from the languages of your product content and public passport. Configure the organization's content languages. Prepare translations, review them, and see which records need attention. Source revisions and translation states remain connected, so a changed source does not quietly leave an old translation looking current.

The localization system includes regional language variants, right-to-left layouts, and locale-aware dates, numbers, and units. The public-passport catalog spans seventy- five languages. Publication respects the available content and its review state. Invitations are localized too, and the Shopify experience has its own language coverage. For an apparel business selling across borders, this is practical: keep one product identity while making the information understandable to different people, in different markets.

A platform has to work for the people responsible for running it. OriginSpan's administration workspace brings organization, people, products, passports, traceability, evidence, translations, integrations, AI, usage, and security into a connected operating view. Invite people with defined roles. Separate editing, publishing, billing, auditing, and viewing responsibilities. Review access, manage service identities, and retain the decisions behind changes.

People and automated connections have distinct controls. Action queues surface missing information, evidence concerns, translation work, and import problems. Connection health and record outcomes help administrators decide where to focus. AI controls let the organization govern feature access, budgets, and recorded usage. Billing and usage views bring entitlements, consumption, and planning into the same administrative experience.

Brand settings, language settings, public engagement policy, and domain controls give the business ownership of the customer experience. Light and dark appearances support how your team prefers to work. This is how the platform becomes part of daily operations: clear responsibilities, visible work, and control that stays with your organization. OriginSpan also works with the systems around it.

The Shopify integration connects catalog intake and the passport experience. Scoped API connections, versioned mappings, and supported EPCIS exchange connect information to the right records. Developers have guides and client examples. Administrators can inspect connection health and delivery outcomes. The goal is to bring information into the same controlled records, with sources and permissions intact.

Ask OriginSpan helps authorized users explore supported questions about recorded passport blockers, translation queues, import jobs, lifecycle events, and AI usage. Answers connect to structured results and source records, so the team can move from a question to the relevant work. Automation is most useful when people can understand its result. OriginSpan combines connected intake and assisted discovery with the review, access, and publication controls your business needs.

Your product story needs infrastructure you can trust. OriginSpan is built on Amazon Web Services, with security and scale designed into the workflow. Managed identity establishes who is asking. Tenant membership, roles, and permissions determine what they may do. PostgreSQL row-level security adds enforcement at the database. Private networks, encrypted storage, and protected evidence reinforce those boundaries.

Elastic computing handles changing demand. Managed database capacity and controlled connections help keep operational work responsive. Public identity lookups and background processing have distinct paths, so they can scale according to the work they perform. The global design combines distributed delivery with a tenant home region. It supports controlled regional expansion and local service requirements while preserving one durable product identity.

Hosting and residency are defined for each engagement. Availability is engineered through separated infrastructure, monitoring, backups, and controlled recovery. Database qualification tests indexed tenant queries against million-row layouts. That gives engineering a measured foundation for growth. Our assurance work is aligned with the Cloud Security Alliance's STAR framework, alongside preparation for an independent SOC 2 examination.

For your security team, that means a reviewable architecture and supporting evidence. For your business, it means a platform designed to grow with the relationships and records you depend on. When you compare platforms, follow the work all the way through. How does a supplier contribute? Can you inspect the original source? Can you trace the affected lot? Who can review it? What becomes public? And can the people running the business control the process?

That is the case for OriginSpan. Product identity, partner collaboration, traceability, evidence, localization, and publication work together. The impressive customer experience has an operational foundation behind it. Start with a product family that matters to your business. Bring the real data, the important partner relationships, and the questions your customers ask. Define the workflow and the measures of success, then build from that foundation. If you need more than another place to store product information, put OriginSpan at the center of how that information becomes useful.

Let's define your first connected product journey. OriginSpan. Your product. Its story. Connected.