How should a component mall connect to ERP? Most projects should not rewrite the ERP core. Start with three paths: RFQ into CRM, confirmed orders back to ERP, then stock and price back to the site. Map fields in the integration layer. DAJIQUN has focused on component digital acquisition since 2019; public capability includes 30M+ MPN-scale architecture—scope follows the signed SOW.

Path 1: RFQ into CRM

Keep RFQ on the part page with ≤6 fields, mobile submit, and a ticket the sales team can open the same day. Damaged attachments still create a record.

Path 2: Order write-back

Only confirmed deals write into ERP. Unpaid or pending quotes must not become warehouse documents. Show matching status enums on both sides.

Path 3: Stock and price back to the site

ERP is the source of truth. Publish available qty, lead-time ranges, or inquire-first wording. Do not claim live exact match. Sample ≥20 real MPNs and spot-check 3 locked-qty cases.

Fields and vendors

Minimum set: MPN, brand, package, customer code, warehouse, available/locked qty, tax flags, lead-time rule, document status. Kingdee, Yonyou, SAP, Oracle, Dynamics, and custom ERPs appear in projects when APIs exist. DAJIQUN is an integrator, not a default reseller.

See ERP / CRM integration, stock mismatch boundaries, and component site production.