Send order statuses

Intended usage
Customers want to know how their order is doing, especially in times of supply chain uncertainty it is important for them to know when their order will be delivered, and if they should be expecting major delays. This may result in them contacting their supplier for updates in an attempt to gain further insight into the process, which is time consuming and frustrating for both parties. However, as a supplier you can try to pro-actively inform your customer by sending status updates of how the order is doing. The sent order statuses message enables this type of communication.
The order status message
Status message content
The order status message always references a defined order and is issued at a specific moment in time on which the status message was sent. The status is provided on the order line level, and a single message may contain the status update for multiple order lines, such as would be the case when a whole order has been updated and thus all order lines are updated.
Each of the order lines in the order status message contain a single reference to the original delivery schedule and the datetime on which the status was present for that orderline.
The status is defined using the status codes, being:
010
Order accepted
020
Order scheduled
030
Ready for production
040
In production
050
Production completed
055
Quality check completed
060
Ship ready
070
Shipped
Finally, the order status message may contain a status value with a string describing the order status and an item quantity to describe the amount of items the status update is referring to. This is for example relevant when only a part of the order is now in production.
Example message
Below an example message of the order status message.
// <?xml version="1.0" encoding="UTF-8"?>
<!--
	Standard: SCSN Order status v2.0
	Last updated: 2020-03-23
-->
<OrderStatus xmlns="SmartConnectedSupplierNetwork:schema:xsd:OrderStatus" xmlns:scsn="SmartConnectedSupplierNetwork:schema:xsd:OrderStatus" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <scsn:IssueDateTime>2018-10-06T15:01:00+01:00</scsn:IssueDateTime>
    <cac:OrderReference>
		<cbc:ID>123456</cbc:ID>
	</cac:OrderReference>
    <scsn:OrderLineStatus>
    	<cac:OrderLineReference>
    		<cbc:LineID>1</cbc:LineID>
    	</cac:OrderLineReference>
    	<scsn:DeliveryStatus>
    		<scsn:DeliveryReference>3</scsn:DeliveryReference>
    		<scsn:StatusDateTime>2018-10-08T15:01:00+01:00</scsn:StatusDateTime>
    		<cbc:StatusCode>020</cbc:StatusCode>
			<scsn:StatusValue>[value]</scsn:StatusValue>
			<cbc:Quantity unitCode="C62">10</cbc:Quantity>
    	</scsn:DeliveryStatus>
    </scsn:OrderLineStatus>
</OrderStatus>

Use-cases - Previous

Simple Order process of custom-made items

Next - Use-cases

Price Catalogue: exchanging dynamic information of articles

Last modified 3d ago

Copy link

Outline

Intended usage

Status message content

Example message