This section describes the integrities of sales channel integration with Uniware.
A sales channel is generally a marketplace or an online selling platform where a seller can showcase his products with relevant details and get orders.
At Unicommerce we encourage marketplaces to integrate with our order management software UNIWARE for ease of sellers to collate orders from different marketplaces and process them with ease. Uniware get details from channels as order consolidation and posts updated inventory on each marketplace.
We have onboarded all major players like Amazon, Flipkart, Myntra, TATA Cliq etc. in our pool of 70+ marketplaces, B2B channels and carts which can be easily configured from Uniware’s intuitive User Interface (UI). Support article for reference: Channels
- Collate orders from multiple marketplaces at a single place.
- Order processing for all configured marketplaces.
- Inventory management on all configured marketplaces.
The marketplaces willing to integrate with Uniware can refer below mentioned pointers to understand the feasibility and the steps to start the process. Our REST APIs are also provided in this section for reference of your developers to understand the information sharing schema. Once you are confident to take the integration forward, get in touch with our solutioning team for completing the integration.
For seamless seller experience at Uniware it is a requisite to stay in sync with the integrated marketplaces. There exist numerous two-way transactions between Uniware and marketplaces. These transactions range from product catalog sync to order shipment updates. The information flow shown below covers all these transactions with their respective APIs for developer reference. The further details on these APIs pertaining to request and response structure can be referred in their specific pages listed in this section.
Following are the elementary APIs required for each marketplace integrations:
Authentication: following are the two possible ways for authentication in Uniware:
- Get Authentication or Post Authentication: the authentication request is initiated by the Uniware, where the login credentials of the seller (provided by the marketplace) are passed to the marketplace. The marketplace after evaluation, sends the apikey in response against valid seller credentials. This method is used where the API request (Get or Post) is initiated by the Uniware and since in most of our marketplace APIs requests are initiated by the Uniware, this method is mostly used for authentication.
- In the second method, a unique static securitykey is provided by the Unicommerce to each marketplace and this needs to be passed as header to post the information in Uniware. This method is used where the API request is initiated by the marketplace, for instance, the API request to post orders in Uniware by marketplace.
- Get Products Count: to get the product count from marketplace.
- Get Products: to get the live products on marketplace.
- Get Orders: to get the orders from marketplace.
- Get Order Status: to get the updated order status from marketplace.
- Post Inventory Update: to post updated inventory of recently revised/shipped products on marketplace.
- The shipping method can either be Self Shipment (i.e. shipping done by the seller) or Third Party Shipment (i.e. shipping done by the marketplace), not both.
- In case of Self Shipment, the shipping label printing, courier allocation and manifest generation is done on Uniware by the seller.
- In case the marketplace wishes to allows sellers to split or merge an order, the same should be communicated to the Unicommerce solutioning team for backend configuration.
- In this Generic MP Integration seller can only process orders through UC. So we recommend MP to use all mandatory (OMS) APIs. Else, inventory and status can not be handled successfully in UC with other (WMS) related tasks.
Following are the conditional APIs, implemented on need basis depending on the operational flow of marketplace:
When the orders are shipped by the marketplace (Third Party Shipping):
In case of Third Party Shipment, the
thirdPartyShippingflag should be set to
truein the response payload of Get Orders API.
- Get On-hold Orders: when the marketplace wants the sellers to start processing the orders on receiving their confirmation, however block the inventory for such orders so that it does not go out-of-stock later.
- Post Order Acceptance: when the marketplaces wants the sellers to confirm that they will process the orders.
- Post Orders: when the marketplaces wants to post orders on Uniware (generally, the orders are fetched by Uniware from marketplaces using the Get Orders API).
- Get Invoice Details: when the marketplace provides the tax details for order items.
The Get Invoice Details API gets invoice details based on
Order Items IDsand not
Order IDs, which helps in getting valid invoice details even for splitted orders.
- Post Order Dispatch: when the marketplace wants the sellers to notify them that the order has been dispatched.
- Post Order Cancel: when the marketplace allows sellers to cancel the orders and expect notification once the order is cancelled.
Refer Frequently Asked Questions regarding marketplace integrations.