Scanner Workflow

Filament scanner resolves scanned barcodes to known catalog presets first, then lets users map unknown codes through community-safe flows.

Default Scan Flow

1. Open scanner from Filaments.
2. Scan barcode.
3. If matched, app opens the filament preset detail page directly.
4. User can optionally add that preset to My Spools from the post-scan prompt.

Spool vs Refill Detection

• Resolver prefers exact package match (with-spool vs refill) when that barcode is known.
• When exact package is unavailable, fallback messaging should explain whether it is sold out or not listed.
• UI result chips indicate package match where available.

Unknown Code Handling

• If no dataset match exists, scanner offers Map Unknown.
• Normal users submit mapping suggestions into moderated community queue.
• Owner/Developer can mark trusted mappings directly (with safeguards).

Community Safety Rules

• Non-privileged mappings are confidence-based and vote-driven.
• Verified owner/dev approvals can promote mapping to trusted state faster.
• Existing verified mappings are protected against unsafe overwrite.

Troubleshooting

• If camera freezes, refresh scanner modal and retry with stable lighting/focus.
• If known barcode still prompts map, check whether trusted mapping exists for that exact code and package type.
• If scan latency is high, verify latest sync status and resolver health in dev/admin diagnostics.

Edit History

• 2026-04-12: Added dedicated scanner docs with resolver flow, package detection, and community mapping behavior.

Sources

Based on scanner modal, resolver services, and mapping/community moderation integration in current runtime.