WooCommerce integrations
An online order is the start of processing. Yindle connects WooCommerce to business administration, planning and support, with control over what is transferred.
An order can change after it has been placed. We therefore define what each event may trigger and when other systems are updated.
Decide whether processing starts after checkout, after payment or after an additional check. Order lines, addresses, amounts and the selected delivery option must then be usable by the destination.
Define which changes can still be processed and who decides if administration or fulfilment has already started. A change must not create a second, independent order.
Choose which data WooCommerce needs, such as a stock figure or order status. The source, meaning and frequency vary by data flow.
A simple order does not represent every online store. Variations, configurators, discount rules, shipping methods and additional order fields can affect the integration.
We investigate which data is available and test the agreed scenarios with your own setup. If a plugin or checkout changes, it must also be clear which checks need to be repeated.
Also want to improve the shopping experience? Explore websites, online stores and WooCommerce plugins.
Do you use AFAS for business administration? The page on Connect WooCommerce to AFAS specifically covers order transfer, customer matching, returned data and recovery after errors.
Yindle Connect handles processing between systems. For the broader process, read how automation helps your team handle exceptions.
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.
The desired starting point is part of the process agreement. An order may first need payment confirmation or a check. Availability of the receiving system also matters.
Processing must recognise the same order again. We test repeated events and uncertain responses from the destination so that recovery does not blindly create another order.
We investigate this based on the available data and interfaces. First describe the transfer you need; we can then determine what fits within your existing setup.
Tell us which data you re-enter or which status you cannot find.