The OrderEstimatedShipDateLineItem JSON object defines the estimated ship date for a line item of an order in the Dsco system.

- Make sure you're familiar with JSON before continuing.
- The JSON objects are defined using Orderly.  Optional attrs end with a "?" all others are required.

- isodate fields use one of these ISO 8601 format: 2014-01-01T10:30:00.000+01:00, 2014-01-01T10:30:00.000+0100, 2014-01-01T10:30:00.000Z
- Dsco reserves the right to add new attributes at any time so Partners should ensure their validators won't break should this happen

Definition

Each line item must uniquely identify the item in question by providing an Item Identifier - either dscoItemId, sku, partnerSku, upc or ean.  If a line item does not include either dscoSupplierId or dscoTradingPartnerId and if the item identifier provided is found on more than one trading partner, Dsco will be unable to determine the desired item.  If more than one Item Identifier is provided, Dsco will use the first of the following found in this order: dscoItemId, sku, partnerSku, upc, ean.

Object
{
    int dscoItemId?;         # The Dsco unique ID of the item, one of
                             # dscoItemId, sku and partnerSku is required
    string sku?;             # The SKU of the item, if dscoItemId is not
                             # present then this attr is required
    string partnerSku?;      # The partner SKU of the item, one of
                             # dscoItemId, sku and partnerSku is required
    isodate estimatedShipDate; # The estimated shipd dateate
};

Example

{
    "dscoItemId": 8276,
    "sku": "aa832934",
    "estimatedShipDate": '2014-01-01T10:30:00.000Z'
}
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.