Skip to content
English
Go to merchantspring.io
  • There are no suggestions because the search field is empty.

Does the MerchantSpring Vendor API return purchase-order-level data?

Amazon purchase orders contain order-level and item-level information, but reporting APIs can return that information at a different level.

The MerchantSpring Vendor API response discussed during training does not return each raw Amazon purchase order as a separate record.

Instead, it groups purchase-order activity by product or ASIN across the selected reporting period.

What does product-level aggregation mean?

A single Amazon purchase order can contain multiple products. The same product can also appear across several different purchase orders.

The discussed API response combines the relevant activity for each ASIN rather than returning one row for every individual purchase order.

For example, if the same ASIN appears in three purchase orders during the selected period, the response may combine the submitted, accepted, rejected and receipted quantities from those orders into aggregated totals for that ASIN.

What information can the response provide?

Depending on the endpoint and available fields, product-level Vendor reporting may include aggregated measures such as:

  • Submitted quantity
  • Accepted quantity
  • Rejected quantity
  • Receipted quantity
  • Shortage quantity
  • Purchase-order value
  • Product cost or pricing measures
  • Acceptance and receipt rates

These results help users analyse product-level purchasing and supply performance across the selected period.

What does it not show?

An aggregated product-level response may not provide the full detail of each underlying purchase order, such as:

  • One separate record for every PO
  • The complete PO lifecycle for a specific order
  • Every individual shipment or delivery event
  • All order-level dates, parties or delivery instructions
  • A direct explanation for a discrepancy on one particular PO
Example

Assume ASIN ABC123 appears across three purchase orders:

Purchase order Submitted Accepted Receipted
PO 1 100 90 90
PO 2 50 50 45
PO 3 75 60 60

A product-level response may return combined totals for ASIN ABC123:

  • Submitted: 225
  • Accepted: 200
  • Receipted: 195

It may not return the three individual purchase-order rows shown above.

When is product-level data suitable?

Use the aggregated response when the question relates to:

  • Product purchasing trends
  • Acceptance or receipt performance by ASIN
  • Total quantities across a reporting period
  • Product-level supply performance
  • Comparing Vendor activity across products
When might a PO-specific investigation be required?

A separate investigation may be needed when the question relates to:

  • One specific purchase order
  • A shipment or receiving discrepancy
  • A purchase-order amendment or cancellation
  • Missing or delayed inventory
  • A shortage linked to a particular delivery

For a specific PO investigation, provide the purchase-order number, ASIN, Vendor code and relevant reporting period.

Important note

API endpoint coverage and response fields can change as MerchantSpring’s API capabilities develop. Check the current API documentation before confirming the fields, filters and reporting level available from a particular endpoint.

Need help?

Contact support@merchantspring.io and include the relevant account, store, ASIN, Vendor code, reporting period and any helpful screenshots or exports.