# 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

## Other Days
- Monday (Core): [To be added next cycle]
- Thursday (Capture): [To be added]
- Friday (IoT): [To be added]