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, warranty terms. Your PLM holds the engineering records. If a new platform can't connect to these systems, you're looking at duplicate data entry, manual syncs, and the kind of data drift that causes customer service nightmares six months post-launch.
The Honest Answer
Most platforms offer integrations — but "integration" means very different things. Some offer native two-way sync with SAP, Oracle, and Microsoft Dynamics. Others offer a CSV export and call it an API. Before you sign anything, ask for a working demo of the specific integration you need, with your version of the ERP, pulling live product data. If they can't demo it, it doesn't exist in the way you need it to.
Also ask: who owns the integration maintenance? When SAP releases an update, does your vendor update the connector? Or do you own that problem?
How BrandedMark Handles It
BrandedMark connects to product data via open API, supporting standard webhook and REST-based integrations with major ERP and PLM systems. Product records — including GTIN, serial number ranges, and warranty parameters — can be ingested from your existing systems, so there's no parallel data universe to manage. For manufacturers with complex multi-system environments, the platform's architecture is designed to treat your ERP as the master record, not replace it.
2. What Happens to Our Data If We Leave?
Why It Matters
Customer registration data, scan histories, warranty records, product interaction data — this is some of the most valuable data your business will ever own. It's data you almost certainly didn't have before. The question of what happens to it when (not if) you switch vendors is not paranoia. It's due diligence.
The Honest Answer
Vendor lock-in is real in this category. Some platforms store your data in proprietary formats that are technically exportable but practically unusable. Others build the QR code infrastructure in a way that means your existing codes break the moment you stop paying. Read the contract terms on data portability carefully. Ask for a full data export in standard formats (CSV, JSON) before you sign — not after you want to leave.
The worst-case scenario: you've registered 200,000 products, built customer relationships, and generated two years of scan analytics — and you can't take any of it with you without a custom extraction project that costs more than staying.
How BrandedMark Handles It
Data portability is a first-class concern. Customer records, scan histories, and warranty registrations are exportable in standard formats on demand. The platform uses GS1 Digital Link-compliant QR codes, which are an open industry standard — your codes remain valid and resolvable even if you move to a different resolver. Your data is yours. That's not a marketing claim; it's in the contract.
3. How Long Does Implementation Take?
Why It Matters
Every software vendor says "quick to deploy." What they mean varies by about 18 months. Implementation timelines directly affect when you start seeing ROI — and in a category where compliance deadlines (looking at you, EU Digital Product Passport) are real and imminent, a slow rollout is a business risk, not just a scheduling inconvenience.
The Honest Answer
Implementation complexity for connected product platforms breaks down into three layers: (1) the platform configuration itself, (2) the ERP/data integration, and (3) the physical rollout — updating packaging to include the new QR codes or NFC tags. The platform layer is usually fastest. Integration can take weeks to months depending on your IT team's availability and your ERP's age. Physical rollout is entirely on your production schedule.
Expect 4–8 weeks for a well-scoped initial launch on a single product line with clean data. Expect 3–6 months for a full enterprise rollout with complex integrations and multiple product families. Anyone quoting less than two weeks for a real enterprise deployment is telling you what you want to hear.
How BrandedMark Handles It
BrandedMark is designed for a phased rollout model. The no-code Experience Designer means your product and marketing teams can configure and publish product experiences without waiting on development resources. A manufacturer can go from signed contract to live product experience in under four weeks for a focused launch — often faster if product data is clean and available via API. The platform also supports a soft launch model, where you deploy to a single product line first, validate the experience, then expand.
4. Can We Brand the Customer-Facing Experience?
Why It Matters
When a customer scans your product, they should land in your world — your visual identity, your tone, your customer journey. Not a generic white-label portal with someone else's brand peeking through in the footer, or worse, the software vendor's logo front and centre.
The Honest Answer
"Fully white-labelled" is another phrase that requires scrutiny. Some platforms let you add your logo and change a primary colour. Others give you genuine design control — custom domains, custom fonts, full CSS access, complete removal of vendor branding. The difference matters enormously for premium brands, where an off-brand support experience actively damages the perception of the product.
Also check: can you create different branded experiences for different product lines or markets? A power tools brand and an HVAC brand might share infrastructure but need completely different visual identities. Gartner research on post-purchase experience platforms consistently identifies brand consistency as a top-three evaluation criterion for enterprise software buyers in this category.
How BrandedMark Handles It
The Experience Designer is a fully no-code visual builder that gives brand and product teams direct control over the customer-facing experience. Custom domain support means customers land on your URL, not a third-party subdomain. There's no BrandedMark branding visible to end consumers. For manufacturers with multiple brands or product ranges, you can create distinct experiences per product line from a single platform account — different visual themes, different journeys, different content, all managed centrally.
5. Does It Handle UK and EU Compliance?
Why It Matters
The EU Digital Product Passport (DPP) under ESPR is not a future problem — for many product categories, it's a present one, with phased deadlines already in motion. According to the European Commission's ESPR implementation timeline, batteries and battery-powered vehicles were among the first categories with firm deadlines, with textiles and electronics to follow by 2027. UK warranty law has specific requirements around consumer guarantees that differ from EU consumer rights directives. If your platform isn't built for these requirements from the ground up, you're either going to be scrambling to retrofit compliance or paying for a separate compliance layer.
The Honest Answer
Most US-built platforms treat EU compliance as an afterthought or an add-on module. If the platform wasn't designed with GS1 Digital Link and DPP data structures in mind from day one, adding them later is an engineering project, not a configuration task. Ask specifically: does the platform generate DPP-compliant data structures? Does it support jurisdiction-aware warranty terms — so a UK customer sees a 24-month statutory guarantee and a German customer sees a 24-month commercial guarantee with the right legal framing?
Also ask about audit trails. DPP compliance requires versioned, auditable product data. Can the platform demonstrate that?
How BrandedMark Handles It
BrandedMark was built with GS1 Digital Link compliance and EU Digital Product Passport (ESPR) readiness as core architecture requirements, not bolt-ons. The platform supports jurisdiction-aware warranty rules across UK, EU (including DE and FR), US, AU, CA, JP, BR, and IN — so the right terms are served to the right customer automatically. Versioned content with full audit trails is built in. For manufacturers facing DPP deadlines, BrandedMark is one of the few platforms where compliance is a feature, not a future roadmap item.
6. What's the Pricing Model — Per Product, Per Scan, Per User?
Why It Matters
Pricing model determines your cost predictability. A per-scan model sounds attractive at low volumes and terrifying when a product goes viral or a recall drives a million scans in a week. A per-product model can balloon if you have a large catalogue. A per-user model penalises you for growing your team.
The Honest Answer
We won't quote specific numbers here — pricing conversations belong in a sales call, not a blog post. But we will tell you what to look for. The worst pricing models are the ones that create perverse incentives: punishing you for customer engagement (per scan), punishing you for product breadth (per SKU at scale), or punishing you for organisational growth (per seat). The best models align the vendor's revenue with your scale and success in a predictable, plannable way.
Ask for a full cost model based on your actual product volumes and expected scan rates. Ask what happens to your bill if scan volume is 10x higher than forecast. Ask whether compliance features are included or priced as add-ons. And always ask what the contract renewal terms look like — year-one pricing that jumps 40% at renewal is a common trap.
How BrandedMark Handles It
BrandedMark's pricing is designed to be predictable and scale-friendly. We don't charge per scan — your customers can engage with your products without that engagement becoming a cost centre. Pricing conversations happen directly with the team, scoped to your specific product portfolio and rollout plan. Compliance features (DPP, GS1, jurisdiction-aware warranty) are not add-ons — they're included.
7. Can We Start With One Product Line and Expand?
Why It Matters
Enterprise software rollouts that start big and go wrong are expensive. The ability to start with a contained pilot — one product family, one market, one use case — lets you validate the technology, build internal confidence, and learn what your customers actually do before committing the entire product catalogue.
The Honest Answer
Some platforms are architected for enterprise-wide deployment from day one, which means the pilot is actually the full implementation. Others genuinely support a modular, phased approach where you can start small, prove value, and expand without rearchitecting anything. The key question is whether your pilot data — customer registrations, scan histories, product configurations — carries forward cleanly when you expand, or whether you're effectively starting over.
Also ask: what does the internal change management look like? Adding a connected product experience to one product line is a manageable project. Rolling it out across 200 SKUs, six markets, and three ERP systems is a transformation programme. A vendor that doesn't distinguish between these two things isn't being honest about the effort involved.
How BrandedMark Handles It
BrandedMark is explicitly designed for phased adoption. You can launch with a single product line, validate the experience, measure the outcomes, and expand — all within the same platform account, with no data migration or re-implementation required. The no-code builder means expanding to new product lines doesn't require developer time. Everything from your pilot — customer registrations, scan analytics, experience templates — scales forward as you expand.
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 and post-purchase experience space has matured considerably. A few platforms worth knowing:
Registria is an established player focused on warranty registration and product ownership, with a strong track record in consumer goods. Their strength is in warranty workflow and CRM integration; manufacturers evaluating them should ask about DPP readiness and the no-code experience layer.
Brij approaches the space primarily through QR-triggered digital experiences, with a focus on consumer brands and packaging activation. They've built a clean consumer-facing product; manufacturers with complex compliance requirements or deep ERP integration needs should probe those areas specifically.
Layerise offers product experience management with a strong emphasis on onboarding flows and support content, particularly popular in the consumer electronics space. Worth evaluating for the experience builder; ask about serialisation depth and compliance coverage.
BrandedMark's positioning is as a unified Product OS — covering identity, warranty, compliance, support, and commerce in a single platform built specifically for manufacturers of durable goods. The right platform depends on your specific combination of requirements; the table above is a starting framework.
For a broader view of what the category covers, 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 you've invested significant evaluation time. A vendor that deflects, hedges, or gives you vague answers on integration, data portability, pricing structure, or compliance is showing you something important.
BrandedMark is built for manufacturers who are serious about the post-purchase relationship — not just ticking a compliance box or adding a QR code to packaging. If you're evaluating platforms and want straight answers, request a demo and bring this list.