SmartTurn Integration: Order Fulfillment

SmartTurn is a very good warehouse management system. It has features which cover from item purchasing to item shipping, within these processes, item inventory/warehouse status will be automically updated.

So how can integration help? Let’s talk about one of the features that we can perform in SmartTurn, Order Fulfillment. Here is one scenario:

1. I am managing a clothing wholesale business, a customer has ordered 200 items from my company. Within these 200 items, 100 will be shipped to location A, 50 will be shipped to location B, and the rest to location C.

2. If the customer is placing an order through my CRM or eCommerce system. The integration process can synchronise the Sales Order into SmartTurn specifying all the item details and customer’s shipping destinations.

3. SmartTurn will then check the inventory status, if the stock is insufficient, the shipment will be put ‘On Hold’.  If everything goes well, the inventory count will be deducted in SmartTurn. We can then synchronise the latest inventory count to our Accounting System.

Below is a simple diagram illustrating the above scenario:

We can integrate SmartTurn with any other CRM, ERP system or etc. which improve efficiency in order processing and fulfillment. As with the above scenario, updating the customer information and purchasing details, processing the transaction before confirming shipment status and other details.

JIRA Integration: Work Logs

The time logged in a specific issue can be retrieved from JIRA by using the JIRA API (getWorklogs). The result returned will include the details of the time logged into an issue. For example:

<multiRef id=”id1″ soapenc:root=”0″ soapenv:encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” xsi:type=”ns3:RemoteWorklogImpl” xmlns:soapenc=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:ns3=”http://service.soap.rpc.jira.atlassian.com”>
<author xsi:type=”xsd:string”>hmkhong</author>
<comment xsi:type=”xsd:string”/>
<created xsi:type=”xsd:dateTime”>2011-10-12T06:22:18.663Z</created>
<groupLevel xsi:type=”xsd:string” xsi:nil=”true”/>
<id xsi:type=”xsd:string”>10002</id>
<roleLevelId xsi:type=”xsd:string” xsi:nil=”true”/>
<startDate xsi:type=”xsd:dateTime”>2011-10-12T06:22:00.000Z</startDate>
<timeSpent xsi:type=”xsd:string”>2 hours</timeSpent>
<timeSpentInSeconds xsi:type=”xsd:long”>7200</timeSpentInSeconds>

<updateAuthor xsi:type=”xsd:string”>hmkhong</updateAuthor>
<updated xsi:type=”xsd:dateTime”>2011-10-12T06:22:18.663Z</updated>
</multiRef>

If you find the “pretty” format too difficult to calculate, you can use the timeSpentInSeconds. This field will returned time logged in seconds.