FAQ
Clear answers for brands, manufacturers, and teams building transparent products.
A DPP is a digital record tied to a product, often accessed via QR or NFC. It contains structured information like materials, origin, production details, and care instructions, plus optional supporting documents. The goal is simple: make product information verifiable, portable, and easier to maintain over time.
Some industries are already moving in this direction, and more are expected to follow as regulations mature. If you sell into the EU, it's smart to prepare early, especially if your data is spread across suppliers, files, and legacy systems. Starting with a pilot helps you get ahead without overcommitting.
Typically, high-impact categories (often consumer goods with complex supply chains) are prioritized first. Apparel, footwear, and other manufactured goods are frequent early candidates because they involve materials, processing steps, and multi-tier sourcing. The practical approach: pick the product lines where transparency is most valuable or most demanded.
You can start with the basics: product ID/SKU, product name, materials, country of origin, and factory/facility information. If you have supplier lists, certifications, and test reports, those can be added next. WorldPulse is built for "start with what you have, improve over time."
Yes, and that's usually the best move. A pilot lets you validate the data model, supplier workflow, and scan experience with a small set of products. Once the process is proven, scaling becomes a repeatable operational task.
Messy data is normal. We map whatever you currently have (CSV exports, spreadsheets, supplier lists) into a consistent structure and flag what's missing. Then we prioritize fixes that matter most, so you can ship a usable passport without waiting for a perfect database.
Yes. QR is usually the fastest and simplest way to start. NFC can be added when you want a higher-end experience, stronger anti-tamper behavior, or tighter control over physical authentication.
Yes. Passports can include certificates, audits, lab testing, restricted substances documentation, or compliance statements, either as visible attachments or internal records. The key is ensuring claims are supported by evidence, not marketing language.
WorldPulse passports can support authenticity by tying a product's identity to a scannable record and a controlled identifier strategy. You can also design what happens when a scan looks suspicious (e.g., repeated scans from different regions). It won't magically eliminate fraud, but it raises the cost of faking and improves verification.
In practice, it's cross-functional. Supply chain often owns the truth of suppliers and materials, compliance owns requirements, IT supports integration, and brand owns the customer scan experience. The best setup is a single accountable owner with a small working group across the other teams.
A pilot can be done quickly when scope is tight: one product line, a defined set of fields, and a simple scan experience. Full rollout depends on how many products you have, how complex the supply chain is, and how structured your current data is. The fastest path is to launch a pilot, then scale in waves.
Pricing is usually based on scope: number of products/passports, complexity of data mapping, and what features you need (templates, evidence attachments, NFC, integrations, etc.). If you're early-stage or running a pilot, the goal is to keep it lightweight and prove value before expanding.
Yes, and that's part of the point. Products evolve over time: repairs happen, components get replaced, ownership changes, or a recall occurs. A DPP can be designed to reflect updates while maintaining a consistent scan destination.
You control what is public and what is internal. Many brands choose to show high-level transparency publicly while keeping sensitive supplier details private. The passport can support "tiers" of visibility depending on the audience.