> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.navipartner.com/product/ecommerce-entria-setup-guide-integration-setup/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.

# Set up the Entria integration

> Configure Entria Integration Setup, stores, items, and job queues, and handle failed imports.

1. Open **Entria Integration Setup**.
2. Prepare stores and Ecommerce processing according to the other sections of this guide before enabling the first import.
3. Enable **Enable Integration** when the system is ready.
4. Use **Stores** for store setup, **Items** to view items with Entria Product enabled, **Job Queue Entries** for import jobs, and **Order Import Failures** for failed attempts.

The global switch alone is not enough for import: the store must also be enabled and have **Sales Order Integration → Enabled** turned on.

## Entria Stores

### Creating a store

1. In Business Central search, find **Entria Stores**.
2. Create a new store and open its Entria Store card.
3. Enter **Code**, a unique store code, and **Description**, a meaningful name.
4. Configure the connection according to the next section before enabling the store.

### Configuring the connection

1. On the card, select **Set Connection Parameters**.
2. In **Entria Base Url**, enter the URL of the Entria Store.
3. In **Secret API Key**, enter the key for that store.
4. Confirm the entry. The message "Connection Parameters saved successfully" confirms that the values were saved.
5. Select **Test connection**.
6. A successful test shows: "Connection successful! Entria backend is reachable and API authentication is working."

The address and key fields on the card are display fields; changes are made through **Set Connection Parameters**.

### Fields on the store card

| Group / field                                     | Purpose                                                                                                                                    |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| General → Code                                    | Unique store code in Business Central; maximum 20 characters.                                                                              |
| General → Description                             | Store name or description.                                                                                                                 |
| General → Enabled                                 | Enables the store for the integration. A URL must be entered.                                                                              |
| Sales Order Integration → Enabled                 | Enables order retrieval for this store.                                                                                                    |
| Last Orders Imported At                           | Starting point for the next retrieval. It is not the job start time and does not prove that all earlier orders were imported successfully. |
| Location Code                                     | Location transferred to imported documents. If blank, the default sales location from Ecommerce setup is used when configured.             |
| Global Dimension 1 Code / Global Dimension 2 Code | Default store dimensions for imported documents. Names depend on the company dimensions.                                                   |

For additional default dimensions, use the **Dimensions** action. On the store list, this action supports multiple selected stores.

### Enabling retrieval

1. Before activation, check **Last Orders Imported At**. If blank, retrieval has no starting-date restriction and includes available orders waiting for BC synchronization, beginning with the oldest.
2. On the card, enable **General → Enabled**.
3. Enable **Sales Order Integration → Enabled**.
4. Open **Entria Integration Setup**, either directly through search or via **Integration Setup** on the store list.
5. Enable **Enable Integration**.
6. Open **Job Queue Entries** and verify that **Get Sales Orders from Entria** has status Ready or In Process.

When enabling retrieval for a store without a start date, the application asks you to confirm that import should start from the oldest available order. If you want to restrict the period, cancel, enter a date, and enable it again. The job is recurring and checks the stores multiple times while running.

## Items

Open the relevant item cards and enable **Entria Product**. Use **Entria Integration Setup → Items** to view items with this setting enabled.

The **Entria Product** field is visible on the item card only when **Enable Integration** is turned on and at least one Entria Store is enabled.

## Failed imports (Order Import Failures)

Open **Entria Integration Setup → Order Import Failures** or find **Entria Order Import Failures** through search. The list contains multiple stores; filter **Store Code** for the required store.

This list shows failures that occur before an Ecommerce document is created. Errors in later processing of an already imported document are checked through **Orders**, as described in [<ins>Monitoring and reprocessing</ins>](/product/ecommerce-entria-setup-guide-daily-order-processing#monitoring-and-reprocessing). If you're not sure which list applies, see [<ins>Troubleshoot the Entria integration</ins>](/product/ecommerce-entria-setup-guide-troubleshooting).

Retry intervals follow a fixed 10-step schedule that grows monotonically from 5 seconds to 3 minutes. Actual timing depends on execution of the shared job. If retrieving the order list for a store fails, individual retries are postponed for that pass. Newer order data can replenish the available retry attempts while the status is Pending. Error and Skipped require **Requeue for Import**.

| Field                  | Meaning                                                                                                                             |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Status                 | Whether the order is waiting for retry, has exhausted its attempts, or was manually skipped.                                        |
| Store Code             | Store to which the order belongs.                                                                                                   |
| Document No.           | External order number, when available.                                                                                              |
| Display No. / Order Id | Additional identifiers. Order Id is used for retrieving the order again.                                                            |
| Order Updated At       | Last update time of the order data at the failed import; this differs from the BC synchronization starting point on the store card. |
| Last Error             | Most recent import error.                                                                                                           |
| Retry Count            | Number of failed retry attempts; the first recorded failure has value 0.                                                            |
| Next Retry At          | Earliest time of the next automatic retry. Blank when attempts are exhausted.                                                       |

| Status  | What happens                                                         |
| ------- | -------------------------------------------------------------------- |
| Pending | Automatic retries are enabled and waiting for their scheduled time.  |
| Error   | 10 failed retry attempts have been reached; user action is required. |
| Skipped | The user stopped automatic retries using Skip.                       |

**Requeueing the import:**

1. Read **Last Error** and correct the cause.
2. Select the row and run **Requeue for Import**.
3. Confirm the dialog. Status changes to Pending, retry count returns to 0, and the order becomes eligible for the next job pass.
4. If the application reports that the integration, store, or job is inactive, correct the stated reason. Requeueing does not enable them automatically.
5. Check **Orders**. After successful import, the record is removed from the failed-import list.

**Requeue for Import** schedules retrieval of the current order data. It does not execute the import immediately. If a document for the same store and external number already exists, its content is not overwritten.

**Stopping retries for one order:** select **Skip** and confirm the dialog. The order remains on the list with Skipped status. This does not cancel the order; use **Requeue for Import** to continue. Even if an earlier retry time is still displayed, Skipped prevents the automatic retry.

## Entria Job Queues

The order import job queue is created automatically when **Enable Integration** is turned on and at least one Entria Store has both **Enabled** and **Sales Order Integration → Enabled** turned on.

If the job is missing or you want to verify its setup:

1. Open **Entria Integration Setup**.
2. Select **Configure Entria Order Import Job Queue** and confirm the dialog.
3. Read the result message and open **Job Queue Entries**.
4. If the job is not ready to run, set it to Ready.

The action creates the job if it is missing and registers it for monitoring. Automatic recreation of a deleted job depends on the background job refresher being enabled — see [<ins>Job Queue Refresher</ins>](/product/ecommerce-entria-setup-guide-job-queue-and-api-keys#job-queue-refresher). If the global integration is disabled, or if no enabled store has order retrieval enabled, the existing job is removed instead of a new one being created.

A message saying that the job has been configured is not a substitute for checking imported orders and the failed-import list.

Further processing of imported documents is handled by the [<ins>Ecommerce job queues</ins>](/product/ecommerce-entria-setup-guide-ecommerce-setup#ecommerce-job-queues).

> Documentation for NaviPartner's NP Retail, NP Attractions, NP Hospitality, NP Store Assistant and Entria products, plus their REST APIs, built on Microsoft Dynamics 365 Business Central.