Schema Release Notes | POA 1.0.11

We've added a new subtotal field to the Purchase Order Acknowledgement (POA) data your integration sends and receives through DataShift.

Today, a POA's order total is made up of a few components; line items, tax, and shipping. Before 1.0.11, only the tax and total amounts were broken out separately. The new subtotal field gives you (and your downstream systems) a clear, explicit figure for the pre-tax order value, making it easier to reconcile what you're being charged and why.

What's changing:

- A new optional subtotal field is now available on the POA schema (version 1.0.11).

- It sits alongside the existing tax and total fields, so no other part of the document format changes.

Do I need to do anything?

No action is required. This field is additive and optional. Existing integrations continue to work exactly as before. If you'd like your mapping updated to populate or consume subtotal, simply refresh the POA schema to retrieve the new version, then map the field by creating a new mapping draft using the new POA schema.

What's next:

This is the first step in a broader improvement to how order totals are calculated and displayed when a line item is rejected or an order is partially fulfilled, including making sure shipping charges are always accounted for correctly. We'll share more details as that work ships.