What it would be
A dealer's current stock, laid out as a document rather than a screen: a cover, a contents page grouped by brand, and a page for each piece with its reference, year, condition and what is included with it.
The point is the audience. A client who wants to see what is available this month, a customer standing at a counter, and a collector who will read a printed page more carefully than a listing grid are all badly served by a link to a marketplace.
Why it is worth building from inventory
The stock record already exists in the application, with photographs and specifications attached. A catalogue assembled by hand goes out of date the day it is made, and a catalogue assembled from the record is correct at the moment it is generated. That is the whole argument for putting it here rather than in a design tool.
What has to be settled first
Which fields print, how a piece with no photograph is handled, what happens to prices that are on request, and whether the document is generated on demand or on a schedule. None of that is decided.
The kit overview lists the rest of what is proposed. Features covers what the inventory record does today.