Files
obsidian/TallyFlow/Marketing/Website/Website Requirements from SOWs.md
T

1.8 KiB

Website Requirements & Insights from SOWs

Key Use Cases Observed Across Projects

1. Receiving & Verification Workflows

  • RFID tunnel / fixed reader receiving
  • Barcode + RFID cross-verification
  • Quantity matching against expected data (PO, GTIN, EPC)
  • Exception handling for mismatches

2. Zone-Based Asset Movement

  • Multiple zones (receiving, storage, outbound, delivery)
  • Push/transition assets between zones
  • Time-in-zone visibility and alerts

3. ERP Integration

  • Optional keyboard wedge / direct injection into ERP
  • Import of expected data from spreadsheets / AWBs
  • Writing received data back to ERP tables

4. Tag Printing & Encoding

  • Custom RFID tag encoding (ASCII, proprietary)
  • Integration with NiceLabel or custom printing software
  • TID + EPC uniqueness handling

5. Reporting & Visibility

  • Zone reports
  • Exception reports (shortages, overages, stuck assets)
  • Excel export
  • Search by zone, asset, partial number

Implications for tallyflow.com

Messaging Opportunities

  • "Close the loop between physical assets and your ERP"
  • "Reduce manual scanning and data entry at receiving and packing"
  • "Real-time visibility into where your assets actually are"
  • "Automate verification without changing your existing workflows"

Feature Highlights to Emphasize

  • TallyFlow IoT (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

Target Audiences Visible in SOWs

  • Fashion / Apparel (Alice + Olivia)
  • Manufacturing / Hardware (Assa Abloy)
  • Logistics / Receiving (Bollore)
  • General industrial receiving and asset tracking

Next: Review source code to validate which of these capabilities are already strong.