機能 > 統合

連携

ERP、CRM、PLM、CAD、PIM との CPQ 連携

Mercura の商談用コンフィギュレーションを、既存の基幹システムと接続します。製品・顧客・価格のコンテキストを再利用し、Mercura で構成と検証を行い、承認済みの結果を ERP、CRM、または製造プロセスへ引き渡します。

CRM
  • Accounts
  • Contacts
  • Opportunities
  • Commercial terms
Accounts, Contacts, Opportunities, Commercial terms
ERP
  • Items
  • Customers
  • Base prices
  • Costs
  • Inventory (when relevant)
Items, Customers, Base prices, Costs, Inventory (when relevant)
PIM
  • Attributes
  • Descriptions
  • Images
  • Documents
  • Classifications
Attributes, Descriptions, Images, Documents, Classifications
PLM / CAD
  • Parameters
  • Variants
  • Technical data
  • Engineering rules
Parameters, Variants, Technical data, Engineering rules
システムへの入力
承認済み出力
CRM
  • Quote
  • Configured lines
  • Configuration reference
Quote, Configured lines, Configuration reference
ERP
  • Quote or order
  • Lines
  • Parameters
  • Components / BOM
Quote or order, Lines, Parameters, Components / BOM
Engineering
  • Configured parameters
  • Technical process data
Configured parameters, Technical process data

製造業が既に利用している ERP、CRM、PIM、エンジニアリング基盤

  • Microsoft Dynamics 365 Business Central
  • SAP S/4HANA向けMercura CPQ
  • Salesforce向けMercura CPQ
  • Oracle NetSuite向けMercura CPQ
  • Odoo向けMercura CPQ
  • IFS Cloud向けMercura CPQ
  • Infor CloudSuite & M3
  • SOLIDWORKS
  • HubSpot向けMercura CPQ
  • Shopify向けMercura CPQ

各システムが本来の役割を担う

Mercuraは既存のスタックを置き換えません。営業に必要な商用構成レイヤーを追加し、各システムは従来のデータとプロセスの責任を維持します。

  • CRM

    顧客と商談

    • 取引先
    • 担当者
    • 商談
  • ERP

    オペレーションと受注

    • 製品
    • コスト
    • 受注
  • PIM

    製品コンテンツ

    • 属性
    • 説明
    • アセット
  • PLM / CAD

    エンジニアリング

    • パラメータ
    • ジオメトリ
    • 技術定義
  • Mercura CPQ

    商用構成

    • ガイド付き販売
    • 製品ルール
    • Pricing
    • 見積

主要な ERP・CRM 連携

Start from the systems most teams already run, then scope object mapping and handoff with your implementer.

連携ディレクトリ

Browse connectors and solution pages by category. Each entry explains what Mercura adds and what stays in your existing stack.

55 integrations

連携プロジェクトの典型的な進め方

  1. 1

    Discover and scope

    Document which systems supply product, customer, and price data, and where configured outcomes must land after approval.

  2. 2

    Map objects and ownership

    Agree field mapping, direction of flow, and which system remains authoritative for each data type.

  3. 3

    Configure CPQ and connectors

    Build the configurator, rules, and pricing model in Mercura, then connect the agreed interfaces or exchange paths.

  4. 4

    Validate and launch

    Test end-to-end scenarios with sales and operations, then roll out to the channels defined for the project.

Mercura との接続方法

  • REST APIs

    Use platform APIs where they are the agreed contract for reading master data or writing quotes, orders, and line structures.

  • File-based exchange

    Import or export structured files when batch updates or legacy interfaces are the practical choice for a data domain.

  • iPaaS and middleware

    Route events and transformations through your existing integration platform when IT standardizes on a hub.

  • Project-specific adapters

    When no standard connector exists, scope a focused adapter that implements only the objects required for CPQ.

Mercura がスタックに適する場合

Mercura is the right layer when

  • Products are configured, not picked from a fixed catalogue
  • Sales needs rules, calculations, and pricing in one guided flow
  • Quotes must reflect valid engineering and commercial constraints
  • Re-keying configured data into ERP or CRM is slowing deals

Your landscape often already includes

  • An ERP that should remain the operational system of record
  • A CRM that owns the opportunity and customer relationship
  • PIM or PLM sources for product structure and attributes
  • Dealer portals, ecommerce, or internal sales tools that need the same logic

If the gap is only document branding without configuration logic, quote templates alone may be enough. CPQ is for valid configurations, prices, and structured outcomes.

連携に関する質問

Does Mercura replace our ERP or CRM?
No. Mercura adds a CPQ layer for guided selling, configuration rules, calculations, and quote output. ERP and CRM continue to own master data, orders, pipeline, and operational processes according to your architecture.
Which system owns product and price master data?
That is decided per project. Mercura can consume items, attributes, and base prices from ERP or PIM while holding configuration-specific logic. The integration design documents which fields are read-only, calculated in CPQ, or written back after approval.
How long does an integration take?
Timeline depends on the number of systems, object scope, and how mature your product model already is. A focused ERP quote handoff can be smaller in scope than a multi-system landscape with PLM parameters and dealer channels.
Will this complicate ERP upgrades?
Connectors target agreed APIs or exchange formats. When the ERP changes interfaces, the mapping layer is updated without moving configuration logic back into spreadsheets or manual re-entry.
Can we integrate gradually?
Yes. Many projects start with one direction of flow, such as items and prices in and quotes out, then extend to orders, BOM lines, or engineering parameters once the first path is validated.
What if our stack is not listed?
Use the directory for similar patterns or contact us with your systems. Custom scope is defined around the objects you need for selling, not a generic connector catalogue.

スタックに合わせた連携を計画

Share which systems should supply context and where configured outcomes must land. We help define scope before build work starts.