Skip to main content

Push ASN Changes

POST 

/api/purchase-orders/:purchase_order/asn/push-changes

Apply this purchase order's changes since its ASN was sent to the warehouse system's copy (ShipHero). The live warehouse PO is read first: a PO that is locked, closed or cancelled there is never changed.

Required scope: purchase-orders:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

  • Quantities are set absolutely; a removed line (or a quantity of 0) deletes that line in the warehouse system.
  • A quantity is never set below what the warehouse already received.
  • Tracking, PO date and note changes are sent with it (a removed PO date is cleared).
  • A SKU added after sending follows the connection's asn.line_addition_policy: a supplementary PO ({po_number}-A, -B…) holding only the new lines; cancel and send again as the next revision ({po_number}-R2…, only while nothing is received); or an email to the 3PL.
  • A changed destination warehouse or vendor cancels and sends the PO again while nothing is received, and is refused once receiving started.
  • With asn.change_notifications = email the 3PL is also emailed the changes (with the revised ASN spreadsheet while the backup spreadsheet is on).

data.status is updated, in_sync when there was nothing to push, or emailed when the connection never changes a sent PO (asn.change_policy = lock) and the 3PL was emailed instead. Returns 422 when the PO was never sent or the change can't be applied. Returns 422 ASN sending is off for {connection}… when the connection's ASN sending (asn.enabled) was switched off after the PO was sent; receipts keep syncing.

Requires permission: purchase_orders.update

Authentication: Requires Bearer token.

Request​

Responses​

OK

Response Headers
    Content-Type