The selling price of the order item. Note that an order item is an item and a quantity. This means that the value of ItemPrice is equal to the selling price of the item multiplied by the quantity ordered. Note that ItemPrice excludes ShippingPrice and GiftWrapPrice. For a more detailed explanation of an order item, see Orders API.

We are working on a sales report system that will include pending orders. So i cannot get item price or unit price. I’m thinking about another way, as we have the product info synced with amazon, but amazon only returns a standard price and no sales price, anyone know how to get the sales price of the product?

Pending orders may not actually become an order so trying to incorporate them in a report is probably not something you may want to do. Also what do you mean standard and sales price? The order information for any orders that isn’t pending has the actual price the product was sold for.

We have a similar business use case where having 600 pending orders for 2 days really hurts your ability to see near real-time order data. 95% of the pending orders do come through, so it’s a reasonable expectation to report on them (with everyone knowing a % error)

What we do is if no price is found, we lookup into our database a similar sku & qty and fill in an estimate price. This way we can still do our reporting, and when a real price is found later (by monitoring last-updated on orders) it updates with a real price.

I am curious what use cases there are for actually taking a real-world action on pending order sell price? I used to really want this and then on the second day of being on the platform I realized it didn’t matter. If you are managing a single day’s worth of WIP relative to sales price that seems… dubious.

@hydrohead: this is very useful for real time monitoring of sales. if there were no sales in say a few hours, I know something went wrong; if daily total was below a threshold, I know something went wrong.
And yes, it did happen. A listing was closed by an accident (by Amazon’s rep…), we had listings auto disabled due to pricing errors ("," and “.” confusion), or Amazon’s new algorithm decided to stop displaying us for certain keyword.

The way we actually achieve this was fairly simple:
If OrderPrice == 0 then fetch price for ASIN from a database and use it instead of ‘0.00’.

@hydrohead there are many reasons why we use ‘sales per hour’ or ‘money in per hour’ as our main monitoring metrics. change in Amazon’s algorithm won’t show anything wrong with the listing, but a drop in sales / deviation from the baseline would tell us there’s something wrong. And it did many times.
Ranking, buy box, etc. are of no interest in our case - we manufacture the products and we are the only sellers.

sales gross/day is a great KPI for management (note the ubiquitous use of it in every channel dashboard)

every time it dips management will want to have a reason why (bumps up are due to great management)

hourly KPI gives some poor schmuck a chance to start looking for problems to blame before the carpet call

there are always problems to find, but if sales are good there are better things to do

End result performance indicators are only actionable in highly controlled testbeds. For instance lap times are great feedback at the track for tuning a cars suspension, but timing a heavily congested commuter lap wouldn’t give much handling info.

Sales gross/day is a very useful number, just not something I would want to have to explain changes in regularly. It is funny how quickly these things turn into a way for the tail to wag the dog.