Hello,

That is how out of the box Line Item Validator works. Optimizely Order management UI uses the same validator, which would throw errors if you have expired product. If your customer's business requirement for line item validation is different from what is in the out of the box, you always override the DefaultLineItemValidator implementing ILineItemValidator. We have done the same for most of our Optimizely commerce implementation.

In you case, you want to allow expired products to stay in cart/ purchase order. In our case, we did not want to remove line item from the cart if there is error, but rather show error message to the end user and let the user makes the adjustment to the cart to proceed to checkout.

Hope that helps.

~ Sujit

What you are saying makes sense. That's a very nice feature to notify a user when an expired product is in their cart.

Our case is slightly different. We don't want to allow expired products in user's carts. But, I don't see the utility of validating product expiration in an order. If we want to mark an order fulfilled, it doesn't really matter if the product has expired. We should still be able to edit the order's properties.

In order to get different behavior betwen carts and order, I thought we might need to override OrderValidationService. But, looking more closely after reading your comment, I see we can get the parent order group from the ILineItem in DefaultLineItemValidator.Validate and examine its type:

• if it is a cart we check expiration,
• if it is an order we skip the exipration check.

I still think that the default behavior is a bug: modifying order MetaField values shouldn't be dependent on the published status of the products. But, I think I see how to work around it now.

Thanks for your help.