# TallyFlow Scout

**Status:** Active product (app v0.5.3+10 as of July 2026 review)  
**Repo:** `tallyflow-assets-iot` (package `tallyflow_scout`)  
**Pairs with:** **TallyFlow Edge** (repo `tallyflow-iot`)  
**Does not replace:** **TallyFlow Assets** (`tallyflow_mobile`) — the Core-connected mobile app for enrollment, inventory, zone moves, seek-and-find, and scan-and-print  

## Overview

**TallyFlow Scout** is a Flutter handheld (and desktop demo) app for barcode and RFID work on the floor **with TallyFlow Edge**. Operators use three destinations:

| Section | What it does |
|---------|----------------|
| **Collect** | Scan barcode/RFID; submit reads to Edge as a **remote reader**, or **export CSV** when Edge is offline / not configured |
| **Verify** | Scan a GS1 barcode, then RFID tags; show whether each EPC encodes the **same GS1 identity key** (SGTIN / SSCC / GRAI / GIAI interoperability). Optional auto-confirm countdown when all match |
| **Locate** | Seek-and-find by EPC hex, GTIN/GS1, or Internal part number with RSSI / geiger feedback — **works fully offline** (no Edge required) |

Scout is the mobile companion for **Edge site deployments** (docks, tunnels, on-prem readers). It is **not** the full asset system of record app: enrollment, zones, Core sync, and scan-and-print remain **TallyFlow Assets**.

## Positioning (marketing truth)

- **Edge path, not Core path** — Scout talks to Edge remote-reader REST (`/api/v1/reader/barcode`, `/api/v1/reader/rfid`, `/health`). Assets talks to Core.
- **Complementary** — Sell Scout with Edge for handheld collect / verify / locate at the reader edge. Sell Assets with Core for asset lifecycle and inventory programs.
- **Offline-capable floor tool** — Collect list + CSV export + Locate work without a live Edge server; submit when online.
- **Hardware-real** — Android industrial scanners via `flutter_hardware_scanner` (e.g. Janam XR2, ATID, SEUIC, URFID stacks); camera barcode fallback on phones; desktop always in simulator mode for demos.

## Target use cases

- Handheld remote reader into a multi-reader Edge site (same feed as fixed Impinj/Zebra readers)
- GS1 barcode↔RFID **Verify** at encode/pack/ship (catch wrong EPC encoding before product leaves)
- Offline **Locate** / seek-and-find on the floor without Core
- CSV collect for demos, audits, or sites not yet wired to Edge submit
- SI / partner demos with desktop simulator (JSON tag groups, optional automation)

## Core features (from product review)

- Material 3 shell: **Collect / Verify / Locate** bottom navigation
- Collect: pending/sent/failed status, manual batch submit or auto-send, CSV share/save (including GS1 type-filter rollup mode)
- Verify: lists all RFID tags (no EPC soft-filter hiding mismatches); Confirm / Reset actions; swipe to Locate or delete
- Locate: EPC mask filters (GS1 / SDG RAIN / hex / part); power slider; geiger audio; handoff from Collect/Verify swipe
- Internal `part_serial` RFID settings aligned with **TallyFlow Print** (group Collect by part; Locate by part)
- Edge health banner; EN + ES localization
- Settings: base URL, remote reader name, optional API key, RFID power, scan beep, symbology filters, verify auto-confirm seconds

## Technical notes

- Android package path renamed toward Scout branding (`com.tallyflow.scout`)
- Vendor AARs for some handheld stacks live under `android/app/lib/` (see repo README); SEUIC uses on-device system libraries
- Desktop (macOS / Linux / Windows): simulation only — load JSON tag groups, send to Edge, add to list, or export CSV
- Service strings in code/README may still say “TallyFlow IoT”; **product name is TallyFlow Edge**

## Related components

- `tallyflow-iot` — **TallyFlow Edge** backend (remote reader + fixed readers + CSV/REST/AMQP egress)
- `tallyflow_mobile` — **TallyFlow Assets** (Core mobile; not replaced by Scout)
- `tallyflow-print` / Print UI — Internal EPC encodings Scout can decode/group
- `flutter_hardware_scanner` (+ XR2 / SEUIC / ATID device plugins)

## Open / watch

- Website and datasheets should say **Scout + Edge**, not “Assets for IoT”
- Distribution channel (Play / sideload / SI bundle) not fixed in vault
- Do not market Scout as Core enrollment or scan-and-print — those stay on Assets