# TallyFlow Clarifying Questions

**Purpose:** Persistent record of clarifying questions asked during daily product research cycles to avoid repetition and build on prior knowledge. Questions are cycled by weekday product focus.

## Previously Asked Questions

*(No prior questions recorded as of start of cycle - June 2026)*

## Tuesday - Mobile App (Enroll, update, inventory, and locate)
**Question Asked:** How does the Mobile App handle asset 'locate' and inventory updates in offline mode, including sync behavior upon reconnection, and are there any specific features or limitations for use in large-scale environments like rail yards or manufacturing facilities with intermittent connectivity?

**Context/Notes:** This question builds on the brief mentions of offline sync and field operations in the User's Guide. It aims to clarify details for improving website content, documentation, and marketing around mobile reliability in challenging environments (e.g., rail, remote sites). Addresses potential gaps in integration with IoT/Capture for real-time locate.

**Date Asked:** Tuesday, June 16, 2026

## Wednesday - TallyFlow Print
**Question Asked:** What Zebra printer models and RFID tag encoding options (e.g., specific memory banks like EPC, TID, user memory; password protection; serialization/prefix logic) are supported or tested in TallyFlow Print, and how does the print job orchestration handle multi-printer environments, queuing, error recovery (printer offline, encoding failures), and safeguards against duplicate asset registrations when using the optional Core auto-registration feature?

**Context/Notes:** Builds on the known Zebra printer support, parent/child structures, multi-printer management, and optional registration in the User's Guide and code reviews. Targets gaps in hardware compatibility details, reliability for industrial/rail use cases, and integration robustness to improve docs, website feature descriptions, and marketing for on-site labeling workflows. Addresses potential AEI/rail-adjacent tag encoding questions indirectly through custom RFID support.

**Date Asked:** Wednesday, June 17, 2026

## Thursday - TallyFlow Capture
**Question Asked:** In TallyFlow Capture, which specific fixed RFID reader hardware (brands/models like Impinj R420/R680, Zebra FX series, or others) and communication protocols are natively supported or have integration examples, how does the edge/gateway processing handle real-time tag event filtering, deduplication, and local decision-making before syncing to Core, and what mechanisms are available for configuring and delivering automated alerts and exception notifications (e.g., email, SMS, webhooks, dashboard flags) in high-throughput environments like receiving docks or manufacturing lines?

**Context/Notes:** Builds on the high-level description of fixed reader integration, gateway/edge processing, exception flagging, and handoff to Core in the User's Guide, as well as the noted gap in AEI rail support and hardware requirements. Targets hardware compatibility details, edge vs cloud architecture, and alerting capabilities to improve website feature clarity, product documentation (e.g., User's Guide, code reviews), marketing for automated high-volume workflows, and positioning for industrial/rail-adjacent use cases. Addresses potential gaps in integration robustness, real-world deployment considerations, and exception handling details.

**Date Asked:** Thursday, June 18, 2026

**Source Code Review Note (2026-06-18):** Reviewed related repos (tallyflow-decode, tallyflow-iot, impinj-iot, zebra-iot, photomicroservice) in /Users/tnb/src/. High-level architecture confirms edge processing and multi-vendor reader support potential via MQTT/REST, but specific models and alert delivery details remain to be clarified with product owner. No changes to question needed.

## Friday - IoT Integration
**Question Asked:** Building on the high-level IoT capabilities for real-time location tracking via gateways and beacons, environmental sensor data (temperature, humidity, shock), automated status updates, and edge-to-cloud pipelines supporting short-range (BLE, RFID) and wide-area (LoRa, cellular) networks, what specific IoT gateway hardware, beacon/sensor vendors or protocols (e.g., particular BLE beacons, LoRaWAN providers, cellular IoT modules), and data normalization approaches does TallyFlow IoT support or have tested integrations for? How are sensor readings and location events ingested, associated with asset records in Core, and used to trigger rules-based alerts, workflows, or status updates—especially in rail, manufacturing, or compliance-heavy environments—and what are the options for local edge processing vs. cloud-only handling to support intermittent connectivity or high-reliability needs?

**Context/Notes:** This question builds directly on the IoT section in the User's Guide and ties into known gaps around rail/AEI support, hardware specifics, and integrations (e.g., RFIDKnow partnership, environmental compliance). It incorporates insights from source code review of tallyflow-iot (new MCP support for AI agents, keyboard wedge, RFID write fixes, and TallyFlow_IoT_Datasheet.md) to seek clarification on production hardware support and event-driven workflows. Aims to improve website feature descriptions, product documentation, marketing for automated/sensor-driven use cases, and positioning for industrial/rail applications. Addresses potential gaps in concrete examples, vendor ecosystem, and edge intelligence details.

**Date Asked:** Friday, June 19, 2026

**Source Code Review Note (2026-06-19):** Pulled latest from tallyflow-iot develop branch (96b5fe7). Key additions include initial MCP (Model Context Protocol) support for AI agents via 'rmcp' crate serving at /mcp with tools for API info, health, reader status; keyboard wedge filter/lookup for Assa Abloy/customers; RFID write command fixes (saving PC Word); new TallyFlow_IoT_Datasheet.md (393 lines); consistent icons and barcode printing in tag stream. Confirms ongoing multi-vendor RFID/IoT evolution and AI integration potential. No changes to question needed; question targets production hardware and workflow details not yet in code/docs.

## Monday - TallyFlow Core (Web Application)
**Question Asked:** Building on the high-level description of TallyFlow Core as the central web platform for asset management, reporting, and integrations (including manual asset creation, Excel import, category/zone configuration, exception management, and ERP integration points), what specific features does the Core web application offer for advanced asset search and filtering (e.g., by zone history, custom attributes, tag status, movement events), customizable reporting and dashboard capabilities (including scheduled reports, export formats like CSV/PDF, visualization types such as charts or maps, zone duration analytics), exception management workflows (flagging rules, assignment, escalation, resolution tracking, notifications), role-based access control (RBAC) and multi-user collaboration features, and the extent of its REST API, webhooks, or other integration mechanisms for real-time or batch sync with ERP systems (SAP, NetSuite, JD Edwards)?

**Context/Notes:** This question targets gaps in detailed feature descriptions to improve website content, product documentation (User's Guide, code reviews), marketing positioning, and clarity for industrial/rail/manufacturing use cases. It builds directly on the Core section in the User's Guide, code review observations (zone imports, exception tracking, reporting, maps via Leaflet/Chart.js, ERP-adjacent flows), and recent source commits (e.g., import-zone feature, tag handling hotfixes in v1.33.x) without repeating questions from other product days. Addresses potential gaps in reporting robustness, integration depth, permissions, and scalability for large asset inventories.

**Date Asked:** Monday, June 22, 2026

**Source Code Review Note (2026-06-22):** Reviewed recent commits in tallyflow-web (v1.33.2 hotfixes for tags array conversion, duplicate handling, import startsWith fix; v1.33.1/1.33.0 with import-zone feature merged). Confirmed strong emphasis on zone/asset import, exception handling, and reporting. No changes to question needed; question seeks production details on search, RBAC, API surface, and dashboard customization not fully documented yet.

## Tuesday - Mobile App (Enroll, update, inventory, and locate) [June 23, 2026 Cycle]
**Question Asked:** Building on the high-level description of the Mobile App for field enrollment, scanning, updates, locate, and inventory, what specific details exist around the enrollment workflow (required/custom fields, support for bulk/rapid scanning, parent-child asset association during enrollment, photo attachments or condition logging, validation against duplicates or existing records), mobile UI/UX considerations for industrial environments (e.g., large buttons, glove-friendly, dark mode, offline-first design), integration points with TallyFlow Print (e.g., triggering print jobs from mobile during enrollment), TallyFlow Capture/IoT (real-time locate handoff), and Core (sync priorities, conflict resolution), and any support for advanced locate features like indoor positioning, asset history trails, or proximity alerts?

**Context/Notes:** This new question avoids repeating the previous Tuesday focus on offline sync/locate limitations and instead targets enrollment details, industrial UX, cross-product integrations (Print, Capture, IoT, Core), and advanced locate capabilities to improve website feature descriptions, User's Guide depth (currently high-level), marketing for field operations in rail/manufacturing/waste management, and documentation gaps around mobile as the primary on-site tool. Addresses known emphasis on mobile enrollment/on-site workflows and potential for tighter product integration.

**Date Asked:** Tuesday, June 23, 2026

## Other Days
- Monday (Core): Question added June 22, 2026 (see above)
- Tuesday (Mobile App): New question added June 23, 2026 (see above)
