Inferred purchases
A purchase marked inferred means ModuleDesk believes the customer has the module, without an order for the module itself.
Where it comes from
A Business Care order covering that module, with no direct purchase of the base module in the data. Business Care is bought for a module you own, so its presence implies the module.
And the link from the Business Care product to the module is itself a guess. It is matched by word overlap between the two product names, so an unusual name can attach a Business Care order to the wrong module — and then the inferred purchase names a module the customer does not have.
Two limits worth knowing
It is not checked for being current. A Business Care order from three years ago produces the same marker as one from last month. So "inferred" answers "they probably have it", not "they are entitled to support today" — check the dates in the purchase history for that.
There is no order behind the module. No date, no amount, no order id, because the only order is the Business Care one. The missing purchase may predate your history window, may have been made under another account, or may simply not be in the data.
What it is good for
Deciding whether a question is about a module this customer plausibly owns, which is usually the question that matters when a thread arrives. Not for counting sales or computing revenue.