diff --git a/docs/partials/_ai-powered-barcode-scanning.mdx b/docs/partials/_ai-powered-barcode-scanning.mdx index 68933961..40c358fc 100644 --- a/docs/partials/_ai-powered-barcode-scanning.mdx +++ b/docs/partials/_ai-powered-barcode-scanning.mdx @@ -1,4 +1,4 @@ -Modern barcode scanning workflows face recurring challenges that slow down operations and induce errors: scanning from awkward angles and long distances, decoding the right code in crowded environments, dealing with damaged labels, and managing intentional versus accidental duplicate scans. Traditional barcode scanners rely on rigid, time-based logic and manual user intervention to handle these scenarios, resulting in slower workflows, more errors, and higher user frustration. +Barcode scanning workflows commonly face operational challenges such as scanning from awkward angles or long distances, selecting the correct barcode in dense environments, handling damaged labels, and preventing unintended duplicate scans. Traditional scanners handle these scenarios with rigid time-based logic and manual user intervention, which slows down workflows and increases errors. Scandit's AI-powered scanning capabilities, built into the **Scandit AI Engine** and available in both **SparkScan** and **Barcode Capture**, solve these problems by analyzing context and user intent in real-time. The scanner adapts dynamically to environmental conditions and user behavior, eliminating the need for manual settings adjustments or workarounds. diff --git a/docs/partials/advanced/_sparkscan-customization.mdx b/docs/partials/advanced/_sparkscan-customization.mdx index 70c2ff43..23796d78 100644 --- a/docs/partials/advanced/_sparkscan-customization.mdx +++ b/docs/partials/advanced/_sparkscan-customization.mdx @@ -43,7 +43,7 @@ export default function SparkScanCustomization({ Trigger button -

The default trigger button in SparkScan has been designed based on our experience and feedback received to be generally suited across a multitude of industry use cases, custom trigger implementations are still supported.

+

The default SparkScan trigger button is optimized for common industry use cases based on customer feedback and implementation experience. Custom trigger implementations are also supported.

This is achieved by hiding the default trigger button (via {triggerButtonApi}), and then controlling the scanning process as best suits your needs: