Dragon Guard includes a native RFID layer that runs entirely within the platform — no ERP-side RFID support required. Every tag is stored in a tenant-scoped EPC registry (Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CodexaCP/DG_BACK/llms.txt
Use this file to discover all available pages before exploring further.
RfidTagRegistry), every hardware read is preserved as an RfidScanEvent, operational behaviour is governed by per-module RfidOperationPolicy records, and connected handheld hardware is described by RfidDeviceProfile entries. Together these four entities give you traceable, configurable RFID from inquiry through receipts, shipments, and movements — without touching your ERP’s document model.
RFID settings are tenant-level and are managed by SUPERADMIN_SUPREMO through the Supreme administration portal. Warehouse operators interact with the RFID layer only through their handheld devices and the standard module workflows.
Operating modes
Every tenant is configured with exactly one RFID operating mode. The mode controls the overall intent; per-module policies then refine the fine-grained behaviour.Disabled
Disabled
RFID is completely inactive for the tenant. The backend applies no RFID rules, the handheld presents no RFID flows, and all capture happens via barcode or manual entry. Use this for tenants that have no RFID hardware or are in an early onboarding stage.
InquiryOnly
InquiryOnly
RFID can be used to look up items — the handheld reads an EPC and Dragon Guard resolves it to an item record and its operational context. Tag reads do not block or validate receipts, shipments, or movements. No RFID evidence is required to complete a transaction. This is the recommended starting mode for pilots and low-risk rollouts.
OperationalAssist
OperationalAssist
RFID actively assists warehouse operations. During receipts, shipments, and movements the handheld can read EPCs and Dragon Guard validates them against the expected items. When a tag fails to resolve or match, the system falls back to barcode or manual entry according to the active policy — the operation is not automatically blocked unless a specific rule says otherwise. All RFID reads are recorded as audit evidence.
StrictValidation
StrictValidation
RFID is a mandatory validation step in every module where the tenant enables it. If an EPC does not resolve to the expected item, or if no valid EPC read is present, the operation is blocked. Manual and barcode fallback can be disabled by policy. Use this mode for high-accuracy environments such as controlled picking, pharmaceutical receiving, or asset-tracking workflows.
Mode capability matrix
| Capability | Disabled | InquiryOnly | OperationalAssist | StrictValidation |
|---|---|---|---|---|
| Item inquiry via EPC | — | ✓ | ✓ | ✓ |
| RFID-assisted receipts | — | — | ✓ optional | ✓ required |
| RFID-assisted shipments | — | — | ✓ optional | ✓ required |
| RFID-assisted movements | — | — | ✓ optional | ✓ required |
| Barcode / manual fallback | ✓ always | ✓ always | ✓ per policy | configurable |
Module scope
RFID participation is controlled independently for each of the four warehouse modules. A tenant runningOperationalAssist might enable RFID only for Shipments while leaving Receipts in barcode-only mode.
| Module | RFID role |
|---|---|
| Items | EPC-to-item inquiry and resolution |
| Receipts | Tag validation during inbound receiving |
| Shipments | EPC confirmation during picking and packing |
| Movements | Physical unit confirmation during bin transfers |
Key entities
| Entity | Purpose |
|---|---|
RfidTagRegistry | Tenant-scoped EPC master record; maps each EPC to an item, object type, quantity, status, and physical location |
RfidScanEvent | Immutable audit record of every tag read; stores the EPC, module, document, resolution outcome, validation outcome, device, and operator |
RfidOperationPolicy | Per-module rules that define the operating mode, fallback permissions, blocking conditions, duplicate-read handling, and evidence requirements |
RfidDeviceProfile | Hardware capability descriptor for a family of handheld readers; specifies vendor, connection type, trigger mode, RFID/barcode support, and reader defaults |
Explore the RFID module
Tags
Commission, resolve, bulk-import, and manage EPC tags in the registry
Policies & Profiles
Configure per-module operation policies and handheld device profiles
Scan Events
Submit tag reads, query the audit trail, and run pre-flight validation