Page body
What this module is for
NX Catalog And Mapping is the backoffice area where operators manage cross-market catalog records and the mapping relations that decide where categories, providers, games, currencies, and offers connect to each other.
Surface map
Aggregators: list and detail for NX aggregatorsCategories: list, detail, game mapping, category mapping, and reorderCountries: restriction list and record detailCurrencies: list, detail, and relation pages for games and providersGames: list, detail, category mapping, currency mapping, and reorderOffers: list and detailProviders: list, detail, and provider-currency mapping
Common confusion
NXsurfaces are not the same as rawCasinocatalog surfaces. NX pages control mapping and exposure, not only source-catalog maintenance.- Relation pages such as
Game Categories MappingorCurrency Providers Mappingare first-class operator surfaces, not secondary tabs with no business effect. - Reorder screens in NX affect curated order inside the NX layer and should not be mixed up with casino-side reorder tools.
Verification scope
This module is currently documented as verified_fe_only baseline coverage:
- FE routes, filters, grid columns, and relation flows are mapped from
nx-admin-fe-workspace - backend read and mutation paths still need explicit Cycle 2 verification
nx-workspacewill be checked only if shared settings or contracts are discovered as explicit dependencies