| Header
| Data
|
| payment-status
| should have a value of paid_ship_now for the order to be picked up
|
| order-id
| unique numeric ID for the order on FillZ. If an order has multiple line items, there will be multiple records with the same ID and they will appear contiguously in the file
|
| order-item_id
|
|
| payments-date
| date the customer paid for the order Date Format: yyyy-mm-dd hh:mm:ss (Example: 2007-05-24 13:32:15)
|
| payments-transaction-id
|
|
| product-id
| ISBN/UPC/ASIN/EAN
|
| item-name
| title of item
|
| listing-id
|
|
| sku
| this is the only field you should use to match your internal database
|
| price
| this field is reliable for all markets, but it is only the customer facing amount, without any deductions for fees. It should be multiplied by the "quantity_purchased" field for a sub-total
|
| shipping-fee
| only reliable for Amazon and Biblio
|
| quantity-purchased
| indicates how many items should be shipped
|
| total-price
|
|
| purchase-date
| date the order was placed
|
| batch-id
|
|
| buyer-email
|
|
| buyer-name
|
|
| recipient-name
|
|
| ship-address-1
|
|
| ship-address-2
|
|
| ship-city
|
|
| ship-state
|
|
| ship-zip
|
|
| ship-country
|
|
| special-comments
| this field will contain the marketplace name followed by a slash (/) and the marketplace order identifier
|
| upc
| this field will be filled in for non-book items
|
| ship-method
| If "Standard" appears anywhere in this field, regardless of case (upper/lower), you should ship using your "slow" method. If "Standard" does not appear, you should ship using a "fast" method. Other text in the field is informational only and should not be used to make shipping method decisions
|
| status
|
|
| location
|
|
| tracking
|
|
