Advanced Product Checks
Besides the previously mentioned basic Product Checks, there are also advanced Product Checks [the ones that we highlighted in the image below]:
Action-Based Checks
Print Check
Before using a print check, create a docx report. The operator taps a button to download the report, or to preview it as a PDF.
- Product order report: the docx report that the operator downloads.
- Filename: the name of the downloaded file. You can use parameters.
- Convert to pdf turns the report into a PDF. Open pdf as a preview shows it on screen instead of downloading it.
Email Check
The operator taps a button to send an email.
- Sender: Open email client opens the device’s email app with the email pre-filled. Send email from Azumuta sends the email from Azumuta.
- To, Subject, and Body are required. Bcc is optional. With Send email from Azumuta, you can also set Reply to and add users and groups as recipients.
- Include email attachment (only when Azumuta sends the email) attaches one product order report, optionally as a PDF.
- You can use parameters in the fields.
Timer Check
The operator can submit the timer check once the timer has run its full duration. Enable Required to be filled in before proceeding to next instruction step under General options to prevent skipping the timer with the forward button.
- Choose Count down from or Count up to a number of seconds.
- Automatically start timer starts the timer when the step opens. Automatically continue after timer finishes moves on without the operator tapping Continue.
- The duration can be read from a parameter.
Procedure Check
The operator taps a button that runs an action.
- Button label: the text on the button.
- Action: Send a command to the selected peripheral (see integrating Azumuta with peripherals), or Call a webhook.
- Always allow re-sending command (or Always allow re-calling the webhook) lets the operator press the button again, even when editing submitted answers is disabled.
- Webhook options: Webhook URL (it must be reachable from Azumuta's servers), the HTTP method, Authentication, Webhook payload (except for GET), and Automatically continue if successful (a 2xx response). The webhook runs when the operator taps the button. See webhooks in Azumuta.
Note: You can contact support@azumuta.com if you need help in integrating peripheral devices or making your own webhooks.
Special Checks
Link Product Order Check
The operator links another product order, such as a sub-assembly, to the current one. This check needs the Quality Management module. See Product order linking to learn how linked product orders are shown.
- Link product order by…: Order number, or Parameter (then enter the Parameter name).
- Product order must be of following article or category and Product order must have the following variants limit which product orders can be linked.
- Only allow linking this product order once: a scanned product order can only be linked once, across all product orders.
Parts Check
A parts check ensures operators use the correct parts, in the correct quantity, when assembling a product. The operator scans a part’s barcode or ticks it off manually. You can add one or multiple parts to a parts check. This check needs the Resources add-on.
If the wrong barcodes/QR codes were scanned or the wrong part names were inputted, then the screen will show a red signal signifying that there’s an error, and the operator cannot proceed to the next step.
Similarly, if the number scanned barcodes/QR codes or inputted part names don’t match the required quantity set by the admin, a red error signal will appear, and the operator won’t be able to proceed to the next step until everything is in order.
This Product Check is useful to prevent incorrect parts from being used in the assembly process, as well as to ensure that the part quantity always matches the required specifications.
- Choose the parts to scan on the step’s Parts tab. By default, operators can scan them or tick them off manually.
- Scan count must match part quantity: a part with a quantity above 1 must be scanned that many times.
- The barcode type and format options work as for the barcode check.
Variants Check
In a work instruction, an operator can choose which variants to show or hide on their screen. This check needs the Variants add-on. This is useful because:
- When an operator works for one specific variant for a long time, the presence of other variants on their work instruction can be distracting. Thus, operators can choose to hide irrelevant variants from their view.
- Operators can quickly adapt to changes in production requirements by switching between different variants quickly and easily. Showing and hiding variants in a Work Instruction can be done in a matter of seconds.
- Operators can skip variants that they aren’t familiar with yet.
When there is no saved answer and no active variant selection has been set, all variants start selected by default. Turn on Show empty selection when no variants have been selected previously to start with none selected in that case. An existing selection or saved answer is kept, even if it is empty.
Automatic ID Check
An automatic ID check generates a unique, formatted identifier that the operator can insert with one tap, instead of typing it manually. This is useful for traceability numbers, batch codes, or serial numbers that need to follow a consistent format.
You configure a single Format field that combines literal text with placeholders:
{###}inserts a zero-padded counter. The number of#characters sets the digit width, and an optional trailing letter sets the number base:dfor decimal (default),xfor hexadecimal,ofor octal, orbfor binary.{YYYY-MM-DD}(or any other date/time pattern) inserts the current date or time.{slot}or{batch}inserts a value specific to the current slot or batch.
A format can contain only one counter section and one slot section, and must include at least one counter or date/time section.
On the operator view, the operator taps Generate to fill in the field with the next value for the configured format, and can edit it before saving.






