Minimum Order Quantities
MOQs exist because wholesale is built around batches, packaging efficiency, testing overhead, and document control.
If you treat MOQs as “seller being difficult,” you’ll keep buying like a retail customer and keep getting retail chaos.
This page explains MOQs in a documentation-first, EU-focused wholesale context.
This is not legal advice and we do not guarantee shipping outcomes.
Related pages: Wholesale hub · Wholesale THCA flower ·
Pricing structure · Bulk shipping ·
Documentation · Compliance
Why MOQs exist (the real reasons)
- Batch economics: wholesale is tied to batch/lot units, not “a little bit of everything.”
- Documentation overhead: COAs, verification notes, traceability mapping, and shipment packets cost time to build correctly.
- Packaging and handling: consistent packaging, labeling, and storage handling controls scale better at batch-aligned quantities.
- Shipping efficiency: consolidation reduces routing complexity and paperwork fragmentation.
The moment you ship cross-border, a clean document set matters:
/documentation/shipping-flow/ and
/compliance/shipping-documents/.
MOQs and batch logic (how to think like a buyer)
A serious buyer thinks in batch units and repeatable approvals. MOQs exist to keep batches coherent and easier to trace.
MOQs map to these operational realities
- Testing: each batch needs a decision-grade COA (and sometimes additional panels) to support buyer approvals.
- Traceability: batch/lot IDs must map across COA, invoice, packing list, and labels—more fragmentation equals more risk.
- Receiving discipline: buyers must log, photo, and verify incoming goods by batch.
If you want fewer disputes, enforce traceability:
/compliance/batch-traceability/.
Documentation scales with MOQ (what buyers should prepare)
As order size increases, documentation needs to become more structured—not less. A “big order” without a coherent batch file is just a bigger problem.
Baseline documentation for any wholesale order
- Batch-linked COA(s) with complete fields:
/compliance/certificate-of-analysis/ - Lab verification note stored with the batch file:
/compliance/lab-verification/ - Batch traceability mapping across documents:
/compliance/batch-traceability/ - Shipment paperwork coherence (invoice + packing list + batch map):
/compliance/shipping-documents/
What changes as you scale beyond MOQ
- More lots: if an order spans multiple batches, you must maintain a lot-to-carton/pallet map.
- More documents: shipment packet becomes mandatory, not “nice to have.”
- More QA structure: receiving logs and quarantine triggers must be defined.
Buyer SOP reference: /documentation/quality-assurance/.
MOQ and pricing (what buyers should expect)
MOQs interact with pricing because they influence packaging, testing overhead allocation, and shipping consolidation.
Pricing is not a single knob. It’s a structure.
- Pricing structure: /wholesale/pricing-structure/
- Bulk shipping considerations: /wholesale/bulk-shipping/
- Documentation standards that affect quotes: /documentation/
How to request a quote (the right way)
If you want fast, clean quoting, provide a controlled request—not an open-ended conversation.
Quote request checklist
- Destination country: [country]
- Product format: THCA flower (/wholesale/thca-flower/)
- Target quantity range: [range aligned to MOQ]
- Documentation requirements: COA fields, panel scope, lab verification expectations
- Packaging/label requirements: batch/lot ID format and placement
- Timeline constraints: [if any, without assuming guarantees]
For inquiries: /contact/.
Common MOQ mistakes (and how to stop making them)
Mistake: trying to “sample” wholesale like retail
- Fix: define internal acceptance specs and run a structured QA approval process.
- Reference: /documentation/quality-assurance/
Mistake: approving batches on incomplete COAs
- Fix: enforce COA field completeness and lab verification before approval.
- Reference: /documentation/sample-coa/
Mistake: shipping without a shipment packet
- Fix: build the packet: invoice + packing list + batch map + COAs + verification notes.
- Reference: /documentation/shipping-flow/
FAQ
Do you publish a fixed MOQ table on this page?
MOQ requirements can vary by product format, batch availability, and documentation scope. This page explains the structure and what buyers should prepare.
For category context, start at /wholesale/thca-flower/.
Can we order below MOQ?
Wholesale programs typically align to batch efficiency and documentation overhead. If you need smaller quantities,
structure your request clearly and expect that availability may be limited.
Why do larger orders require more documentation, not less?
Because risk scales with volume and complexity. More lots, more packaging units, and higher inspection exposure require tighter traceability.
Reference: /compliance/batch-traceability/.
Where do I learn what documents should ship with an order?
Use /compliance/shipping-documents/ and
/documentation/shipping-flow/.
Is this legal advice about importing into my country?
No. For context references use /legal-status/, and consult qualified professionals for decisions.