Propago’s Aggregates already let you group several parts (SKUs) under a single quantity-based limit. Now, with our Multi-Layered Part Aggregate Limits update, you can place the same part in multiple Aggregates that each have their own rules—so you can nest, overlap, and combine limits any way your programs demand.
Quick refresher
Part Limits– cap how many units of one SKU a user (or group) can order during a time-frame, with optional approval or hard stop.
Aggregates – group different SKUs and apply one shared part-limit across the set (e.g., 10 total polos + tees per month).
Previous behaviour
NEW behaviour
A part could belong to one QTY-type Aggregate at a time.
A part can belong to many QTY-type Aggregates simultaneously.
Only one aggregate limit could fire for that part.
All applicable limits are evaluated, and whichever triggers first stops the order (or routes for approval) based on each Aggregate’s setting.
Benefits to You
Layered compliance – impose a category limit (e.g., any shirts ≤ 6/mo) and a collection-wide limit (e.g., all apparel ≤ 10/mo) without extra configuration.
Budget protection – prevent shoppers from side-stepping limits by mixing items across categories.
Simpler catalog administration – build granular or umbrella rules with the same parts, no duplicates.
How It Works
Create (or edit) your Aggregates
Portals → Select a Customer → Aggregates → Add New.
Add parts to each Aggregate. The same SKU can now be picked in more than one Aggregate list.
Assign Part Limits to individual parts in these Aggregates as needed to create the desired multi-layered Aggregate limitations.
Example of Multi-Layered Part Limit Aggregation
SKU
Individual Part Limit
Aggregate membership
PANTS-A
6 / month
Pants AggregateApparel Aggregate
PANTS-B
10 / month
Pants AggregateApparel Aggregate
SHIRT-A
6 / month
Shirts AggregateApparel Aggregate
SHIRT-B
—
Shirts AggregateApparel Aggregate
Multi-Layered Aggregate in action:
User buys 6 SHIRT-A on April 5.
On April 20 the same user tries to buy PANTS-B (qty 10).
Shirts Aggregate is already maxed → no shirt issue.
Pants Aggregate would allow 10 pants.
Apparel Aggregate has 10-unit limit, but 6 units already spent on shirts → only 4 units remain.
Result: cart is blocked (or routed for approval) unless quantity is reduced to 4 or less.
