PeopleVox: Update to Request Schema 2.0
G
Georgia Kirkham
We are currently using version 1.1, can we update to 2.0?
Use this version if any of the following apply:
- You are writing a new integration to the platform
- You need data to know from where in the warehouse (which print station) the request originated
- You need information about kitting relationships on the request
m
matt thomson
One of the big drivers for this one is that the 2.0 schema changes the way that the sale price is represented on kitted items. In 1.1, this was ambiguous between the parent and child SKU, but in 2.0 it's explicitly defined against the parent, which helps to prevent issues with over-reporting the value of products in a parcel (e.g. for customs declarations).