> 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-ecommerce-setup/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server. # Configure Ecommerce Setup and job queues > Complete the shared Ecommerce setup and create its background jobs before receiving the first document. Open **Ecommerce Setup** and complete the shared setup before receiving the first document. Other fields in Ecommerce Setup should be configured according to the customer's process and the product types in use. ## Customer matching and creation | Field | What to define | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Customer Mapping | Which value is used to match the customer: E-mail, Phone No., a combination of email and phone, Customer No., or Phone No. to Customer No. The choice must match the data actually sent by orders. | | Customer Update Mode | Whether the flow may create and update customers, only create, only update, or neither: Create and Update, Create, Update, None. | | Def. Customer Template Code | Template for customers that processing should create. Check posting groups and other mandatory fields. | | Def. Customer Config. Template Code | Select the default customer configuration template, if used, to supply customer field values during processing. | ## Document creation defaults and retry limits | Field | What to define | | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Def. Sales Location Code | Fallback location when the document does not provide one. The location on the Entria Store takes precedence when populated. | | Release Sales Order After Process | Whether the created sales order is automatically released after processing. This is not confirmation of posting. | | Release Sales Return Order After Process | Equivalent behavior for return orders, if they are received through the Ecommerce flow. | | Max. Document Process Retry Count | Limit for automatic retries when creating the sales document. | | Max Capture Retry Count | Limit for payment capture retries. | | Max Virtual Item Retry Count | Limit for digital-product processing retries. | | Max Attr. Wallet Retry Count | Limit for Attraction Wallet processing retries. | ## Ecommerce Job Queues On Ecommerce Setup, run the relevant actions below and confirm their dialogs. Then open **Job Queue List** and check the created jobs and their statuses. The jobs process different document stages. | Action | When it is required | | ------------------------------------------------- | -------------------------------------------------------------- | | Configure Sales Order Processing Job Queue | Creates sales orders from received Ecommerce documents. | | Configure Sales Return Order Processing Job Queue | Creates sales return orders from received Ecommerce documents. | | Configure Capture Processing Job Queue | Automates payment capture in the Ecommerce flow. | | Configure Voucher Processing Job Queue | Issues vouchers. | | Configure Ticket Processing Job Queue | Processes tickets. | | Configure Membership Processing Job Queue | Creates and processes memberships. | | Configure Coupon Processing Job Queue | Issues coupons. | | Configure Wallet Processing Job Queue | Processes Attraction Wallet packages. | | Configure Digital Notification Job Queue | Sends Ecommerce digital notifications. | Only configure the job queues for the product types and processing steps you actually use — see [Product Setup](/product/ecommerce-entria-setup-guide-product-setup) for which jobs each product type needs. **Verification:** after a test order, check Creation Status, Capture Processing Status, digital-product statuses, and related documents. For a job error, inspect its execution entry; for a document error, inspect the last error on the document. See [Monitoring and reprocessing](/product/ecommerce-entria-setup-guide-daily-order-processing#monitoring-and-reprocessing) and [Failed imports](/product/ecommerce-entria-setup-guide-integration-setup#83-failed-imports-order-import-failures). > 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.