An inbound message is a request that WebSphere Commerce receives from an external application. Each inbound message activates a command in WebSphere Commerce that performs a particular function. If there is an error processing an inbound message, it is placed into the error queue.
WebSphere Commerce supports inbound back-end messages that accomplish the following five functions:
- Create a customer registration
- Update a customer registration
- Update the status of an order
- Update the inventory for a product
- Update the price of a product
Each of the functions listed above can be activated by a request message in XML format, and some can be activated using the legacy message format. In general, the XML format is recommended. The XML messages are encoded in UTF-8 format.
To create a customer registration, use the Create_WCS_Customer XML message. If you already record customer information on an existing back-end system, rather than re-create this information from scratch, use this message to register the customer data on the WebSphere Commerce database. The message sends existing customer information from the back-end server to the WebSphere Commerce server. You can also use the Create_NC_Customer XML message, and the Customer Update legacy messages to perform similar function. However, the Create_WCS_Customer XML message provides you with capability to enter more customer information.
To update a customer registration that already exists in the WebSphere Commerce database, use the Update_WCS_Customer XML message. When you use this message, the back-end customer management system updates customer information and sends the message to WebSphere Commerce to update information about a registered customer. You can also use the Update_NC_Customer XML message, and the Customer Update legacy messages to perform a similar function. However, the Update_WCS_Customer XML message provides you with capability to update more customer information.
To update the status of an order that already exists in the WebSphere Commerce database, use the Update_WCS_OrderStatus XML message. Use this message to update the WebSphere Commerce database with the status of orders that are processed by a back-end application. For example, the shipping status of an order from the back-end fulfillment system can be updated in the WebSphere Commerce system by sending this message from the back-end system to WebSphere Commerce. You can also use the Update_NC_OrderStatus XML message or the Order Status Update legacy message to perform similar function. However, the Update_WCS_OrderStatus XML message provides you with capability to update more order status information.
To update the inventory for a product that already exists in the WebSphere Commerce database, use the Update_WCS_ProductInventory XML message. This message is ideal for instances when an external or back-end inventory system maintains product inventory. The external system can send the message to WebSphere Commerce to update inventory in the WebSphere Commerce database. You can also use the Product Quantity Update legacy message to perform the same function. Alternatively, the Update_NC_ProductInventory XML message performs a similar function. However, the Update_WCS_ProductInventory XML message provides you with capability to update more inventory information.
To update either the list price or the offer price of a product that already exists in the WebSphere Commerce database, use the Update_WCS_ProductPrice XML message. This message is ideal for instances when an external or back-end system maintains product information, including prices. The external system can send one of these messages to WebSphere Commerce to update list prices or offer prices of products in the WebSphere Commerce database. If you are updating the offer price of a product, you can also use the Update_NC_ProductPrice XML message or the Product Price Update legacy message to perform the same function. However, only the Update_WCS_ProductPrice message can be used to update list price information.