A: Since Uniware offers Centralized Inventory management, it has a defined mechanism for auto inventory sync as well as manual updates as soon as an offline sale is made. Please see below the two methods readily available on our interface: Auto-inventory sync, which is system initiated. Manual Inventory adjustments can…

Click here for Tutorial Video – English Click here for Tutorial Video – Hindi Once an order is created, the system automatically checks and blocks inventory for the order items in all the pending orders. Order Items which are fulfillable (inventory available in warehouse) are created as a shipment, while…

The Inventory and stock out updates form a very important aspect of keeping the centralized inventory in line with the warehouse scenario. The real time stock adjustments are reflected in the system. There are some background processes running periodically to carry out the task of keeping the inventory updated. The…

Before knowing how to create put away for cancelled order items, let’s understand that put away for cancelled items can be created only for those shipments which have been cancelled after being packed/invoiced or even ready to ship. This is because after being cancelled the order item blocked and allocated to that order…

A: Steps to cancel an order: 1- Search and open the sale order whose items are to be cancelled. 2- Click on the Order action icon and select ‘Cancel’ Order. 3- Select the orders, all or specific, to apply the cancel action on them.   4- You can cite the reason…

Order can search through the global search option at the top bar for more details watch the video:

Recommended for you: What is Order Management and Processing?  

A: Serviceability determines all the pin codes (or areas) where a store can deliver its orders. In Unicommerce O2O, we can upload the serviceable pin codes via CSV files. To do the same, follow these steps: 1- Select “Tools” in the main menu, then click “Import”. 2- Select “Shipping Provider…

Description- This API is to be used to get GRN details providing GRN code in provided facility. API detail – <soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ser=”http://uniware.unicommerce.com/services/“>    <soapenv:Header/>    <soapenv:Body>       <ser:GetInflowReceiptDetailRequest>          <ser:InflowReceiptCode>?</ser:InflowReceiptCode>       </ser:GetInflowReceiptDetailRequest>    </soapenv:Body> </soapenv:Envelope>   Sample Request: <soapenv:Envelope xmlns:ser=”http://uniware.unicommerce.com/services/” xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/“>    <soapenv:Header>    <wsse:Security soapenv:mustUnderstand=”1″ xmlns:wsse=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd” xmlns:wsu=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd“>       <wsse:UsernameToken wsu:Id=”UsernameToken-DE3DF51DD092A8B61714338585185482″>          <wsse:Username>techsupport@unicommerce.com</wsse:Username>          <wsse:Password Type=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText“>f5556bcf74d15ddb67ca3035b8bc969c</wsse:Password>…

Description: The API is to create Purchase order via API in the given facility. API detail: <soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ser=”http://uniware.unicommerce.com/services/“>    <soapenv:Header/>    <soapenv:Body>       <ser:CreateApprovedPurchaseOrderRequest>          <!–Optional:–>          <ser:PurchaseOrderCode>?</ser:PurchaseOrderCode>          <ser:VendorCode>?</ser:VendorCode>          <ser:VendorAgreementName>?</ser:VendorAgreementName>          <!–Optional:–>          <ser:CurrencyCode>?</ser:CurrencyCode>          <!–Optional:–>          <ser:ExpiryDate>?</ser:ExpiryDate>          <!–Optional:–>          <ser:DeliveryDate>?</ser:DeliveryDate>          <ser:PurchaseOrderItems>             <!–1 or more repetitions:–>             <ser:PurchaseOrderItem>                <ser:ItemSKU>?</ser:ItemSKU>                <ser:Quantity>?</ser:Quantity>                <ser:UnitPrice>?</ser:UnitPrice>                <!–Optional:–>                <ser:MaxRetailPrice>?</ser:MaxRetailPrice>                <!–Optional:–>                <ser:Discount>?</ser:Discount>                <!–Optional:–>                <ser:TaxTypeCode>?</ser:TaxTypeCode>             </ser:PurchaseOrderItem>          </ser:PurchaseOrderItems>       </ser:CreateApprovedPurchaseOrderRequest>…

Description: This API is to be used to get GRN Code in the provided facility. API detail: <soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ser=”http://uniware.unicommerce.com/services/“>    <soapenv:Header/>    <soapenv:Body>       <ser:GetInflowReceiptsRequest>          <!–Optional:–>          <ser:PurchaseOrderCode>?</ser:PurchaseOrderCode>          <!–Optional:–>          <ser:CreatedDateRange>             <ser:Start>?</ser:Start>             <ser:End>?</ser:End>          </ser:CreatedDateRange>       </ser:GetInflowReceiptsRequest>    </soapenv:Body> </soapenv:Envelope>   Sample Request: <soapenv:Envelope xmlns:ser=”http://uniware.unicommerce.com/services/” xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/“>    <soapenv:Header>    <wsse:Security soapenv:mustUnderstand=”1″ xmlns:wsse=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd” xmlns:wsu=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd“>       <wsse:UsernameToken wsu:Id=”UsernameToken-89D7DFA8EF321344FA14368696947561″>          <wsse:Username>babasupport@unicommerce.com</wsse:Username>…

API Operations   Description: The API is used to mark given Shipment as Delivered. This is specific to O2O channel (Offline To Online model), and only if the order is of the type “Pick up”. API: <soapenv:Envelope     xmlns:ser=”http://uniware.unicommerce.com/services/“     xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/“>     <soapenv:Header>         <wsse:Security             xmlns:wsse=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd“             xmlns:wsu=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd” soapenv:mustUnderstand=”1″>             <wsse:UsernameToken wsu:Id=”UsernameToken-1″>                 <wsse:Username></wsse:Username>                 <wsse:Password Type=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText“></wsse:Password>                 <wsse:Nonce…

API Operations Description: The API is used to mark DISPATCH the given Shipment code. The pre-condition is that the shipment must be READY TO SHIP status for the API to return success, for other statuses it will return an error. API: <soapenv:Envelope     xmlns:ser=”http://uniware.unicommerce.com/services/“     xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/“>     <soapenv:Header>         <wsse:Security             xmlns:wsse=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd“             xmlns:wsu=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd” soapenv:mustUnderstand=”1″>             <wsse:UsernameToken…

API Operations Description: The API is used to create invoice for the shipment passed. It will also allocate the Shipping provider. Thus, post this action the shipment status will be “PACKED”. API: <soapenv:Envelope     xmlns:ser=”http://uniware.unicommerce.com/services/“     xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/“>     <soapenv:Header>         <wsse:Security             xmlns:wsse=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd“             xmlns:wsu=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd” soapenv:mustUnderstand=”1″>             <wsse:UsernameToken wsu:Id=”UsernameToken-1″>                 <wsse:Username></wsse:Username>                 <wsse:Password Type=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText“></wsse:Password>                 <wsse:Nonce EncodingType=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary“>HdMl9CcEHxcEQjlVeB4eOg==</wsse:Nonce>                 <wsu:Created />             </wsse:UsernameToken>…

API Operations Description: The API is used to the inventory snapshot of your warehouse, which implies that it will carry the inventory count of product SKU placed in the warehose, irrespective of whether it is in stock or even out of stock. API: <soapenv:Envelope     xmlns:ser=”http://uniware.unicommerce.com/services/“     xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/“>     <soapenv:Header>         <wsse:Security             xmlns:wsse=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd“             xmlns:wsu=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd”…