ERP Synchronization | IMI Life Science

Link a Node to Its ERP Article

  • Node header: Enter the verified ID_ARTICLE in ERP article index (ID_ARTICLE) in the sticky node editor header, then save. The value is internal and never appears in the storefront.
  • One article, one node: Use a positive integer from the configured ERP environment. Duplicate links are rejected. Clearing the field unlinks the node; new and duplicated nodes are not automatically matched by code.
  • Stock and pricing: Generate a fresh preview after changing a link. Synchronization uses the saved article index, not an article-number, order-code or FAS-reference guess. Missing, inactive or protected articles block processing.
  • Order export: The connector captures the saved IDs on every order line before ERP creation. Captured order IDs cannot be changed by editing the node. Failed capture prevents export; conflicting identities or unknown ERP outcomes require integration-owner reconciliation.
  • Existing orders: Enter missing node links and re-queue only eligible paused failures after resolving their cause. An ERP acknowledgment remains distinct from shipment or invoicing.

ERP Export Alerts and Retries

  • Home dashboard: Administrators see failed ERP exports and eligible orders awaiting export in Needs attention. Each alert opens its filtered Order delivery queue. Counts refresh every minute while the dashboard is open and with Refresh. Unpaid orders are not counted as failed exports.
  • Retry ERP sync: For a paused failure, resolve the recorded cause, choose Retry ERP sync, and confirm that the order is not already in ERP. The command clears the failure counter so the existing scheduler can try again. Retry queued is not confirmation of ERP delivery. The previous error and administrator are recorded in the audit trail.
  • Already scheduled: Orders below the three-failure pause remain eligible for the next scheduler cycle. Refresh reads status; it does not force an extra export or reset an active attempt.
  • Do not duplicate orders: An unknown ERP outcome requires reconciliation through ERP services. The retry endpoint refuses these orders, acknowledged exports, unpaid card orders, and orders outside your permitted brands.
  • Failure feedback: A rejected retry keeps the confirmation and error visible. Cancel sends no request. An unavailable dashboard queue is not an all-clear result.

Track ERP Order Delivery

Purpose: Identify why an IMI Life Science order has not reached ERP and who must resolve it.

What You Can Do Here

  • Order delivery: The default view separates export issues, queued orders, payment prerequisites, acknowledged exports and orders outside the queue. Search by order number, UUID, SKU, company, ERP reference or error. Totals cover your complete authorized search, not just the visible page.
  • Inspect: Open a diagnosis to see the recorded error, order lines, failure count, payment state, ERP reference and recommended next action. Open order returns to the original Sales record.
  • Refresh: Refresh reads saved Sales diagnostics only. Optional auto-refresh reads once per minute. Neither action retries an export or changes ERP data. A failed refresh preserves the last successful read with a visible warning.
  • ERP article not found: Compare the SKU in the saved error against the configured ERP environment. The catalogue or ERP owner must identify the correct active, unprotected article. Do not guess an ERP article ID or assume that a catalogue SKU exists in ERP.
  • Retry state: The first failed attempt appears immediately. The scheduler stops selecting an order after three recorded failures. Resolve the cause before using Retry ERP sync to re-queue a paused order.
  • Unknown ERP outcome: A lost response may mean the ERP order already exists. Search the exact website order reference through ERP services and reconcile the result before any reset or resubmission. Unknown-outcome orders cannot be retried from the monitor.
  • Payment: Card orders require Confirmed and Paid. Authorized invoice orders may be unpaid. Do not simulate a payment to bypass a real payment failure.
  • Evidence limits: Failed-attempt timestamps and a full attempt history are not stored. A successful sync or administrator reset clears failure counters and errors. An export acknowledgment does not prove shipment or invoicing.
  • Stock and pricing: The existing review and apply workflow is in its own tab. Under the existing-HTTP-endpoints-only integration, Article number is the supported matching mode; other modes and unsupported currency conversions fail closed. ERP master data is never overwritten.

ERP Synchronization

Purpose: Review and apply ERP-authoritative stock and Client CB selling prices to IMI Life Science.

What You Can Do Here

  • Preview: Select Stock, Pricing, or both and a configured Client CB currency source. Generate preview reads both systems without changing either.
  • Review: Compare platform values with ERP values, reservations, article identities and validation blockers. Search and filters affect display only.
  • Select scope: Select specific SKU rows and choose Preview selected to generate a new review for that scope. Blocked rows are never silently skipped.
  • Apply: Every selected row must pass validation. Confirm that ERP is the master. Tickets expire after fifteen minutes and cannot be reused.
  • Missing prices: Populate the Client CB selling conditions in ERP. Customs-origin values, costs and unrelated customer contracts are not selling-price substitutes.
  • Stock: Physical shelf stock is replaced; platform reservations remain unchanged. Missing mappings, excluded articles and unsupported quantities block apply.
  • Price scope: Generic prices in the selected currency are replaced. Historical prices and customer-specific contracts remain. Regional price differences and unsupported order/delivery minimums require platform support before synchronization.
  • Changed or partial results: Generate a fresh preview to reconcile current values. ERP is never modified and obsolete platform values are not restored automatically.

Automatic Matching and Default Prices

  • Matching key: Saved node ERP article index (ID_ARTICLE). Code-based matching is no longer supported.
  • Match evidence: Each row shows the saved ERP article index and current ERP article number. An excluded saved ID cannot be replaced by another revision.
  • Price precedence: A specific Client CB schedule wins. If absent, the ERP-designated default sales condition is used. The selected default and each effective price source are visible. A zero next quantity break keeps the preceding base price, following ERP rules.
  • Missing default: Not configured in ERP means the Client CB condition has no designated default. Set its intended default in ERP or add its specific selling prices. No unrelated customer price, platform price or manufacturing cost is substituted.
  • Currency and constraints: Default prices use ERP annual currency conversion. Missing rates and unsupported quantity/delivery constraints remain blockers. Regional schedules are stored separately.

Client CB Destination and Currency Mappings

  • Settings: Open Settings, Integrations, Client CB mappings. Set the domestic ISO country and the ERP company, currency and sales-condition identifiers for each Domestic or Export currency. Save mappings commits the whole configuration together.
  • Destinations: Orders shipped to the configured domestic country use Domestic; all other destinations use Export. Currency does not determine the destination account.
  • Regional prices: Preview and apply each account/currency separately. Domestic and Export schedules can differ. Applying one leaves the other account, legacy schedules and customer-specific contracts unchanged.
  • Validation: Configured identifiers must match active ERP conditions. Missing selling prices, missing ERP-designated defaults and unsupported quantity or delivery constraints block application. Regional schedules are never converted into an unconfigured currency.
  • Checkout: Product displays use the detected country as an estimate. Final pricing is resolved server-side for the shipping country. Run a fresh preview after changing mappings.

Download the Synchronized Price Table

  • Download: In Stock and pricing, select Download price table after synchronizing every configured account/currency. The CSV includes id_article, SKU, name, and separate destination/currency price columns.
  • Eligible articles: Only articles with a valid saved ERP link, no pricing validation errors and saved prices matching ERP in every configured column are included. Blocked, partially synchronized and unpriced articles are excluded. If none qualify, no file is created.
  • Quantity breaks: Base prices are for one unit. Additional columns preserve higher quantity breaks and the preceding price between breaks.
  • Scope: Download uses the complete catalog and all configured mappings, not the displayed preview, search filter or selected rows. It reads comparisons only; it does not apply prices or change ERP data.
  • Changed data: Retry after mapping changes or upstream read failures. If prices changed in ERP, review and synchronize the affected sources again before downloading.

ERP-Managed Synchronization Scope

  • Default scope: Generate preview includes only SKU products with a saved positive ERP article index. Products not managed through ERP are excluded and their stock and prices remain unchanged.
  • Blocked linked articles: Missing ERP records, lifecycle restrictions, duplicate schedules and invalid quantities or prices remain validation errors for ERP-managed articles.
  • Eligible subset: Preview eligible articles creates a fresh server-approved comparison for every error-free linked article in the current preview, across all pages and filters. Review the resulting subset, then use Apply ERP values and confirm synchronization.
  • No automatic writes: Selecting or filtering rows never applies values. An empty, expired or blocked selection cannot be applied; if no articles qualify, resolve the source errors first.