Test packages

What packages are

Packages bundle tests for a commercial or operational reason. They are useful for checkups, campaigns, chronic disease monitoring, corporate contracts, and seasonal promotions.

A package is different from a profile. A profile is a clinical test composition. A package is a sales or ordering bundle that can carry its own price and discount logic.

Package fields

Packages include name, code, description, selected tests, package price, discount type, discount value, active status, and creation date. The table shows code, name, number of tests, price, discount, active status, and created time.

Use a package code that staff can recognize. If reception has to guess which campaign package is correct, order creation slows down.

Selecting tests

Choose tests that should be ordered together. Avoid adding tests only because they are popular if they do not belong clinically or commercially. The selected tests still depend on their own sample, reference range, and reporting setup.

If a package contains tests with different sample needs, make sure the collectors know what will be generated.

Pricing and discounts

Package price is the starting price for the bundle. Discount type and value describe how the package is reduced, such as percentage or fixed discount. Keep package pricing aligned with the Pricing Console and contracts.

Do not create hidden financial exceptions in package descriptions. Use the pricing fields so order totals and finance reports remain correct.

Active packages

Only active packages should be available for ordering. Deactivate a package when a campaign ends. Do not delete it immediately if historical orders used it; older records should remain understandable.

Before launching a package

Confirm every included test is active, priced, and configured with sample requirements. Create a trial order, verify price, sample creation, and report layout, then train reception on the exact package name and code.