# Salesforce SAP integration > Customers, orders, and credit limits move both ways between Salesforce and SAP. We design the interface, build the integration, and test the failure paths. URL: Your rep closes the deal in Salesforce. Then somebody types the customer and the order into SAP by hand, and the rep phones the back office to ask for the delivery status. You work directly with **an architect who can also write code**. We're in Grünwald near Munich. More than **12 years** on Salesforce, for companies directly and inside Salesforce partner teams. [Book a call](https://calendly.com/kkazlovich-helpfulbits/30min) ## What we build - **Data in both directions**: Customers and orders go from Salesforce to SAP. Order numbers and credit limits come back, so sales sees what SAP knows. - **One owner for each field**: Before we write code, we agree which system owns each field. SAP keeps the customer number and the credit limit, Salesforce keeps the opportunity. - **REST and SOAP interfaces**: We connect Salesforce to SAP directly or through middleware like MuleSoft. Apex callouts and REST services stay within governor limits. - **A service between the systems**: Some integrations need a service of their own between the two systems. We write that service too. - **Tests for the paths that fail**: An order within the credit limit, an order over it, and SAP not reachable. Each of these paths gets a test. - **Documented for your support team**: The decisions are written down, and your support team has documentation to use when an order doesn't arrive. ## Examples from client projects **SAP and Salesforce in sync**: Data moves **both ways** between SAP and Salesforce, so sales sees what SAP knows. We wrote the integration service in Java for a food service wholesaler. ## Tell us about your project Book a call, or send a few lines about your system and what should change. [Contact us](https://helpfulbits.com/contact.md)