Direct vs Hyper Tags: Choosing the Right Execution Path

A common implementation mistake is using one tag mode for every workflow. Hypertag provides two execution paths because operational goals differ.

Direct tags

Direct tags are ideal when a scan should route immediately to a destination URL.

Use Direct when you need:

• Fast setup
• Minimal integration overhead
• Reliable redirect behavior

Typical examples include SOP pages, asset instructions, and customer-facing landing routes.

Hyper tags

Hyper tags trigger a webhook and can include a JSON payload.

Use Hyper when you need:

• Workflow automation
• System-to-system integration
• Context-aware processing on scan

Typical examples include check-in workflows, maintenance logging, inventory transitions, and event-driven backend actions.

Decision framework

Choose Direct if:

• Your primary requirement is immediate destination routing.
• No backend orchestration is required.

Choose Hyper if:

• A scan must initiate business logic.
• You need execution responses and downstream handling.

Implementation pattern that works

Many teams start with Direct for initial rollout speed, then migrate selected tags to Hyper as process maturity increases.

This phased model limits early complexity while keeping a clear path to automation.

Create one Direct and one Hyper tag to compare behavior.