Supply Chain & Procurement worked example

MOQ Impact with unit cost or throughput at the moq order size of 63 units: a worked example

Suppose unit cost or throughput at the moq order size falls to 63 units. This page works the full calculation at that level so you can see exactly which result moves and by how much. Estimate MOQ overbuy exposure from MOQ and required demand.

The inputs for this scenario

  • Unit cost or throughput at the MOQ order size: 63 units (the input this scenario stresses; the baseline uses 125)
  • Unit cost or throughput at your ideal order size: 100 units (held at the documented default)
  • Baseline demand for this part: 100 units (held at the documented default)

Working through the calculation

  • The calculation starts from the formula this tool documents: Margin = gain or available amount - cost or required amount.
  • Moq impact margin works out to -37 % at these inputs, and this is the headline figure for the scenario.
  • Moq impact amount gap works out to -37 value at these inputs.
  • Available moq impact amount works out to 63 value at these inputs.
  • Required moq impact amount works out to 100 value at these inputs.

How this compares with the baseline

  • Against the tool's baseline example, where unit cost or throughput at the moq order size sits at 125 units and the headline result is 25 %, this scenario comes in 248% below the baseline at -37 %.
  • It computes the margin and dollar gap between buying at the supplier's MOQ and buying at your ideal order size. When the numbers land here, the stressed input is the lever to work; the walkthrough above shows exactly how much each output recovers as it climbs back toward the baseline.

Results at a glance

  • Moq impact margin: -37 % (headline result)
  • Moq impact amount gap: -37 value
  • Available moq impact amount: 63 value
  • Required moq impact amount: 100 value

Run it with your numbers

  • To rerun this with your own numbers, open the live MOQ Impact calculator, set unit cost or throughput at the moq order size to your actual value, and adjust the remaining inputs to match your operation.

Last reviewed 2026-05-12.