---
title: Grouped Service - Separate Order Processes?
slug: grouped-service-separate-order-processes
createdAt: 2026-01-28T03:03:22.412Z
---

This document answers common questions about ordering behaviour for grouped services in Activate.

# Overview

Grouped services allow multiple related services to be ordered and managed together through a single parent service. The ordering behaviour for grouped services is intentionally constrained to ensure consistency and predictable workflow execution.

# Can a grouped service have a separate order process per child service?

No. The order process is defined and executed only on the parent grouped service.

Child services within a grouped service do not support their own independent order processes.

# Why separate order processes are not supported

Allowing individual child services to run separate order processes would introduce ambiguity and increase the risk of inconsistent provisioning behaviour.

By enforcing a single order process at the parent level, Activate ensures:

- A clear and predictable execution flow
- Consistent validation and approval handling
- Reduced complexity in workflow design and support

# Recommended Approach

Design the order process on the parent grouped service to account for all required logic across its child services.

Where conditional behaviour is required:

- Use Activate expressions to branch logic within the parent order process
- Evaluate selected child services or service options at runtime
- Control downstream actions based on grouped service configuration

This approach keeps grouped services aligned with supported design patterns and avoids unsupported workarounds.