obsidian/TallyFlow/TallyFlow Use Cases.md

# TallyFlow Use Cases

**RFID, barcode, and photo capture workflows for operations that need visibility, accuracy, and proof.**

This document describes practical use cases where TallyFlow is a strong fit. Each use case uses common industry language so operations, warehouse, quality, and supply chain teams can map TallyFlow to how they already work.

---

## Internal: Pain Authenticity Tags

> **Internal only — not for customer-facing copies.** These tags judge whether the *problem statement* is a real operations pain versus manufactured marketing. They do **not** rate product completeness by themselves.

| Tag | Meaning |
|-----|---------|
| **Real** | Genuine, named ops problem with clear time, money, risk, or compliance cost. Buyers already use this language. |
| **Real-but-packaged** | Underlying pain is real, but the use case is framed as a distinct product category more cleanly than many buyers spontaneously name it—or it is niche / derivative of a stronger adjacent pain. |
| **Watch-overclaim** | The pain is real; the risk is overstating how completely TallyFlow covers the full industry outcome (regulation, ERP depth, sensors, QMS, etc.). Sell the slice you actually deliver. |

**Sales rule:** Lead with **Real**. Use **Real-but-packaged** as supporting outcomes. For **Watch-overclaim**, name the concrete TallyFlow slice (labels, photos, zone history, dock reads) and do not promise the whole regulated or enterprise system of record.


---

## Platform at a Glance

TallyFlow is a unified asset intelligence platform with five integrated components:

| Component | Role |
|-----------|------|
| **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** (works with **Core**) |
| **TallyFlow Capture** | Mobile photo + barcode/RFID capture for documentation and claims |
| **TallyFlow Edge** | Fixed RFID readers, tunnels, multi-reader site edge, and real-time tag streaming |
| **TallyFlow Scout** | Handheld **Collect / Verify / Locate** companion for **Edge** (does **not** replace Assets) |
| **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).

---

## Core Operational Use Cases

### 1. Receiving & Inbound Verification

**Pain authenticity (internal):** `Real` — Shortages, overages, wrong SKUs, chargebacks, and ERP cleanup are concrete dock pains—not invented.

**Also called:** inbound receiving, ASN verification, dock receiving, goods receipt

**Problem:** Teams do not know what actually arrived versus what was expected. Shortages, overages, and wrong SKUs create rework, chargebacks, and ERP cleanup.

**How TallyFlow helps:**
- Match expected shipments (for example ASN / pre-shipment data) against what is read or scanned
- Use fixed RFID tunnels or handheld readers for high-volume box and pallet reads
- Flag shortages, overages, and mismatches as exceptions for follow-up
- Optionally capture photos of damaged or questionable receipts

**Best for:** Distribution centers, retail DCs, 3PLs, manufacturing inbound docks, apparel and packaged-goods receiving

---

### 2. Shipping & Outbound Verification

**Pain authenticity (internal):** `Real` — Wrong/incomplete ship and lack of load proof drive claims and customer disputes every day.

**Also called:** shipping verification, outbound check, load verification, pre-ship scan

**Problem:** Wrong items leave the building, incomplete orders ship, and there is no proof of what was loaded.

**How TallyFlow helps:**
- Confirm tagged cartons, cases, or assets as they pass a dock door, tunnel, or handheld checkpoint
- Document packed and staged freight with photos linked to order, job, or tracking numbers
- Reduce claims by creating a clear record of condition and quantity before the truck leaves

**Best for:** Manufacturing shipping lanes, custom product shippers, 3PLs, produce packing and shipping

---

### 3. Cycle Counting

**Pain authenticity (internal):** `Real` — Full physicals are disruptive; location drift between counts is a standing warehouse/MRO cost.

**Also called:** cycle count, perpetual inventory count, rolling inventory

**Problem:** Full physical inventories are disruptive and expensive. Location accuracy drifts between counts.

**How TallyFlow helps:**
- Run lightweight mobile inventory counts by zone or category without shutting down the floor
- Use barcode or RFID to count faster and with fewer keying errors
- Update asset location with optional zone moves during the count
- Export reports for reconciliation with ERP or WMS

**Best for:** Warehouses, tool cribs, MRO stockrooms, food banks and multi-shelf storage, manufacturing WIP areas

---

### 4. Physical Inventory & Stock Audits

**Pain authenticity (internal):** `Real` — Finance and auditors need a defensible on-hand picture; this is a scheduled, budgeted pain.

**Also called:** wall-to-wall inventory, annual inventory, stocktake, inventory audit

**Problem:** Auditors and finance need a defensible count of what is on hand and where it is.

**How TallyFlow helps:**
- Enroll and count items with handheld devices
- Organize inventory by zone, category, and item identifiers
- Produce searchable records and Excel-exportable reports for audit packages
- Combine tag reads with photo evidence when visual confirmation is required

**Best for:** Operations preparing for financial audits, regulated inventory environments, multi-location stockrooms

---

### 5. Zone-Based Asset Tracking

**Pain authenticity (internal):** `Real` — Lost WIP/tools and invisible bottlenecks are standard manufacturing and repair-shop problems.

**Also called:** location tracking, WIP tracking, yard/floor tracking, process-stage tracking

**Problem:** High-value tools, components, and work-in-process disappear into the facility. Teams waste time searching and cannot see bottlenecks.

**How TallyFlow helps:**
- Define operational zones (dock, inspection, repair bay, cold storage, staging, and so on)
- Track movement between zones via mobile scans or fixed readers
- Measure **time in zone** to spot items stuck too long
- Alert stakeholders when assets exceed configured dwell times

**Best for:** Repair shops, manufacturing cells, component MRO, multi-step production and inspection flows

---

### 6. Exception Management

**Pain authenticity (internal):** `Real-but-packaged` — Exceptions are real, but buyers usually buy this inside receive/ship/zone—not as a standalone category.

**Also called:** shortage/overage handling, variance management, exception reporting

**Problem:** Exceptions are found too late, buried in spreadsheets, or never tied back to a specific shipment or asset.

**How TallyFlow helps:**
- Automatically surface shortages, overages, and unexpected tags during receive/ship workflows
- Flag assets that remain in a zone longer than allowed
- Give supervisors a reporting view so issues can be acted on the same day
- Keep an auditable trail of what was detected and when

**Best for:** High-volume receiving, FSMA and compliance operations, multi-zone repair and manufacturing

---

### 7. Seek & Find (Asset Locate)

**Pain authenticity (internal):** `Real` — Time hunting tools and tagged equipment is a visceral, easy-to-prove floor cost.

**Also called:** asset locate, find-my-asset, tool find, Geiger-style RFID locate

**Problem:** Time and money are lost looking for tools, tagged equipment, or specific cases on a busy floor.

**How TallyFlow helps:**
- Mobile seek-and-find with a Geiger-counter-style experience for one or many tagged assets
- Narrow location using RFID signal strength while walking the facility
- Reduce downtime caused by missing tools or misplaced WIP

**Best for:** Manufacturing tool tracking, field equipment, large warehouses, facilities with high-value tagged assets

---

### 8. Asset Enrollment & Tag Commissioning

**Pain authenticity (internal):** `Real` — Inconsistent tag-to-asset setup is a common reason RFID programs fail before fancy reads matter.

**Also called:** asset onboarding, tag association, item registration, master data setup

**Problem:** Tags exist without a system of record, or assets are entered inconsistently so later tracking fails.

**How TallyFlow helps:**
- Enroll assets in the field with barcode or RFID via mobile
- Create and manage assets in Core, including bulk Excel import
- 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)

**Best for:** New RFID programs, tool and equipment fleets, produce case tagging, any site standing up structured asset data

---

### 9. Label Printing, Encoding & Scan-and-Print

**Pain authenticity (internal):** `Real` — Wrong serials, print disconnected from inventory, and damaged-tag reprint are daily floor friction.

**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, printing is disconnected from the inventory system, or operators must leave the floor app to reprint a damaged or missing tag.

**How TallyFlow helps:**
- 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
- Keep print history and optionally register printed items as assets
- 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

**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

### 10. Freight Claims Documentation

**Pain authenticity (internal):** `Real` — Shippers lose money without proof of condition/quantity at ship time; photo evidence is a known fix.

**Also called:** pre-shipment photography, damage claims support, proof of condition

**Problem:** When freight is damaged or short, the shipper cannot prove what left the dock in good condition and complete quantity.

**How TallyFlow helps:**
- Photograph products, pallets, and loads before shipment
- Associate each photo with job numbers, barcodes, order IDs, tracking numbers, and categories
- Retrieve evidence quickly for carriers, insurance, and customers
- Scale to high photo volume across many users and devices

**Best for:** Manufacturers shipping finished goods, fixture and equipment makers, anyone with recurring freight claims cost

---

### 11. Quality Control (Incoming, In-Process, Outgoing)

**Pain authenticity (internal):** `Real` — Searchable visual history is a real gap for many mid-market plants. Do not stretch into full QMS/CAPA.

**Also called:** IQC, IPQC, OQC, inspection documentation, visual QC

**Problem:** Defects and damage are hard to prove, trends are invisible, and paper inspection records are slow to retrieve.

**How TallyFlow helps:**
- **Incoming QC:** photograph materials and components; tag by PO, supplier, and issue type
- **In-process QC:** capture checkpoints on the line with workstation and defect tags
- **Outgoing QC:** document finished goods, packaging, and labeling before ship
- Build a searchable visual history for root-cause analysis and supplier discussions

**Best for:** Discrete manufacturers, rebuild/repair operations, suppliers under strict customer quality requirements

---

### 12. Repair & MRO Process Documentation

**Pain authenticity (internal):** `Real` — High-value rebuild shops need customer-facing proof and multi-step history; photos + zones match the work.

**Also called:** work-order documentation, repair history, teardown photos, service records

**Problem:** Repair shops need to show customers what was done and retain a visual history of high-value equipment over time.

**How TallyFlow helps:**
- Link arrival, in-process, and completion photos to repair tickets or asset IDs
- Track components through multi-step repair zones
- Use zone duration reporting to find process bottlenecks
- Share clear visual records with customers and auditors

**Best for:** Component repair, compressor/pump rebuild, industrial MRO, aviation-adjacent and high-value part shops

---

### 13. Food Traceability & FSMA 204 Compliance

**Pain authenticity (internal):** `Watch-overclaim` — Regulatory/customer pressure is real. Full FSMA 204 compliance is broader than labels + movement history—sell the TallyFlow slice only.

**Also called:** produce traceability, CTEs/KDEs capture, farm-to-ship tracking, food safety audit support

**Problem:** Manual or paper tracking will not meet modern food traceability expectations or FSMA 204-style audit needs.

**How TallyFlow helps:**
- Track produce and food cases through packing, storage, and shipping with barcode and RFID
- Print compliant labels with dedicated FSMA-oriented templates and GS1 case labeling support
- Use zone and movement history for location and dwell reporting
- Export records for regulators, customers, and internal audits

**Best for:** Produce farms, packing houses, food distributors, cold-chain and perishable operations

---

### 14. Compliance Audits & Audit Trails

**Pain authenticity (internal):** `Real-but-packaged` — Strong under real scrutiny; softer as a generic pitch to unregulated sites that are not being asked these questions yet.

**Also called:** regulatory audit support, chain-of-custody reporting, operational audit trail

**Problem:** When auditors ask “where was this, when, and who touched it?”, answers live in email, paper, and tribal knowledge.

**How TallyFlow helps:**
- Maintain event history for tags, zones, photos, and status changes
- Produce exception and duration reports that show control of the process
- Centralize searchable evidence (scans, reads, photos, documents)
- Support both operational reviews and external compliance requests

**Best for:** Food safety programs, quality system audits, multi-site operations under customer or regulatory scrutiny

---

### 15. Field Document Capture

**Pain authenticity (internal):** `Real` — BOLs and receipts lost in email/text/mail delay accounting and service; boring and very common.

**Also called:** digital BOL capture, paperwork digitization, proof-of-delivery imaging

**Problem:** Bills of lading, receipts, and signed deliveries are mailed, texted, or lost—delaying accounting and customer service.

**How TallyFlow helps:**
- Photograph paperwork in the field or warehouse
- Tag images with sales order, BOL, location, or work order identifiers
- Sync to a shared cloud library so office and field share one source of truth
- Search and filter instead of sorting physical stacks or email threads

**Best for:** Distributed sales teams, multi-site shippers, delivery-heavy manufacturers, field service organizations

---

### 16. Field Installation & Service Tracking

**Pain authenticity (internal):** `Real-but-packaged` — Real in niches (irrigation, distributed equipment); not a universal pain across all TallyFlow prospects.

**Also called:** installed base tracking, as-built documentation, service locate

**Problem:** Equipment installed in the field is hard to find later, especially when buried or spread across sites.

**How TallyFlow helps:**
- Document installations with photos and barcode/RFID identifiers
- Capture GPS location with the visual record
- Help service teams locate equipment and understand site conditions before arrival

**Best for:** Irrigation and controls, construction-related products, distributed equipment fleets

---

## Automation & Integration Use Cases

### 17. Automated Dock-Door & Tunnel Reads

**Pain authenticity (internal):** `Real` — Manual scan cannot keep up with conveyor or high-volume doors; this is why portals/tunnels exist.

**Also called:** RFID portal reading, tunnel scanning, hands-free dock capture

**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 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

**Best for:** Retail/apparel DCs, automated shipping lines, multi-reader warehouses

---

### 18. ERP & System Integration

**Pain authenticity (internal):** `Watch-overclaim` — The handoff gap is real and kills projects. “We integrate” is only as strong as proven patterns per customer ERP/WMS.

**Also called:** ERP handoff, WMS/ERP receive update, system of record sync

**Problem:** RFID and mobile capture data never reliably lands in the systems people trust (ERP, WMS, BI).

**How TallyFlow helps:**
- Integrate via keyboard wedge, database patterns, REST APIs, webhooks, and spreadsheet/CSV paths
- Support intermediary integration patterns when direct ERP access is constrained
- Keep TallyFlow as the operational capture layer while the ERP remains the financial/system of record
- Feed BI tools (for example Power BI) from unified reader and event data

**Best for:** Mid-market manufacturers and distributors already on ERP platforms who need RFID/mobile data without replacing core systems

---

### 18b. Handheld Collect, Verify & Locate with TallyFlow Scout (Edge)

**Pain authenticity (internal):** `Real` — Floor teams need a simple handheld to feed the site edge, check barcode↔RFID identity, and find a tag without standing up full Core mobile.

**Also called:** remote reader handheld, GS1 RFID verify, seek-and-find offline

**Problem:** Fixed readers cover portals; people still walk the floor with handhelds. Wrong EPC encodings slip through when barcode and RFID are not checked together. Full Core asset apps are heavier than a dock verify/find job.

**How TallyFlow helps:**
- **Collect** — scan barcode/RFID on industrial Android devices (or camera barcode on a phone); submit to **TallyFlow Edge** as a remote reader, or export **CSV** when Edge is offline
- **Verify** — scan a GS1 barcode, then RFID tags; confirm each EPC encodes the same GS1 identity key (SGTIN/SSCC/GRAI/GIAI-style interoperability). Optional auto-confirm when the list is all matches
- **Locate** — seek-and-find by EPC, GTIN/GS1, or Internal part with RSSI/geiger feedback; works **offline** without Edge or Core
- Does **not** replace **TallyFlow Assets** (Core enrollment, inventory, zones, scan-and-print)

**Typical fit:** Edge sites, SI demos, encode/pack verify, floor find next to tunnels/portals.

---

### 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.

**Also called:** cold-chain monitoring, shock/temperature tracking, sensor-linked assets

**Problem:** Location alone is not enough when temperature, humidity, or handling damage matter.

**How TallyFlow helps:**
- Link environmental sensor data to assets or shipments
- Automate status updates without constant manual scanning
- Combine condition events with zone and movement history in Core

**Best for:** Perishables, sensitive components, high-value shipments with handling risk

---

## Use Case Matrix (Quick Reference)

| Use case | Pain authenticity (internal) | Primary TallyFlow components | Typical industries |
|----------|------------------------------|------------------------------|--------------------|
| Receiving & inbound verification | **Real** | Edge, Scout, Assets, Core | Distribution, retail, manufacturing |
| 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, Edge, Core | Repair, manufacturing WIP |
| 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, 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** | Edge, Scout, Core | High-volume DCs |
| ERP / BI integration | **Watch-overclaim** | Core, Edge | ERP-centric enterprises |
| Condition monitoring | **Watch-overclaim** | Edge, Core | Cold chain, sensitive goods |

---


### Pain authenticity rollup (internal)

| Tag | Count | Use cases |
|-----|-------|-----------|
| **Real** | 13 | Receiving; shipping; cycle count; physical inventory; zone tracking; seek & find; enrollment; label/scan-and-print; freight claims; QC photos; repair/MRO docs; field document capture; dock/tunnel automation |
| **Real-but-packaged** | 3 | Exception management; compliance audit trails; field installation tracking |
| **Watch-overclaim** | 3 | FSMA 204 / food traceability; ERP & system integration; condition & environmental monitoring |

**One-pager note:** The Capabilities one-pager compresses these same pains into outcome lines. It does not introduce separate manufactured pains. Prefer leading the one-pager with **Real** outcomes; keep FSMA, ERP, and condition language tied to the concrete slice delivered.

## How Customers Typically Start

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  
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  
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, Edge, or full Core visibility in the combination that matches your operation—not an all-or-nothing project.

---

## Workflows TallyFlow Does Not Cover

The following are common industry workflow names that customers often ask about. They are **not primary TallyFlow products**. Saying “no” (or “not without a partner system”) early protects fit and avoids competing with full WMS, ERP, CMMS, or rail platforms.

Use this list when scoping deals: if the customer’s *main* buy is one of these, TallyFlow is usually the wrong primary system—or only a side car (tags, photos, dock reads) next to another product.

### Warehouse & fulfillment (WMS / OMS territory)

| Workflow name | What buyers usually mean | Why it is out of scope |
|---------------|--------------------------|------------------------|
| **Directed picking / pick paths** | System tells pickers *what* to pick, *where*, and *in what order* | TallyFlow tracks and verifies tagged items; it does not run order-driven pick logic, pick waves, or path optimization |
| **Wave / batch / cluster picking** | Group orders into pick waves for the floor | Order orchestration and labor assignment live in WMS/OMS |
| **Pack & ship / cartonization** | Decide box sizes, pack lists, carrier labels as a packing station app | Print can do labels; TallyFlow is not a packing-station WMS |
| **Slotting / putaway rules engine** | Optimal bin assignment based on velocity, cube, affinity | Zone moves exist; automated slotting algorithms do not |
| **Inventory allocation / soft allocation** | Reserve stock against open orders | Financial/order allocation belongs in ERP/WMS |
| **Replenishment / min-max / kanban automation** | Auto-create moves when locations hit reorder points | Exception and visibility yes; replenishment planning no |
| **Labor management (LMS)** | Time standards, productivity scoring, incentive pay | Outside the asset/tag domain |

### Transportation & yard

| Workflow name | What buyers usually mean | Why it is out of scope |
|---------------|--------------------------|------------------------|
| **TMS / carrier selection** | Rate shopping, tendering, freight audit | TallyFlow documents freight condition; it does not manage carriers |
| **Route planning / last-mile** | Delivery routes and driver apps | Not a delivery management platform |
| **Yard management (YMS)** | Trailer spots, gate appointments, yard jockey tasks | Dock/tunnel reads can feed a YMS; full yard ops are not built in |
| **AEI rail / AAR equipment ID** | Automatic Equipment Identification on railcars | **No native AEI tag support** today; not a rail AEI system |
| **Fleet telematics** | GPS trailers/trucks, ELD, engine data | Different stack from site RFID/photo capture |

### Asset finance & shared equipment pools

| Workflow name | What buyers usually mean | Why it is out of scope |
|---------------|--------------------------|------------------------|
| **Fixed-asset accounting / depreciation** | Capex books, depreciation schedules, cost centers | Competitors in “office asset tracking” lead here; TallyFlow is operational, not GL |
| **Equipment rental / reservations** | Book assets, due dates, late fees, availability calendar | Check-out style products (e.g. Cheqroom-class) are a different product category |
| **Customer self-service portal** | External users reserve or return gear without staff | Not a multi-tenant self-service rental portal |
| **ITAM / software license management** | Laptops, SaaS seats, MDM | Different vertical (IT asset management) |

### Maintenance & production systems

| Workflow name | What buyers usually mean | Why it is out of scope |
|---------------|--------------------------|------------------------|
| **CMMS / EAM work orders** | Preventive maintenance schedules, work order lifecycle, spare parts BOM for PM | Capture/repair photos and zone tracking help *around* MRO; full CMMS is not the goal |
| **MES / production scheduling** | Work centers, routing, OEE, dispatch | WIP zone visibility ≠ manufacturing execution |
| **Full serial genealogy / as-built BOM** | Multi-level as-built tree for every component forever | Parent/child tags exist; deep product genealogy is PLM/MES |
| **Quality management system (QMS)** | CAPA, NCR, ISO document control | Capture supports *visual* QC evidence; not a QMS |

### Advanced location & AI (often assumed, not shipped as product)

| Workflow name | What buyers usually mean | Why it is out of scope |
|---------------|--------------------------|------------------------|
| **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 | 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”)

These names appear in RFPs. TallyFlow can **support a piece** of the story (tags, photos, zone events, dock reads) but is not the system of record for the full process:

| Name | Partial fit | Still needs another system for… |
|------|-------------|----------------------------------|
| **Putaway** | Confirm item moved into a zone | Slotting rules, directed putaway tasks |
| **Returns / RMA** | Photo damage on return, re-enroll tags | RMA authorization, credit, reverse logistics |
| **Transfer orders** | Scan/move between zones or sites | Inter-company inventory accounting |
| **Proof of delivery (POD)** | Photo of paperwork or load | Carrier POD workflows, e-signature standards at scale |
| **Chain of custody** | Event + photo timeline | Legal/forensic custody products with locked evidence kits |
| **Cold chain compliance** | Sensor-linked events when integrated | Validated pharmaceutical cold-chain platforms |

**Sales rule of thumb:** If the buyer’s success metric is “orders ship correctly from a WMS,” buy WMS. If the metric is “we know what was tagged, where it was, what it looked like, and what the dock read,” buy TallyFlow (often *with* WMS/ERP).

---

## Internal: Low-Hanging Fruit (Minor Coding)

> **Not for customers.** Internal product notes: workflows that are *adjacent* to what TallyFlow already does, where a small amount of productized UI/API work would let sales honestly claim more of the industry name—without becoming a WMS or CMMS.

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)

| Industry name we could claim more cleanly | What already exists | Minor coding idea | Effort | Components |
|-------------------------------------------|---------------------|-------------------|--------|------------|
| **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 / 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** | 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)

| Industry name | Minor coding direction | Effort | Notes |
|---------------|------------------------|--------|-------|
| **ASN receive UI (repeatable)** | Productize Alice+Olivia-style expected-vs-actual box matching as a configurable profile (expected list import + match + exceptions) instead of one-off console | **M** | High sales leverage for retail/DC; keep ERP write as config |
| **Approval on leave-zone** | Rule: if asset leaves Zone X without status/approval flag → exception | **M** | Competitive gap list item; don’t build full BPM |
| **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 |
| **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”)

- Full **WMS** picking, waves, cartonization  
- **Depreciation / fixed-asset accounting**  
- **CMMS** PM schedules and work-order engines  
- Native **AEI rail** compliance stack  
- True **indoor RTLS**  
- **AI demand planning**  

Those are multi-quarter product bets or partner plays, not a small coding sprint.

### Suggested sequencing (internal)

1. **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. **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. **Capture signature + before/after templates** — strengthens claims, POD, and repair packaging  
6. **Live dock visibility on mobile** — next cross-pillar integration after scan-and-print

### Positioning reminder (internal)

When a low-hanging feature ships, update the **covered** use-case section and the matrix—but keep this **out of scope** list honest. The commercial edge remains: **tag → read/scan → photo → exception → ERP-adjacent handoff**, not “replace the WMS.”

---

## Next Steps

- **Map your process** — identify whether your biggest pain is receiving accuracy, claims, tool loss, cycle counts, or compliance documentation  
- **Schedule a demo** — walk through the use cases above with sample hardware and your real labels or identifiers  
- **Pilot one site or one workflow** — prove value in weeks with a focused scope before multi-site rollout  

**Contact**  
info@sdgsystems.com  
[sdgsystems.com/tallyflow](https://sdgsystems.com/tallyflow)

---

*TallyFlow — unified asset intelligence across web, mobile, Edge, print, and photo capture.*