Encapsulation means an object guards its own rules. Keep fields private and expose properties. A property can validate in its setter:
public decimal Price { get => price; set => price = value >= 0 ? value : throw new ArgumentOutOfRangeException(nameof(value)); }
A readonly field can only be set in its declaration or the constructor. An init accessor allows setting a property only while the object is being created, often with an object initializer: new Product { Sku = "K-12", Price = 4.20m }. Mark properties required when callers must always set them.
Never hand out your internal List<T>: callers could add or clear items behind your back. Expose it as IReadOnlyList<T> and provide methods such as Add that enforce the rules. A computed property (public decimal Total => ...) is recalculated on every read, so it can never be stale.
A private list, a read-only view of it, a computed total and one way in that checks its input.