- **TallyFlow Assets (Mobile) integration with TallyFlow Print** — Enables Scanand Print workflows (e.g. on-demand label printing triggered from mobile asset scans/enrollment). Valuable for field operations where operators need to both locate/verify assets and produce/reprint tags without switching apps.
-~~**TallyFlow Assets (Mobile) integration with TallyFlow Print**~~ — **Shipped:** Scan-and-print (on-demand label printing/encoding triggered from mobile asset scans or enrollment). See [[TallyFlow Use Cases]] §9.
## Code Review Summary
## Code Review Summary
All core repos reviewed and documented in `Product/Code Reviews/`. Key themes:
All core repos reviewed and documented in `Product/Code Reviews/`. Key themes:
- **Mobile (Assets) integration** for Scan-and-Print workflows — Allow the mobile app to trigger print jobs (e.g., reprint, on-demand encoding during field scans or enrollment). Closes the gap between mobile asset management and the Print pillar.
-~~**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.
- **IoT integration** — Expose print job status/events and printer health to TallyFlow IoT for unified dashboards and alerts.
## Recent Changes (develop branch pull - July 2026)
## Recent Changes (develop branch pull - July 2026)
@@ -16,7 +16,7 @@ This repo represents the **mobile pillar** of TallyFlow, distinct from the web,
## Status
## Status
Initial structure review complete.
Initial structure review complete.
## Roadmap / Integration Opportunities
## Roadmap / Integration Opportunities
- Integration with **TallyFlow Print** for Scan-and-Print workflows (scan existing asset or during enrollment → trigger print job for new/replacement labels directly from mobile). Would unify field operations across Assets (Mobile) and Print components.
-~~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 IoT** for real-time location, sensor data, and zone-based workflows directly in the mobile Assets app.
**RFID, barcode, photo, and IoT 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.
---
## The Platform
| Component | What it does |
|-----------|----------------|
| **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 |
| **Print** | On-demand barcode & RFID label printing and encoding (Zebra / ZPL-compatible) |
@@ -13,12 +13,12 @@ TallyFlow is a unified asset intelligence platform with five integrated componen
| Component | Role |
| Component | Role |
|-----------|------|
|-----------|------|
| **TallyFlow Core** | Web dashboard for assets, zones, categories, reporting, exceptions, and integrations |
| **TallyFlow Core** | Web dashboard for assets, zones, categories, reporting, exceptions, and integrations |
| **TallyFlow Assets** | Mobile app for inventory, enrollment, zone moves, and seek-and-find |
| **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 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 IoT** | 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 |
| **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**.
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).
---
---
@@ -143,27 +143,32 @@ Together they cover the full path from **print a tag → scan or read it → doc
**How TallyFlow helps:**
**How TallyFlow helps:**
- Enroll assets in the field with barcode or RFID via mobile
- Enroll assets in the field with barcode or RFID via mobile
- Create and manage assets in Core, including bulk Excel import
- Create and manage assets in Core, including bulk Excel import
- Print and encode labels, then optionally register them automatically in Core
- Print and encode labels during enrollment via **scan-and-print** (mobile → Print), or from Print with optional Core registration
- Support parent/child relationships (for example case and contents, or assembly and components)
- Support parent/child relationships (for example case and contents, or assembly and components)
**Best for:** New RFID programs, tool and equipment fleets, produce case tagging, any site standing up structured asset data
**Best for:** New RFID programs, tool and equipment fleets, produce case tagging, any site standing up structured asset data
---
---
### 9. Label Printing & Encoding
### 9. Label Printing, Encoding & Scan-and-Print
**Also called:** RFID encoding, case labeling, GS1 labeling, SSCC labeling
**Also called:** RFID encoding, case labeling, GS1 labeling, SSCC labeling, field re-label, scan-and-print, on-demand reprint
**Problem:** Labels are inconsistent, serials are wrong, or printing is disconnected from the inventory system.
**Problem:** Labels are inconsistent, serials are wrong, printing is disconnected from the inventory system, or operators must leave the floor app to reprint a damaged or missing tag.
**How TallyFlow helps:**
**How TallyFlow helps:**
- Print and encode RFID and barcode labels (Zebra and ZPL-compatible printers)
- Print and encode RFID and barcode labels (Zebra and ZPL-compatible printers)
- Use workflow profiles for common formats, including **GS1-128 / case labels**, **SSCC**, and **FSMA 204** food traceability templates
- Use workflow profiles for common formats, including **GS1-128 / case labels**, **SSCC**, and **FSMA 204** food traceability templates
- Keep print history and optionally register printed items as assets
- Keep print history and optionally register printed items as assets
- Support simple tags as well as more structured GS1 and parent/child schemes
- Support simple tags as well as more structured GS1 and parent/child schemes
- **Scan-and-print (shipped):** from TallyFlow Assets (mobile), scan an existing asset or complete enrollment and trigger a Print job for a new or replacement label—without switching apps or re-keying identity data
**Best for:** Produce and food packing, retail/apparel case tagging, internal asset labeling, shipping container identification
**Typical scan-and-print moments:**
- Damaged or unreadable label on the floor → scan asset → reprint/encode replacement
- New asset enrollment in the field → print and encode as part of the same mobile workflow
- Correct a wrong label without walking back to a standalone print station workflow
**Best for:** Produce and food packing, retail/apparel case tagging, internal asset labeling, shipping container identification, tool and equipment fleets that re-tag in place
---
---
## Documentation & Compliance Use Cases
## Documentation & Compliance Use Cases
@@ -340,7 +345,7 @@ Together they cover the full path from **print a tag → scan or read it → doc
@@ -359,7 +364,7 @@ Together they cover the full path from **print a tag → scan or read it → doc
Most successful deployments begin with **one high-pain workflow**, then expand:
Most successful deployments begin with **one high-pain workflow**, then expand:
1.**Start with proof** — freight claims photos, QC documentation, or a single receiving dock
1.**Start with proof** — freight claims photos, QC documentation, or a single receiving dock
2.**Add structure** — zones, categories, and consistent tag enrollment
2.**Add structure** — zones, categories, and consistent tag enrollment (including **scan-and-print** for on-demand labeling)
3.**Automate volume** — fixed readers or tunnels where handheld scanning becomes the bottleneck
3.**Automate volume** — fixed readers or tunnels where handheld scanning becomes the bottleneck
4.**Connect systems** — push exceptions and receipts into ERP, WMS, or BI
4.**Connect systems** — push exceptions and receipts into ERP, WMS, or BI
5.**Expand sites** — same playbook across DCs, plants, or packing locations
5.**Expand sites** — same playbook across DCs, plants, or packing locations
@@ -446,11 +451,16 @@ These names appear in RFPs. TallyFlow can **support a piece** of the story (tags
Effort is relative (**S** ≈ days–1 week, **M** ≈ 1–3 weeks). Validate against current code before committing.
Effort is relative (**S** ≈ days–1 week, **M** ≈ 1–3 weeks). Validate against current code before committing.
### Recently shipped (remove from backlog)
| Capability | Status | Notes for sales / docs |
|------------|--------|------------------------|
| **Scan-and-print / field re-label** | **Shipped** | Assets (mobile) → Print: scan existing asset or enroll → print/encode new or replacement label. Covered above in use case **§9**. Prefer this over describing print as desktop-only. |
### Highest leverage (near existing features)
### Highest leverage (near existing features)
| Industry name we could claim more cleanly | What already exists | Minor coding idea | Effort | Components |
| 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** | IoT tag stream + mobile locate | Show recent IoT reads / zone hits inside Assets (read-only first) | **M** | Assets + IoT |
| **Tool crib check-out / check-in** | Assets, zones, history | Simple status + assignee + optional due date; no reservations calendar | **S–M** | Assets + Core |
| **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 |
| **Directed zone transfer (light putaway)** | Zone moves | “Expected zone” on asset + flag if scan lands elsewhere; optional confirm list | **S** | Assets + Core |
@@ -487,12 +497,12 @@ Those are multi-quarter product bets or partner plays, not a small coding sprint
### Suggested sequencing (internal)
### Suggested sequencing (internal)
1.**Scan-and-print (mobile ↔ Print)** — unblocks field ops demos immediately
1.**Cycle count sessions + variance export** — turns “lightweight inventory” into language finance recognizes
2.**Cycle count sessions + variance export** — turns “lightweight inventory” into language finance recognizes
2.**Simple check-out / assignee** — captures tool-crib deals without building rental software
3.**Simple check-out / assignee** — captures tool-crib deals without building rental software
3.**Expected zone + mismatch exception** — half of putaway RFPs without a rules engine
4.**Expected zone + mismatch exception** — half of putaway RFPs without a rules engine
4.**Webhooks + exception digests** — makes ERP/SI partners happier with less custom code
5.**Webhooks + exception digests** — makes ERP/SI partners happier with less custom code
6.**Live dock visibility on mobile** — next cross-pillar integration after scan-and-print
### Positioning reminder (internal)
### Positioning reminder (internal)
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
TNB