When your ERP, CRM and online store do not communicate with each other, your team becomes the "human interface" between systems — copying data manually, correcting errors, and losing hours every day on tasks that should be automatic.
The "Human Interface" Problem
In many Portuguese companies, the integration between systems is done by people. Literally. Joana receives an order on the e-commerce platform, opens the ERP, manually copies the order data, then opens the CRM, updates the customer record, sends a confirmation email, and updates the stock spreadsheet. All of this for a single order.
When there are 5 orders a day, it is tedious. When there are 50, it is unsustainable. And the real cost is not just the time — it is the errors. A tax ID entered incorrectly on the invoice. A wrong quantity in inventory. A confirmation email that was never sent because Joana was on the phone.
This scenario is so common in Portugal that many companies consider it "normal". It is not. It is a problem with a solution.
Without Integration vs. With Integration: The Real Difference
A Day Without Integration
Let us see what happens when a customer places an order on the online store of a company without integration between systems:
- Order enters the e-commerce platform — email notification
- Someone opens the email, copies the data, and manually enters the order in the ERP
- That person (or another) opens the CRM and manually updates the customer record
- Someone manually sends the confirmation email to the customer
- Someone goes to the inventory file and manually decrements the quantities
- When the order is dispatched, someone manually generates the invoice in the ERP
- Someone manually sends the email with the shipping tracking
That is 7 manual steps for a single order. Multiplied by dozens of daily orders, they represent hours of repetitive, error-prone work.
A Day With Integration
Now, the same scenario with integrated systems:
- Order enters the e-commerce platform
- Automatically: the order is registered in the ERP, the CRM is updated, the confirmation email is sent, inventory is decremented, the invoice is generated, and the tracking email is sent when the status changes to "dispatched"
One human step. The rest happens in seconds, without errors, 24 hours a day.
The difference in numbers: Companies that integrate these 3 systems typically report a reduction of 4 hours of manual work per day and 90% fewer inventory errors. It is not magic — it is automation of processes that already exist.
The 3 Types of Integration
There is no single way to connect systems. The choice depends on complexity, budget, and the systems involved.
1. Direct API Integration
The two systems communicate directly with each other through their APIs (Application Programming Interfaces). It is the most robust and fastest solution in terms of performance.
- Advantages: real-time communication, no intermediaries, greater reliability
- Disadvantages: requires technical development, each pair of systems needs a dedicated integration
- Ideal for: critical integrations with high data volume (ERP-ecommerce with hundreds of orders/day)
2. Middleware (Zapier, Make, n8n)
An intermediary platform that connects the systems to each other. It works as a universal "translator" that speaks the language of each system.
- Advantages: visual configuration (no code), easy to modify, connects dozens of tools
- Disadvantages: dependency on a third-party platform, may have volume limitations, monthly costs per automation
- Ideal for: SMEs with moderate volume that need to connect 3-5 tools without custom development
Practical example with Make (Integromat): "When a new order arrives in WooCommerce → Create a record in PHC → Update contact in HubSpot → Send confirmation email via Gmail → Update Google Sheets inventory". All configured visually, without a single line of code.
3. Custom Webhooks
The source system sends a notification (webhook) when something happens, and the destination system receives and processes that notification.
- Advantages: real-time reaction, lightweight and efficient, highly customisable
- Disadvantages: requires technical development, needs error handling and retries
- Ideal for: specific events that need immediate reaction (payment confirmed, stock depleted)
Common Integrations in Portuguese Companies
The Portuguese market has its particularities. These are the integration scenarios we encounter most frequently:
PHC + WooCommerce
The most popular combination in Portuguese SMEs. PHC handles invoicing, accounting and inventory. WooCommerce handles the online store. The integration synchronises products, prices, stock and orders between the two. When an order is placed on WooCommerce, PHC automatically generates the dispatch note and invoice.
Primavera + Shopify
For larger companies that use Primavera as their ERP. Shopify handles the online shopping experience and Primavera handles all operational management. The integration ensures that catalogue, prices, promotions, stock and orders are always synchronised.
SAP + Salesforce
For large companies or multinationals with operations in Portugal. SAP manages all operations (finance, logistics, production) and Salesforce manages customer relationships. The integration is typically more complex and done via direct API or enterprise middleware.
Important note: Regardless of the systems you use, the integration logic is always the same: define which data flows, in which direction, when, and what happens in case of error. The systems change; the principles do not.
Costs and Realistic Timelines
Because nobody likes surprises in technology projects:
- Middleware integration (Zapier/Make): €1,000 - €3,000 setup + €50-300/month subscription. Timeline: 2-4 weeks.
- Direct API integration (2 systems): €3,000 - €8,000 development. Timeline: 4-8 weeks.
- Complete ERP + CRM + E-commerce integration: €5,000 - €15,000. Timeline: 6-12 weeks.
- Enterprise projects (SAP, Oracle): €15,000 - €50,000+. Timeline: 3-6 months.
These figures are indicative for the Portuguese market. They vary significantly with the complexity of systems, data volume, and level of customisation required.
The 5 Steps to Implement the Integration
Step 1: Map the Data Flows
Before touching any technology, document exactly which data flows between systems, in which direction, and how frequently. Draw it on a whiteboard: "When [event] happens in [System A], data [X, Y, Z] must appear in [System B] within [maximum time]." Do this for each flow.
Step 2: Choose the Integration Method
Based on the mapping, choose the appropriate method for each flow. Not all flows need the same method — you can use middleware for product synchronisation and direct API for order processing, for example.
Step 3: Build and Test
Develop the integration and test it thoroughly with test data. Simulate every scenario: standard order, discounted order, return, out-of-stock product, new customer vs. existing customer. Also test error scenarios: what happens when a system is unavailable? Is there automatic retry?
Step 4: Parallel Execution Period
This step is critical and frequently overlooked. For 1-2 weeks, keep both methods running in parallel: the automatic integration AND the manual process. Compare the results. If the data matches consistently, the integration is ready for production.
Step 5: Go-Live and Monitoring
Deactivate the manual process and rely on the integration. But set up alerts: if a synchronisation fails, the team must be notified immediately. The first 30 days are the most important for detecting edge cases that testing did not catch.
Typical Results
After implementing integrations between ERP, CRM and e-commerce, companies consistently report:
- 4 fewer hours of manual work per day — time the team can redirect to high-value tasks (serving customers, improving processes, selling)
- 90% fewer inventory errors — because inventory is updated automatically in real time, not manually at the end of the day
- Invoices issued in seconds — instead of the next day "when there is time"
- Superior customer experience — immediate confirmation, automatic tracking, no communication failures
- 360-degree customer view — the CRM automatically shows online purchase history, interactions, and total customer value
The First Step
If your team is currently acting as the "human interface" between the ERP, CRM and e-commerce, the first step is not to choose technology. It is to take a piece of paper and note down, over one week, every time someone copies data from one system to another manually. The volume and frequency of that manual work will make the business case self-evident — and the decision to integrate will be obvious.
