The short answer
A single product can only be governed by one active Prime MOQ rule at a time. This is resolved automatically. There is no manual conflict-resolution screen to configure, unlike discount-stacking tools where several campaigns can target the same product and need a priority order.
Why it works this way
An order limit is a pass or fail gate, not a stackable adjustment like a discount. Two limits on the same product at once would create ambiguous outcomes: which minimum wins, and do both maximums apply? The design keeps the relationship one to one, so whichever rule currently resolves to matching a product is the one enforced for it.
What to do instead
If you need different constraints on the same product line, split by scope rather than stacking rules.
- Different pack sizes for different variants. Use separate products or variants, or separate rule scopes that do not overlap.
- A weight cap and a case-pack requirement on the same SKUs. Decide which one actually governs, usually weight since it is the harder physical limit, and express the other through your catalogue structure, for example by selling the item only as fixed-size carton variants.
- A tighter limit for one customer group and a looser one for another. Use Customer eligibility, not a second product-scoped rule. Eligibility narrows who the rule applies to without creating a scope overlap.