Operator guideEN

NX Catalog And Mapping

Operator guide for NX catalog and mapping surfaces, including games, categories, providers, currencies, countries, aggregators, offers, and ordering screens.

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

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 aggregator status, JSON settings, and links into filtered provider/category lists.
  • Categories: list, detail, category-to-game mapping, parent/child category mapping, and reorder.
  • Countries: restriction list, record detail, and country-to-game/provider restriction mappings.
  • Currencies: list, detail, and read-only relation pages for games and providers.
  • Games: list, detail, category mapping, read-only currency mapping, country restrictions, and reorder.
  • Offers: list/create and detail configuration for offer definitions.
  • Providers: list, detail, read-only currency mapping, and country restrictions.

Common confusion

  • NX surfaces are not the same as raw Casino catalog surfaces. NX pages control mapping and exposure, not only source-catalog maintenance.
  • Relation pages are first-class operator surfaces, but they are not all editable. Check each page before expecting row selection or Save.
  • Reorder screens in NX affect curated order inside the NX layer and should not be mixed up with casino-side reorder tools.
  • Aggregator detail saves status and JSON settings, but the visible name field is not persisted by the current save flow.
  • Offers can store configuration that is not yet usable in live processing. In particular, Automatic activation and Group offers are not supported by the currently verified flow.

Verification scope

The child modules are verified against the visible CRM surfaces and their current catalog read/mutation sources. Each child page records its own fields, actions, save behavior, read-only limits, and known product gaps.

This status means the documentation matches the verified current flow. It does not mean every visible option is fully implemented; unsupported or inconsistent behavior remains called out on the relevant child page.

More help

Related pages

Affiliate Deals / Dashboard

Affiliate deal cohort report that period-bounds registrations, then combines the selected players with cumulative deposit and linked-event values.

Affiliate Deals / Form

Create and edit form for affiliate deals, including PID, date window, commercial terms, and responsible person.

Affiliate Deals / List

Searchable table of affiliate deal rows with PID filter, create action, dashboard shortcut, and edit/delete row actions.

Affiliates / Affiliate Deals

Operator guide for affiliate-deal records, their create/edit flow, and the performance dashboard that compares contract settings with delivered traffic and revenue metrics.

Automatic Withdrawal / Detail

Management workspace for automatic withdrawal, combining the rules register with processed history and the non-qualified withdrawal queue.

Automatic Withdrawal / Form

Create and edit form for one automatic-withdrawal rule, including thresholds, KYC, countries, methods, tags, and per-currency limits.