7 Questions Manufacturers Ask Before Buying Product Software
Key Takeaways
- ERP integration depth varies enormously — demand a live demo with your specific system before signing anything
- Data portability and GS1 Digital Link-compliant QR codes are non-negotiable to avoid vendor lock-in
- Implementation timelines realistically run 4–8 weeks for a focused pilot and 3–6 months for full enterprise rollout
- EU Digital Product Passport compliance (ESPR) must be built-in from day one, not retrofitted later
Most software vendors will tell you what you want to hear. This article tells you what you need to know.
If you're a manufacturer evaluating connected product software — platforms that sit between your product and your customer after the sale — you've probably already sat through three demos that looked identical and promised everything. The decks were glossy. The case studies were vague. And nobody answered the questions you actually had.
That changes here.
This is a bottom-of-funnel buying guide. It's for the operations director who's been burned by a failed ERP implementation, the marketing lead who needs something that doesn't require a six-month IT project, and the compliance officer who has one eye on Brussels and one eye on the contract. These are the seven questions we hear most often — along with the honest answers, not the sales answers.
1. Does It Work With Our Existing ERP/PLM?
Why It Matters
Your ERP is the source of truth for product data — SKUs, serial numbers, BOMs, and warranty terms. Your PLM holds the engineering records and change history. If a new platform cannot connect to these systems cleanly and reliably, you face duplicate data entry, manual synchronisation tasks, and the kind of data drift that creates compounding customer service problems months after launch. Every disconnected data store introduces risk that grows over time. Before evaluating any other features, confirm that any platform you consider can actually speak to the systems your business already runs on — otherwise the entire deployment is built on an unstable foundation that will cost you far more to fix later than it would have cost to verify upfront. Integration depth is the single most differentiating factor in this category and the one vendors are most likely to overstate during a sales process.
The Honest Answer
Most platforms offer integrations, but that word covers a very wide range of actual capabilities. Some platforms provide genuine native two-way sync with SAP, Oracle, and Microsoft Dynamics, with tested connectors maintained across version updates. Others offer a scheduled CSV export and call it an API. Before signing anything, require a live working demo of your specific ERP integration, running against your exact version of the system, pulling real product data from a test environment. If they cannot demonstrate it in that form, assume the integration does not exist in the way your operations team needs it to function. Also ask explicitly who owns integration maintenance when your ERP vendor releases an update — whether that responsibility sits with the software vendor or falls back to your IT team is a detail that matters enormously at the wrong moment.
How BrandedMark Handles It
BrandedMark connects to product data via open API, supporting standard REST and webhook-based integrations with major ERP and PLM systems. Product records — including GTIN, serial number ranges, bill-of-materials references, and warranty parameters — are ingested directly from your existing systems without requiring manual re-entry or parallel maintenance. The platform is architecturally designed to treat your ERP as the master record, not to replace it or sit beside it as an equal and competing system requiring its own governance. For manufacturers running complex multi-system environments across different production sites, regions, or subsidiaries, that design principle means your data governance policies stay intact, your IT team retains full control, and the single source of truth remains exactly where it already lives — in the systems your operations team already knows, audits, and trusts daily.
2. What Happens to Our Data If We Leave?
Why It Matters
Customer registration data, scan histories, warranty records, and product interaction data are among the most commercially valuable assets your business will accumulate once connected product infrastructure is deployed at scale. This is data you almost certainly do not have today. The question of what happens to it when — not if — you eventually switch vendors is not paranoia or premature pessimism. It is straightforward commercial due diligence that any rigorous procurement process should include. Vendor relationships end for many reasons entirely outside your control: pricing restructures, platform pivots, acquisitions, or simple deterioration in product quality over time. Ensuring your data survives that transition intact, in usable formats, without prohibitive extraction costs, is a contractual and architectural requirement that must be confirmed before you sign, not investigated under pressure after you have already decided to leave.
The Honest Answer
Vendor lock-in is a genuine and common risk in this category, not a theoretical one. Some platforms store data in proprietary formats that are technically exportable but practically unusable without custom transformation tooling. Others build QR code infrastructure using proprietary resolvers that stop working the moment you stop paying the invoice. Read every contract term related to data portability carefully, and request a demonstration of a full data export in standard formats before you sign — not after you have already decided you want to leave. The worst-case scenario plays out like this: you have registered 200,000 products, built two years of scan analytics, established real customer relationships through the platform — and you discover you cannot take any of that data without a custom extraction project that costs more than simply accepting the next renewal price increase and staying put.
How BrandedMark Handles It
Data portability is treated as a first-class platform requirement, not an edge case addressed in the exit clause of a long contract. Customer records, scan histories, and warranty registrations are exportable in standard CSV and JSON formats on demand, without requiring a support ticket submission, a formal request process, or an additional fee. The platform uses GS1 Digital Link-compliant QR codes — an open industry standard maintained by GS1 — which means your codes remain valid and resolvable through any compliant resolver even if you move to a different platform later. Your product identity infrastructure is not held hostage by the vendor relationship. That commitment is written explicitly into the contract terms you can review before you sign, so there are no ambiguities about data ownership to discover at renewal time when your leverage is lowest.
3. How Long Does Implementation Take?
Why It Matters
Every software vendor in this category describes their product as fast and easy to deploy. What they mean by that varies by approximately eighteen months of actual elapsed time when you look across the category honestly. Implementation timelines determine directly when you begin generating return on the investment you are about to make — and in a market where compliance deadlines like the EU Digital Product Passport are already set and actively moving, a slow rollout is not just a scheduling inconvenience. It is a genuine business risk that can affect your market access in regulated product categories. Asking for a realistic, clearly layered timeline breakdown during evaluation is one of the most reliable ways to test whether a vendor truly understands your operating environment or is simply optimising to close the deal before the quarter ends and move on.
The Honest Answer
Implementation complexity for connected product platforms breaks into three distinct layers that move at very different speeds. First is platform configuration — setting up product records, experience templates, and workflow logic — which is usually the fastest layer. Second is ERP and data integration, which can take anywhere from weeks to months depending on your IT team's bandwidth, your ERP system's age, and the cleanliness of your existing product data. Third is the physical rollout: updating packaging artwork and production runs to incorporate new QR codes or NFC tags, which runs entirely on your production schedule and is usually the longest lead-time item of all. Expect four to eight weeks for a focused pilot on a single product line with clean, API-accessible data. Expect three to six months for a full enterprise deployment across multiple product families and ERP systems. Any vendor quoting under two weeks for real enterprise scope is not being straight with you.
How BrandedMark Handles It
BrandedMark is designed around a phased rollout model that reflects how manufacturers of durable goods actually make decisions and manage change. The no-code Experience Designer lets your product and marketing teams configure and publish customer-facing product experiences without depending on development resources at every step. A manufacturer with clean product data accessible via API can go from a signed contract to a live customer experience in under four weeks for a well-scoped initial launch. The platform explicitly supports a soft-launch model — deploy to a single product line first, validate the experience design against real customer scan behaviour, measure outcomes, then expand to additional lines. Each expansion phase reuses the same account, templates, configurations, and integrations, so you are not rebuilding the foundation each time you extend the programme to a new product family or market.
4. Can We Brand the Customer-Facing Experience?
Why It Matters
When a customer scans your product, they should land inside your world — your visual identity, your brand tone, your designed customer journey — not a generic white-label portal with a third-party subdomain in the browser address bar, or a vendor's logo quietly visible in the page footer. For premium and mid-market brands, the quality of the post-purchase digital experience is a direct extension of the physical product itself. An off-brand, visually inconsistent digital experience communicates that the manufacturer did not prioritise this moment — which sends exactly the wrong signal to a customer who just made a deliberate purchasing decision and is now looking for validation that they chose the right product. Brand control over the post-scan experience is not an aesthetic preference or a nice-to-have refinement; it is a commercial necessity that affects repeat purchase and referral behaviour.
The Honest Answer
"Fully white-labelled" is a phrase that demands specific, detailed scrutiny during any platform evaluation rather than being accepted at face value. Some platforms allow you to upload a logo and select a primary accent colour, and then describe that as full brand control. Others provide genuine design ownership: custom domains on your own URL, custom typography, complete CSS access for layout and spacing control, and total removal of vendor branding from every customer-visible touchpoint. The gap between those two is substantial, particularly for premium brands where visual inconsistency actively damages product perception and erodes customer confidence in the purchase decision. Also probe whether you can create distinct branded experiences for different product lines or regional markets from a single platform account. A power tools range and an HVAC division may share backend infrastructure but need entirely separate visual identities, content structures, and journeys.
How BrandedMark Handles It
The Experience Designer is a fully no-code visual builder that gives brand and product teams direct, hands-on control over every element of the customer-facing experience — layout, typography, colour system, content structure, conditional logic, and post-purchase flow. Custom domain support means customers land on your own URL rather than a third-party subdomain, which matters for both brand perception and the customer's confidence that they are in the right place. There is no BrandedMark branding visible to end consumers at any point in the experience. For manufacturers managing multiple brands or distinct product ranges, you can create entirely separate experiences per product line from a single platform account — different visual themes, different customer journeys, different support content — all managed centrally by your own teams without requiring developer involvement each time a campaign or product line requires an update.
5. Does It Handle UK and EU Compliance?
Why It Matters
The EU Digital Product Passport under ESPR is not a future risk to begin planning for eventually — for many product categories, the deadlines are already confirmed and the regulatory clock is running now. Batteries and battery-powered vehicles carried firm early implementation deadlines under the European Commission's phased ESPR timeline, with textiles and electronics following by 2027. UK warranty law carries specific statutory requirements around consumer guarantees that diverge from EU consumer rights directives in ways that matter operationally. A platform that was not architected with these requirements as foundational design decisions from the outset cannot simply add compliance through a configuration change or an add-on module. Retrofitting DPP-compliant data structures onto a non-compliant architecture is an engineering project that consumes exactly the runway time you do not have when a regulatory deadline is actively approaching.
The Honest Answer
Most US-built platforms treat EU compliance as a future roadmap item or a separately purchased add-on module. If the platform was not designed with GS1 Digital Link and DPP data structures as core architecture requirements from the beginning, adding them retroactively requires genuine engineering work — not a settings toggle or a module activation. Ask specifically and directly: does the platform generate DPP-compliant data structures today, in the current shipping version — not in an upcoming release? Does it support jurisdiction-aware warranty terms so that a UK customer automatically sees the correct statutory guarantee and a German customer receives the legally appropriate commercial framing for that jurisdiction? Ask about audit trails too. DPP compliance requires versioned, auditable product data — that capability must live in the data model itself, not be patched on as a reporting layer after the underlying architecture was already finalised without it.
How BrandedMark Handles It
BrandedMark was built with GS1 Digital Link compliance and EU Digital Product Passport readiness baked into the core platform architecture from day one — not added to an existing product after ESPR was announced and demand emerged. The platform supports jurisdiction-aware warranty rules across UK, EU member states including DE and FR with correct local legal framing, US, AU, CA, JP, BR, and IN — automatically serving the right terms to the right customer based on their detected location without any manual configuration required per market. Versioned content with full audit trails is built into the underlying data model, not bolted on through a reporting interface. For manufacturers facing active DPP compliance deadlines, BrandedMark is one of the few platforms where compliance is a current shipping feature rather than a roadmap commitment dependent on future development cycles you cannot control.
6. What's the Pricing Model — Per Product, Per Scan, Per User?
Why It Matters
Pricing model structure determines cost predictability across your entire planning horizon — not just the first invoice. A per-scan model appears attractively low at modest volumes and becomes alarming when a product recall drives unexpected traffic spikes, a seasonal campaign lands harder than projected, or a viral moment sends scan volume ten times above forecast. A per-product model can balloon painfully when applied to a large catalogue spread across multiple product generations. A per-user model systematically penalises you for growing the internal team that works with the platform. The pricing structure you agree to at contract stage locks in the fundamental incentive alignment — or misalignment — of your vendor relationship for the entire term. Understanding exactly what behaviours get penalised under the model before you sign is far more valuable than negotiating a slightly better year-one rate.
The Honest Answer
We will not quote specific pricing here — those conversations belong in a direct dialogue scoped to your actual situation, not in a blog post that cannot account for your specific portfolio size, scan volumes, or geography. What we will tell you is the evaluation framework that matters. The worst pricing models in this category create perverse incentives: per-scan charges punish you for customer engagement, per-SKU charges at scale punish you for product breadth, and per-seat charges punish organisational growth. The best models align vendor revenue with your success in a predictable, forecastable way. Before signing, request a full cost model built on your actual product volumes and realistic scan rate projections. Ask explicitly what your monthly bill looks like if scan volume exceeds forecast by ten times. Ask whether compliance features — DPP, GS1, jurisdiction-aware warranty — are included or invoiced as separate add-ons once you are already committed.
How BrandedMark Handles It
BrandedMark's pricing is designed to be predictable and scale-friendly from the first focused deployment through to enterprise-wide rollout, without structural penalties for success or customer engagement. There are no per-scan charges — your customers can interact with your products as often and as deeply as they choose, and that engagement generates useful insight for your business rather than an invoice line to monitor and manage. Pricing conversations happen directly with the team and are scoped to your specific product portfolio, anticipated rollout phasing, and realistic growth projections over the full contract term. Compliance features — DPP readiness, GS1 Digital Link support, and jurisdiction-aware warranty rules across ten-plus markets — are included in the platform as standard, not separated into add-on modules that appear on the invoice after you are already mid-implementation and well past the point where switching would be practical or affordable to consider.
7. Can We Start With One Product Line and Expand?
Why It Matters
Enterprise software rollouts that begin at full organisational scale and go wrong are expensive, slow, and genuinely demoralising to unwind — and they happen more often than vendors acknowledge during a sales process. The ability to start with a genuinely contained pilot — one product family, one market, one focused use case — lets you validate the technology against real customer behaviour, build internal confidence with measurable evidence, and understand how your customers actually engage before committing your entire product catalogue. A phased approach allows your IT, operations, marketing, and customer service teams to build capability incrementally, rather than absorbing a full transformation programme while simultaneously managing normal business operations. The pilot is not a compromise or a sign of insufficient commitment; it is the safest and most reliable route to confident, fully informed, full-scale adoption.
The Honest Answer
Some platforms are architecturally designed for enterprise-wide deployment from day one, which means in practice the pilot is the full implementation — just applied to a smaller initial scope without any reduction in the surrounding complexity. Others genuinely support a modular, phased approach where you start contained, prove value against specific metrics, and expand without rearchitecting any component of the existing setup. The critical test is whether your pilot data — customer registrations, scan histories, product configurations, and experience templates — carries forward cleanly and completely when you scale up, or whether expanding to new product lines effectively means starting over. Also ask directly about the change management profile. Deploying connected product experience to one product line is a manageable project. Rolling it out across 200 SKUs, six international markets, and three separate ERP systems is a full transformation programme, and a vendor that treats those two things identically is not being honest about the effort required.
How BrandedMark Handles It
BrandedMark is explicitly designed for phased adoption, because that is how manufacturers of durable goods actually make technology investment decisions and build internal buy-in in practice. You can launch with a single product line, validate the customer experience design against real scan data from actual customers in the field, measure the outcomes that matter specifically to your business case, and then expand to additional lines — all within the same platform account, without any data migration, re-implementation work, or architectural changes required at any subsequent expansion stage. The no-code builder means extending the programme to new product lines does not create a dependency on developer availability or sprint planning cycles. Every asset from your pilot — customer registrations, scan analytics, experience templates, integration configurations, and warranty rule sets — carries forward automatically as you extend to additional product families, markets, and distribution channels.
Platform Comparison: How to Evaluate Your Options
When you're comparing platforms in this category, these are the criteria that actually differentiate them. Use this as your evaluation scorecard:
| Evaluation Criterion | Generic QR Platforms | Enterprise CX Suites | Connected Product Platforms (e.g. BrandedMark) |
|---|---|---|---|
| Serial-level product identity | Rarely | Sometimes | Yes — SGTIN/GS1 Digital Link |
| No-code experience builder | Basic | Limited | Full drag-and-drop, conditional logic |
| EU Digital Product Passport | No | Roadmap | Built-in, ESPR-compliant |
| Jurisdiction-aware warranty | No | Custom dev | 10+ jurisdictions, out of the box |
| ERP/PLM integration | Manual import | Complex, costly | Open API, bi-directional |
| Data portability | Poor | Contractual | First-class, standard formats |
| Phased rollout support | Yes | Difficult | Yes — designed for it |
| Per-scan pricing risk | High | N/A | No per-scan charges |
| White-label / custom domain | Partial | Yes | Full, no vendor branding |
| Warranty + commerce + support | Separate tools | Multiple modules | Unified platform |
Competitors and Alternatives
The connected product space has several credible platforms worth knowing before finalising your shortlist. Understanding the landscape sharpens your questions in every demo.
Registria focuses on warranty registration and product ownership, with strong CRM integration and a solid track record across consumer goods. Probe DPP readiness and the depth of no-code experience customisation beyond the warranty flow.
Brij centres on QR-triggered digital experiences for consumer brands and packaging activation. Clean product; manufacturers with complex compliance requirements or deep ERP integration needs should investigate those areas specifically.
Layerise emphasises onboarding flows and post-purchase support content, with traction in consumer electronics. Evaluate the experience builder carefully and probe serialisation depth and compliance coverage for regulated categories.
BrandedMark's position is as a unified Product OS — covering product identity, warranty, compliance, post-purchase support, and commerce in a single platform built for manufacturers of durable goods. The right choice depends on your specific requirements. The comparison table above provides a structured evaluation framework.
For a broader view of the category, see our piece on what a connected product platform actually is.
Internal Links: Further Reading
Before finalising your evaluation, these articles are worth reading:
- What Is a Connected Product Platform? — a category definition that clarifies what you're actually buying and what problems it solves.
- Beyond Checkout: The Post-Purchase Experience Opportunity — how leading brands are rethinking what happens after the sale, and why it's where the real value sits.
- The Cost of Disconnected Products — a framework for calculating what you're actually losing today by not having connected product infrastructure.
Frequently Asked Questions
How long does it typically take to get a connected product platform live?
For a focused pilot on a single product line with clean product data available via API, a realistic timeline is 4–8 weeks from signed contract to live customer experience. Full enterprise rollouts across multiple product families, markets, and ERP integrations typically run 3–6 months. The physical packaging change — printing new QR codes or adding NFC tags — runs on your production schedule and is usually the longest lead-time item. Platforms that promise deployment in days for enterprise clients are glossing over the integration and change management work that makes a rollout actually succeed.
What data does a connected product platform actually collect, and who owns it?
A properly implemented platform collects product-level data (scan events, scan location, device type), customer data (warranty registrations, contact details, preferences), and engagement data (support content accessed, spare parts browsed, troubleshooting paths taken). All of this data should be owned by the manufacturer — not the platform vendor. Before signing, confirm you can export all customer and product data in standard formats on demand, and check whether your QR codes use an open standard (like GS1 Digital Link) or a proprietary resolver that breaks if you switch vendors.
Is the EU Digital Product Passport mandatory for our products, and when?
The EU Digital Product Passport is being rolled out under the Ecodesign for Sustainable Products Regulation (ESPR) in waves by product category. Batteries and battery-powered vehicles were among the first categories with firm deadlines; textiles, electronics, and construction products follow. If you manufacture and sell into the EU market, you should be actively tracking the timeline for your specific product category — it is not a speculative future requirement. The DPP requires structured, machine-readable product data linked to each product unit, which is exactly what a serial-level connected product platform provides. Waiting until the deadline is announced to start evaluation is leaving insufficient runway.
Ready to Ask These Questions?
The best way to test how a vendor handles these questions is to ask them directly — in a demo, before significant evaluation time or internal political capital is invested. A vendor that deflects integration questions with roadmap promises, data portability questions with legal vagueness, or pricing questions with "it depends" and no specifics is showing you exactly how they will behave when you have a problem and they already have your signature on a contract.
BrandedMark is built for manufacturers serious about the post-purchase relationship — not ticking a compliance box or adding a QR code because a competitor did. The platform exists because manufacturers of durable goods deserve software that treats product identity, warranty, compliance, and customer experience as a unified problem rather than four separate tools to integrate and maintain. If you are evaluating platforms and want direct answers applied to your actual situation, request a demo and bring this list.