Doba

Miscellaneous FAQ's

Miscellaneous

  1. What is the relationship between products and items?

    Although synonyms, “products” and “items” have unique definitions and relationship for Doba. Products and items have a parent-child relationship in terms of what each supplier sells. A “T-shirt” is a product while the “Small Red T-shirt” is an item or item option of the “T-shirt” product. This relationship as well as corresponding data will be explained below.

    A product is what a supplier provides that may or may not have item options. It is not necessarily specific beyond the title, brand, description, and image. An example of a product is a T-shirt. One does
    not know the size or color options available. It is simply a product that the supplier sells. Product-specific data only specifies the following:

additional_details
brand_name
categories
condition
description
flags
images
items
manufacturer
messages
product_group
product_id
product_sku
ship_cost
ship_freight
ship_height
ship_length
ship_width
status
supplier_name
title
warranty

Items are the options available for a product. They could be a single option, but can also be a large array of options spanning colors, sizes, and models. An example of items are the options available for a T-shirt: small, medium, and large in colors white, pink, red, orange, yellow, green, blue, and purple. Item-specific data specifies the following:

attributes
custom_price
est_avail
in_specified_list
in_warehouse
item_dim1
item_dim2
item_dim3
item_id
item_sku
item_weight
last_update
map
mpn
msrp
name
prepay_price
price
qty_avail
stock
supplier_id
upc


 
  1. Where can I get a taxonomy file or an index tree of the Doba categories?

    You can send an email to enterprise@doba.com requesting it and it will be given. As the categories can change at any point, we like to provide you the most up-to-date taxonomy file. We can run a report that produces this in a csv file that matches whatever is currently displaying in the catalog and database.

     
  2. Where can I get definitions for what is included in the exports?

    You can check this information in the API documentation under the “API Introduction” page in the “Export Automation” section.

    Product Files: http://www.doba.com/developer/20110301/api_introduction_retailer.php#data_export_product_definition

    Inventory Files:
    http://www.doba.com/developer/20110301/api_introduction_retailer.php#data_export_item_definition

     
  3. What is the difference between product_sku, item_sku, product_id, and item_id?

    SKUs are usually created by a supplier. They are only a Stock Keeping Unit number. That means that it is used as a way to identify and maintain stock on an item. It is essentially a barcode given by the supplier to help maintain a quick reference on the item by simply scanning in--and out--items available and items that are ordered.

    There is a parent-child relationship between the product_sku and the item_sku. The product could be a T-shirt, while the item could be the Red Small T-shirt.

    Doba’s system mimics the SKUs with the product_id and item_ids. These are identifiers that are unique to Doba and will likely not be found online. They are very important as these identifiers will not ever repeat. Often the SKUs will repeat in our catalog because suppliers may use the same convention in naming or creating SKUs. This would normally cause problems in a standardization process like Doba’s (where a catalog is aggregating many suppliers into one unified and standardized catalog) if only the
    SKU were to be used as a unique identifier. As a side effect of using unique identifiers, we require the most granular of those identifiers--the item_id--as the only orderable identifier we allow.

    Sometimes there are other ways to artificially create parent-child relationships or product and item-option groups. One of those methods is by grouping UPCs or MPNs. Those could then be grouped to the existing parent-child groups either based on product_sku & item_sku OR product_id & item_id.

     
  4. Why are there duplicates in the order statuses?

    There are two separate statuses that are at play here: “Supplier Order Status” and “Line Item Status.” These statuses depend on the different aspects of the order. There could be multiples of a single item that are ordered and there could potentially be multiple suppliers fulfilling the order. The most up-to-date information can be found on the links below:

    Supplier Order Statuses
    (http://www.doba.com/developer/20110301/api_introduction_retailer.php#Supplier_Order_Status)




    Line Item Statuses
    (http://www.doba.com/developer/20110301/api_introduction_retailer.php#Line_Item_Status)



    Keep in mind that when you are updated on the status, if there are multiples of an item ordered or if there are multiple suppliers involved with the order, it will generally provide a few updates to you.

     
  5. Can the API work natively in .NET framework?

    No. You will be required to initially build a DLL file with the WSDL file that we provide you. We do not currently provide that DLL file or an SDK for .NET. For more information see the following link:
    http://www.doba.com/developer/20110301/index_retailer.php#SOAP_Code_Example_dotNET

     
  6. Which identifiers will Doba accept when placing orders?

    Doba will only accept the item_id when placing orders. That identifier is the most unique, granular identifier in our system. There is overlap and duplicates when it comes to UPC, MPN, SKU, and the related identifiers.

    See the following links with more information:
    API: http://www.doba.com/developer/20110301/method_reference_retailer_order.php#createOrder
    Batch Order Upload: https://enterprise.doba.com/members/orders/upload-column-headers.html

     
  7. Can I create and fund an order simultaneously?

    There is currently no true way to do this. There are two API methods that must be used when creating and funding an order: ‘createOrder’ and ‘fundOrder’ respectively. Some retailers use the two methods in tandem through if-else statements in their code. However, there is no way to truly do both simultaneously.

    http://www.doba.com/developer/20110301/flowchart/Order%20Process%20Flow%202011-03-01.pdf


     
  8. My credentials are all correct, why is my API call failing?

    The API Documentation appears to indicate that there are 3 parts to authenticate. However, there is actually a fourth aspect of your credentials: the URL that you are posting to.

    Make sure that you use the correct username, password, retailer ID, and URL in order to get success in your API call. If there is something else that is wrong with your API call, you will get the respective error.

    API Failure Codes:
    http://www.doba.com/developer/20110301/api_introduction_retailer.php#Failure_Codes

     
  9. Can I use different API versions in order to send more than 144,000 calls daily?

    No. The 144,000 API call limit per day is counted regardless of the API version you are consuming. We highly recommend using the most up-to-date version of the API (20110301) as the information provided is validated. The legacy versions of the API will be sunset and should not be used, unless you are in a migration phase and must maintain a working application.

    If you are ever in doubt as to the version you are using, please check your API URL that you are posting to. It will be listed within the URL as follows:

    https://www.doba.com/api/20110301/xml_retailer_api.php ← This is the 20110301 version (current)
    https://www.doba.com/api/20101012/xml_retailer_api.php ← This is the 20101012 version (old)

Did you find this article helpful?