How Far Back Do We Re-Sync Sales from Toast POS?

When using Toast POS, sales and order updates are automatically synchronized with Axial — including corrections made to past checks.

How the Sync Works

Axial retrieves order data from Toast using the OrderBulk endpoint. This endpoint pulls orders based on a startDate and endDate range.

Instead of syncing only “new” orders, Axial fetches:

From the last successful polling time (minus 1 second) up to the current time (“now”).

This ensures we capture:

• New orders

• Recently modified orders

• Corrections made to previous checks

What Happens When a Past Check Is Updated?

If an order is updated in Toast (for example, a correction made to a check from a week or two ago), Toast updates the order’s modifiedDate field.

Axial uses this modifiedDate value to detect changes. As long as the order’s modifiedDate falls within the polling window, the update will be included in the next sync cycle.

In Practical Terms

• ✔ If a check from last week is corrected today, it will sync to Axial.

• ✔ If a check from two weeks ago is updated today, it will sync to Axial.

• ✔ Any order updated after the last successful sync will be captured.

Is There a Time Limit?

There is no fixed “lookback window” (such as 7 or 14 days).

The system does not rely on the original order date — it relies on the most recent modification date. If Toast registers a modification, it will be picked up in the next polling cycle.

Summary

Axial does not re-sync based on how old the order is.
It re-syncs based on when the order was last modified.

As long as the update changes the modifiedDate in Toast, the correction will automatically be reflected in Axial.