A quick reference for the terms you will see across the ForgeStop Dashboard, BatchMaker, and Help Center articles.

A physical NFC label with a ForgeStop chip inside. When a consumer taps their phone on the tag, it triggers the authentication flow. Tags are applied to individual products during the BatchMaker process. Also called: NFC tag, smart label.

A unique identifier (UUID) assigned to each physical tag at the moment it is activated during the BatchMaker process. Every product gets its own TID — think of it as the digital fingerprint of that specific item. TIDs are visible on the Scan Details page. Distinct from the Batch Serial #, which is the human-readable sequential identifier for the same tag.

The virtual representation of a physical tagged product, created in the ForgeStop platform the moment the tag is activated in BatchMaker. The digital record stores the tag's identity (TID, Batch Serial #), its production context (product, batch, location), and its lifecycle events (every scan). This enables full traceability from production to the end consumer.

A production run — a group of tags that are activated and associated with a specific product at the same time. A batch has a lot number, a production date, and a set of metafields that apply to every tag in the batch.

A human-readable, sequential identifier assigned to each activated tag during the batching process. The format is configurable per brand and product — for example, FAPR-20-90/2026-003/000002 where the segments encode brand, product line, batch, and sequence number. Operations teams use the Batch Serial # for physical reconciliation; the TID is the same tag's system UUID.

The lot identifier entered at batching time. Typically matches the lot printed on the physical product packaging.

The system-generated unique identifier (UUID) for a batch, shown on the Batch Details screen. Distinct from the Batch Serial # (human-readable, per-tag) and the Lot Number (your own identifier entered at batching time).

A production request for new tags, sent to ForgeStop. Orders become the physical tags that your team later activates through BatchMaker. The Orders sidebar item in your Dashboard shows every order's status (submitted, in production, shipped, delivered) and tracking information.

A production facility, warehouse, or labeling site belonging to your brand. Locations are configured in Settings and can be attached to batches so that every scan traces back to where the product was manufactured or labeled.

Two possible Loc. Source values on a scan. Precise Location means the consumer granted GPS permission and the scan is pinpointed to a specific point. Approximate Location means no GPS was granted and the location was derived from the consumer's IP address — accurate to the city level only.

A single SKU registered in your Dashboard. Each product has a name, SKU, slug, type, image, and an active theme template. Products exist before batches — you must create a product before you can associate tags to it.

Stock Keeping Unit — the unique identifier for a product variant. SKUs cannot be changed after a product is created.

A short, URL-friendly identifier derived from the SKU, used for TID serial number generation. 1–20 characters, A–Z, 0–9, hyphens only.

A configuration record that controls how the consumer sees the authentication page — fonts, colors, brand logo, heading text, button labels, and any custom CSS. Templates can be shared across multiple products or dedicated to one product.

A Plus-plan-and-above feature that lets brand designers override the template's basic styles with their own CSS for finer control (padding, hover states, typography, shadows). Applies only to the consumer-facing authentication pages.

The expandable content area below the authenticated product screen. Used for regulatory info, video content, loyalty signups, coupons, or anything else you want to show consumers after authentication.

A custom data field (key-value attribute) you define once and attach to batches during the BatchMaker process. Metafields display on the authentication page and inside Show More content. Example: lot_number = "LOT-2026-A7".

The sidebar section of the Dashboard where metafields live. Today, Metafields is the only feature under Metadata; more custom data types will be added in the future.

A descriptive label you attach to a batch for internal reporting — for example, a destination city or a campaign name. Batch tags are not shown to consumers. Distinct from NFC tags (physical) and metafields (consumer-facing).

The Windows application your production team runs to activate tags and associate them with products. BatchMaker reads physical tags, applies the batch's lot number and metafields, and uploads the activated tags to your Dashboard.

A virtual boundary (country, region, or city) associated with alert rules on a batch. Fires a notification when a percentage of the batch's tags are scanned inside or outside the zone.

A single NFC read event by a consumer or operator. Scans have one of four statuses (Authentic, Counterfeit, Rescan, or Invalid) and record a timestamp, location, and tag/batch context.

The four possible scan statuses. See the What Does Each Scan Status Mean? FAQ for the full meaning of each.

The end-user experience — a consumer taps their phone on a product and sees your branded authentication page. No app, no account, just the browser.

If you need further assistance, contact us at [email protected] or use the chat widget in your Dashboard.

Last Synced: 2026-04-23 · Sync Status: Current · ID: 14750094 · Language: English