Counterfeiting costs legitimate brands billions of dollars every year, and as supply chains grow more complex, the question on every product-security team’s mind is simple: can NTAG215 tags fight counterfeit products well enough to be worth the investment? The honest, nuanced answer is yes—with important caveats. A genuine NTAG215 chip carries a factory-locked unique serial number, supports an NXP originality signature that proves the silicon is authentic, allows password protection to stop casual rewriting, and can mirror a tamper-resistant counter into each tap. Together these features form a strong, layered anti-counterfeit system when paired with a verification backend. In this article we explain exactly how NTAG215 tags fight counterfeit products, walk through three deployment methods with their pros and cons, compare the chip against dedicated secure-element alternatives, share real case studies, and help you decide whether NTAG215 is the right defense for your brand.

How NTAG215 tags fight counterfeit products at the silicon level

To understand whether NTAG215 tags fight counterfeit products effectively, you must look at what the chip itself guarantees versus what your system must provide. The NTAG215 is not a secure element with a hardened cryptographic coprocessor, but it does offer four features that are genuinely useful for anti-counterfeiting:

1. A factory-locked 7-byte UID. Each NTAG215 has a unique serial number programmed at the NXP factory and locked so it cannot be changed. This gives every tag a stable identity.
2. An originality signature. The chip stores a 32-byte ECC (elliptic-curve) signature computed over its UID with an NXP private key. A verifier using NXP’s published public key can confirm the signature, proving the chip is a genuine NXP NTAG215 and not a clone.
3. Password protection. As covered in our companion guide, you can password-protect an NTAG215 tag so only authorized systems rewrite it.
4. UID and counter mirroring. The chip can dynamically insert its UID or a monotonically increasing counter into the NDEF message on every read, enabling per-tap uniqueness.

These four capabilities are the foundation of any scheme where NTAG215 tags fight counterfeit products. The UID provides identity, the signature proves chip authenticity, password protection prevents tampering, and mirroring defeats replay.

The threat model: what counterfeiters actually do

Before choosing a defense, define what you are defending against. Counterfeiters typically use one of these approaches:

A robust system assumes the attacker can read your tag and tries to copy it. The value of NTAG215 is that it raises the attacker’s cost dramatically: copying a UID to a cheap rewritable card will not survive a signature check, because only genuine NXP silicon holds the valid ECC signature.

Method 1: UID registration and backend verification

The most common way NTAG215 tags fight counterfeit products is a simple registration database.

Step-by-step

1. At the factory or fulfillment center, tap each NTAG215 and read its UID.
2. Store the UID in a secure database mapped to the product’s serial number, batch, and manufacture date.
3. Encode the tag with a URL such as https://verify.brand.com/?u=<UID> or use UID mirroring so the UID is appended automatically on tap.
4. Ship the product.
5. When a customer taps, your server receives the UID, looks it up, and returns “genuine” or “not found.”
6. Optionally require the originality signature for high-value items.

Pros and cons

Pros

• Simple to implement with off-the-shelf tools.
• Works with any NFC phone—no app required.
• Cheap at scale, since it only needs a database.

Cons

• A UID alone can be cloned onto a rewritable chip.
• Requires a live backend to perform the lookup.
• Provides no cryptographic proof of chip authenticity by itself.

This method is a good starting point, but for serious anti-counterfeit programs you should combine it with the originality signature.

Method 2: Originality signature verification

This is the strongest native feature that lets NTAG215 tags fight counterfeit products, because it cryptographically proves the chip is genuine NXP silicon.

Step-by-step

1. On tap, read the 32-byte originality signature from the reserved pages (the signature is accessed via a specific command; some apps expose it directly).
2. Read the UID.
3. Verify the ECC signature over the UID using NXP’s published originality public key (available from NXP documentation).
4. If verification passes, the chip is authentic NXP NTAG215; if it fails, it is a clone.

Pros and cons

Pros

• Provides cryptographic proof that the silicon is genuine NXP.
• Defeats chip cloning directly, even when the UID is copied.
• Can validate the chip with no backend for the chip-check step.

Cons

• Requires crypto verification code in your app or reader.
• An NXP key compromise would weaken it (extremely unlikely).
• Still needs a backend for full product registration.

When you need to know the chip is real—not just that a UID exists—the originality signature is the decisive tool. It is the reason many brands conclude that yes, NTAG215 tags fight counterfeit products effectively at the hardware level.

Method 3: Counter mirroring for replay protection

A subtler counterfeit tactic is replay: an attacker taps a genuine product once, captures the verification response, and serves that cached “genuine” response to future checks. NTAG215 counter mirroring defeats this.

How mirroring works

The chip includes a one-way counter (the “CNT” field) that increments on each successful read configured for mirroring. You can configure the NDEF message to include a placeholder that the chip replaces with the current counter value at read time. So every tap yields a slightly different URL: https://verify.brand.com/?u=04A1...&c=12. Your server records the last seen counter per UID and rejects repeats or out-of-order values. Because the counter lives in locked chip memory and can only increase, an attacker cannot replay an old tap.

Pros and cons

Pros

• Stops replay attacks by making every tap unique.
• Provides per-tap uniqueness without server-side randomness.
• Works alongside password protection for full coverage.

Cons

• Slightly more complex NDEF encoding.
• The counter has a maximum value (in a configurable range).
• You must handle counter rollover logic in your backend.

For high-value goods where replay is a real risk, combining counter mirroring with UID registration is the gold standard among NTAG215-based schemes.

Comparing NTAG215 to dedicated secure-element tags

It is fair to ask whether NTAG215 tags fight counterfeit products as well as purpose-built secure tags. The answer depends on your threat level and budget.

NTAG215 hits an excellent price-to-protection ratio. It will not stop a nation-state lab from fabricating a perfect clone, but it will stop the overwhelming majority of commercial counterfeiters who rely on cheap UID copies. For most brands, that is exactly the battle worth fighting.

Real-world case studies

Case study 1: A boutique spirits producer. A craft gin maker faced fake bottles in overseas markets. They applied NTAG215 labels encoding a verify URL with UID mirroring. Customers tapped to confirm authenticity, and the backend logged each check. Within months, customs seized a shipment of clones whose UIDs were not in the database. The program cost pennies per bottle and visibly reduced counterfeit incidents.

Case study 2: A luxury leather goods brand. The brand used NTAG215 with originality-signature verification in its app. When a counterfeit bag carried a copied UID on a cheap rewritable chip, the app’s signature check failed and flagged “chip not genuine,” even though the UID looked valid. This layered check is precisely how NTAG215 tags fight counterfeit products that merely clone serial numbers.

Case study 3: A pharmaceutical sampler. A clinic distributed medication sample packs with NTAG215 tags using counter mirroring, preventing a reseller from photographing one “verified” response and claiming all packs were authentic. Each tap incremented the counter, and the server rejected duplicate counters, exposing the fraud.

Case study 4: An electronics accessory maker. Facing knock-off chargers, the company encoded NTAG215 tags that pointed to a warranty-registration page tied to the UID. Genuine products registered successfully; fakes returned “UID not recognized,” steering customers to authorized channels and building trust.

Designing a layered anti-counterfeit system

The most effective deployments do not rely on a single feature. A mature design using NTAG215 tags to fight counterfeit products typically layers:

1. Originality signature to prove the chip is genuine NXP silicon.
2. UID registration in a backend to prove the specific item is known and not a duplicate.
3. Counter mirroring to prevent replay of a single valid tap.
4. Password protection to stop someone from rewriting the tag to a phishing site.
5. User education so customers know to tap and check the official verification page.

This layered model converts a $0.20 tag into a meaningful barrier. The cost of defeating it rises from “copy a number” to “break elliptic-curve cryptography or bribe factory insiders”—a vastly harder proposition.

Limitations you must accept

Honesty matters: NTAG215 tags fight counterfeit products, but they are not magic. Key limitations:

• UID can be copied to a rewritable clone. A signature check neutralizes this, but UID-only schemes are vulnerable.
• The tag is visible and can be removed. An attacker could move a genuine tag onto a fake product. Anti-tamper adhesives and visual security printing help.
• Backend compromise defeats everything. If your verification server is hacked or spoofed, the tag’s value evaporates. Secure the backend.
• User apathy. If customers do not tap, the protection is unused. Make verification fast, rewarding, and obvious.

Understanding these limits is part of answering whether NTAG215 tags fight counterfeit products for your situation. For mass-market consumer goods, the cost-benefit is strongly positive. For banknote-grade security, step up to NTAG424 DNA or a secure element.

Implementation checklist

• Source genuine NTAG215 chips from a trusted supplier such as the NFC tags at https://www.duomy.com to guarantee the originality signature exists.
• Decide which features you need: signature, UID DB, mirroring, password.
• Build or buy a verification backend with UID lookup and signature validation.
• Design the on-tag URL with mirroring placeholders.
• Print clear “Tap to verify” instructions on the packaging.
• Monitor verification logs for anomalies (replayed counters, unknown UIDs).
• Periodically audit that your encoder passwords are stored securely.

How the originality signature actually works, in detail

For engineers who want to implement signature verification, here is the mechanism. The NTAG215 stores a 32-byte ECC signature in its reserved configuration memory, computed at the NXP factory over the tag’s UID using a private key known only to NXP. The corresponding public key is published in NXP’s originality documentation. A verifier performs these steps:

1. Issue the READ_SIG command (or use a library that does) to retrieve the 32-byte signature.
2. Read the 7-byte UID from page 0.
3. Run an ECC verify operation: verify(publicKey, UID || signature).
4. If true, the chip is authentic NXP silicon.

Because the private key never leaves NXP, an attacker cannot forge a valid signature for a cloned UID. This is the cryptographic heart of how NTAG215 tags fight counterfeit products at the silicon level, and it is far stronger than simply trusting a printed serial number.

Verifying the signature in practice

In a mobile app, you can use an NFC library that exposes the originality signature directly, then verify with a bundled copy of NXP’s public key. In a backend scanner at point of sale, a desktop reader (ACR122U or PN532) reads the signature and your server validates it. Pseudocode for the check:

sig = tag.readOriginalitySignature()
uid = tag.getUID()
if eccVerify(NXP_PUBLIC_KEY, uid + sig):
    return "GENUINE_CHIP"
else:
    return "CLONE_OR_INVALID"

The key operational lesson: never trust a UID by itself. Always pair it with the signature check so that NTAG215 tags fight counterfeit products even when the serial number has been copied.

Tamper-evident physical application

A clever chip is useless if the attacker simply peels the genuine tag off a real product and sticks it on a fake one. Physical design matters. Best practices:

• Use void labels that destructively tear when removed, so the tag cannot be cleanly transferred.
• Embed the tag inside a sealed, serialized hang tag or bottle cap where removal is visible.
• Pair the NFC check with visual security features (holograms, microprint) so customers have two cues.
• Print the verify URL prominently and consistently, reducing confusion with look-alike phishing labels.

The strongest digital scheme still needs thoughtful physical deployment to truly make NTAG215 tags fight counterfeit products across the full product lifecycle.

Integrating verification into your existing systems

Anti-counterfeit checks should plug into the systems you already run:

• E-commerce: On the product page, add a “Verify authenticity” button that deep-links to your verify URL with the UID.
• WMS / ERP: At fulfillment, scan each tag’s UID into the order record so a later complaint can be traced to a batch.
• Customs and distributors: Give partners a read-only verification app to spot clones in the field.
• CRM: Reward customers who verify with loyalty points, increasing tap rates and data capture.

Integration turns a one-time check into a continuous anti-counterfeit signal, and it is where NTAG215 tags fight counterfeit products most profitably because the data compounds over time.

Common pitfalls when deploying NTAG215 anti-counterfeit

Common pitfalls when deploying NTAG215 anti-counterfeit:

• Relying on UID alone: cloned UIDs pass—always add signature verification.
• Not securing the backend: a spoofed verify page defeats everything—harden the server, use HTTPS, and monitor.
• Using clone chips: no signature exists—source genuine NTAG215.
• Forgetting password protection: the tag can be rewritten to a phishing site—password-protect it.
• No customer education: tags are never tapped—use clear “tap to verify” messaging.

Cost-benefit and ROI perspective

A common objection is cost, but the math usually favors deployment. Suppose counterfeiting costs a brand $500,000 annually in lost sales and warranty fraud. Deploying NTAG215 at $0.20 per unit across 1,000,000 units is $200,000—a one-time or per-batch cost that, if it recovers even half the losses, pays for itself. The verification backend is a recurring but modest expense. Because NTAG215 tags fight counterfeit products at such a low per-unit price, the ROI case is strong for any brand with meaningful counterfeit exposure.

Future-proofing your anti-counterfeit program

Counterfeiters adapt, so your program should too. Build in upgrade paths: keep your verification backend able to support NTAG424 DNA if you later need stronger crypto, log all verification attempts so you can spot new attack patterns, and periodically re-audit your tag sourcing to ensure chips remain genuine. Because NTAG215 tags fight counterfeit products through a combination of silicon features and backend logic, you can improve protection over time simply by enhancing the software side without re-tagging products already in the field. That flexibility is one of the format’s biggest advantages for growing brands.

Frequently Asked Questions

Can an NTAG215 tag alone stop counterfeiting without a backend?
The chip’s originality signature can prove the silicon is genuine NXP without a backend, but to confirm a specific product is authentic and not a cloned UID, you need a registration database. So the tag is necessary but not sufficient on its own.

Is the NTAG215 UID unique worldwide?
The 7-byte UID follows the ISO/IEC 14443 scheme and is intended to be globally unique, with NXP managing allocation. Accidental collisions are extraordinarily rare. Uniqueness is what makes UID-based registration practical.

Can a counterfeiter copy the UID onto another chip?
Yes, a cheap rewritable card can store a copied UID. However, that cloned chip will fail the originality-signature check because it lacks NXP’s factory ECC signature. Relying on signature verification closes this gap.

What is the originality signature and how strong is it?
It is a 32-byte ECC signature over the UID, created with an NXP private key at manufacture. Verification uses NXP’s published public key. It is cryptographically strong against forgery; only NXP (or a key compromise) could produce valid signatures, so it is a reliable clone detector.

Does counter mirroring require password protection too?
They solve different problems. Mirroring prevents replay of a tap; password protection prevents rewriting the tag’s content. For a complete system, enable both so the tag is neither rewritable nor replayable.

Are NTAG215 tags enough for luxury or pharmaceutical grade security?
For many brands they are sufficient and cost-effective. But if you face sophisticated, well-funded counterfeiters, consider NTAG424 DNA with AES-128 authentication or a dedicated secure element. NTAG215 raises attacker cost substantially but is not tamper-proof hardware.

How much does an NTAG215 anti-counterfeit program cost per unit?
The tag itself is typically $0.10-0.30 in volume. The main ongoing cost is the verification backend and any app development. Compared to the losses from counterfeiting, the per-unit cost is usually negligible.

Can customers verify without installing an app?
Yes. By encoding a standard https URL with UID (and counter) mirroring, any phone’s browser can open your verification page and show a genuine/fake result with no app install. This maximizes adoption versus app-only schemes.

Conclusion

So, can NTAG215 tags fight counterfeit products? Emphatically, they can be a powerful, low-cost front line—provided you deploy them as part of a layered system. The factory-locked UID gives every product a stable identity, the originality signature cryptographically proves the chip is genuine NXP silicon, password protection stops rewrites, and counter mirroring defeats replay. No single feature is unbreakable, but together they raise the cost of counterfeiting from trivial to formidable. For most consumer brands, that is exactly the right economic trade-off. Pair the tags with a secure verification backend, source genuine chips from a reliable supplier like https://www.duomy.com, and educate customers to tap and verify. With those pieces in place, NTAG215 tags fight counterfeit products effectively and at a price that makes protecting every unit realistic.

Tags: ntag215, anti-counterfeit, nfc authentication, product security, originality signature, uid mirroring, brand protection, nfc tags, supply chain, duomy nfc

The post Can NTAG215 tags fight counterfeit products? appeared first on DuoMy Sensing.

Custom NFC NTAG215 labels for package tracking and product authentication are the quiet workhorse of modern supply chains because a single 504-byte chip can carry a unique serial, a tamper signal, and a link to a verification page, all readable by any phone without an app. Custom NFC NTAG215 labels for package tracking and product authentication let a brand follow a parcel from warehouse to doorstep and let a customer prove a product is genuine with one tap, two jobs that used to require separate systems and dedicated hardware. A barcode tells you what a thing is; an NTAG215 label tells you which specific unit it is, where it has been, and whether it is real. This guide explains why the NTAG215 chip is the right choice, how labels support tracking and authentication, how to design and encode them, three deployment approaches with honest trade-offs, security and anti-counterfeit technique, and the cost structure for a growing brand.

Suggested media: A cutaway infographic of an NFC label showing the NTAG215 inlay, the antenna loop, the adhesive layer, and the printed face, with a callout of the 504-byte memory and the UID.

Why Custom NFC NTAG215 Labels Are the Right Tool

The NTAG215 sits at the intersection of memory, compatibility, and cost that package and authentication use cases need.

Memory: 504 bytes is enough for tracking and proof

The NTAG215 offers 504 bytes of user-programmable memory. For tracking, a URL with a 12-character serial and UTM parameters consumes 70 to 120 bytes, leaving room for a second record such as a status flag or a verification token. For authentication, the same budget holds a signed URL or a short cryptographic counter. The 215 is meaningfully larger than the 144-byte NTAG213, which cannot hold both a serial and a fallback, and it is far cheaper than the 888-byte NTAG216 that most labels do not need.

Compatibility: read by every modern phone

The NTAG215 is an ISO/IEC 14443 Type A, NFC Forum Type 2 tag at 13.56 MHz. Every iPhone from the XS and XR onward reads NDEF records natively, and every NFC-enabled Android phone reads it in the background. No app, no account, no special scanner. For a customer verifying a product on the street, that universality is the entire point.

Security features that matter for authentication

The chip carries a seven-byte unique identifier burned in at the factory, supports a 32-bit password, and supports UID and tap-counter mirroring, which appends the serial or a tap count to a URL. For genuine cryptographic anti-counterfeit, NTAG424 DNA adds AES mutual authentication, but for most brands the 215 with UID mirroring and a server-side check is enough.

How Custom NFC NTAG215 Labels Support Package Tracking

Tracking at the unit level means every parcel carries its own identity, not just a batch code.

The tracking flow

Each label is encoded with a unique URL such as track.brand.com/p/AB12CD34. At each checkpoint, a handler taps or scans the label and the server records the location and time. The customer later taps the same label to see the journey, and support taps it to find the parcel in the system. One identifier serves warehouse, carrier, and consumer.

What the label stores versus what the server stores

The label stores only the serial and a short URL. All history, location, and status live on the server, which keeps the chip small and the data rich. The label is a key; the server is the database. This split means a lost or rewritten label does not lose the history, and a history change does not require re-labeling.

Suggested media: A flow diagram of a parcel moving through pick, pack, carrier scan, delivery, and customer tap, with the same NTAG215 serial threading every step.

How Custom NFC NTAG215 Labels Support Product Authentication

Authentication means proving a specific unit is genuine, not just that the model exists.

The verification flow

The label encodes a URL with the unit serial, for example verify.brand.com/AB12CD34. A customer taps the label, the page reads the serial, and the server confirms the serial exists in the issued range and has not been reported fake. The page returns a green “verified genuine” result with the product name and manufacture date.

UID mirroring for tamper evidence

By enabling UID mirroring, the chip appends its factory serial to the URL automatically. The server can then match the printed serial to the silicon serial, making it hard to duplicate a label by copying the printed code alone, because the silicon UID cannot be cloned on a standard 215.

Counter mirroring for engagement and reuse detection

Tap-counter mirroring appends how many times the chip has been read. A sudden spike in counts for one serial can flag a copied label in the wild, because a genuine unit is only tapped a handful of times. The counter is a lightweight anomaly signal.

Comparison Tables for Labels

Three tables make the choices concrete.

NTAG215 versus alternatives for labels

Label material and adhesive by use

Deployment model comparison

Designing Your Label: A Step-by-Step Guide

A label that survives shipping and verifies cleanly is the product of deliberate choices.

Step 1: Choose the inlay and material

Specify an NTAG215 inlay. For parcels, choose a PET or PP label with permanent adhesive. For authentication on a box, a tamper-evident void label adds a visible breach signal. For metal products, use a ferrite-backed flexible label.

Step 2: Plan the serial and URL scheme

Decide the serial format and the domain. Use a short, owned domain such as verify.brand.com/XXXX and a serial that is random enough to resist guessing. Keep the full URL under about 120 bytes so it sits comfortably in the 504-byte budget with room for a second record.

Step 3: Encode the primary record

Write one URI record with the serial URL. On Android, NFC Tools handles this; on iPhone XS and later the same app writes URI records. Keep the total under about 470 bytes.

Step 4: Add a second record if needed

For authentication, add a small text record with a status flag or a short token. Order the URI first so phones prioritise it and the experience is deterministic.

Step 5: Print the face

Print the brand, a tap icon, and the serial in human-readable form matched to the UID or counter mirror. Add a QR fallback pointing to the same URL for phones that block the tap.

Step 6: Test across devices and surfaces

Test the tap on an iPhone and an Android phone, on the actual package material, through a case, and near metal if applicable. Read the label exactly the way a handler or customer will.

What to Put on the Verification Page

The page is where authentication becomes believable.

Genuine confirmation

A clear “verified genuine” result with the product name, SKU, and manufacture date. Green and unambiguous. The customer should need no interpretation.

Journey or status

For tracking, show the checkpoint history as a simple timeline: packed, shipped, in transit, delivered. A compact table a customer can screenshot beats a paragraph.

Reporting path

Offer a “report this as fake” button for mismatches. Every report is intelligence that helps you find leak points in the supply chain.

Suggested media: A screenshot of a verification page showing a green genuine result, the product name, the manufacture date, and a report-fake button.

Multiple Approaches: DIY, Platform, or Managed Print

Brands have three deployment paths, each with trade-offs.

Approach 1: Fully DIY

Buy blank NTAG215 label rolls and encode them with a phone or a desktop writer, pointing each to your own lookup page.

• Pros: Lowest cost; full control; editable; fast to prototype.
• Cons: You own serial management and reliability; error-prone at volume; no professional print.

Approach 2: Authentication platform

Use a SaaS that issues serials, hosts verification, and provides analytics, then buy labels encoded to it.

• Pros: Dashboards included; easy serial control; tamper reporting.
• Cons: Recurring subscription; data with a third party; less brand control of the page.

Approach 3: Managed custom print

Order custom-printed NTAG215 labels from a supplier who prints your art, pre-encodes from your serial list, and tests them. A partner such as duomy.com can deliver labels printed, encoded, and verified before shipping.

• Pros: Professional print; pre-encoding at volume; QR fallback; consistent quality.
• Cons: Higher upfront cost than DIY; two-to-four-week lead time; less flexibility if locked.

Suggested media: A three-column comparison infographic of DIY, platform, and managed print along cost, control, and quality axes for labels.

Pairing Tracking and Authentication on One Label

The elegant move is one label, two jobs.

Pattern A: Tracking URL on the parcel, auth URL on the product

Use one label type encoded differently: parcels get a track URL, product units get a verify URL. Same chip, same print, different serial prefix. Operations and customers use the same tap hardware.

Pattern B: One URL, two views

Encode every label to one domain that detects context: a handler sees the tracking timeline; a customer sees the authentication result. Simplest to manage and easiest to explain to staff.

Case Studies

DTC apparel brand, 5,000 units. The brand applied tamper-evident NTAG215 labels to high-value jackets, encoded to a verification page with UID mirroring. Over a season they received four “report fake” clicks that traced to a single marketplace listing, which they had taken down. Genuine customers tapped an average of 1.3 times, mostly at unboxing.

Electronics manufacturer, parcel tracking. The manufacturer moved from QR to NTAG215 labels on outbound cartons, encoded to a tracking URL with a per-carton serial. Warehouse handlers tapped at pack and at dispatch, cutting mis-ships and giving support a single lookup. Customer “where is my order” tickets fell because the same label answered the question.

Craft spirits producer, anti-counterfeit. The producer used NTAG215 labels with counter mirroring on premium bottles. A spike in tap counts on one serial in a distant city flagged a copied label, and the producer used the report to warn retailers. The counter turned a static seal into a live signal.

Pharma distributor, cold chain. The distributor used PP synthetic NTAG215 labels on insulated shippers, encoded to a tracking URL. Handlers tapped at each transfer, building a temperature-excursion audit trail that satisfied a regulator without dedicated RFID hardware.

Luxury accessories, brand protection. The brand encoded NTAG215 labels inside product tags, with a verification page showing the item name and a registration step that bound the serial to the owner. Resale value rose because buyers could prove provenance with one tap.

Media: Using Images, Infographics, Tables, and Video

Labels are physical, but the pages and dashboards are where media earns trust.

• Images: A product photo next to its label at the top of the verification page builds recognition.
• Infographics: A journey timeline graphic summarises tracking in a screenshot-friendly form.
• Tables: A checkpoint table lets a customer or support read status without prose.
• Video: A fifteen-second clip showing a tap returning “verified genuine” increases confidence at point of sale.

Suggested media: A verification-page thumbnail with a green result and a play icon over a tap demo, captioned with the product name.

Security, Privacy, and Anti-Counterfeit Technique

A label is only as trustworthy as the system behind it.

Do not store secrets on the chip. The URL and serial are public by design. Put any validation logic server-side, where you control it.

Use UID mirroring to bind print to silicon. Matching the printed serial to the chip UID makes casual copying harder, because the silicon UID cannot be rewritten on a standard 215.

Understand the lock trade-off. Password protection stops casual rewriting but not cloning. For cryptographic proof, choose NTAG424 DNA with AES mutual authentication and a tap counter.

Treat the counter as an anomaly signal. A genuine unit is tapped a few times. A serial with thousands of taps is likely copied; investigate.

Privacy matters for tracking. Do not embed personal customer data in the label. Track the parcel, not the person, and keep PII in the server tied to the order, not the chip.

Cost and Ordering for a Growing Brand

Pricing follows volume and material.

• 100–500 labels: highest unit cost; good for prototyping and a pilot.
• 1,000 labels: first sensible break; covers a small product line.
• 5,000–10,000 labels: medium cost; encoding usually included; best for a growing SKU set.
• 50,000+ labels: low unit cost; roll format; long lead time; artwork and adhesive approval are the critical path.

Budget separately for artwork setup, for custom adhesive or tamper features, and for rush production. The biggest hidden cost is rework: if your serial scheme changes after printing, either rewrite by hand or waste the roll. Design the scheme and the domain before the first order.

Troubleshooting

Label reads on Android but not iPhone. You may have a MIFARE chip or an oversized record. Switch to NTAG215 and trim the URL.

Tap works without metal nearby but not on the product. Metal detunes the antenna. Use a ferrite-backed on-metal label.

Verification page says serial unknown. The serial was never registered server-side or the URL is mistyped. Register the range and test the exact link.

Label stopped reading after shipping. Adhesive failure, creasing, or antenna fracture. Use a durable PET/PP substrate and avoid folds across the antenna.

Encoding reports out of memory. Shorten the URL or move to NTAG216.

Common Mistakes Brands Make With NFC Labels

A few errors separate a label program that works from one that erodes trust.

Mistake 1: Printing dates or prices on the label

Any printed variable that changes forces a reprint. Keep the label to a stable serial and URL; put changing data on the server.

Mistake 2: No QR fallback

Thick cases and RFID wallets block taps. A label with no QR fallback fails for that customer. The fallback costs almost nothing and covers high-pressure moments.

Mistake 3: Weak serial scheme

Sequential or guessable serials let attackers forge valid-looking URLs. Use random, sufficiently long serials and validate server-side.

Mistake 4: Server-side checks missing

A label that “verifies” anything client-side is trivially spoofed. All genuine checks must happen on your server, where the attacker cannot alter the logic.

Mistake 5: Forgetting analytics

Encoding without logging taps means you cannot see leaks or anomalies. Log every verification with timestamp and source to build a counterfeit map.

Mistake 6: Over-designing the face

A busy label with tiny print and no tap icon confuses handlers and customers. Three elements win: brand, tap icon, and serial. Decoration that competes with the instruction reduces the tap rate.

Suggested media: A side-by-side of a failed label (dates printed, no QR, weak serial) versus a winning label (stable serial, QR fallback, server check), with trust signals annotated.

Frequently Asked Questions

Why use custom NFC NTAG215 labels instead of QR codes for tracking?
A QR code only carries a link and is trivially copied, while an NTAG215 label carries a unique factory UID and supports counter mirroring, so you can bind a printed serial to the silicon and detect copies by tap anomalies. The tap is also faster and more reliable than framing a QR in a warehouse. For unit-level tracking and proof of authenticity, the chip wins.

What can I store on an NTAG215 label for authentication?
About 504 bytes of user memory, of which 400 to 470 are usable after overhead. A typical authentication URL with a 12-character serial and UTM parameters uses 70 to 120 bytes, leaving room for a short second record such as a status flag. For reference, a plain URL uses roughly 30 to 60 bytes.

Do customers need an app to verify a product?
No. Every iPhone from the XS and XR onward reads NDEF records natively and shows a notification to tap. Modern Android phones read NFC tags in the background. The verification page opens in the browser, and no install or account is required, which is why the format works at point of sale.

Can I use one label for both tracking and authentication?
Yes. Encode the label to one domain that detects context: a handler sees the tracking timeline and a customer sees the authentication result. Alternatively use one label type with different serial prefixes for parcels versus product units. Both approaches use the same chip and the same tap hardware.

Is NTAG215 secure enough for anti-counterfeit?
For most brands, yes, especially with UID mirroring and server-side validation, which make casual copying hard. If you need cryptographic proof against determined counterfeiters, choose NTAG424 DNA with AES mutual authentication and a tap counter. The 215 stops opportunists; the 424 stops professionals.

How long does the data last on the chip?
NXP rates the NTAG215 for ten years of data retention and 100,000 write cycles. In practice the chip outlives the label substrate. The realistic lifespan of your label is set by the adhesive and face material, typically one to five years depending on environment.

Will the label work on metal products?
A standard label will be detuned by metal and may not read. Use a ferrite-backed flexible on-metal NTAG215 label, which shields the antenna from the surface and restores reliable reading. Specify this variant whenever the product or its packaging is metal.

What should I print on the label face besides the brand?
A clear instruction and a visible tap target. “Tap with your phone to verify” plus the NFC wave icon, positioned where a phone naturally lands, outperforms decorative layouts. Keep it to three elements: brand, tap icon, serial. Add a QR code as a fallback.

Conclusion

Custom NFC NTAG215 labels for package tracking and product authentication give a brand one identifier that serves the warehouse, the carrier, and the customer, and that proves a unit is genuine with a single tap. Specify an NTAG215 inlay suited to your surface, design a stable serial and URL scheme, keep changing data server-side, add UID and counter mirroring for tamper signals, and print a QR fallback on every label. Use the chip for both tracking and authentication, then log every tap to build a counterfeit map. When you are ready to specify material, adhesive, and encoding, you can order custom NFC NTAG215 labels pre-encoded to your tracking or verification domain, and pair them with a custom NFC business card for trade shows where you hand out samples.

Tags: NFC NTAG215 labels, package tracking, product authentication, NFC anti-counterfeit, supply chain, NFC tags, UID mirroring, tamper-evident, NTAG215, custom printed labels

The post Custom NFC NTAG215 Labels for Package Tracking & Product Authentication appeared first on DuoMy Sensing.

Custom NTAG215 NFC tags have become the working standard for brands that want a physical object to open a digital experience, and custom NTAG215 NFC tags earn that position by hitting the one combination that matters: enough memory for a real payload, native reading on every modern phone, a factory-unique identifier for per-item tracking, and a unit cost low enough to attach to a product you sell for a few dollars. Paper labels inform. QR codes link. A tag does something else: it removes the decision to engage, because a tap costs less effort than aiming a camera. This guide covers the chip specifications that matter, form factors and print methods, five marketing campaign patterns, four smart labeling architectures from anti-counterfeit to cold chain, three encoding approaches with honest trade-offs, artwork and production workflow, the security features most buyers never enable, testing procedures, three case studies with numbers, and a transparent cost breakdown.

Suggested media: Product photograph of a reel of custom NTAG215 NFC tags next to finished examples — a circular sticker, a square label on packaging, and an epoxy dome tag — with a magnified inset of the chip and antenna.

Why the NTAG215 Is the Right Chip for This Job

NXP’s NTAG21x family covers most of the passive NFC tag market, and three members dominate purchasing decisions: the 213, the 215, and the 216. The 215 sits in the middle and wins for a specific reason — it is the smallest chip that comfortably holds a complete, useful NDEF message with room left over.

The numbers

In practice, 144 bytes holds a short URL and nothing else — not a URL plus a vCard, a product serial, or a fallback instruction. The 504 bytes of the NTAG215 holds a 60-character URL plus a text record and still leaves roughly 300 bytes free. That headroom is what makes the chip “custom” in a meaningful sense: you design a payload rather than squeeze one in.

Compatibility is not optional

The NTAG215 is an ISO/IEC 14443 Type A, NFC Forum Type 2 tag at 13.56 MHz with 106 kbit/s transfer. Every iPhone from XS and XR forward reads its NDEF records natively with no app; every NFC-enabled Android device reads it in the background. Nothing needs installing on the customer’s side, the single most important property of any tag you hand to a stranger.

Contrast this with MIFARE Classic, which is cheap, abundant, and completely wrong here: modern iPhones cannot read its NDEF implementation at all. A marketing tag built on Classic silently fails for every iPhone owner who taps it, and you will never know, because failure produces no error message.

Features most buyers never turn on

Three features separate a professional deployment from an amateur one:

• 32-bit password with acknowledge byte. Once set, the tag cannot be rewritten without it. Without it, anyone with a free writer app can overwrite your tags with anything they like.
• Seven-byte unique identifier. Burned in at the factory and guaranteed unique, enabling per-item tracking, per-unit analytics, and authentication without printing a serial number.
• SUN (Secure Unique NFC) mirroring. The chip can append a cryptographic MAC to the UID when read, letting a backend verify that the tag is genuine. This is the foundation of real anti-counterfeit work.

Choosing a Form Factor and Print Finish

The chip is invisible; the form factor is what your customer touches, and choosing badly costs more than choosing an expensive chip.

Print methods and when each makes sense

Full-colour digital or offset printing on a PET or paper face is the default for packaging tags. It carries photography, gradients, and brand colour accurately and is economical at any quantity.

Thermal transfer is right when you need variable data — a different serial, batch code, or URL on every tag. It prints black only, so it usually sits on a pre-printed colour base.

Laser engraving suits anodised aluminium and some plastics. It is permanent, cannot be scratched off, and reads as premium, but it is monochrome. Dye-sublimation is what PVC cards use, giving photographic quality with good abrasion resistance.

One rule overrides all of these: keep the antenna area free of dense metallic ink. Metallic silver and gold inks, and conductive carbon black, can detune the antenna if printed over the coil. Specify a keep-out zone around the inlay, or print on a face stock laminated over the inlay rather than directly onto it.

Suggested media: Infographic showing the layer stack of a custom NTAG215 NFC tag label: printable face stock, adhesive, NTAG215 inlay with etched aluminium antenna, liner, plus a callout marking the metallic-ink keep-out zone.

Five Marketing Patterns That Work

Pattern 1: The tap-to-land campaign

A tag on a poster, shop window, flyer, or display links to a campaign page. Unlike a QR code, the tap works in dim light, works through a laminated cover, and produces a system notification rather than requiring a camera. Expect 2–6% of footfall to tap a well-placed poster tag, with 60–80% of taps continuing to the offer.

Pattern 2: Packaging that re-engages

A tag inside the box lid, under the label, or on the insert card. The customer has already bought, so the tap rate is high — 8–20% of shipped units — and the destination should be registration, a how-to video, a replenishment offer, or loyalty enrolment. Timing is the design decision: a tag that fires on first open should lead with setup help, while a tag on the product itself should lead with support and reorder, because that is where the customer will be in three months.

Pattern 3: Event and conference badges

Attendees tap to exchange contact details, collect session notes, or enter a draw. These produce the highest raw tap counts of any format because everyone is standing around looking for something to do: expect 30–60% of attendees to tap at least once.

Pattern 4: Out-of-home and transit

Bus shelter panels, elevator wraps, and gym equipment. These work because the audience is stationary and bored, a far better condition than walking past a billboard at speed. Use a large, obvious tap target and a benefit headline, not a logo.

Pattern 5: The connected business card or counter stand

The tag carries a link hub or a vCard. This is the most common use of custom NTAG215 NFC tags in retail and hospitality, and the most measurable, because you can count taps against footfall.

Typical tap rates and the risks to watch: poster and out-of-home placements convert 2–6% of impressions and live or die on whether anyone notices the tag; packaging inserts convert 8–20% of units but are often found after purchase intent has faded; event badges reach 30–60% of attendees with congestion at the tap point as the main risk; on-product labels convert 5–15% of owners and are exposed to physical damage; counter stands convert 3–8% of footfall but depend entirely on staff mentioning them.

Smart Product Labeling: Four Architectures

Marketing gets the attention; smart labeling is where custom NTAG215 NFC tags create durable operational value.

Architecture 1: Authentication and anti-counterfeiting

The counterfeit problem is not that fakes look different; it is that they look identical. A cloned QR code is trivial to reproduce, because the code is just printed data. A cloned NFC tag is harder, because the UID is burned in at the factory and will not copy onto a standard writable tag.

The practical architecture: each tag’s UID is registered in your database at production time. When a customer taps, your backend checks whether that UID exists, how many times it has been scanned, and from where. A UID scanned four hundred times across three continents is a red flag. Add SUN mirroring and the tag emits a cryptographic MAC that only a genuine NXP chip can generate, closing the clone gap almost entirely.

• Pros: Strong deterrence; customer-facing verification in two seconds; no app required.
• Cons: Needs a backend and database; a determined counterfeiter can still copy UIDs onto special writable-UID tags, so SUN is strongly recommended for high-value goods.

Architecture 2: Supply chain and cold chain

Tags on cases, pallets, or high-value items are scanned at each custody transfer. Unlike UHF RFID, NFC is read by a worker’s phone with no dedicated reader, which collapses the hardware cost of a tracking programme to nearly zero. For temperature-sensitive goods, pair the tag with a separate indicator or use a logging NFC sensor tag where budget allows; the tag becomes a pointer to the record rather than the record itself.

• Pros: No proprietary reader hardware; any phone is a scanner; minimal training.
• Cons: Short range means deliberate one-item scanning, not bulk reads. UHF RAIN RFID is correct for reading a whole pallet at once; NFC is correct for reading one item deliberately.

Architecture 3: Interactive product information and compliance

Regulations increasingly demand machine-readable product information — the EU Digital Product Passport being the clearest example. A tag carries the URL to the passport record: materials, repair instructions, recycling guidance, and provenance.

• Pros: Satisfies disclosure rules without printing a booklet; content updateable after manufacture; supports circular-economy programmes.
• Cons: The record must be maintained for the product’s whole life, a decade-long commitment for durable goods.

Architecture 4: Post-purchase engagement and replenishment

A washing machine with a tag on the door frame, a coffee machine with a tag behind the drip tray, a printer with a tag on the housing: tap it and you get the manual, the consumable reorder link, and support contact. This pattern has the best return of the four, because it intercepts the customer at the exact moment of need and measurably deflects support calls.

Three Ways to Encode Your Tags

Method 1: Static URL

Write one URL to every tag as a single URI record and lock it.

• Pros: Simplest, cheapest, no infrastructure, cannot break server-side.
• Cons: No per-item data, no analytics, destination is permanent.
• Use when: One campaign, one destination, and you do not care which unit was tapped.

Method 2: UID-parameterised URL (recommended for product labeling)

Every tag gets the same base URL, and the chip’s UID is mirrored into it as a query parameter, so tag A produces brand.co/p/04A2F1B3C4D5E6 and tag B a different string. The NTAG215 supports UID mirroring natively in its configuration pages, so the phone appends it with no per-tag encoding.

• Pros: Per-item analytics and authentication with no per-tag step; mass encoding takes seconds per reel; content updateable server-side.
• Cons: Needs a backend that resolves the parameter; the mirror must be configured correctly or the UID lands in the wrong place.
• Use when: You are tagging products, not posters.

Method 3: Fully dynamic redirect

The tag carries a short URL on your domain that redirects based on server-side logic — time of day, geography, scan count, or A/B bucket.

• Pros: Maximum flexibility; change the whole campaign without touching a tag; full analytics.
• Cons: Needs hosting; offline taps fail; adds latency.
• Use when: Campaigns across many locations, or testing destinations.

Artwork, Ordering, and Production Workflow

Getting custom NTAG215 NFC tags manufactured is straightforward once you know the sequence. Most delays come from artwork problems, not chip availability.

1. Define the payload first. Decide the URL structure and whether you need UID mirroring before designing anything, because it determines what goes on the tag.
2. Pick the form factor above, matching the surface material: metal requires an on-metal inlay, curved or washable surfaces the right substrate.
3. Specify the inlay — NTAG215, antenna size, and whether you need the SUN variant.
4. Prepare artwork at 300 dpi or as vector, CMYK, with a 3 mm bleed and a marked keep-out zone over the antenna.
5. Approve a physical proof. Never approve from a PDF alone: colour shifts between screen and print are real, and antenna position errors are invisible in a mockup.
6. Confirm the encoding plan — encoding service or blank, password protection, lock settings, UID logging.
7. Run a pilot batch of 50–200 units in the real environment before committing to 10,000.
8. Verify on receipt: sample-test at least 1% of the batch and record UIDs.

Artwork rules that prevent reprints

Keep the tap target icon directly over the antenna and at least 25 mm across. Put no metallic ink, foil blocking, or carbon black over the inlay. Keep text above 8 pt at final size and leave a 3 mm quiet margin from the die-cut edge. If the label goes on a curved surface, test adhesion on the actual curvature — flat-to-curved application is where labels lift.

Suggested media: Short video walking the production floor path: inlay reel, printing pass, die-cutting, encoding station, and a QC tap test on a sample from the batch.

Security Settings Most People Forget

A tag with no protection is a public whiteboard. Four settings matter.

Set the password. A 32-bit password with the acknowledge byte prevents casual rewriting. It is not military-grade — 32 bits is brute-forceable with dedicated hardware and time — but it stops someone with a free app from replacing your product label with a meme.

Lock the configuration pages. The NTAG215’s configuration pages control mirroring and protection; locking them stops anyone disabling the mirror or changing the lock bits.

Enable read-only where content is static. For a permanent URL, set the NDEF message to read-only. This is irreversible, so do it last, after verification.

Use SUN for anything worth counterfeiting. SUN appends an AES-based MAC over the UID and a read counter, which your backend validates. Without SUN a UID can be cloned onto a special writable-UID tag; with SUN it cannot.

Be honest about the limits: NFC is a short-range, unauthenticated radio link. Put nothing secret on a tag and never use one as an access credential for anything that matters.

Testing and Quality Control

Test in three stages, and do not skip the middle one.

Stage 1 — Bench test. Read ten tags from the batch on an iPhone and an Android device; verify payload, UID, and lock state.

Stage 2 — Applied test. Apply tags to the real product, in the real packaging, on the real shelf. This is where failures appear: a metalized film, a foil-lined pouch, or a curved glass bottle all change the read characteristics. Test through the packaging a customer will actually receive.

Stage 3 — Field test. Place fifty units with real customers and monitor tap rates for two weeks before scaling.

Common failure causes, in order of frequency: metal or foil in the packaging laminate, metallic ink over the antenna, a tag on a curve that flexes the antenna, adhesive failure on low-surface-energy plastics such as polypropylene, and tags applied over a dense printed barcode area.

• No read at all — metal in the packaging or behind the tag. Fix: on-metal inlay or ferrite spacer.
• Read only at one exact spot — small antenna, or the tag sits on a curve. Fix: larger antenna, flatter placement.
• Works, then fails after days — antenna cracked from flexing. Fix: rigid substrate, relocate the tag.
• Read works on Android only — antenna position versus the iPhone coil. Fix: enlarge the tap target, reposition.
• Falls off within a week — wrong adhesive for the substrate. Fix: high-tack or specialty adhesive.

Case Studies

Case study 1: Specialty coffee brand, 40,000 bags

A roaster put a 30 mm custom NTAG215 NFC tag on the back of every bag, printed with “Tap for brew guides,” using UID-parameterised URLs so the brand could see which roasting batch each tap came from. Over six months, 14.2% of bags were tapped at least once and 3.1% were tapped more than five times. The unexpected result was in support: questions about grind size and brew ratio dropped roughly 40%, because the landing page answered them while the customer held the bag. Repeat taps also triggered a replenishment email, producing an 11% reorder rate among tappers versus 4% among non-tappers.

Case study 2: Electronics accessory brand, anti-counterfeit

A mid-sized accessory maker was losing an estimated 8–12% of revenue to marketplace counterfeits. They embedded an epoxy dome NTAG215 with SUN inside the product housing and printed “Tap to verify” on the packaging. Within two quarters, customer verification taps exceeded 90,000, and takedown requests became easy to substantiate: a screenshot of a failed verification against a known UID was accepted as evidence by every platform they approached. Reported counterfeit listings fell by roughly half, at a tag cost under $0.35 against an average product price of $59.

Case study 3: Trade conference, 2,400 attendees

An organiser replaced printed handouts with badge tags pointing at a dynamic link hub. Attendees tapped to collect session slides, and exhibitors tapped attendee badges to capture leads, with the badge UID as the attendee identifier. Result: 61% of attendees tapped at least once, 4,100 total taps, and 1,850 exhibitor-to-attendee lead captures — roughly triple the previous year’s QR-based system, with far better data quality because there was no manual form. Printing costs also fell, since the handout pack was eliminated.

Cost Breakdown and Return

The chip is rarely the expensive part. Printing, converting, and encoding dominate, so the biggest cost lever is simplifying artwork and post-print work rather than downgrading the chip. Moving from an NTAG215 to an NTAG213 on a 10,000-unit order saves perhaps $200 and costs 360 bytes of design freedom — a bad trade in almost every case.

For ROI, assign a value to the action the tap replaces or creates. A counterfeit verification is worth the margin you protect; a support deflection is worth the average cost of a contact, typically $3–15; a reorder is worth the full margin. Most product-labeling deployments break even at tap rates between 3% and 8%, well within the range good placement reliably produces.

Frequently Asked Questions

What is the difference between NTAG213, NTAG215, and NTAG216?
They are the same family with different memory: 144, 504, and 888 user bytes. All three are ISO 14443 Type A, read natively by modern iPhones and Android phones, support 32-bit password protection, and carry a seven-byte UID. The 215 is the practical default because it holds a full NDEF message with headroom at a small premium.

Can I write to custom NTAG215 NFC tags with my phone?
Yes. Android writes NDEF records with free apps such as NFC Tools. iPhones from XS and XR onward write tags using App Store apps, though iOS is more restrictive about record types. For production runs, have your supplier encode on a desktop encoder — faster, and it sets passwords and lock bits in bulk.

How much data can one tag hold?
504 bytes of user memory, of which 492 are available for the NDEF message. A URL of 40 to 60 characters consumes under 100 bytes including NDEF overhead, so a realistic tag holds a URL plus a text record with room to spare.

Will these tags work on metal or foil packaging?
A standard inlay will not. Metal detunes the antenna and absorbs the field, so the tag either fails or reads only at one precise spot. Use an on-metal inlay with a ferrite spacer, which costs more but restores full performance. Always test through the finished packaging before a large order.

How do I stop someone from rewriting my tags?
Set a 32-bit password with the acknowledge byte, lock the configuration pages, and set the NDEF message to read-only once verified. For anti-counterfeit work, use the SUN variant so the tag emits a cryptographic MAC that a cloned tag cannot reproduce.

Do customers need to install an app to use them?
No. Every iPhone from XS and XR forward reads NDEF records through the system and shows a notification banner; Android phones have read tags in the background for years. The customer taps, taps the notification, and your page opens. This is a main reason NFC beats QR codes in low light and on glossy surfaces.

What is the read range, and does it vary by phone?
Typically 10 to 40 mm. The variable is the phone, not the tag: iPhones place the antenna near the top edge by the rear camera, most Android phones in the upper-middle of the back. Design a tap target at least 25 mm across so both orientations land somewhere useful.

Can the tag be changed after it is attached to a product?
A static URL cannot — you would have to re-encode or replace it. With a redirect or UID-parameterised URL on a domain you control, change the server-side destination and every tag in the field updates instantly. That is the strongest argument for the dynamic approach on long-lived products.

Getting Started

Start with the payload, not the hardware. Decide what the tap should do, what data you need back, and how long the product will live, then work backwards to the chip, form factor, and encoding method. Order a pilot batch of 100, test through the real packaging, and measure tap rates before committing to volume. Enable password protection on day one and use SUN if anything of value depends on the tag being genuine.

Duomy supplies custom NTAG215 NFC tags in every form factor described above, handling chip selection, artwork, encoding, and per-tag UID logging, and the same tags power a Google review NFC standee for businesses that want to turn in-store footfall into reviews as well as engagement.

Suggested media: Comparison infographic of tapping a custom NTAG215 NFC tag versus scanning a QR code in bright light, dim light, and through a laminated cover, with read-success rates annotated.

Tags: custom NTAG215 NFC tags, NTAG215 specifications, NFC product labeling, NFC marketing campaigns, smart packaging NFC, anti-counterfeit NFC tags, NDEF encoding, NFC tag form factors, UID mirroring, NFC supply chain tracking

The post Custom NTAG215 NFC Tags for Marketing & Smart Product Labeling appeared first on DuoMy Sensing.