Internal ID and display name
The internal ID is the name your team uses for the item, such as rp.guild.pass; the display name is what players read. Keeping both stops the visible name from becoming the only reference.
This is the planning layer between "we have a few cool items" and "we now have thirty identifiers and nobody remembers which paper is which". Keep a local registry, search it, export it, and stop guessing.
One entry per custom item. The catalog keeps them searchable, flags clashes and exports the list for the rest of the team.
The internal ID is the name your team uses for the item, such as rp.guild.pass; the display name is what players read. Keeping both stops the visible name from becoming the only reference.
The vanilla item underneath and the version you ship decide which visual hook makes sense: numeric CustomModelData before 1.21.4, item_model and the newer custom_model_data lists from 1.21.4.
The hidden ID is what commands and villagers check in custom_data. Tags group items by faction, quest or season; notes hold the rules that are easy to forget.
The summary counts duplicate hidden IDs and duplicate visual hooks, and each clashing entry is marked, so two items never answer to the same ID or share one model by accident.
Entries are stored locally in the browser you use. Another browser or device starts empty, and clearing site data removes the list, so export it now and then.
JSON can be imported back later; CSV opens in any spreadsheet; Markdown pastes cleanly into a wiki page or a team chat.
If a teammate sends a JSON export, import it first and then add your entries, rather than keeping two separate lists.
The catalog plans items; it does not write commands. Build the actual /give command in the custom item builder, and give the item a model with the item model builder from 1.21.4 or the resource pack generator before that.