Choose the first catalog release around a complete buyer route

The first catalog release does not need every future filter or integration. It does need a complete route from useful information to an understandable next action.

Choose a representative scope

A Czech supplier might start with a reviewed product family and its key items. The selection should include enough variation to test the content model, documents and inquiry, rather than only the easiest record.

Name the manual work

If staff still check availability or prepare a quotation manually, explain that process. A deliberate human step can work; an unsupported instant-order promise cannot be filled by an unfinished integration.

Agree acceptance examples

• A buyer identifies a specific item and sends a useful request.
• A buyer needs help choosing and can explain the application.
• A document is missing or a product is unavailable.
• Staff can recognize the request and continue it.

Keep later work visible

Record which integrations, content and features are deferred and who owns the current workaround. The next phase should extend a known process rather than repair an unexplained gap.

W3C's planning material illustrates the value of assigning responsibilities early. Use the handover sheet to identify your own first release and discuss whether catalog work should begin with data review or development.