ERP Integrations2 min read
ERP API Integration Explained: REST, Webhooks, Auth and Idempotency
A plain-English explanation of ERP API integration: REST APIs, webhooks, authentication methods, idempotency, pagination, rate limits and error handling.
Integration · CRM & Marketing
Salesforce ERP integration without the handoff gap
Sales lives in Salesforce; operations and finance live in the ERP. Without integration, closed deals are retyped as orders and salespeople call the warehouse to ask about delivery.
Overview
What this integration is for
We connect Salesforce and the ERP with clear ownership rules: Salesforce owns the pipeline, the ERP owns products, prices, orders, stock and invoices.
01Data
What data syncs, and in which direction
| Entity | Direction | Notes |
|---|---|---|
| Accounts & contacts | ⇄ Both | Created in Salesforce, enriched with ERP customer number, credit and terms. |
| Products & price books | ERP → App | ERP as master for products and prices used in quotes. |
| Closed-won opportunities | App → ERP | Converted into ERP sales orders with lines. |
| Order & delivery status | ERP → App | Status and tracking visible on the opportunity or order. |
| Invoices & payments | ERP → App | Invoice and overdue status shown on the account. |
02Use cases
Common use cases
01
Quote-to-order automation
Won deals become orders without re-entry.
02
Account 360 in Salesforce
Sales sees orders, deliveries and balances.
03
Accurate pricing
Quotes use ERP prices and availability.
03 — Architecture
API architecture
Salesforce Change Data Capture or Platform Events notify the integration layer of relevant changes; the ERP side uses its own events or polling. Both feed a queue processed by the middleware.
API usage is monitored against Salesforce's daily limits, and bulk operations use the Bulk API for large initial loads.
04Reliability
Authentication, errors and retries
01
Authentication
A Salesforce connected app with OAuth 2.0 (JWT bearer flow for server-to-server), using a dedicated integration user with a minimal permission set.
02
Error handling
Validation rule failures in Salesforce and mapping errors in the ERP are captured with full context and routed to an exception queue owned by sales operations.
03
Retry strategy
Retries with backoff for transient errors and limit responses; duplicate prevention through external ID fields on both sides.
05 — Data mapping
Field mapping essentials
| Salesforce | ERP |
|---|---|
| Account.Id | Partner (external ID)ERP number written back |
| Opportunity (Closed Won) | Sales order |
| OpportunityLineItem.Product2 | Product |
| PricebookEntry | Pricelist itemERP master |
| Invoice status (custom object) | Invoice payment state |
06 — Automation
Automation opportunities
- Create ERP customer and order automatically when an opportunity is won
- Notify the account owner when an order ships or an invoice becomes overdue
- Block quotes for accounts on credit hold
- Sync renewals for recurring contracts
07 — Security
Security considerations
The integration user has least-privilege access. Credentials and certificates are stored in a secrets manager. Field-level security applies to financial data exposed in Salesforce.
Related
Where this integration fits
Other integrations
Often connected together
HubSpotContacts, companies, deals and order data synchronised between HubSpot and your ERP.DocuSignSend ERP quotes, contracts and agreements for signature and store signed copies automatically.Microsoft 365Outlook, Teams, SharePoint and Entra ID connected to ERP via Microsoft Graph.Custom APIConnect any system with an API, database, file feed or EDI — built with production-grade reliability.
Insights
Related reading
ERP Integrations2 min read
ERP Integration Guide: Patterns, Data Ownership and Reliability
How to integrate an ERP with eCommerce, CRM, payments and other systems: data ownership, integration patterns, middleware, error handling, monitoring and common failure modes.
ERP Integrations2 min read
RFID Integration with Odoo: A Practical Architecture
How to integrate RFID readers with Odoo inventory: middleware design, mapping EPCs to products and serials, receiving and counting flows, performance and what to build vs buy.
FAQ
Frequently asked questions
Which system should own customers?
Usually Salesforce creates prospects and the ERP becomes master for billing data once a customer is active. We document ownership per field.
Will this consume our API limits?
Event-driven design and batching keep usage efficient; we monitor consumption.
Can quotes be built in Salesforce with ERP prices?
Yes, by synchronising products and price books from the ERP.
Next step
Connecting Salesforce to your ERP?
Describe the data that needs to move and who owns it. We will propose a design with error handling and monitoring included.