One operation behind multiple channels
Web, WhatsApp, phone, marketplaces, sales staff and branches can originate orders in different formats. The coordination layer transforms those inputs into normalized state before affecting inventory, billing or fulfillment.
Explicit inventory source of truth
If the ERP or inventory system is authoritative, it remains so. The AI layer reads and executes through authorized interfaces; it does not create a parallel stock record that can silently diverge.
Exceptions are part of the model
Shortages, substitutions, variable quantities, weighted products, delivery windows, returns and rejected payments are not peripheral cases. Each exception has state, policy and a resolution or escalation path.
Customer and operator share the same state
A substitution accepted on WhatsApp must appear in the order the operator fulfills. A shortage found during preparation must return to the correct channel. The goal is to eliminate contradictory versions of the same order.
Automation with action limits
The system can validate, propose alternatives, reserve or update when permissions allow. Economic changes, unauthorized substitutions and out-of-policy exceptions require human intervention.
Traceability for error correction
When an order fails, reviewers should reconstruct which input arrived, which rule executed, which system confirmed inventory and which person intervened. This evidence supports process improvement and dispute resolution without relying on memory.
Operational metrics
Fulfillment errors, substitutions, cancellations, resolution time, inventory divergence and manual work per order measure the actual impact of multichannel coordination.