Contract & Liability · 12 min read
QR Code Subscription Disputes: Who Pays After Delivery?
A design project is delivered. The QR code works. Then 30 days later: a surprise subscription bill. Vendor says "customer should pay." Customer says "it was part of my deliverable." How to avoid this contract dispute.
The scenario repeats across design agencies, print shops, and software vendors: A QR code is added to a deliverable as a "trackable element" or "interactive feature." The project is invoiced, delivered, and closed. Everyone's happy—until the first subscription renewal notice arrives. Then the blame game starts.
The Core Problem
QR code platforms are priced as SaaS subscriptions: $10–300/month depending on features. But a QR code is often delivered as part of a one-time project. The mismatch creates ambiguity: Is the QR cost a project expense (vendor pays)? Or a customer asset cost (customer pays)? Without explicit contract language, this becomes a dispute.
Real Scenarios Where This Becomes a Problem
Scenario 1: The Vendor Covers It (Until They Don't)
A design agency builds a website for a client. The site includes QR codes linking to PDF menus, downloadable assets, etc. The agency sets up the QR codes on their own subscription account (convenience, they use it for other clients). The site launches, everything works. The client is happy.
Two years later: The agency loses the contract with that client. They delete the QR code account to save costs. The client's website is now broken—all QR codes dead. The client calls: "Why did you break my site?" The agency says: "Our contract was for design, not ongoing QR hosting." The client says: "The QR codes were part of the delivered product—you broke it."
Reality: The contract was silent on QR ownership and subscription costs. Dispute ensues.
Scenario 2: The Surprise Bill
A print shop embeds QR codes on product packaging as a value-add feature (not explicitly itemized in the quote). They use a free QR generator to create codes, print 100,000 units. The customer's product ships and sells well.
Six months later: The free QR service sends a notice—free tier is being deprecated. Upgrade to paid ($35/mo) or codes die. The print shop doesn't have a relationship with this customer anymore (one-off project). Codes silently die. Customers scan QR codes, nothing happens. Customer complaints flood in. The original print shop receives calls: "Your QR codes don't work!" Print shop: "We don't manage the codes anymore—ask the platform."
Reality: No one owns the renewal obligation. Codes die. Customer brand suffers.
Scenario 3: The Vendor Lock-In Dispute
A software vendor adds QR code tracking as a feature in their product (e.g., equipment labeling, asset management system). Customers get codes "included" with their subscription. Then the vendor notices: customers don't pay attention to the QR feature, so why not monetize it separately?
The vendor announces: QR codes are now a separate $50/month add-on. Existing customers who embedded QR codes in their workflows receive a "sunrise" notice: "Your codes will stop working unless you upgrade." Customers feel trapped. Lawsuit threats emerge: "You changed the contract."
Reality: The original contract said "QR codes included" but didn't specify in writing, so the vendor's unilateral change is hard to contest.
Why Contract Ambiguity Exists
QR codes are new enough that they weren't common in standard contracts 10 years ago. Today, they're often added to projects as a "nice-to-have" feature without clear ownership language. Typical contract gaps:
- ✗No line-item cost: "QR codes" appear in scope-of-work but not in the pricing breakdown. Are they free? Is the vendor absorbing costs?
- ✗No ownership clause: Who owns the QR codes after delivery? The vendor's account? The customer's account? Transferable?
- ✗No post-delivery responsibility: If the QR platform changes or shuts down, whose problem is it?
- ✗No subscription disclosure: Customers don't know the QR codes they're using are on a $35/mo subscription tied to the vendor's account.
Who Pays? The Legal Default
In the absence of clear contract language, courts look to:
- Who benefits from the QR code? If the customer's product relies on the QR code, the customer may be liable for upkeep.
- Who has access/control? If the vendor controls the QR account and can unilaterally change terms, the customer may have a breach claim.
- Industry standard practice. Courts look at what's "typical" in the industry—and since this is murky, disputes get expensive.
Result: Disputes often settle via negotiation or lawyers, not clear contract language. Whoever can afford litigation usually wins. This is a bad outcome for everyone.
How to Avoid QR Subscription Disputes
The solution is contractual clarity. Here's sample language for different scenarios:
Option A: Vendor Pays & Owns (Risky for Vendor)
"Deliverables include [X] QR codes for [purpose]. Vendor is responsible for all QR platform subscriptions, hosting, and uptime through [date]. After [date], QR codes are transferred to Customer account at no cost, and Customer assumes subscription responsibility."
Risk: Vendor is locked into paying subscriptions indefinitely, or codes die post-handoff.
Option B: Customer Owns & Pays (Standard)
"Deliverables include [X] QR codes with Customer-owned perpetual licenses. QR codes are delivered to Customer-controlled account with full management access. Vendor retains no obligation for QR platform subscription renewal or uptime beyond [date]. Customer is solely responsible for platform subscription and redirection maintenance."
Benefit: Clear ownership. Customer controls codes. Vendor has no ongoing liability.
Option C: One-Time Payment (Best Practice)
"Deliverables include [X] permanent QR codes ($49 one-time per code). QR codes are delivered as Customer-owned digital assets with perpetual, renewable licenses. No recurring subscription fees apply. Customer receives dashboard access and full transfer rights. No platform shutdown risk—permanent codes remain active for the product lifespan."
Benefit: Zero ambiguity. One-time cost. Customer owns forever. No recurring dispute risk.
The Real Cost of Ambiguity
QR subscription disputes aren't just legal headaches—they damage customer trust and vendor reputation:
- •Customer churn: Customers feel "locked in" or "tricked" by surprise subscription bills. They switch vendors next project.
- •Broken trust: If QR codes die because of subscription lapses, customers blame the vendor: "You broke my product."
- •Referral damage: Customers tell peers: "Don't use [vendor]—their QR codes died after project ended."
- •Legal costs: Disputes that could be avoided through clear language cost lawyers $500–5,000 to resolve.
Why Permanent QR Codes Solve This Entirely
Permanent QR codes ($49 one-time per code) eliminate every dispute:
Subscription Model Problem
- ✗ Ambiguous: Who pays?
- ✗ Recurring: Costs surprise customers
- ✗ Lock-in: Codes die if subscription lapses
- ✗ Dispute-prone: Contracts need lawyers
Permanent QR Solution
- ✓ Clear: One-time cost, customer owns forever
- ✓ No surprises: No recurring bills
- ✓ No lock-in: Customer owns codes perpetually
- ✓ Dispute-proof: Simple contract language
The easiest way to avoid QR subscription disputes is to never have a subscription. One-time payment means clear ownership from day one.
Sample Contract Language for Permanent QR Codes
SOW Line Item:
"Deliverables: [X] permanent QR codes ($49 one-time per code). Total: $[amount]. QR codes are Customer-owned perpetual digital assets with unlimited scans and edits. No renewal fees. No expiration date."
MSA Clause:
"Permanent QR codes are delivered as one-time-purchase digital assets. Full ownership and perpetual license rights transfer to Customer upon invoice payment. Vendor retains no ongoing hosting obligation, liability, or renewal responsibility post-handoff."
Scope Clarification:
"QR code edits post-delivery are Customer responsibility. Vendor provides one-time training and documentation only. Customer assumes full control and liability for code content and destination URLs after delivery date."
Why This Matters for Your Next Project
If you're quoting a project with QR codes:
- →Line-item the QR cost explicitly. Don't bury it in scope or assume the customer understands you're using a subscription platform.
- →State ownership in writing. Who controls the codes post-delivery? Transferable? Editable by the customer?
- →Use permanent QR codes if you want zero ambiguity. One-time cost, customer owns forever, no disputes.
- →Include a handoff date in scope. When does vendor responsibility for QR end? Make it explicit.
Related reading
Frequently Asked Questions
Should QR code costs be in the original contract?
Yes, explicitly. If a QR code is part of the deliverable, the renewal/subscription obligation should be stated upfront. Buried in terms-and-conditions is how disputes start. Line-item it in the SOW.
Who owns the QR code after project delivery?
If not explicitly stated, this becomes a dispute point. Best practice: Customer owns the code post-delivery. Vendor owns the hosting but customer owns the license/usage rights. With permanent QR codes, this is automatic—customer owns it forever after purchase.
What happens if a vendor doesn't pay their QR subscription?
If the vendor is paying for the subscription on the customer's behalf without disclosure, the code dies when the vendor's payment lapses. Customer's printed assets become broken. This is a common scenario that triggers disputes.
Can a customer be locked into a QR platform?
Yes. If a customer's QR codes are tied to the vendor's account (not transferable), the customer can't switch vendors or self-manage the codes. They're locked in until they reprint. Permanent QR codes eliminate this by giving customers perpetual ownership.
What's the best way to avoid QR subscription disputes?
One-time payment QR codes. No ambiguity. No recurring bills. No vendor lock-in. Clear ownership from day one. Include language in your SOW: 'QR codes are delivered as permanent, one-time-payment assets with customer-owned perpetual licenses.'