Orders and customer accounts
When can an order be sent to AFAS? We define how customers are identified and which data is required.
AFAS integrations
Connect AFAS to your e-commerce process.
Align business administration with your online store and operations. We determine which data AFAS receives, what it returns and which checks are needed.
What role will AFAS play?
An online order must fit the item codes, customer records and process rules in your business administration. We therefore first agree what each system does.
Data returned to the online store
Stock, items and statuses each need an agreed source. We check what AFAS can supply and what your online store needs.
Operations after administration
Planning and logistics have their own next steps. Successful processing in AFAS does not mean every subsequent step has also succeeded.
The order flow
From WooCommerce to AFAS
The integration defines the data you want to transfer. Yindle Connect handles validation, mapping and processing between the systems.
- Online store
WooCommerce
Order lines and customer details from the order.
- Processing
Yindle Connect
Validate and map according to the agreed rules.
- Business administration
AFAS
Process the agreed data in your business administration.
Preparation
What do we need beforehand?
We review your AFAS environment and the available data. The setup for AFAS Profit is not necessarily the same as for another AFAS product variant.
Data and direction
Which data do you want to read or write, and which system is the source?
Connectors and access
Which connectors and access permissions are available in your environment?
Rules in your business administration
Which item, customer and order rules must the transfer follow?
A suitable test environment
We use test data to check that the agreed transfer works.
We assess technical access and functional setup together. The supplier, licence and permissions may limit the options.
In use at ForaVida
How this works at ForaVida
Connect links WooCommerce, AFAS and route planning. Order data is checked, mapped and processed for each destination. A failed transfer remains traceable for investigation and reprocessing.
ForaVida uses Desk in production to handle customer enquiries and exceptions with the same order context.
View the ForaVida case studyConnect
Data between systems
WooCommerce, AFAS and route planning.
Desk
Context for your team
Customer enquiry, order and next action together.
Frequently asked questions
Is AFAS always the source for stock levels?
We agree this explicitly. A warehouse system or another source may take precedence. If AFAS becomes the source, we also define which stock figure is transferred and how reservations are counted.
What happens if data is missing or an order is rejected?
Processing must remain identifiable, including the source, destination and cause of the error. We define which errors are retried automatically and which need to be corrected by a team member first.
How are changes managed?
Changes to fields, permissions or process rules may affect the integration. Maintenance, testing arrangements and responsibility for error notifications are part of the setup.
What should AFAS receive or return?
Bring one example order and an overview of your current systems. We can then make the desired transfer concrete.