This article explains what a Stale PO Acknowledgement (PO Ack) is, why it happens, and what to do when you receive a Stale PO Ack alert from Leverage. Understanding the 400-degree sync process is key to resolving these alerts quickly.
What is a Stale PO Ack?
When a supplier submits a PO Acknowledgement and the buyer accepts it, Leverage starts what we call the 400-degree sync: Leverage writes the updated order details back to your system of record (ERP), your ERP ingests the writeback and sends confirmation back to Leverage, and Leverage then moves the order status. This full round trip must complete successfully for the acknowledgement to be considered synced.
If your ERP does not send that confirmation back to Leverage within seven days, the affected PO Ack line items are marked as Stale. Stale lines are indicated by a circular arrow icon and can be filtered using the Stale filter on the orders page.
When you hover over the sync icon, the tooltip states: “Supplier's changes have been written back to your system of record. Leverage has not yet received your updates to this PO Line from your system of record.”
Leverage also sends an automated alert to your distribution list with a subject similar to:
[ACTION REQUIRED, integrationId X] Stale PO Ack Line Items: N
The alert includes a file attachment listing the affected line items.
Note: Occasional sync interruptions between Leverage and your ERP are not always a cause for alarm. An occasional Stale order may only require a resync. If Stale orders appear regularly, investigate the integration more deeply.
Steps to resolve
1. Compare the details in Leverage and your ERP
For each Stale line, compare the order details in Leverage with the corresponding line in your ERP. Look for supplier acknowledgement changes, such as an updated promise date or revised quantity, and confirm whether those changes are reflected in your ERP.
2. Update your ERP if needed
If the changes did not reach your ERP, coordinate with your integration or IT team. If you have the required permissions and your team confirms that a manual update is appropriate, update the ERP order so its details match Leverage before attempting another sync.
3. Start a sync
Follow the resync method defined for your integration. Depending on the ERP and integration configuration, re-saving or re-releasing the order may trigger a sync. In some cases, an authorized edit to the order details may also trigger it.
After the details are aligned and the sync completes, Leverage should receive confirmation and move the order status. If you are unsure which action triggers a sync, ask your integration or IT team.
4. Investigate recurring or unresolved Stale lines
If the order remains Stale after syncing, or Stale orders recur regularly, involve your IT or integration team. Determine:
Is the ERP processing the writeback attempt from Leverage?
If so, why is the ERP not sending confirmation back to Leverage?
The specific investigation steps depend on your ERP and integration configuration. Leverage Support can provide details from our side, including the timestamp and data in the latest writeback attempt, to help your team pinpoint the issue.
Key terms
PO Acknowledgement (PO Ack): A supplier’s formal response to a purchase order confirming details such as ship dates, quantities, and pricing.
Writeback: The process of Leverage sending accepted acknowledgement data to your ERP or system of record.
400-degree sync: The full round-trip confirmation process. Leverage writes updated order data to your ERP, your ERP ingests the changes and sends confirmation back to Leverage, and Leverage moves the order status.
Stale: A PO Ack line that has not completed the 400-degree sync within seven days. The ERP has not yet confirmed receipt of the writeback.
Need additional help?
Contact Leverage Support through the Help Desk or email support@tryleverage.ai.