docs: TallyFlow Scout marketing + Edge/Print/Capture feature refresh
Review tallyflow-assets-iot (TallyFlow Scout v0.5.3): Collect, Verify, Locate with Edge remote reader / offline CSV locate. Clarify Scout does not replace Core Assets. Refresh Edge, Print parent-container and multi- unit identity notes, Capture share/offline/barcode notes, architecture, use cases, capabilities, and website drafts after src/ repo pulls.
This commit is contained in:
@@ -85,3 +85,15 @@ Operator → TallyFlow Print app → Print API → Print worker → Zebra printe
|
||||
- Additional bug fixes and profile enhancements.
|
||||
|
||||
*Last updated: 2026-07-17 by Hermes Agent (after develop pull using hermes_agent_ed25519 key)*
|
||||
|
||||
|
||||
## Recent Changes (develop pull - 2026-07-27)
|
||||
|
||||
**Theme:** Parent container namespace + safer multi-unit retail identity + register preflight.
|
||||
|
||||
- Reserve **SDG RAIN assignment 8000** for parent container tags (Internal/simple CIN and part-serial reject 8000 for customer unit tags).
|
||||
- Inject **per-unit AI 21** into retail GS1-128 companion barcodes (quantity > 1 no longer identical GTIN+lot barcodes).
|
||||
- **Reject print-and-register** when units share identity tags (post-print preflight; clear Core collision error).
|
||||
- Print UI: hide retail parent linking; require serials for multi-unit register; same 8000 parent reservation on Internal tags.
|
||||
|
||||
*Marketing implication:* Prefer concrete language — parent/container EPC namespace, unique serials on multi-unit retail companions, register blocked on duplicate identities — over vague “better serialization.”
|
||||
|
||||
Reference in New Issue
Block a user