{"id":105,"date":"2026-09-14T09:00:00","date_gmt":"2026-09-14T07:00:00","guid":{"rendered":"https:\/\/yindle.com\/?p=105"},"modified":"2026-09-21T22:01:44","modified_gmt":"2026-09-21T20:01:44","slug":"webshoporders-filteren-voor-integratie","status":"publish","type":"post","link":"https:\/\/yindle.com\/en\/filter-orders-for-integration\/","title":{"rendered":"Which online store orders may start your integration?"},"content":{"rendered":"

Do not automatically send every WooCommerce order to ERP and logistics. Define in advance which statuses, sales channels<\/a>, payment methods, order types and attributes may start a workflow, and record the applicable rule for every rejection. An explicitly filtered order is healthy; an order that silently disappears is not.<\/p>\n

Why \u201csynchronise everything\u201d is risky<\/h2>\n

An online store contains more than ordinary paid sales orders. Consider test orders, manually entered corrections, failed payments, drafts, subscription instalments, zero-value replacement deliveries and orders handled by another process. If one generic integration treats all of them as new revenue, errors arise that only become visible in administration or the warehouse.<\/p>\n

Filters therefore belong before the first external write operation. They must use the current, validated order<\/a> rather than an isolated webhook record. Give the outcome a recognisable status such as processed, filtered or needs attention. This lets you explain later why order 7319 did not become an AFAS order without reconstructing log entries.<\/p>\n

Create a filter checklist for each process<\/h2>\n
\n\n\n\n\n\n\n\n\n\n
Question<\/th>\nExample rule<\/th>\nWhen uncertain<\/th>\n<\/tr>\n<\/thead>\n
Is the status suitable?<\/td>\nOnly paid or explicitly released<\/td>\nDo not write; set aside<\/td>\n<\/tr>\n
Is the sales channel included?<\/td>\nOnly store NL, not the test store<\/td>\nCheck the workspace and store ID<\/td>\n<\/tr>\n
Is this a standard financial order?<\/td>\nA zero-value replacement delivery follows its own process<\/td>\nClassify the order type<\/td>\n<\/tr>\n
Which fulfilment method applies?<\/td>\nPost, own delivery or collection<\/td>\nBlock unknown methods<\/td>\n<\/tr>\n
Is all required information complete?<\/td>\nValid debtor, address and order lines<\/td>\nCreate a task that can be resolved<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

Use one filter checklist per workflow, rather than one opaque collection of exceptions for the entire system landscape. The flow to AFAS may have different entry requirements from the flow to a carrier. See connecting WooCommerce and AFAS<\/a> for why source and destination rules must be defined for each business object.<\/p>\n

Fictional example: a test order does not become revenue<\/h2>\n

Fictional example: furniture store Kader & Kurk uses a hidden payment method for internal showroom tests. An employee places order 11204 to check a new delivery option. The order receives the status \u201cprocessing\u201d, but its \u201cinternal test\u201d attribute and specific payment method exclude it from the financial workflow.<\/p>\n

The event remains visible as \u201cfiltered: internal test order\u201d. If required, the logistics test can continue in a separate sandbox process without creating a sales entry in AFAS or a real shipment. When an ordinary customer order arrives with the same shipping method but no postcode, that is not a filtering case: the order falls within the intended scope but is incomplete. It moves to \u201cneeds attention\u201d, with a task to correct the address. The distinction between out of scope and a recoverable error is operationally essential.<\/p>\n

Review filters as product rules<\/h2>\n

Document each rule's owner, reason and expected lifespan. A temporary block for one campaign must not silently become a permanent business rule. Test positive and negative examples: an order that should proceed, one that should be filtered and one that needs human attention. Ask operations to review the descriptions; \u201cpredicate false\u201d is technically correct but helps nobody.<\/p>\n