...
Triggering scheduled jobs, for fetching orders, return orders, sending sales posting
Saving external identifier to internal Identifiers mappings,
Applying buffer on Inventory
Sending Inventory update to integration/marketplaces
We have a separate team that manages all Omni related integrations.
A channel is either an ERP or a Marketplace. The CIMS module allows OMS to be integrated with channels. It performs the following key tasks of communication b/w OMS and a channel.
Receiving new masters, updates in masters from channel
Sending inventory updates to channel (as and when GRN or inventory allocation happens)
Receiving new orders and order-updates
Creation of invoice, AWB and manifest
Receiving return orders
Channel Configuration
One can easily configure a channel for integration using the CIMS UI. The following information needs to be supplied.
Channel credentials (this can be obtained from the market places)
Mappings
warehouse-id to channel warehouse-id mapping
product-id to channel product-id mapping
channel-id to ERP customer-id mapping (in case of ERP integration)
Inventory exposure buffer (say 1 or 2) to expose lesser inventory than available. So if buffer is 1, and available inventory is 3, then only 2 pieces will be sent to the channel. This is useful in peak sales periods, where the chances of excess orders are high.
Logs
The system automatically stores last 10 inventory updates with the channels, so that in case there is any inventory discrepancy, then it be easily diagnosed.
CIMS Screenshot
...