Products, pricing, quotes, orders, shipments and installed equipment move between Salesforce and the ERP, engineering and channel systems behind a manufacturer.
For manufacturers, integration closes the gap between the commercial team in Salesforce and the ERP that plans, builds and ships. We bring the product catalog, customer-specific pricing and inventory availability into Salesforce, send quotes and orders to the ERP, and return order status, shipments and invoices so sales and service teams can answer customers without chasing planners. Where products are configured or engineered to order, rules from the product lifecycle system drive what can be quoted. Distributors and dealers are connected through portals or data feeds, and installed equipment data supports service and aftermarket sales.
Manufacturing product data is complex and owned elsewhere. Part numbers, bills of materials, revision levels and units of measure are mastered in ERP and engineering systems, and a quote that references an obsolete revision can create costly production errors. Pricing is layered too, with list prices, contract prices, distributor discounts, rebates and surcharges that change with raw material costs. Sales often happen through distributors and dealers whose sell-through data the manufacturer does not directly control. And the commercial relationship continues after shipment, because installed equipment needs parts, service and eventual replacement, which means serial numbers must travel from production records into the customer relationship.
Active parts, descriptions, revisions, units of measure and price lists flow from ERP into Salesforce products and price books, with customer-specific contract pricing kept in step. Obsolete revisions are retired automatically so they cannot be quoted. Surcharges and index-based adjustments update on the schedule finance sets, and reps see the price that the ERP will invoice, not one that finance must later correct.
Approved quotes in Salesforce or Revenue Cloud become sales orders in the ERP, with validation for credit holds, minimum order quantities and ship-to details before submission. Order acknowledgments, promised dates and changes from planning return to the Salesforce opportunity and account. Customer service sees the same promise date the plant is working toward, and changes to it raise a task for the account owner.
Shipments, tracking numbers, invoices and open receivables summarize on the account in Salesforce. Sales and service teams answer where-is-my-order and billing questions without switching systems or contacting accounting or the warehouse, and partial shipments show which lines remain open. Credit holds appear before a rep promises a new order to a customer with overdue invoices, avoiding awkward conversations after the order is already stuck in the plant.
Serial numbers, configurations and warranty terms of shipped equipment are linked to customer assets in Salesforce. Field Service uses that data for repairs and preventive maintenance, and sales uses it to spot aftermarket parts opportunities and aging equipment ready for replacement. IoT or telemetry signals, where available, can open service cases before the customer notices a problem on the line.
Integration planning starts with a product data workshop including sales operations, engineering, the ERP owner and finance, because product and pricing ownership decisions affect every later flow. We connect products and pricing first, then accounts and credit status, then orders outbound and status inbound, and finally installed base. Integrations are tested with real historic orders, including partial shipments, backorders and returns. Plant shutdowns, fiscal close and ERP upgrade windows determine release timing, and the ERP team approves any change touching order entry.
Products, price books, customer accounts, credit status, sales orders, shipments and invoices synchronize, with ERP remaining master for items, inventory and financial transactions.
Configurable product rules, revisions and engineering changes feed quoting, so sales configures only buildable combinations and engineering sees commercial demand for options.
Point-of-sale and inventory reports from channel partners are normalized and loaded, supporting rebates, market development funds and demand visibility beyond direct sales.
Decide that ERP or product lifecycle management owns item data, and keep Salesforce read-only for part numbers, units and revisions. Allowing edits in two places leads to quotes that cannot be converted into orders and to arguments about which description is correct.
Orders rejected by the ERP after a customer has been promised a date damage trust. Check credit, ship-to validity, item status and minimum quantities in Salesforce before submission, and show rejections clearly to the rep who owns the order so they can correct and resubmit.
Some products are controlled for export or require screening against restricted party lists. If your ERP or trade compliance tool holds those flags, bring them into Salesforce so sales sees restrictions early, and keep the actual compliance decision in the system designed and audited for it.
Client names are anonymized.
For many manufacturers, yes, but only for the products and locations reps can promise from. Real-time lookups to the ERP work well for available-to-promise checks at quoting time, while a scheduled summary covers general visibility. We choose based on how often availability changes and what the ERP can handle without slowing plant operations or the order entry screens used by customer service staff.
Configuration rules are usually defined once, either in a product configurator or Revenue Cloud, and the resulting configuration is sent to the ERP as a structured order or generated bill of materials. The integration must carry every selected option accurately, so we test configurations end to end with engineering before any customer quote uses them.
Yes, if distributors share point-of-sale or inventory reports. Formats vary, so an integration layer normalizes files and maps distributor part numbers and end customers to your records. The result supports rebate calculations, territory credit and market insight. Agreements with distributors should define what data is shared and how often it is sent, including how end-customer names are handled.
That is common after acquisitions. An integration layer can present one set of APIs for products, orders and customers to Salesforce, routing each request to the right ERP behind it. Salesforce users see a consistent experience, and when a plant migrates to a standard ERP, only that connection changes rather than every Salesforce process. Reporting across plants also becomes consistent, because each ERP's data is translated into the same shape.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.