> 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-daily-order-processing/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.

# Review and reprocess Entria orders

> Review imported orders, monitor processing, and reprocess documents that failed.

## Reviewing imported orders

1. Open **Entria Stores** and select the store.
2. On the card, select **Orders**.
3. **Ecommerce Sales Documents** opens, filtered by store code.
4. Find the order by external number and open the document.
5. Check the customer, shipping address, currency, location, dimensions, lines, and payments.
6. Check the processing statuses and use **Related Sales Documents** for the related sales documents.

The number by which an order is identified during import comes from Entria `custom_display_id`. When investigating a missing order, confirm this value with the store administrator; it does not have to match another Entria number shown elsewhere.

## Data that is imported

| Data           | Import behavior                                                                                                         |
| -------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Customer       | Name, billing address, contact, phone, and email from the order data.                                                   |
| Shipping       | Shipping address, if provided, and the name of the first shipment method.                                               |
| Currency       | Order currency; for local currency, the currency field on the BC document may remain blank.                             |
| Prices and tax | Prices are treated as VAT-inclusive amounts. Quantity, unit price, line amount, and tax information are imported.       |
| Products       | Items, vouchers/gift cards, tickets, memberships, coupons, and Attraction Wallet packages, depending on data and setup. |
| Payments       | Amount, payment service provider, and payment reference; voucher payment is also supported.                             |
| Store          | Store code, location, and default dimensions.                                                                           |

For orders with a non-zero total, payment data must be available. If it is missing, the import is recorded as failed and a retry is scheduled. An order with a zero total can be imported without payment data.

## Monitoring and reprocessing

On the document list, check:

* **Creation Status** — status of sales-document creation.
* **Posting Status** — posting status.
* Processing statuses for virtual products, vouchers, and capture.
* Fields containing the latest error and its date and time.
* **Process Retry Count** — number of attempts so far to create the sales document.

If the document has an error:

1. Open the error text and identify the cause.
2. Correct the data or setup related to the error.
3. If the sales document has not yet been created, use **Process** and follow the dialog.
4. If the sales document has already been created and a later stage failed, use the action for that stage, for example **Capture Virtual Items**, or wait for its job.
5. Check the statuses and **Related Sales Documents** again.

Important notes for reprocessing:

* **Process** processes the already imported document. It does not retrieve the content again from the Entria store.
* **Process** works only while Creation Status is not Created. On a document that already has a created sales document, the action raises an error on Creation Status; this is a safeguard against creating the document twice, not a defect.
* The sales-order processing job retries automatically, but only up to **Max Doc Process Retry Count** from Ecommerce setup. When attempts are exhausted, Creation Status changes to an error state and the document leaves automatic processing. Further attempts are started manually with Process. Manual processing does not increment the retry count, and successful creation resets it to zero.

For digital products, the card contains views such as **Vouchers**, **Tickets**, **Memberships**, **Coupons**, and **Attraction Wallets**. Use **Digital Notification Entries** to review digital-notification records.

If an error isn't covered above, see [<ins>Troubleshoot the Entria integration</ins>](/product/ecommerce-entria-setup-guide-troubleshooting).

## Temporarily disabling the integration

| What you want to stop                        | Setting                                                 | What it stops                                                                                   |
| -------------------------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Order retrieval for one store                | Disable Sales Order Integration → Enabled on its card.  | Retrieval of new orders and retries of failed imports for that store.                           |
| One store's participation in the integration | Disable General → Enabled on its card.                  | Import for that store and its participation in the integration, without affecting other stores. |
| The entire Entria integration                | Disable Enable Integration on Entria Integration Setup. | All stores at once, without changing their individual switches.                                 |

When no store remains eligible for retrieval, the system removes the managed import job and related monitoring. When the integration is enabled again, the job is configured again; verify that it has status Ready or In Process.

Already imported Ecommerce documents have separate processing; stopping that processing requires checking the [<ins>Ecommerce job queues</ins>](/product/ecommerce-entria-setup-guide-ecommerce-setup#ecommerce-job-queues). The switches in the table stop import, including import retries, while processing of already imported documents can continue.

For a temporary pause, use the switches in the table above. Deleting a store removes its API key, import timestamp, default dimensions, and failed-import records. A recreated store with no start date retrieves available orders waiting for BC synchronization without a starting-date restriction.

> 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.