Khaos Control integration for ecommerce fulfilment

iWeb builds the integration to capture orders from your commerce platform as soon as they are confirmed and payment is authorised. Depending on your architecture, orders typically reach Khaos Control within 30 seconds to 2 minutes. We use event-driven queues where possible to minimise polling delays, and we monitor end-to-end latency so any slowdowns are caught before despatch is impacted.

iWeb designs the integration with a fallback queue so orders continue to arrive in a temporary buffer while Khaos Control is offline. Once the system is back online, orders are replayed in sequence so no orders are lost. We also set up monitoring and alerting so your team is notified immediately and can escalate if the outage extends beyond 15-30 minutes.

If your business requires split shipments, iWeb configures an orchestration layer that decides which warehouse location ships which line items based on stock availability and carrier routing rules. The commerce order splits into multiple despatch instructions in Khaos Control, one per location. Tracking numbers are consolidated back to the customer so they see a single order with multiple shipments.

iWeb flows every warehouse event (pick, adjustment, write-off, return received) from Khaos Control to your ERP in real time. Your ERP inventory reflects what actually left the warehouse. At month-end, we reconcile Khaos Control physical counts against ERP records and flag any discrepancies so your team can investigate and correct the count.

iWeb routes the return request from your commerce platform to Khaos Control as an RMA with a unique reference number. The warehouse receives the inbound return, inspects it and records the outcome (restocked, damaged, other). The result flows back to your commerce platform and ERP so the customer sees refund progress and your finance team issues the correct credit note.

Your commerce platform displays available shipping options based on the delivery address and configured carrier rules. Once the customer selects a carrier, iWeb ensures that preference flows to Khaos Control with the order. The warehouse uses that selection to request the correct label from the carrier. If the carrier is temporarily unavailable, iWeb alerts your team so you can contact the customer before despatch.

Yes. iWeb tags orders with service level and priority flags from your commerce platform and passes them to Khaos Control. The warehouse team can sort the queue by priority and despatch express orders first. iWeb also monitors whether express orders are being handled in SLA; if despatch is slipping, alerts go to your operations team.

iWeb builds a despatch dashboard that shows order throughput, average time from confirmation to label print, label success rates, and any exceptions (missing stock, address validation failures, carrier errors). Your team can see whether despatch is meeting SLA and drill into any failures so they can intervene quickly.

iWeb sets up alerts so that label failures (due to invalid address, carrier outage, or missing weight data) are surfaced to your operations team immediately. The order is flagged in Khaos Control so it is not assumed to be shipped. Your team can correct the issue and retry without the customer seeing the delay.

Khaos Control is UK-focused, so international shipments require careful mapping of address formats, customs data and regulatory requirements. iWeb creates custom transformations to handle address validation for common destinations, adds required customs fields to the label, and ensures carrier selection rules account for international service levels and costs.

iWeb consolidates orders from each sales channel into a single Khaos Control picking queue. Each order retains its source channel and customer contact details so returns and complaints can be routed correctly. Stock is reserved and managed centrally so you avoid oversell across channels.

iWeb runs end-to-end tests covering order capture, despatch, label generation, tracking return, stock reconciliation and returns workflows. We test failure scenarios (carrier outage, missing stock, invalid address) to confirm exceptions are visible and the team knows how to intervene. We also run a parallel period so you can compare despatch performance before and after the integration is live.

iWeb designs a rollback path where orders can be manually captured in Khaos Control if the automated flow fails. We also retain a 7-day order history so you can re-trigger despatch for any orders that were missed. During cutover, we keep both systems running in parallel for 24-48 hours so we can identify and fix any data gaps before switching fully.

iWeb defines clear ownership with your team. Operational exceptions (missing stock, address errors) are handled by your warehouse team with our support. System exceptions (integration failure, Khaos outage) are escalated to our support team and your IT team. We provide a runbook so your team can restart the flow without waiting for external help.