The InvoiceLineItem JSON object defines a line item of an invoice 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
# One of the item identifiers must be present, exactly one of
# dscoItemId, sku, partnerSku, upc, ean
Object
{
int lineNumber;
int quantity;
string sku?;
string partnerSku?; # Added in V2
string upc?; # Added in V2
string ean?; # Added in V2
string title?;
double unitPrice?;
string basisOfUnitPrice?;
string unitOfMeasure?;
double extendedAmount?;
double handlingAmount?;
isodate shipDate?;
string trackingNumber?;
double shipAmount?;
string shipCarrier?;
string shipMethod?;
string shippingServiceLevelCode?;
string promotionReference?;
double promotionAmount?;
double taxAmount?;
double subtotal?;
double dscoExpectedAmount?; # The item cost multiplied by the quantity
double dscoExpectedDifference?; # subtotal - dscoExpectedAmount
int dscoItemId?; # The DSCO unique ID for the associated item
int originalLineNumber?; # Added in V2
int originalOrderQuantity?; # Added in V2
int dscoPackageId?; # Added in V2
double shipWeight?; # Added in V2
string shipWeightUnits?; # Added in V2
};
Example
{
"lineNumber": 1,
"quantity": 1,
"sku": "82342222"
}
Comments
Please sign in to leave a comment.