| Data | Direction | What do we agree on? |
|---|---|---|
| Online order and order lines | WooCommerce → AFAS | Starting point, item codes, amounts, addresses and required fields. |
| Customer and account details | WooCommerce → AFAS | Matching existing accounts and rules for guests and business customers. |
| Stock | AFAS → WooCommerce, if AFAS is the chosen source | Data availability, the stock definition and synchronisation frequency. |
| Order, delivery or invoice status | From the agreed source system to WooCommerce | Which statuses are available and what they mean for your team and customers. |
Connect your online store and ERP
Connect WooCommerce to AFAS.
Let online orders reach your business administration through a controlled process. Yindle connects WooCommerce and AFAS with agreements on data, duplicate processing, returned information and recovery.
What does Yindle connect between WooCommerce and AFAS?
Order transfer is the starting point. Stock and other returned data become part of the solution when the required data is available and the setup has been agreed.
Which data source takes precedence?
We agree one source for each piece of data. If AFAS takes precedence for stock, we determine which figure goes to the online store: the stock definition and any reservations must fit your sales process.
WooCommerce remains the source of the online order. The integration retains the link to the AFAS record so the same order can be found during investigation or recovery.
From order to controlled processing
- Receive. The order starts at the agreed moment, for example after payment.
- Validate. Required fields, item codes, customer matching and destination rules are checked.
- Process. The data is mapped for AFAS. Repeated events must remain identifiable as part of the same processing operation.
- Trace. Processing and errors remain traceable. Returned data follows the agreed direction and frequency.
Yindle Connect is the integration layer behind this process. Yindle Desk is the workspace for agreed exceptions that a team member needs to review.
What happens if synchronisation fails?
An unknown item code needs a different next step from a temporary outage. We define when a retry may take place, which data must first be corrected and who receives the notification.
After an unclear response from AFAS, first check whether the order has already been processed. That scenario also belongs in the test approach: retrying must not create an unnoticed duplicate order.
Monitoring, maintenance, log availability and responsibility for recovery become part of the management agreements. There should be no uncertainty about who handles an error.
How do implementation and testing work?
We start with your WooCommerce setup and AFAS environment: which connectors and permissions are available, which fields are required and which plugins affect the order?
We then document data flows, agreed sources and exceptions. In a suitable test environment, we check scenarios including a normal order, an existing customer, an unknown item, repeated events, a temporary outage and an order change.
The foundation for controlled processing can be reused. Your mappings, customer rules, chosen data flows and any logistics steps determine how much additional configuration or custom development is needed.
How this works at ForaVida
For ForaVida, we implemented an integration connecting WooCommerce, AFAS and route planning. Order data is checked, mapped and processed for each destination. A failed transfer remains traceable for investigation and reprocessing.
The ForaVida case study: WooCommerce, AFAS and route planning shows how Connect handles data exchange and how ForaVida uses Desk in production for customer enquiries and exceptions.
Frequently asked questions
When is this integration suitable?
When you want to connect WooCommerce orders to your AFAS administration and need control over the data transfer. We assess beforehand whether the available access and your process rules align.
Is everything real-time?
How current the data is varies by flow and available interface. Order events can trigger processing; data from AFAS may be retrieved at a different frequency. We agree this for each flow.
Is stock always included?
Stock is a separate data flow. We investigate its availability and definition, and agree which system is the source. It is not automatically assumed to be part of every order integration.
What determines the cost?
The number of data flows, non-standard process rules, quality of available data, test scenarios and management agreements determine the scope. After the initial assessment, we make the scope and costs concrete.
Where can I find the technical background?
Read the technical guide to WooCommerce and AFAS. The AFAS page and WooCommerce page explain each system's role.
Discuss your WooCommerce and AFAS process.
Show us how an order currently reaches your business administration. We will map the desired data flow and the first step.