Knowledge & insights
Integrations
Design decisions and practical lessons for reliable integrations between business systems.
-
Finding revenue discrepancies with lifecycle net per order
A matching daily total can conceal two order errors. Follow payments, refunds, invoices and credits by identity and across period boundaries.
-
Record the sending intent of every financial posting
An after-the-fact success log misses the most dangerous window. An execution register records exactly what the integration intended before sending.
-
Safely adding an iDEAL bank account from Mollie to AFAS
An iDEAL account from one order is not automatically general master data. Enable enrichment only with exact identity, policy and privacy checks.
-
Sending PayPal transactions to AFAS with technical controls
Technical reliability starts with the transaction type and a fixed reference. An amount alone does not identify the financial event.
-
Reliably linking Mollie settlements to online store orders
A settlement is not a single order. Use an evidence hierarchy for payment IDs, metadata and references, and do not force fees into an order match.
-
Delivered is not the same as proof of delivery available
A delivery status and a proof object may arrive at different times. Model them separately and base customer communication on precise evidence.
-
How to monitor an online store–ERP integration after launch
A practical monitoring plan that takes administrators from technical logs to traceable orders and concrete recovery actions.
-
Why write vehicle and route sequence back to AFAS?
Vehicle and stop sequence are temporary planning context, not permanent order facts. Write back only a current, fully validated route.
-
Processing Track-POD route updates without reversing statuses
Route, ETA and status events can arrive out of sequence. Protect each field with its own version and delete only from current snapshots.
-
Idempotency in e-commerce: prevent duplicate orders, notes and refunds
Why messages must be safely repeatable and how to prevent duplicate administrative and financial actions in practice.
-
Linking a Sendcloud parcel to exactly the right order
Name, postcode and amount do not constitute parcel identity. Follow a controlled identity hierarchy and stop when matches are missing or multiple.
-
When does an online order become an AFAS sales order or invoice?
Payment, delivery and invoicing happen at different moments. Use a fulfilment matrix to choose the right AFAS route for each order type.