Published: · Updated:
Connecting a webshop to AFAS can reduce manual entry of customer and order information. The integration still needs to handle missing product codes, customer-specific arrangements and temporary outages. Start with the process you want to improve before selecting a connector or custom implementation.
A clear brief explains what moves from the shop to AFAS, what must come back and who reviews discrepancies. This helps establish whether an existing connector is sufficient or additional development is needed.
What should synchronise between your shop and AFAS?
Describe each data flow. “Connect everything” is not enough to compare proposals or test whether the result works.
| Data flow | Questions to resolve |
|---|---|
| Customers | When is a customer created, and how is an existing account recognised? |
| Products | Which system owns product codes, variants and units? |
| Prices | Which source owns prices, discounts and customer agreements? |
| Inventory | Which stock definition appears in the shop, and how often is it updated? |
| Orders | When is an order ready to be transmitted? |
| Delivery and returns | Which status changes must both systems support? |
Document the direction, frequency and source for each flow. If AFAS owns a customer field, a shop update should not inadvertently replace it.
How do AFAS App connectors work?
AFAS uses App connectors to give external applications access to selected connectors. Its documentation explains that an App connector controls the available GetConnectors, UpdateConnectors and other supported connectors. An external application uses a token for that access.
A GetConnector retrieves information. Available fields and selections depend on the connector and your configuration. Check the capabilities of your actual Profit environment rather than assuming a connector name guarantees every required field.
Use a separate App connector for the external application and limit its access to the required functionality. Have an administrator review the configuration and permissions. Transfer tokens securely and keep them out of public documents and shop frontend code.
Standard connector or custom integration?
A standard integration may work when its supported data flows match your process. Check supported versions, required AFAS configuration and recovery procedures before committing.
For a Shopware, Magento or WooCommerce shop, investigate the actual capabilities of the chosen integration. Listing a platform does not establish support for every extension, pricing rule or return workflow.
Custom development may fit a separate B2B portal, several administrations or additional approval steps. A Laravel application can support such workflows, but also adds maintenance responsibilities. Compare the complete solution, including monitoring and future updates.
An example of controlled order processing
Suppose a business customer orders through the shop. A manageable workflow might:
- Check whether the order meets the agreed payment or approval requirements.
- Match the customer and product lines to the correct administrative identifiers.
- Send the order with a stable external reference.
- Store the response and returned reference against the original order.
- Show an actionable exception when processing fails.
This is a design example, not a description of a standard AFAS feature. The implementation depends on your administration and selected connectors.
What happens after a timeout or duplicate message?
A timeout does not always reveal whether the receiver saved the data. Resending the message could otherwise create another order. The integration needs to recognise earlier processing and make retries an explicit, traceable action.
Agree how long messages may wait. A stock update several hours old needs different attention from an order briefly waiting for another attempt. Show unprocessed messages and assign responsibility for recovery.
Test exceptions and returns too
Acceptance testing should cover more than one successful order. Include existing and new customers, unknown product codes, discounts, different addresses, cancellations and partial deliveries. Also test an unavailable environment and a repeated message.
Compare amounts and quantities on both sides. Have the people who use the process every day assess whether the result is usable. Document which manual steps remain after launch.
Prepare a useful integration brief
Collect your platform and AFAS versions, the required data flows and representative examples. Describe existing failures and time spent on manual processing. Ask specifically about the test environment, documentation, monitoring, maintenance and outage recovery.
A clear scope makes proposals easier to compare. It also supports starting with one data flow and expanding only after processing is demonstrably correct.
AFAS integrations and e-commerce development at Qualide
Explore our Laravel platform development with AFAS for B2Bshop. For additional workflows alongside Magento, read about Laravel development and API integrations. If you later want reorder recommendations, start with reliable inventory data and demand forecasting.
Discuss your webshop–AFAS integration with Qualide. An overview of your systems and current bottlenecks helps identify which data flow needs attention first.
Sources
Have a project in mind or a question? Give us a call and we’ll help you explore the possibilities.From idea to something that works
Let’s talk about your project