How MOQ Numbers Are Used When Generating Parts Orders

You’ve probably heard that Parts-in-Place takes into account the Multiple Order Quantity (MOQ) settings for parts when calculating the quantities to purchase. There are some nuances in how this calculation works, so let me explain it a bit more.

First of all, the MOQ values are treated in Parts-in-Place as the Multiple Order Quantities, not simply Minimal. This means that the system will try to round the order quantities up to the nearest multiple of MOQ. More specifically, here is how it works:

The MOQ values are set in the Parts Library, in the Multiple field.

MOQ values are set on the Parts Library screen

The Parts Order document has three quantity-related columns:

  • Min Required
  • Multiple
  • To Order

Parts Orders Have Three Quantity Fields

When you instruct Parts-in-Place to generate a Parts Order for your upcoming builds, the system will fill in those quantity columns as follows:

  1. The Min Required quantities will be calculated to satisfy the needs of your planned builds, taking into account your current inventory on hand.
  2. The Multiple values are just copied “as is” from the Parts Library.
  3. The To Order is set based on the following rule:
    • If the Multiple is a numeric value, the To Order is rounded up based on the Multiple and the Mininimum Required.
    • If the program is unable to interpret the Multiple value as numeric, the Qty To Order is set to match the Minimum Required, and in addition the text “Verify Multiple” is added to the Notes field on the Parts Order, which causes this particular table row to be highlighted in yellow.

If the MOQ setting is not numeric, the system will highlight that item

Generally, whenever the program finds the word “verify” in the Notes field, it will highlight that row, so you can use this feature to highlight any item for your convenience.

So, the important things to remember about the MOQ setting are these:

  • The value is set on the Parts Library screen, individually for each part.
  • You may leave the MOQ field blank, in which case it will not be used for that particular part.
  • If you specify a numeric MOQ value, it will be used when generating lists of parts to order: the calculated minimum required quantities will be rounded up to the nearest MOQ multiple.
  • If the system finds the MOQ setting for a component to be non-numeric, it will be ignored in the calculation, and the text “Verify Multiple” will be added to the Notes field, and that item on the Parts Order will be highlighted.


  1. Your app looks very interesting, probably what we need right now, but I want to clear up some things first. We’re a small operation right now, maybe going to grow a bit more in the next year.

    Does “free” right now mean that next year there’s going to be a fee for this? That might be fine, as long as the price isn’t crazy. Please explain more about your plans in this regard.

    We tried to use some other programs and apps, but didn’t commit to them. Their prices blew us out of the water. Budget is a big concern for us.

    • Nick Ivanter says:

      We are very likely to keep a free tier indefinitely. I.e. there will be different pricing plans, depending on usage levels, and an entry level will always be free. I can’t tell you yet how exactly those usage levels will be defined, i.e. what will be included in each pricing plan. We are going to need to collect more usage statistics to determine what makes sense.

      For paid-for plans, we are thinking $20-$60 range per month, again depending on usage levels.

      • That kind of pricing structure won’t break the bank. We’d be up for it especially if we see a strong level of commitment in terms of support and new features. But not so many new features that the “soup gets too thick to stir.” Functionality and speed are important aspects too.