Every time a new customer tier or shape arrives, a switch on type forces you to edit code that already works and was tested. OCP says new behaviour should come from new classes, not edits to old ones. Use it when you can see a list of variants that will keep growing, such as discount types or payment methods. It does not ban editing files for bug fixes, and for two fixed variants a plain if is simpler.