---
title: "Set up skip logic"
slug: "bc-how-to-set-up-skip-logic"
description: "Set up skip logic with Value Class and Activity Class to manage test levels, accepted tests, and frequency for effective quality control."
tags: ["BC", "Business Central", "Concept", "Food", "Task"]
updated: 2026-06-25T09:59:14Z
published: 2026-06-25T09:59:14Z
canonical: "docs.staedean.com/bc-how-to-set-up-skip-logic"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up skip logic

Enter skip logic setup through the **Skip Logic Setup** page.

This page controls the main setup where each combination of **Value Class** and **Activity Class** is linked to several additional settings that the system uses to determine the skip logic.

The **Value Class** and the **Activity Class** are two settings from quality theory that can be set at the item level (see also the **Item Quality Skip Logic Template**).

An example of the setup is:

| Value Class | Activity Class | Level | Accept | Skip | Frequency | Rejected Level | Max Interval |
| --- | --- | --- | --- | --- | --- | --- | --- |
| a | A | 1 | 2 |  | 3 | 1 | 6M |
| a | A | 2 | 3 | 1 | 2 | 1 | 6M |
| a | A | 3 | 4 | 2 | 2 | 2 | 6M |
| a | A | 4 | 6 | 3 | 2 | 2 | 1Y |

In this example, four levels of tests are created for a combination of Value Class a and Activity Class A.

For each level, a number of accepted tests is determined before the system allows the item to move up another level, depending on the frequency. The **Skip** column tells the system when and which tests can be skipped within the current level.

The frequency is the number of times a set of accepted tests must be created within the current level before the system moves to the next level. In this example, three sets of two tests, six tests in total, must pass before the system moves to the next level.

The **Rejected Level** is the level the system applies once a Quality Control test fails.

The **Max Interval** is the time within which the checks take place. If a new Quality Control activity is created later than the time interval after the last activity, the system automatically reverts to the rejected level.

Based on this example, the following rules apply (assuming all tests pass):

Tests 1 through 6 are created and passed and the level remains 1 **(accept (2) + skip (0) times frequency (3) = 6)**.

Test 7 leads to a jump to level 2. Tests 8 and 9 are created and passed, while test 10 is skipped **(three accepts on level 2 and then the fourth is skipped)**.

This repeats twice on level 2: tests 11, 12, and 13 are created and test 14 is skipped.

Creating test 15 leads to a jump to level 3, where tests 16, 17, and 18 are also created **(level 3, Accept = 4)**.

After that, tests 19 and 20 are skipped **(level 3: first accept four, then skip two)**.

This repeats again: tests 21 through 24 are created and tests 25 and 26 are skipped.

> [!NOTE]
> Notes
> 
> - If a test fails on level 2, the level is set back to 1. If a test fails on level 3, the level is set back to 2, and so on.
> - For each level, the system checks whether the last Quality Control activity created falls within the Max Interval set on the line. If that time interval is exceeded, the level is adjusted down as if there was a failed test.
> - The number of levels and the values for Accept, Skip, Frequency, Rejected Level, and Max Interval are set up by the user.

## Related

- [Use skip logic](/bc-how-to-use-skip-logic.md)
- [Skip logic functionality](/bc-skip-logic-functionality.md)
- [Add skip logic templates to items](/bc-how-to-add-skip-logic-templates-to-items.md)