Which integrations we build
A WMS rarely stands alone. To really work, it has to talk to other systems. We build those links on both sides.
ERP links. Dynamics 365, Exact, AFAS, NetSuite and others. Orders, inventory, invoices, customer records, pricing agreements.
Carrier links. DHL, PostNL, DPD, GLS, couriers and own fleet. Labels, track and trace, returns, customs data.
Client portals. Multi-tenant 3PL portals where clients see their inventory, drop in orders and pull reports.
Marketplaces and webshops. Bol, Amazon, Shopify, Magento, custom storefronts.
Our approach
Assessing API maturity. Not every API is equally well documented or stable. We assess the real limitations up front.
Working out the mapping. Fields, codes, units and exceptions. The devil is in the details, so we make those details explicit.
Parallel run. At least two weeks alongside the old system, to spot deviations before it has to go live.
Monitoring and alerting. A link that fails silently is more expensive than a link that was never built. We set up monitoring from day one.
Support after go-live. We stay your point of contact for the first months. Adjustments are often needed once real volumes arrive.
Vendor-independent
We work inside and outside Corax and Boltrics. We also build standalone integration layers (middleware, iPaaS solutions) if that is the right call. No vendor interest.
Typical integration projects
ERP link from scratch. 6-12 weeks, depending on API maturity on both sides and the number of exceptions.
Adding a carrier. 2-4 weeks per carrier. More often the bottleneck: labels and returns, not the happy path.
Client portal for 3PL. 2-4 months for a production-grade portal with self-service and reporting.
Webshop integration. 3-6 weeks, with attention to return flows and inventory synchronisation.
FAQ
Do you write the code yourselves or use low-code platforms? Both, depending on what fits. For production-grade high-volume links often custom code; for fast integrations sometimes middleware. We pick based on what is maintainable and affordable for your situation.
What if the vendor says the integration we want cannot be done? We test that claim. Often it can be done via a workaround or a separate middleware layer.
How do you handle API rate limits and performance? We design for them from the start. Queues, batching, retry logic and monitoring are standard parts of an integration, not bolt-ons after the fact.
What does it cost? Our rate is €110 per hour. For longer integration projects, a tailored price after a first conversation.
How we work
We design integrations from the workflow, not from the tooling. First understand what has to happen in your operation, then decide which system does which piece.
Read more about our approach on our approach page. For platform context see Corax or Boltrics.
“A link that fails silently is more expensive than a link that was never built.”