Connect Salesforce with Comarch to sync profiles, points, and rewards across channels, so your teams run targeted loyalty campaigns with accurate, real-time customer data.
• Customer and account records are matched between Salesforce and Comarch using external IDs, with field-level mapping for addresses, tax details, payment terms, and sales organizations.
• Salesforce opportunities or quotes can be converted into sales orders that are sent to Comarch via API or middleware, with order headers and line items mapped to Comarch document types.
• Product identifiers (SKU/EAN), units of measure, and customer-specific price conditions are mapped so Comarch-calculated pricing can be returned to Salesforce when required by the flow.
• Inventory availability and delivery dates are synchronized from Comarch to Salesforce on a schedule or via events, typically scoped by warehouse, company code, or customer group.
• Order status, shipment, and invoice updates are pushed from Comarch back to Salesforce, with status codes translated into Salesforce fields for consistent reporting.
• Validation rules handle missing references and rejected documents, while integration logs store payloads, timestamps, and error details for traceability across both systems.
.png)
We map Salesforce accounts, products, price lists, and orders to Comarch objects, then sync key fields via API or middleware. Sales sees current stock and pricing, while Comarch remains the system of record.
Yes, Comarch shipping, invoicing, and delivery statuses can flow back into Salesforce so agents answer from one screen. You can also log status changes as activities for a clean service timeline.
We typically call Comarch for price and availability validation during quote building, then write the approved values back to Salesforce CPQ. This reduces manual rework and avoids quotes that cannot be fulfilled.
Yes, we can sync multiple legal entities, currencies, and price books, and route orders to the right Comarch company code. scandiweb has delivered 2,100+ eCommerce projects, many with complex B2B and multi-market integrations.
Timeline depends on data quality, the number of entities, and whether you need real-time sync or batch jobs. A focused discovery to confirm objects, endpoints, and edge cases is what keeps it predictable.





