Organize device and product reference data

Fusion Owned License is end of life; these instructions describe existing legacy installations, and labels can vary by build.

Product features

Use **Settings > Product Feature** to create feature names for each product group. Then edit the relevant **Catalog / Cart** product and enter its feature values. Examples in the source are Colour, Size, Type and Storage Capacity. Use consistent names within a group so comparisons refer to the same features.

Country and provider lists

Open **Settings > Country - Provider**.

For a country entry:

1. Choose the **API** server.

2. Enter the **Country** name.

3. Enter the corresponding **API ID**.

For a provider entry:

1. Select the **API** server and **Country**.

2. Enter **Provider** names, one per line.

3. Enter the **API ID**.

4. Fill **MEP New** and **MEP Old** where that provider mapping requires them.

These lists are used to identify devices and manage mobile orders. Match API identifiers to the selected provider rather than substituting a display name.

Brand and model lists

Open **Settings > Brand - Model** for the brand list, and **Settings > Brand - Model > Model List** for models.

The archived form descriptions reuse unexpected labels:

- On the brand list, **API** selects the API server, **Country** is described as the brand-name field, and **API ID** is the mapping identifier.

- On **Model List**, **API** selects the server, **Country** is described as selecting the brand, and **Provider** is described as the mobile-model names, one per line, followed by **API ID**.

Check those labels in your build. They describe brand/model entries on these pages, not a separate instruction to enter a network provider where a model is required.

Other reference lists

**Manufacture - Warehouse** stores device-manufacturer and warehouse master entries. Keep existing record references in mind when renaming entries.

The standalone **MEP**, **Provider - Model - MEP**, and **PRD** sources only say that these features help identify devices and manage mobile orders. They do not specify code formats or extra setup steps. Use the required identifiers from your actual service/provider mapping; the archive does not justify inventing values.