Rename product TallyFlow IoT → TallyFlow Edge across vault

Update product naming in docs, marketing, architecture, use cases, and capabilities materials. Rename related notes, screenshot folder, and marketing image filenames. Keep git/repo identifiers (e.g. tallyflow-iot) and generic industry IoT language unchanged.
2026-07-27 15:48:08 -04:00
parent 4d09d3195b
commit cf1e09e1c4
33 changed files with 128 additions and 128 deletions
@@ -20,7 +20,7 @@
 ## Status / Notes
 - **TallyFlow Mobile**: Currently uses the main `TallyFlow-Product-Icon.png` (no dedicated Mobile icon yet).
- **TallyFlow IoT**: No icon created yet.
+- **TallyFlow Edge**: No icon created yet.
 - **TallyFlow Core** and **TallyFlow Capture**: No dedicated icons yet.
 *This index is maintained for easy reference by the daily TallyFlow cron and marketing tasks.*
@@ -11,7 +11,7 @@
 ## Code Review Summary
 All core repos reviewed and documented in `Product/Code Reviews/`. Key themes:
- Multiple overlapping implementations (Flutter, Rust, Vue, Swift) for capture/IoT/printing
+- Multiple overlapping implementations (Flutter, Rust, Vue, Swift) for capture/Edge/printing
 - Strong RFID, reporting, and ERP-adjacent capabilities
 - Opportunity to consolidate messaging under unified TallyFlow platform
@@ -22,4 +22,4 @@ All core repos reviewed and documented in `Product/Code Reviews/`. Key themes:
 _Last updated: 2026-06-23_
 ## Additional Roadmap Note (added later in session)
- **TallyFlow Assets (Mobile) + TallyFlow IoT integration** — Real-time location, sensor data, and zone-based workflows accessible directly from the mobile app.
+- **TallyFlow Assets (Mobile) + TallyFlow Edge integration** — Real-time location, sensor data, and zone-based workflows accessible directly from the mobile app.
@@ -14,7 +14,7 @@ flowchart LR
    A[TallyFlow Assets Mobile] -->|REST / WebSocket| B[TallyFlow Core]
    C[TallyFlow Print] -->|REST| B
    D[TallyFlow Capture] -->|REST| B
-    E[TallyFlow IoT] -->|REST / MQTT| B
+    E[TallyFlow Edge] -->|REST / MQTT| B
    B -->|REST / Integration Hub| F[ServiceNow]
    F -->|REST| B
 ```
@@ -26,7 +26,7 @@ flowchart LR
 | Direction                  | Typical Data                          | Trigger                          | Recommended Method                  |
 |---------------------------|---------------------------------------|----------------------------------|-------------------------------------|
 | **ServiceNow → TallyFlow** | Asset master data, locations, status  | Scheduled or event-driven        | ServiceNow Integration Hub → Core REST |
-| **TallyFlow → ServiceNow** | Real-time location, RFID scans, condition updates | Mobile scan, IoT event, zone change | Core → ServiceNow REST / Flow Designer |
+| **TallyFlow → ServiceNow** | Real-time location, RFID scans, condition updates | Mobile scan, Edge event, zone change | Core → ServiceNow REST / Flow Designer |
 | **Bidirectional**          | Asset status synchronization          | On change or scheduled           | Core as middleware                  |
 ## Key Integration Points
@@ -41,7 +41,7 @@ flowchart LR
 - This data is pushed to ServiceNow for visibility in Asset Management, Work Orders, or CMDB.
 ### 3. Real-time Location & Condition
- IoT and mobile events flow through Core and are published to ServiceNow (via REST or Integration Hub).
+- Edge and mobile events flow through Core and are published to ServiceNow (via REST or Integration Hub).
 ## Authentication & Security
@@ -1,4 +1,4 @@
-# TallyFlow IoT Multi-Reader Benefits
+# TallyFlow Edge Multi-Reader Benefits
 **Status:** Customer talking points  
 **Date:** 2026-07-13  
@@ -17,21 +17,21 @@ Customers often ask why they should not call reader APIs (e.g. Impinj) directly.
 - A path out to apps and reports (spreadsheet, API, or message bus)
 - Day-2 ops: is the dock reading? restart inventory? which reader is down?
-Downstream systems consume data; they do not control readers. Something has to sit in the middle either way. TallyFlow IoT is that site edge layer.
+Downstream systems consume data; they do not control readers. Something has to sit in the middle either way. TallyFlow Edge is that site edge layer.
 ## Architecture story
 ```text
 [Fixed readers × N per site]
        ↓
-[TallyFlow IoT edge]  ← ops UI, start/stop, health
+[TallyFlow Edge]  ← ops UI, start/stop, health
        ↓
  Spreadsheet (CSV)  /  REST  /  AMQP (TallyFlow)  /  …
        ↓
 [Downstream systems]
 ```
-## Benefits of TallyFlow IoT
+## Benefits of TallyFlow Edge
 General product strengths—useful even when the conversation is not only about multi-reader fan-in.
@@ -89,7 +89,7 @@ Events are normalized to a simple model: reader name, antenna, EPC, TID, RSSI, t
 ### 3. Unified data can go to a spreadsheet
-TallyFlow IoT’s CSV logger writes the combined feed from all readers into spreadsheet-friendly files:
+TallyFlow Edge’s CSV logger writes the combined feed from all readers into spreadsheet-friendly files:
 - One file (or folder of files) per site instead of N reader streams
 - Easy pilot path before investing in heavier integration
@@ -101,18 +101,18 @@ When a spreadsheet is not enough, TallyFlow can also export via:
 | Path                  | Status                              | Typical use                                                  |
 | --------------------- | ----------------------------------- | ------------------------------------------------------------ |
-| **CSV / spreadsheet** | Built into IoT (`logger`)           | File or folder drop (simplest)                               |
+| **CSV / spreadsheet** | Built into Edge (`logger`)           | File or folder drop (simplest)                               |
-| REST API              | Built into IoT (`rest_api`)         | Middleware, custom apps, automation (`/tags`, stream, etc.)  |
+| REST API              | Built into Edge (`rest_api`)         | Middleware, custom apps, automation (`/tags`, stream, etc.)  |
-| AMQP → TallyFlow      | Built into IoT (`tallyflow`)        | Cloud / Core path                                            |
+| AMQP → TallyFlow      | Built into Edge (`tallyflow`)        | Cloud / Core path                                            |
-| **Database**          | Via app, not a native IoT processor | App consumes REST (or AMQP later) and writes SQL/SQLite/etc. |
+| **Database**          | Via app, not a native Edge processor | App consumes REST (or AMQP later) and writes SQL/SQLite/etc. |
 | MQTT export           | Not shipped                         | Future processor candidate; same JSON shape as REST.         |
-**Database path (today):** We do **not** write customer databases from TallyFlow IoT itself. Pattern in production: a site app talks to IoT over REST and persists what the customer needs.
+**Database path (today):** We do **not** write customer databases from TallyFlow Edge itself. Pattern in production: a site app talks to Edge over REST and persists what the customer needs.
- Example: Alice+Olivia console (`alice_olivia_console`) connects to TallyFlow IoT REST, handles warehouse workflow, and stores box/EPC state in **local SQLite**.
+- Example: Alice+Olivia console (`alice_olivia_console`) connects to TallyFlow Edge REST, handles warehouse workflow, and stores box/EPC state in **local SQLite**.
- Sell as: “unified multi-reader feed + your app (or ours) into the database you already run”—not “IoT has a Postgres plugin” unless/until we add one.
+- Sell as: “unified multi-reader feed + your app (or ours) into the database you already run”—not “Edge has a Postgres plugin” unless/until we add one.
-**Optional future:** a native DB processor in IoT is possible (same event bus as logger/REST), but app-level integration keeps schema and business rules with the customer app.
+**Optional future:** a native DB processor in Edge is possible (same event bus as logger/REST), but app-level integration keeps schema and business rules with the customer app.
 ### 5. Operations without opening each reader
@@ -154,9 +154,9 @@ They pay for reader hardware either way. The real cost of DIY is owning multi-re
 ## Related
- Product: TallyFlow IoT (edge service)
+- Product: TallyFlow Edge (edge service)
 - Egress today: **spreadsheet (CSV)**, REST API, **AMQP → TallyFlow**
- Database today: **via app** (e.g. Alice+Olivia console → SQLite over REST), not a built-in IoT processor
+- Database today: **via app** (e.g. Alice+Olivia console → SQLite over REST), not a built-in Edge processor
 - AI today: **MCP Streamable HTTP** at `/mcp` (read-only tools; see below)
 - Not yet: MQTT *export* (MQTT is used inbound for Zebra today); optional native DB processor; full REST surface as MCP tools
 - Typical stack: Impinj Speedway / R700 family fixed readers
@@ -176,7 +176,7 @@ Today’s MCP surface is **narrow and read-only**. That is a feature for early u
 |-------------|----------------|
 | **Ops / support copilot** | “Which readers are configured?” “Any recent tags?” “Is the service up?” without custom scripts |
 | **Site awareness for agents** | An agent (Cursor, Claude Desktop, custom) that already talks MCP can poll health, reader list, and recent tag cache |
-| **Troubleshooting** | Compare “UI shows tags” vs “API/MCP shows tags”; confirm IoT is running before blaming the reader |
+| **Troubleshooting** | Compare “UI shows tags” vs “API/MCP shows tags”; confirm Edge is running before blaming the reader |
 | **Light inventory questions** | “What EPCs did we see lately?” from the in-memory recent-tag buffer (not full history or BI) |
 | **Safe by default** | No start/stop/write over MCP → lower risk of an agent turning RF on/off by mistake |
@@ -209,9 +209,9 @@ Prioritize in order of risk vs value:
 3. **Align gen descriptors with live tools** — or generate the live router from OpenAPI so docs and runtime do not diverge  
 4. **Optional MQTT (or other) export** for agent/event buses — separate from MCP; still not required for copilot Q&A  
 5. **Higher-level “site summary” tool** — one call: readers up/down, last tag time, tag counts, obvious faults (better for LLMs than raw dumps)  
-6. **Cross-product AI** — IoT MCP + Core/ServiceNow patterns so an agent can go from “tag seen at dock” to business context (asset, order, location)
+6. **Cross-product AI** — Edge MCP + Core/ServiceNow patterns so an agent can go from “tag seen at dock” to business context (asset, order, location)
-**Sell carefully:** “AI can check site RFID status through TallyFlow IoT” is true today. “AI runs your readers” is a future, opt-in story.
+**Sell carefully:** “AI can check site RFID status through TallyFlow Edge” is true today. “AI runs your readers” is a future, opt-in story.
 ---
@@ -226,7 +226,7 @@ Power BI is a consumer of data, not a controller of readers. TallyFlow is the mi
 **Why this matters for Power BI customers:**
 - **Unified multi-reader feed** — all site readers in one schema (reader, antenna, EPC, TID, RSSI, time)
- **Spreadsheet path** — TallyFlow IoT can output that unified data to a **CSV/spreadsheet**; Power BI can load the file, folder, or gateway path with no custom Impinj client
+- **Spreadsheet path** — TallyFlow Edge can output that unified data to a **CSV/spreadsheet**; Power BI can load the file, folder, or gateway path with no custom Impinj client
 - **Other paths when needed** — REST into middleware / Azure Function / a warehouse DB app, or AMQP into TallyFlow then downstream
 - **Ops without opening Power BI** — site staff can confirm reads and reader health locally
 - **Stable contract** — add readers or change hardware without rebuilding every report
@@ -234,7 +234,7 @@ Power BI is a consumer of data, not a controller of readers. TallyFlow is the mi
 **Typical flow:**
 ```text
-[Impinj × N] → [TallyFlow IoT] → [CSV / REST / AMQP→TallyFlow]
+[Impinj × N] → [TallyFlow Edge] → [CSV / REST / AMQP→TallyFlow]
                                      ↓
                         [optional app → database]
                                      ↓
@@ -244,11 +244,11 @@ Power BI is a consumer of data, not a controller of readers. TallyFlow is the mi
 <!-- Add more use-case sections below as needed (e.g. WMS, ERP, ServiceNow). -->
 ## Example Tunnel Hardware (RMS Omega)
-These conveyor/tunnel RFID readers are representative of the fixed reader hardware TallyFlow IoT integrates with:
+These conveyor/tunnel RFID readers are representative of the fixed reader hardware TallyFlow Edge integrates with:
 - rms-omega-rfid-tunnel-reader-front.jpg
 - rms-omega-rfid-tunnel-reader-rear.jpg
 - rms-omega-rfid-tunnel-reader-side.jpg
 - rms-omega-rfid-tunnel-reader-control-panel.jpg
-*Images added July 2026 for IoT marketing and benefits documentation.*
+*Images added July 2026 for Edge marketing and benefits documentation.*
@@ -15,7 +15,7 @@ This folder is for organizing app and web screenshots used for the TallyFlow web
 - **TallyFlow Print/**
  - Printer setup and label printing screenshots (TSC/Printronix hardware)
- **TallyFlow IoT/**
+- **TallyFlow Edge/**
  - Fixed RFID readers, tunnels, and gateway hardware
 ## Guidelines
@@ -5,13 +5,13 @@
 ## PAGE 1 – FRONT (Hero + Platform Overview)
 ### Headline
-**Unified Asset Intelligence Across Web, Mobile, IoT, and Print**
+**Unified Asset Intelligence Across Web, Mobile, Edge, and Print**
 ### Subhead
 RFID + Barcode Asset Tracking That Actually Integrates With Your ERP
 ### Hero Description
-TallyFlow is the complete asset intelligence platform that combines real-time RFID/IoT data, mobile capture, powerful web dashboards, and integrated printing — all designed to work seamlessly with your existing ERP systems.
+TallyFlow is the complete asset intelligence platform that combines real-time RFID and edge data, mobile capture, powerful web dashboards, and integrated printing — all designed to work seamlessly with your existing ERP systems.
 **See Everything. Catch Exceptions. Move Faster.**
@@ -29,7 +29,7 @@ TallyFlow is the complete asset intelligence platform that combines real-time RF
 | **TallyFlow Web**   | Central web platform, reporting & ERP integration | Real-time visibility & control  |
 | **TallyFlow Assets**| Mobile asset management app                      | On-the-floor tracking & updates |
 | **TallyFlow Capture**| Mobile photo + barcode capture (formerly PhotoTag) | Fast, accurate receiving & inspection |
-| **TallyFlow IoT**   | Reader management & real-time streaming          | Automated zone & tunnel tracking |
+| **TallyFlow Edge**   | Reader management & real-time streaming          | Automated zone & tunnel tracking |
 | **TallyFlow Print** | Encoding & printing workflows                    | Consistent, error-free labeling |
 ---
@@ -73,7 +73,7 @@ Print and encode tags on demand with full integration to your workflows. Strong
 ### Why TallyFlow Is Different
 - **True ERP Integration** — Works with your existing systems (not just another silo)
- **Unified Platform** — One system for web, mobile, IoT, and print
+- **Unified Platform** — One system for web, mobile, Edge, and print
 - **Rapid Deployment** — Get value in weeks, not months
 - **Hardware Agnostic** — Works with leading RFID readers, printers, and labels
 - **Real Customer Results** — Documented success in food traceability, repair operations, and high-volume logistics
@@ -100,7 +100,7 @@ Print and encode tags on demand with full integration to your workflows. Strong
 info@sdgsystems.com  
 sdgsystems.com/tallyflow
-*Part of the TallyFlow platform — unified asset intelligence across web, mobile, IoT, and print.*
+*Part of the TallyFlow platform — unified asset intelligence across web, mobile, Edge, and print.*
 ---
@@ -45,7 +45,7 @@
 ## TallyFlow Pricing Recommendations (Based on Competitive Analysis)
 **Important Product Structure Note**:
- **TallyFlow Capture** (aka PhotoTag), **IoT**, and **Print** can be sold as **standalone** products.
+- **TallyFlow Capture** (aka PhotoTag), **Edge**, and **Print** can be sold as **standalone** products.
 - **TallyFlow Mobile** requires **TallyFlow Core**.
 **Recommended Model**: Modular pricing with a Core platform + optional standalone modules. This allows flexibility for customers who only need specific capabilities (e.g., just Capture/PhotoTag or just Print).
@@ -89,7 +89,7 @@
 - Lower tiers could be offered (e.g., $79 base for smaller teams with 50 GB).
-**TallyFlow IoT**: $79–$129/month + per-device fees
+**TallyFlow Edge**: $79–$129/month + per-device fees
 **TallyFlow Print**: $69–$99/month (tag printing & encoding focused)
@@ -20,7 +20,7 @@ They position themselves as a hardware provider looking for strong software and
 - Request co-marketing support (logos, case studies, joint webinars)
 ### 2. Product Integration Opportunities
- **TallyFlow IoT** → Native support / certification for RFIDKnow antennas and portals
+- **TallyFlow Edge** → Native support / certification for RFIDKnow antennas and portals
 - **TallyFlow Print** → Compatibility with their mounts and sensor accessories
 - Create a “RFIDKnow + TallyFlow” solution bundle
@@ -36,7 +36,7 @@ They position themselves as a hardware provider looking for strong software and
 - Provide TallyFlow demos and training to RFIDKnow’s sales and technical teams
 ### 5. Technical Collaboration
- Develop reference architectures showing RFIDKnow hardware feeding directly into TallyFlow IoT
+- Develop reference architectures showing RFIDKnow hardware feeding directly into TallyFlow Edge
 - Create configuration guides for common RFIDKnow portal setups
 - Explore joint R&D on new antenna + software features
@@ -45,7 +45,7 @@ They position themselves as a hardware provider looking for strong software and
 2. Prepare a short partnership proposal highlighting mutual benefits
 3. Schedule a technical call to explore integration points
 4. Propose a joint webinar or content piece as a low-risk starting point
-5. **Hardware evaluation action:** Reach out to RFIDKNOW to request a demo or borrow unit of an Industrial Portal or FlexAntenna system (mention TallyFlow IoT needs for testing read performance and IoT integration)
+5. **Hardware evaluation action:** Reach out to RFIDKNOW to request a demo or borrow unit of an Industrial Portal or FlexAntenna system (mention TallyFlow Edge needs for testing read performance and Edge integration)
 ---
 *Document created to guide partnership development with RFIDKnow*
@@ -15,9 +15,9 @@ This document highlights where TallyFlow is meaningfully differentiated from com
 - Few competitors offer this level of hardware abstraction
 ### 3. Unified 5-Pillar Platform
- Core (Web) + Assets (Mobile) + Capture (Photos) + IoT + Print
+- Core (Web) + Assets (Mobile) + Capture (Photos) + Edge + Print
 - Most competitors are either software-only or hardware-only
- TallyFlow can own the full workflow from tag printing → capture → IoT → reporting
+- TallyFlow can own the full workflow from tag printing → capture → Edge → reporting
 ### 4. Zone Duration & Movement Intelligence
 - Time-in-zone analytics
@@ -1,25 +1,25 @@
-# TallyFlow Assets for IoT
+# TallyFlow Assets for Edge
 **Status:** New component (v0.1.0+1)  
 **Primary Mobile App:** `tallyflow_mobile` remains the main TallyFlow Assets experience  
-**Role:** Companion / specialized app for IoT remote reader workflows
+**Role:** Companion / specialized app for Edge remote reader workflows
 ## Overview
-TallyFlow Assets for IoT is a Flutter-based mobile and desktop application that submits barcode and RFID tag reads directly to the TallyFlow IoT service using the remote reader API.
+TallyFlow Assets for Edge is a Flutter-based mobile and desktop application that submits barcode and RFID tag reads directly to the TallyFlow Edge service using the remote reader API.
-It is designed for scenarios where tag data needs to be delivered to a local or on-premise TallyFlow IoT instance rather than going through the main TallyFlow Core mobile app.
+It is designed for scenarios where tag data needs to be delivered to a local or on-premise TallyFlow Edge instance rather than going through the main TallyFlow Core mobile app.
 ## Key Positioning
 - **Complementary to `tallyflow_mobile`** — Not a replacement. `tallyflow_mobile` remains the primary app for general asset capture, enrollment, and mobile workflows.
- **IoT-focused** — Optimized for pushing reads to the TallyFlow IoT remote reader endpoint.
+- **Edge-focused** — Optimized for pushing reads to the TallyFlow Edge remote reader endpoint.
 - **Hardware + Simulation** — Full hardware scanner support on Android; simulation mode on desktop for testing and demo purposes.
 ## Target Use Cases
- Fixed or semi-fixed IoT reader workflows where a mobile device acts as a remote reader
+- Fixed or semi-fixed Edge reader workflows where a mobile device acts as a remote reader
- Environments with local TallyFlow IoT deployments (on-prem or edge)
+- Environments with local TallyFlow Edge deployments (on-prem or edge)
 - Testing and validation of remote reader configurations
 - Desktop-based simulation and automation of tag submissions during development or demos
@@ -29,26 +29,26 @@ It is designed for scenarios where tag data needs to be delivered to a local or
 - Camera barcode fallback using ML Kit
 - Barcode / RFID mode switching
 - Local scan list with send status and retry
- Manual or automatic submission to TallyFlow IoT
+- Manual or automatic submission to TallyFlow Edge
- IoT service health monitoring with offline banner
+- Edge service health monitoring with offline banner
 - Desktop simulator with JSON tag group loading and automation
 ## Technical Notes
- Connects to TallyFlow IoT remote reader endpoints (`/reader/barcode` and `/reader/rfid`)
+- Connects to TallyFlow Edge remote reader endpoints (`/reader/barcode` and `/reader/rfid`)
 - Requires configuration of Base URL, Remote Reader Name, and optional API key
 - Android builds require vendor AAR files for hardware scanner support
 - Desktop platforms always run in simulation mode
 ## Marketing Angle
- Positions TallyFlow as having flexible ingestion paths (mobile app + dedicated IoT remote reader app)
+- Positions TallyFlow as having flexible ingestion paths (mobile app + dedicated Edge remote reader app)
- Supports both field mobility (`tallyflow_mobile`) and IoT/edge integration scenarios
+- Supports both field mobility (`tallyflow_mobile`) and Edge integration scenarios
- Simulation mode lowers the barrier for prospects and partners to test IoT connectivity without hardware
+- Simulation mode lowers the barrier for prospects and partners to test Edge connectivity without hardware
 ## Related Components
- `tallyflow-iot` (backend service)
+- `tallyflow-iot` (backend service; **product name: TallyFlow Edge**)
 - `tallyflow_mobile` (primary mobile app)
 - `flutter_hardware_scanner` (shared scanning library)
@@ -2,7 +2,7 @@
 ## Hero Section
 **Headline:**  
-Unified Asset Intelligence Across Web, Mobile, IoT, and Print
+Unified Asset Intelligence Across Web, Mobile, Edge, and Print
 **Subheadline:**  
 RFID and barcode tracking that reduces manual work and gives you real-time visibility across every zone.
@@ -27,7 +27,7 @@ Mobile asset tracking and lightweight inventory. Key features include:
 ### TallyFlow Capture
 Mobile photo + barcode + RFID capture (formerly PhotoTag). Processing tens of thousands of photos per week for major manufacturers like Madix (retail shelving).
-### TallyFlow IoT
+### TallyFlow Edge
 Real-time reader management and tag streaming from Impinj, Zebra, and more.
 ### TallyFlow Print
@@ -1,7 +1,7 @@
 # New TallyFlow.com Site Plan (For Cursor)
 ## Goal
-Build a modern, professional marketing site at tallyflow.com that positions TallyFlow as the unified asset intelligence platform (web + mobile + IoT + print).
+Build a modern, professional marketing site at tallyflow.com that positions TallyFlow as the unified asset intelligence platform (web + mobile + Edge + print).
 ## Target Audiences
 - Operations / Warehouse managers in retail, manufacturing, logistics
@@ -12,7 +12,7 @@ Build a modern, professional marketing site at tallyflow.com that positions Tall
 ### 1. Home (/)
 - Hero: Strong value prop + primary CTA ("Schedule a Demo")
- Platform overview (5 pillars: Web, Mobile, Capture, IoT, Print)
+- Platform overview (5 pillars: Web, Mobile, Capture, Edge, Print)
 - Key benefits / proof points
 - Featured use cases (Receiving, Zone Movement, Exception Management)
 - Trust bar (industries + logos if available)
@@ -26,7 +26,7 @@ Build a modern, professional marketing site at tallyflow.com that positions Tall
 - /web — TallyFlow Core (central web platform, reporting, ERP integration)
 - /assets — TallyFlow Assets (Mobile) — mobile asset management app
 - /capture — TallyFlow Capture (Photos) — mobile + photo + barcode (formerly PhotoTag)
- /iot — TallyFlow IoT (reader management, real-time streaming)
+- /edge — TallyFlow Edge (reader management, real-time streaming)
 - /print — TallyFlow Print (encoding & printing workflows)
 ### 4. Solutions
@@ -47,12 +47,12 @@ Build a modern, professional marketing site at tallyflow.com that positions Tall
 ## Messaging Framework
 **Primary Headline Ideas:**
- "Unified Asset Intelligence Across Web, Mobile, IoT, and Print"
+- "Unified Asset Intelligence Across Web, Mobile, Edge, and Print"
 - "RFID + Barcode Asset Tracking That Actually Integrates With Your ERP"
 - "See Everything. Catch Exceptions. Move Faster."
 **Positioning Statement:**
-TallyFlow is the complete asset intelligence platform that combines real-time RFID/IoT data, mobile capture, powerful web dashboards, and integrated printing — all designed to work seamlessly with your existing ERP systems.
+TallyFlow is the complete asset intelligence platform that combines real-time RFID and edge data, mobile capture, powerful web dashboards, and integrated printing — all designed to work seamlessly with your existing ERP systems.
 ## Visual Direction
 **Brand Colors:**
@@ -89,7 +89,7 @@ RMS Omega is TallyFlow’s preferred partner for RFID hardware, labels, printers
 **Website Placement Ideas:**
 - Footer or dedicated “Partners” page with RMS Omega logo and short description.
 - “How It Works” diagram showing RMS Omega hardware feeding into TallyFlow platform.
- Mention on product pages (especially IoT and Print) as the recommended hardware partner.
+- Mention on product pages (especially Edge and Print) as the recommended hardware partner.
 **Recommended Content:**
 - Joint one-pager: “RFID Asset Tracking – Hardware + Software”
@@ -7,7 +7,7 @@ Make targeted, low-effort improvements to sdgsystems.com/tallyflow and sdgsystem
 ### 1. Messaging & Positioning
 - On the TallyFlow page, add a short line near the top:  
-  **"Part of the TallyFlow platform — unified asset intelligence across web, mobile, IoT, and print."**
+  **"Part of the TallyFlow platform — unified asset intelligence across web, mobile, Edge, and print."**
 - On the PhotoTag page, add TallyFlow Capture language:  
  PhotoTag is the standalone product and is also integrated with TallyFlow.
@@ -36,7 +36,7 @@ Add or emphasize these capabilities on the TallyFlow page:
 ## Stretch Goal: Update the main TallyFlow page to focus on the 5 components:
 * TallyFlow Core (Web)
-* TallyFlow IoT
+* TallyFlow Edge
 * TallyFlow Capture
 * TallyFlow Mobile
 * TallyFlow Print
@@ -12,7 +12,7 @@
 - Products (or Solutions)
  - TallyFlow Core
  - TallyFlow Capture
-  - TallyFlow IoT
+  - TallyFlow Edge
  - TallyFlow Print
 - Use Cases / Solutions
 - Case Studies
@@ -76,7 +76,7 @@
 - Make the Capture product page the strongest right now (it has the most supporting content)
 - Ensure mobile experience is excellent (many use cases are field-based)
 - Include clear CTAs on every page: “Request Demo” and “Start Free Trial”
- Plan for future expansion into Core, IoT, and Print (keep navigation flexible)
+- Plan for future expansion into Core, Edge, and Print (keep navigation flexible)
 - Use consistent tagging/categorization language across the site
 ---
@@ -17,7 +17,7 @@
 - **Parent/child asset handling** (asset can remain while children/tags are detached)
 ### 3. ERP Integration
- Primary: TallyFlow IoT using keyboard wedge, database integration, and spreadsheet output
+- Primary: TallyFlow Edge using keyboard wedge, database integration, and spreadsheet output
 - Additional opportunities in TallyFlow Core using the API and webhooks
 ### 4. Tag Printing & Encoding
@@ -40,11 +40,11 @@
 - "Automate verification without changing your existing workflows"
 ### Feature Highlights to Emphasize
- TallyFlow IoT (fixed infrastructure / tunnels)
+- TallyFlow Edge (fixed infrastructure / tunnels)
 - TallyFlow Capture (photo + barcode association)
 - TallyFlow Print (tag printing + registration)
 - Seamless ERP integration via keyboard wedge or API
- Mobile + Web + IoT working together
+- Mobile + Web + Edge working together
 ### Target Audiences Visible in SOWs
 - Retail / Apparel (Alice + Olivia)
@@ -6,13 +6,13 @@ This note will contain ongoing code review findings across the TallyFlow ecosyst
 - [x] phototag-swift (iOS Swift capture app)
 - [x] phototag-connector (Rust connector)
 - [x] phototag-web (Vue web interface)
- [x] tallyflow-iot (Rust core + Leptos web; RFID/reader management + REST API)
+- [x] tallyflow-iot (**product: TallyFlow Edge**; Rust core + Leptos web; RFID/reader management + REST API) — note: [[tallyflow-edge]]
 - [x] tallyflow-web (initial pass complete — core views + entities documented)
 - [x] tallyflow-decode (Flutter mobile app for tag decoding)
 - [x] tallyflow-print (print/encoding backend)
 - [x] tallyflow-print (print/encoding backend)-ui
 - [x] tallyflow_spreadsheet_importer (Flutter spreadsheet import tool)
- [x] flutter_tallyflow_iot_rest_client (Flutter REST client for IoT)
+- [x] flutter_tallyflow_iot_rest_client (Flutter REST client for Edge)
 ## General Observations
 (Notes will be added here as review progresses)
@@ -20,4 +20,4 @@ This note will contain ongoing code review findings across the TallyFlow ecosyst
 ## Action Items
 - [ ] 
 ## Architecture Notes
- **TallyFlow Core as central hub**: TallyFlow Assets (Mobile), TallyFlow Print, TallyFlow Capture, and TallyFlow IoT all integrate with TallyFlow Core (web) for asset registration, synchronization, reporting, and configuration.
+- **TallyFlow Core as central hub**: TallyFlow Assets (Mobile), TallyFlow Print, TallyFlow Capture, and TallyFlow Edge all integrate with TallyFlow Core (web) for asset registration, synchronization, reporting, and configuration.
@@ -1,4 +1,4 @@
-# tallyflow-iot Review
+# TallyFlow Edge Review (repo: tallyflow-iot)
 **Tech Stack:** Rust (Cargo workspace) + Leptos (web UI)
@@ -19,11 +19,11 @@
 ## Key Capabilities
 - Hardware abstraction for multiple RFID vendors
 - Real-time data pipeline from readers → REST → web UI
- Designed for always-on IoT deployment
+- Designed for always-on Edge deployment
 - Strong documentation (REST_API.md, LIBRARY.md, etc.)
 ## Relevance to TallyFlow Platform
- Primary ingestion layer for RFID/IoT data
+- Primary ingestion layer for RFID/Edge data
 - Feeds the web app, reporting, and exception systems
 - Complements tallyflow-web (which consumes the data)
@@ -71,7 +71,7 @@ Operator → TallyFlow Print app → Print API → Print worker → Zebra printe
 ## Roadmap / Integration Opportunities
 - ~~**Mobile (Assets) integration** for Scan-and-Print~~ — **Shipped:** mobile can trigger print jobs (reprint, on-demand encoding during field scans or enrollment).
- **IoT integration** — Expose print job status/events and printer health to TallyFlow IoT for unified dashboards and alerts.
+- **Edge integration** — Expose print job status/events and printer health to TallyFlow Edge for unified dashboards and alerts.
 ## Recent Changes (develop branch pull - July 2026)
 **Major theme:** CSV import for batch printing, GS1 Sunrise dual-carrier retail tags, custom field registration, internal profile standardization.
@@ -10,7 +10,7 @@
 ## Key Areas to Investigate
 - Asset / Zone management
- RFID / IoT integration points
+- RFID / Edge integration points
 - Reporting & exports
 - User workflows (receiving, movement, printing)
 - ERP integration surface (API and webhooks)
@@ -26,4 +26,4 @@
  - Reporting on zone durations, events, zone categories (`ReportZoneDurations.vue`, etc.)
  - Map-based visualization (`Map.vue`)
 - **Tech Notes**: Uses Leaflet for maps, Chart.js for reports, Vuetify for UI. Strong emphasis on ERP-adjacent data flows (imports, reports, exceptions).
- **Next**: Review API layer and shared components for integration patterns (RFID, printing, IoT).
+- **Next**: Review API layer and shared components for integration patterns (RFID, printing, Edge).
@@ -11,13 +11,13 @@ Dedicated mobile application for TallyFlow.
 - Appears to be the primary/official TallyFlow mobile client
 ## Relevance to Platform
-This repo represents the **mobile pillar** of TallyFlow, distinct from the web, IoT, print, and capture components.
+This repo represents the **mobile pillar** of TallyFlow, distinct from the web, Edge, print, and capture components.
 ## Status
 Initial structure review complete.
 ## Roadmap / Integration Opportunities
 - ~~Integration with **TallyFlow Print** for Scan-and-Print~~ — **Shipped:** scan existing asset or enroll → trigger print job for new/replacement labels from mobile.
- Integration with **TallyFlow IoT** for real-time location, sensor data, and zone-based workflows directly in the mobile Assets app.
+- Integration with **TallyFlow Edge** for real-time location, sensor data, and zone-based workflows directly in the mobile Assets app.
 ## UX Design
 - Built with **Material 3**
@@ -9,7 +9,7 @@
 ## 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.
+**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 Edge/Capture for real-time locate.
 **Date Asked:** Tuesday, June 16, 2026
@@ -29,14 +29,14 @@
 **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
+## Friday - Edge 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?
+**Question Asked:** Building on the high-level Edge 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 Edge 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.
+**Context/Notes:** This question builds directly on the Edge 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.
+**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/Edge 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)?
@@ -48,9 +48,9 @@
 **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?
+**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/Edge (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.
+**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, Edge, 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
@@ -7,7 +7,7 @@
 ## Overview
-TallyFlow is an asset tracking and management platform designed to reduce time and material waste in operations that rely on physical assets, tools, and tagged items. It combines mobile data capture, web-based core management, on-site printing/encoding, automated capture, and IoT connectivity.
+TallyFlow is an asset tracking and management platform designed to reduce time and material waste in operations that rely on physical assets, tools, and tagged items. It combines mobile data capture, web-based core management, on-site printing/encoding, automated capture, and Edge connectivity.
 TallyFlow is particularly well suited for industries requiring reliable identification and traceability, including manufacturing, logistics, rail, and agriculture.
@@ -20,7 +20,7 @@ TallyFlow is particularly well suited for industries requiring reliable identifi
 - Fast asset enrollment and editing
 - Reduce time spent locating and managing assets  
 - Minimize material waste through better visibility and accountability  
- Provide practical, affordable RFID, barcode, and IoT solutions for systems integrators
+- Provide practical, affordable RFID, barcode, and Edge solutions for systems integrators
 ---
@@ -29,7 +29,7 @@ TallyFlow is particularly well suited for industries requiring reliable identifi
 ### 1. TallyFlow Core (Web Application)
 The central web platform for managing assets, tags, categories, zones, and reporting.
-**Integration Hub:** TallyFlow Assets (Mobile), TallyFlow Print, TallyFlow Capture, and TallyFlow IoT all integrate with TallyFlow Core.
+**Integration Hub:** TallyFlow Assets (Mobile), TallyFlow Print, TallyFlow Capture, and TallyFlow Edge all integrate with TallyFlow Core.
 **Key Capabilities:**
 - Add and manage assets manually
@@ -86,17 +86,17 @@ Automated data capture system for fixed and high-volume scanning environments.
 - Exception flagging and automated alerts
 - Seamless handoff to TallyFlow Core for record updates
-### 5. TallyFlow IoT
+### 5. TallyFlow Edge
 Connectivity layer for sensors, gateways, and connected devices. Runs as an always-on Windows or Linux service.
 **Key Capabilities:**
- Real-time location tracking via IoT gateways and beacons
+- Real-time location tracking via Edge gateways and beacons
 - Environmental sensor data (temperature, humidity, shock) linked to assets
 - Automated status updates without manual scanning
 - Edge-to-cloud data pipelines feeding TallyFlow Core
 - Support for both short-range (BLE, RFID) and wide-area (LoRa, cellular) IoT networks
 - RFID GPIO support for reader triggers and control
- Endpoint configuration available for IoT and Mobile readers
+- Endpoint configuration available for Edge and Mobile readers
 - ERP integration via keyboard wedge, database integration, and spreadsheet output
 - Optional custom receiving or shipping user interface that integrates with an ERP system
 - Compatible with TallyFlow Core deployed in the cloud or on-premises
@@ -122,7 +122,7 @@ TallyFlow supports multiple ways to bring tags and asset data into the system:
 5. **TallyFlow Capture (Automated)**  
   Fixed readers and gateways automatically detect and record tag movements.
-6. **IoT Devices**  
+6. **Edge Devices**  
   Sensors and connected devices push location, condition, or status data directly into the platform.
 ---
@@ -131,7 +131,7 @@ TallyFlow supports multiple ways to bring tags and asset data into the system:
 TallyFlow is a **distributor** of Atid handheld RFID readers (such as the AT909) to systems integrators. These devices are commonly used for mobile scanning and enrollment workflows.
-The platform also supports fixed RFID readers, IoT gateways, and sensor devices through the Capture and IoT modules.
+The platform also supports fixed RFID readers, edge gateways, and sensor devices through the Capture and Edge modules.
 **Note:** TallyFlow does not currently provide native support for AEI (Automatic Equipment Identification) tags used in the rail industry.
@@ -144,7 +144,7 @@ The platform also supports fixed RFID readers, IoT gateways, and sensor devices
 - **Automated Receiving/Shipping:** Fixed readers (Capture) detect tagged assets moving through dock doors or checkpoints.
 - **Condition Monitoring:** IoT sensors track environmental data tied to specific assets or shipments.
 - **Bulk Operations:** Import large numbers of assets via Excel.
- **Compliance & Traceability:** Use category, zone, tag, and IoT data for reporting and audit trails (e.g., FSMA 204 food traceability scenarios).
+- **Compliance & Traceability:** Use category, zone, tag, and Edge data for reporting and audit trails (e.g., FSMA 204 food traceability scenarios).
 ---
@@ -163,15 +163,15 @@ TallyFlow is designed to work alongside existing systems:
 - No native AEI rail tag support
 - TallyFlow Print requires a local print server (Print API + Worker) for production use
 - Some advanced rail-specific compliance features are not yet implemented
- IoT and Capture modules may require additional gateway hardware and configuration
+- Edge and Capture modules may require additional gateway hardware and configuration
 ---
 ## Getting Started
-1. Work with your systems integrator to deploy TallyFlow Core and any required backend services (Print, Capture, IoT gateways).
+1. Work with your systems integrator to deploy TallyFlow Core and any required backend services (Print, Capture, Edge gateways).
 2. Configure categories, zones, and org settings in Core.
-3. Install the Mobile App, TallyFlow Print, and/or Capture/IoT components as needed.
+3. Install the Mobile App, TallyFlow Print, and/or Capture/Edge components as needed.
 4. Begin enrolling, printing, or automatically capturing tagged assets using the methods that best fit your operation.
 For detailed Print-specific instructions, see the **TallyFlow Print – User Guide**.
@@ -1,6 +1,6 @@
 # TallyFlow — Capabilities at a Glance
-**RFID, barcode, photo, and IoT asset intelligence that works with your floor—and your ERP.**
+**RFID, barcode, photo, and edge asset intelligence that works with your floor—and your ERP.**
 TallyFlow gives operations teams a practical way to **tag, scan, locate, document, and report** physical assets and shipments. Deploy the full platform or start with the module that solves your biggest pain.
@@ -13,7 +13,7 @@ TallyFlow gives operations teams a practical way to **tag, scan, locate, documen
 | **Core** | Web hub for assets, zones, categories, reporting, exceptions, and integrations |
 | **Assets** | Mobile inventory, enrollment, zone moves, seek-and-find, and **scan-and-print** |
 | **Capture** | Mobile photo capture linked to barcodes, RFID, job/order IDs, and categories |
-| **IoT** | Fixed RFID readers and tunnels—unified multi-reader feeds, health, and control |
+| **Edge** | Fixed RFID readers and tunnels—unified multi-reader feeds, health, and control |
 | **Print** | On-demand barcode & RFID label printing and encoding (Zebra / ZPL-compatible) |
 **End-to-end flow:** print & encode → scan or auto-read → photo proof → exceptions & reports → ERP / BI handoff
@@ -45,7 +45,7 @@ TallyFlow gives operations teams a practical way to **tag, scan, locate, documen
 - **Unified stack** — Web, mobile, fixed RFID, print, and photo in one family—not five disconnected tools  
 - **Hardware flexible** — Works with leading RFID readers (e.g. Impinj, Zebra) and industrial printers  
 - **ERP-friendly** — Complements your system of record; does not force a rip-and-replace  
- **Modular start** — Capture, Print, or IoT can stand alone; Assets + Core when you need full asset control  
+- **Modular start** — Capture, Print, or Edge can stand alone; Assets + Core when you need full asset control  
 - **Proven operations** — Manufacturing, repair/MRO, logistics, retail, and produce / food traceability  
 ---
@@ -56,7 +56,7 @@ TallyFlow gives operations teams a practical way to **tag, scan, locate, documen
 |------------------|-------------|
 | Freight claims or QC photos | **Capture** |
 | On-demand tags & FSMA/GS1 labels | **Print** (+ **scan-and-print** with Assets) |
-| Tunnel / multi-reader RFID | **IoT** |
+| Tunnel / multi-reader RFID | **Edge** |
 | Tool find, counts, zone visibility | **Assets + Core** |
 | Full receive → track → document | **Full platform** |
@@ -1,6 +1,6 @@
 # TallyFlow — Capabilities at a Glance
-**RFID, barcode, photo, and IoT asset intelligence that works with your organization—and your ERP or Asset Platform.**
+**RFID, barcode, photo, and edge asset intelligence that works with your organization—and your ERP or Asset Platform.**
 TallyFlow gives operations teams a practical way to **tag, scan, locate, document, and report** physical assets and shipments. Deploy the full platform or start with the module that solves your biggest pain.
@@ -13,7 +13,7 @@ TallyFlow gives operations teams a practical way to **tag, scan, locate, documen
 | **Core** | Web hub for assets, zones, categories, reporting, exceptions, and integrations |
 | **Assets** | Mobile inventory, enrollment, zone moves, seek-and-find, and **scan-and-print** |
 | **Capture** | Mobile photo capture linked to barcodes, RFID, job/order IDs, and categories |
-| **IoT** | Fixed RFID readers and tunnels—unified multi-reader feeds, health, and control |
+| **Edge** | Fixed RFID readers and tunnels—unified multi-reader feeds, health, and control |
 | **Print** | On-demand barcode & RFID label printing and encoding (Zebra / ZPL-compatible) |
 **End-to-end flow:** print & encode → scan or auto-read → photo proof → exceptions & reports → ERP / BI handoff
@@ -45,7 +45,7 @@ TallyFlow gives operations teams a practical way to **tag, scan, locate, documen
 - **Unified stack** — Web, mobile, fixed RFID, print, and photo in one family—not five disconnected tools  
 - **Hardware flexible** — Works with leading RFID readers (e.g. Impinj, Zebra) and industrial printers  
 - **ERP-friendly** — Complements your system of record; does not force a rip-and-replace  
- **Modular start** — Capture, Print, or IoT can stand alone; Assets + Core when you need full asset control  
+- **Modular start** — Capture, Print, or Edge can stand alone; Assets + Core when you need full asset control  
 - **Proven operations** — Manufacturing, repair/MRO, logistics, retail, and produce / food traceability  
 ---
@@ -56,7 +56,7 @@ TallyFlow gives operations teams a practical way to **tag, scan, locate, documen
 |------------------|-------------|
 | Freight claims or QC photos | **Capture** |
 | On-demand tags & FSMA/GS1 labels | **Print** (+ **scan-and-print** with Assets) |
-| Tunnel / multi-reader RFID | **IoT** |
+| Tunnel / multi-reader RFID | **Edge** |
 | Tool find, counts, zone visibility | **Assets + Core** |
 | Full receive → track → document | **Full platform** |
@@ -30,7 +30,7 @@ TallyFlow is a unified asset intelligence platform with five integrated componen
 | **TallyFlow Core** | Web dashboard for assets, zones, categories, reporting, exceptions, and integrations |
 | **TallyFlow Assets** | Mobile app for inventory, enrollment, zone moves, seek-and-find, and **scan-and-print** |
 | **TallyFlow Capture** | Mobile photo + barcode/RFID capture for documentation and claims |
-| **TallyFlow IoT** | Fixed RFID readers, tunnels, and real-time tag streaming at the dock or line |
+| **TallyFlow Edge** | Fixed RFID readers, tunnels, and real-time tag streaming at the dock or line |
 | **TallyFlow Print** | On-demand barcode and RFID label printing and encoding (including jobs triggered from mobile) |
 Together they cover the full path from **print a tag → scan or read it → document condition → report exceptions → connect to your ERP**, including **scan-and-print** from the field (enroll or locate an asset and print/encode a label without switching apps).
@@ -342,7 +342,7 @@ Together they cover the full path from **print a tag → scan or read it → doc
 **Problem:** Manual scanning cannot keep up with conveyor or high-volume outbound/inbound flow.
 **How TallyFlow helps:**
- Connect multi-reader sites (for example Impinj and Zebra fixed readers) through TallyFlow IoT
+- Connect multi-reader sites (for example Impinj and Zebra fixed readers) through TallyFlow Edge
 - Unify tag reads from tunnels and portals into one clean feed
 - Provide local health, start/stop, and visibility for operations teams
 - Hand off events to Core, spreadsheets, REST consumers, or downstream systems
@@ -369,7 +369,7 @@ Together they cover the full path from **print a tag → scan or read it → doc
 ---
-### 19. Condition & Environmental Monitoring (IoT)
+### 19. Condition & Environmental Monitoring (Edge)
 **Pain authenticity (internal):** `Watch-overclaim` — Cold-chain and handling damage are real. Lead only where sensor-linked deployments are actual and repeatable.
@@ -390,25 +390,25 @@ Together they cover the full path from **print a tag → scan or read it → doc
 | Use case | Pain authenticity (internal) | Primary TallyFlow components | Typical industries |
 |----------|------------------------------|------------------------------|--------------------|
-| Receiving & inbound verification | **Real** | IoT, Assets, Core | Distribution, retail, manufacturing |
+| Receiving & inbound verification | **Real** | Edge, Assets, Core | Distribution, retail, manufacturing |
-| Shipping & outbound verification | **Real** | IoT, Capture, Assets, Core | Manufacturing, 3PL, produce |
+| Shipping & outbound verification | **Real** | Edge, Capture, Assets, Core | Manufacturing, 3PL, produce |
 | Cycle counting | **Real** | Assets, Core | Warehouse, MRO, food distribution |
 | Physical inventory & stock audits | **Real** | Assets, Capture, Core | Any inventory-heavy operation |
-| Zone-based asset tracking | **Real** | Assets, IoT, Core | Repair, manufacturing WIP |
+| Zone-based asset tracking | **Real** | Assets, Edge, Core | Repair, manufacturing WIP |
-| Exception management | **Real-but-packaged** | Core, IoT, Assets | High-volume ops, compliance |
+| Exception management | **Real-but-packaged** | Core, Edge, Assets | High-volume ops, compliance |
 | Seek & find | **Real** | Assets | Tools, equipment, large facilities |
 | Enrollment & commissioning | **Real** | Print, Assets, Core | New programs, fleet tagging |
 | Label printing, encoding & scan-and-print | **Real** | Print, Assets, Core | Produce, retail cases, assets, field re-label |
 | Freight claims documentation | **Real** | Capture | Manufacturing, shipping |
 | Quality control (IQC/IPQC/OQC) | **Real** | Capture, Core | Manufacturing, suppliers |
 | Repair & MRO documentation | **Real** | Capture, Assets, Core | Component repair, industrial MRO |
-| FSMA 204 / food traceability | **Watch-overclaim** | Print, Assets, Core, IoT | Produce, food distribution |
+| FSMA 204 / food traceability | **Watch-overclaim** | Print, Assets, Core, Edge | Produce, food distribution |
 | Compliance audits | **Real-but-packaged** | Core, Capture | Regulated and audited ops |
 | Field document capture | **Real** | Capture | Multi-site sales and logistics |
 | Field installation tracking | **Real-but-packaged** | Capture | Field equipment, controls |
-| Dock-door & tunnel automation | **Real** | IoT, Core | High-volume DCs |
+| Dock-door & tunnel automation | **Real** | Edge, Core | High-volume DCs |
-| ERP / BI integration | **Watch-overclaim** | Core, IoT | ERP-centric enterprises |
+| ERP / BI integration | **Watch-overclaim** | Core, Edge | ERP-centric enterprises |
-| Condition monitoring | **Watch-overclaim** | IoT, Core | Cold chain, sensitive goods |
+| Condition monitoring | **Watch-overclaim** | Edge, Core | Cold chain, sensitive goods |
 ---
@@ -433,7 +433,7 @@ Most successful deployments begin with **one high-pain workflow**, then expand:
 4. **Connect systems** — push exceptions and receipts into ERP, WMS, or BI  
 5. **Expand sites** — same playbook across DCs, plants, or packing locations  
-TallyFlow is designed so you can adopt mobile capture, print, IoT, or full Core visibility in the combination that matches your operation—not an all-or-nothing project.
+TallyFlow is designed so you can adopt mobile capture, print, Edge, or full Core visibility in the combination that matches your operation—not an all-or-nothing project.
 ---
@@ -490,7 +490,7 @@ Use this list when scoping deals: if the customer’s *main* buy is one of these
 | **Indoor RTLS / x-y positioning** | Continuous meter-level map position | Seek-and-find and zone presence ≠ full RTLS |
 | **Digital twin / 3D warehouse map** | Live 3D facility model | Not productized |
 | **Predictive reorder / AI demand** | Forecast usage and auto-purchase | Not inventory planning software |
-| **Autonomous dock / AI operates readers** | Agents start/stop readers and run the dock without humans | IoT can expose status/MCP-style read tools; autonomous control is not the default product story |
+| **Autonomous dock / AI operates readers** | Agents start/stop readers and run the dock without humans | Edge can expose status/MCP-style read tools; autonomous control is not the default product story |
 ### Partial overlap (do not sell as “we do that end-to-end”)
@@ -525,16 +525,16 @@ Effort is relative (**S** ≈ days–1 week, **M** ≈ 1–3 weeks). Validate ag
 | Industry name we could claim more cleanly | What already exists | Minor coding idea | Effort | Components |
 |-------------------------------------------|---------------------|-------------------|--------|------------|
-| **Live dock visibility on mobile** | IoT tag stream + mobile locate | Show recent IoT reads / zone hits inside Assets (read-only first) | **M** | Assets + IoT |
+| **Live dock visibility on mobile** | Edge tag stream + mobile locate | Show recent Edge reads / zone hits inside Assets (read-only first) | **M** | Assets + Edge |
 | **Tool crib check-out / check-in** | Assets, zones, history | Simple status + assignee + optional due date; no reservations calendar | **S–M** | Assets + Core |
 | **Directed zone transfer (light putaway)** | Zone moves | “Expected zone” on asset + flag if scan lands elsewhere; optional confirm list | **S** | Assets + Core |
 | **Cycle count session / variance** | Lightweight inventory | Named count session, expected vs scanned, export variance list | **S–M** | Assets + Core |
-| **Return-to-stock / reverse ship** | Receive/ship style reads | Explicit “return” event type + reason codes; photo optional via Capture | **S** | Assets / IoT + Core |
+| **Return-to-stock / reverse ship** | Receive/ship style reads | Explicit “return” event type + reason codes; photo optional via Capture | **S** | Assets / Edge + Core |
 | **Digital signature on claims/POD** | Capture photos + tags | Capture signature pad or image + link to shipment ID | **S** | Capture |
 | **Before/after photo sets** | Capture categories | Workflow template: paired “before” / “after” (or arrival/complete) groups on same ticket | **S** | Capture |
 | **Exception email digests** | Zone alert time + email recipients | Scheduled daily digest of open exceptions (not only real-time) | **S** | Core |
 | **Webhook on key events** | REST / ERP patterns | Emit webhooks for zone enter/exit, exception opened, print registered | **S–M** | Core |
-| **MQTT / CSV already; MQTT export polish** | IoT CSV, REST, AMQP | Ship MQTT *export* processor if customers already asked (pattern exists as future candidate) | **S–M** | IoT |
+| **MQTT / CSV already; MQTT export polish** | Edge CSV, REST, AMQP | Ship MQTT *export* processor if customers already asked (pattern exists as future candidate) | **S–M** | Edge |
 | **Count reconciliation report pack** | Reports + Excel export | One “audit pack” export: by zone, category, exceptions, duration outliers | **S** | Core |
 ### Slightly larger but still product-shaped (not a platform rewrite)
@@ -546,7 +546,7 @@ Effort is relative (**S** ≈ days–1 week, **M** ≈ 1–3 weeks). Validate ag
 | **Multi-site rollup views** | Org/site filter + consolidated exception counts | **M** | Gap analysis multi-site; start read-only |
 | **QR/barcode generate-from-Core** | Generate simple barcode/QR for assets missing print hardware | **S** | Print already strong; this is “printless” internal tags |
 | **Offline cycle count package** | Harden offline count queue + conflict rules for spotty Wi-Fi | **M** | Market expectation for warehouse; scope carefully |
-| **IoT MCP control (guarded)** | Opt-in start/stop inventory tools with explicit enable + auth | **M** | Status/read already; control is product risk if not gated |
+| **Edge MCP control (guarded)** | Opt-in start/stop inventory tools with explicit enable + auth | **M** | Status/read already; control is product risk if not gated |
 ### Explicitly *not* low-hanging (don’t schedule as “minor”)
@@ -586,4 +586,4 @@ info@sdgsystems.com
 ---
-*TallyFlow — unified asset intelligence across web, mobile, IoT, print, and photo capture.*
+*TallyFlow — unified asset intelligence across web, mobile, Edge, print, and photo capture.*
@@ -32,7 +32,7 @@ TallyFlow is built around exactly **five primary components**, with **Core** as
 - Focused on quality control and visual documentation
 - Sends data to Core via API
-### 5. IoT
+### 5. Edge
 - Rust-based service
 - Integrates fixed RFID readers (Impinj, Zebra, ATID ATF862 / Invengo XC-RF861 — same reader rebranded) and environmental sensors
 - Pushes tag events and sensor data to Core (optional / dashed connection)
@@ -42,7 +42,7 @@ TallyFlow is built around exactly **five primary components**, with **Core** as
 ## Data Flows
 - **Assets, Print, Capture** → Core: Solid lines (primary flows)
- **IoT → Core**: Dashed line (optional, event-driven)
+- **Edge → Core**: Dashed line (optional, event-driven)
 - **Print** additionally supports asset registration back into Core
 - Core Web UI communicates with Core Backend via the same API used by other components