Insights

Case-pack and MOQ enforcement for wholesale distributors

A customer orders 7 when it only ships in cases of 12, or places an order too small to be worth the drop. Why letting the order through anyway is more expensive than saying no at the point it's placed.

Most products in wholesale and food distribution aren't actually sold one at a time, whatever the order form allows. A product might only leave the warehouse by the case, a supplier might only sell it to you by the carton, or a delivery run might genuinely not be worth making for anything under a certain order value. None of that is negotiable after the fact — it's decided by how the product is packed and what it costs to get a truck to a customer. The problem is that most ordering systems, especially a B2B store bolted onto a website, don't know any of it, so they take the order anyway and leave someone else to sort out the mismatch.

Where the order breaks before it ever reaches the warehouse

It usually looks small in isolation. A customer types 7 into a quantity field for a product that only comes in cases of 12. A new account places a single-line order for two cartons because nobody told them there's a practical minimum. A rep, trying to be helpful on the phone, says yes to a quantity they shouldn't have. Each one individually is a minor annoyance — a case gets broken open, a delivery goes out under-loaded, someone rings the customer to confirm what they actually meant. Multiplied across a week of orders coming in from a website, a rep app and the phone all at once, it's a steady leak of margin and staff time that never shows up as a single line item anyone notices.

Why "the warehouse will catch it" doesn't hold up

Relying on someone downstream to catch a bad quantity assumes they'll always know the rule, always have time to act on it, and always be willing to push back on a customer's order. None of those hold reliably. A new picker doesn't know which products are case-locked and which aren't. A busy morning means a mismatched order gets waved through rather than queried. And a picker facing an order for 7 units of a 12-pack is put in exactly the position our guide on pick-pack accuracy is about — deciding, under time pressure, whether to break a case, round the quantity up unasked, or hold the order and chase someone for an answer. That's a decision that shouldn't reach the bench at all.

What enforcement should actually do

The point isn't to make ordering rigid — it's to make the rule visible at the moment it matters, before the order exists rather than after:

  • A case pack recorded against the product itself, so an order for a case-locked line rounds to or blocks on a valid quantity, on the online store and when a rep keys it in through sales, not just one or the other
  • A minimum order value or quantity set per customer or per delivery zone where it genuinely reflects delivery cost, rather than one blanket figure applied to every account regardless of size or location
  • Exceptions that follow your actual customer tiers — a long-standing account that always orders oddly can be allowed to, while a new or casual buyer sees the rule applied properly, the same logic behind customer-specific pricing
  • The same rule enforced everywhere an order can start, so a phone order taken by a rep isn't a quiet backdoor around a limit the online store enforces strictly

Get that right and a mismatched quantity gets caught while the customer is still placing the order — where it's a quick prompt to round up or add a line — instead of after it's already a pick-pack problem, a part-loaded delivery, or a call your office has to make.

It compounds with how the product is actually packed

Case-pack rules only work if they're built off the same numbers as everything else the product touches — the same pallet, case and each quantities covered in our guide on unit-of-measure conversions. A case pack rule that's set once and never updated when a supplier changes their case size just becomes a second wrong number for staff to work around, on top of the first.

Built around what actually ships from your warehouse

Which products are case-locked, which customers get an exception, and what a delivery genuinely needs to cost to be worth running are all specific to your business — there's no universal setting that fits every wholesaler. Tell us how your products are packed and which accounts should and shouldn't get flexibility, and we build the enforcement into your ordering rules on your B2B store and everywhere else an order can be placed, rather than selling a generic minimum that doesn't match how you actually trade.

Stop letting the wrong quantity through

If odd quantities and under-value orders are still getting caught on the warehouse floor or by a phone call after the fact, it's worth working out what the ordering step should have stopped instead. See pricing or get in touch to talk through how your products are packed and how your customers actually order.

Frequently asked questions

What actually breaks when case packs and MOQs aren't enforced online?

The order still gets placed — that's the problem. A customer keys in 7 when the product only ships in cases of 12, or places a single-line order too small to be worth a delivery run, and the order sits in the queue looking valid until someone in the office or the warehouse spots it. From there it's a phone call to the customer to round the quantity up, a case broken open to fill an odd number, or a delivery run out for less than it costs to make — none of which shows up until after the order's already in the system.

Isn't this just a warehouse problem, not an ordering one?

It starts as an ordering problem and becomes a warehouse one. If the rule only lives in a picker's head — 'we don't sell that one as a single' — it depends on whoever's on the bench that day catching it, and a new or rushed staff member won't. Enforcing the case pack or the MOQ at the point the order is placed, whether that's a rep keying it in or a customer on your B2B store, stops the bad order before it exists rather than relying on someone downstream to catch it.

Will strict MOQ rules just push small orders away and lose sales?

Only if the rule is applied the same way to every customer, which is rarely what a distributor actually wants. A long-standing account might reasonably get a lower minimum or a case-pack exception a brand-new one doesn't. That's exactly why we build the rule around your actual customer tiers and product ranges rather than one global setting — the same way we build customer-specific pricing — so the system enforces what you'd actually allow, not a blunt cutoff that treats every customer the same.

Does this apply to reps keying in phone orders too, or just the online store?

It has to apply everywhere an order can originate, or the rule isn't really a rule. A case-pack or MOQ check that only fires on the B2B store but not when a rep enters a phone order in the office just moves the same problem to a different entry point. We build the check into the order itself, so it applies the same way regardless of who's placing it or how.

How does this connect to picking and packing once the order's confirmed?

If an order is allowed through in a quantity that doesn't match how the product is actually packed, the problem lands back on the warehouse floor — a picker facing an order for 7 units of a 12-pack still has to decide whether to break a case, round up without asking, or hold the line and chase the customer. Catching the mismatch at the order stage is what keeps it from becoming a picking decision at all, which is the same principle behind getting pick-pack accuracy right in the first place.

Run your whole business on one system.

Book a 30-minute demo and see Cognit running a business like yours — online store and all.

Book my demo →