MoSCoW: definition and role in PIM
MoSCoW is a prioritisation method that ranks requirements as Must have, Should have, Could have or Won't have this time.
In PIM practice, MoSCoW helps a buying committee separate deal-breakers from preferences. Must-haves become knockout criteria and demo scenarios, and should-haves carry weight in scoring. Could-haves break ties, and won't-haves document what is out of scope for the first release.
Illustrative example: a manufacturer classifies ETIM export and ERP integration as must-haves and a supplier portal as should-have. AI description generation becomes a could-have, and print automation a won't-have for phase one.
In a selection, the common failure is too many must-haves. When 80 percent of requirements are musts, prioritisation stops working and every vendor looks similar. Buyers should keep must-haves few and testable, and link each to a scenario. Each must-have should also state how it will be verified, so the scoring team can confirm it during demos.
Related terms
Sources and method
How this page was made: drafted by the PIM Selection editors from the sources listed, checked against the PIMvendors selection method, and signed off by a named expert. Editorial policy.
Cite this page
PIM Selection (2026). MoSCoW: definition and role in PIM. PIMvendors.com. https://pimselection.com/glossary/moscow/ (version 2026-10-14).