Each product needs a unique SKU to be imported. Products without a SKU are skipped during import. You can add SKUs to those products in your Shopify admin, then retry the import from the Integrations page.

An EPC (Electronic Product Code) identifies an individual tagged item; a UPC is the 12-digit GTIN commonly used by a product's barcode and identifies the product type. For standards-based SGTIN-96 tags, the EPC contains both a product identifier and a unique serial number. When DropRFID scans one, it first checks for an explicitly registered EPC. If none exists, it decodes the EPC's company prefix and item reference, reconstructs the GTIN and its check digit, and matches that GTIN to the UPC, EAN, or GTIN in your product catalog. That is why every serialized tag does not need to be entered manually: import or sync the catalog barcode once, and compatible tags can resolve automatically. A manual EPC-to-SKU mapping is still needed for tags that are not SGTIN-96, or when the catalog barcode is missing or ambiguous.

A routine is a guided scan workflow for a specific job such as receiving, cycle counting, order verification, returns, or tag onboarding. It controls what operators enter or scan, what information appears with the session, and what completion actions are evaluated when scanning finishes.

A completion action can update Shopify inventory, verify a Shopify order, send a signed webhook to another system, or create a session report. Actions can run automatically, only when there are no exceptions, after administrator approval, or in review-only mode.

Searchable fields become filters and lookup indexes for sessions. Use them for values you will search by later, such as brand, PO number, order, carton, location, or count scope. Do not mark every note, status detail, temporary scan, or operator-only prompt searchable: too many searchable fields make the filter list noisy, make it harder to find the field that matters, add unnecessary indexed metadata, and can imply reverse lookup behavior you do not actually need. If a value is only captured for recordkeeping or only displayed to the operator, leave Searchable off.

No. Routine fields are stored and displayed by field key, not by label. A routine cannot reuse the same field key, so two fields with different keys remain separate columns even if they have the same visible label. That can be confusing on the sessions page, so use unique labels for fields you choose to show, or leave Show on sessions page off for fields that are only internal context.

A device is any RFID scanner or reader registered to your organization. You only pay for active devices — decommissioned devices are not counted.

Every new organization gets 14 days free after activating its first scanner, with full access to all features. No credit card required to start.

The Business plan covers up to 10 devices at a flat $249/month — whether you have 2 devices or 10, the price is the same. That means the more devices you add, the lower your per-device cost.

Our industrial RFID scanners are $699 each. Comparable competitor scanners are often around $1,000 each. Purchase directly from our shop; each scanner ships pre-configured and ready to scan out of the box.

Legacy RFID vendors often quote $20K–$40K customization or implementation fees before hardware and subscriptions. DropRFID is AI-assisted DIY: $0 startup fee, 14 days free, then a transparent subscription.

We accept all major credit cards through Stripe. Invoicing is available for Custom plans.

Scanners ship pre-configured for DropRFID. Power on the scanner, connect it to Wi-Fi, and it will self-register and appear in your Admin → Devices page within a few minutes. No manual registration is needed.

A UPC (Universal Product Code) is the everyday barcode number that identifies a product type — the same GTIN you already store on each SKU in your catalog. An EPC (Electronic Product Code) is the number written to an RFID tag's chip: unlike a barcode it identifies each individual item, and it carries the product's UPC/GTIN inside it along with a unique serial number. Because the UPC is embedded in the EPC, DropRFID can identify a scanned tag on its own — when a scanner reads a tag, it first checks whether that exact EPC is already linked to a SKU, and if not it decodes the EPC (the standard SGTIN-96 format) to recover the GTIN/UPC and matches it against your products' barcodes. Either way the tag resolves to the right product automatically. That's why you never register or type in RFID codes by hand: as long as your products carry barcodes in your catalog, scanning is enough for DropRFID to know exactly which product — and which unit — it is.