Skip to main content

Sync orders from before PalSync was installed

Use Historical Orders to request and review eligible older fulfillments.

Written by Mike Hammon

Historical Orders is a separate, controlled lifecycle

Use Historical Orders for fulfillments created before PalSync was installed or outside the realtime path. Tokens apply only to this workflow; they are not order-sync credits and do not affect normal realtime processing.

Annotated Historical Orders request screen showing start date, Get orders, tokens, and request status

Before you click Get orders

  • An active paid PalSync plan is required.

  • The screen must show at least one available token.

  • Only one merchant-initiated historical request is allowed per UTC day.

  • Select the earliest date you need. The request runs from that start date through the current date shown as Orders up to.

  • Include the complete required range because every confirmed request consumes one token.

Request procedure

  1. Open Historical Orders.

  2. Select Start date.

  3. Select Get orders. This estimates the possible order count; it does not yet consume a token.

  4. Review the confirmation dialog and its estimated count.

  5. Select Yes once. PalSync reserves one token and creates the request.

  6. If the queue event cannot be published, PalSync deletes the failed reservation and restores the token.

  7. Monitor the request table until its status becomes terminal.

Token lifecycle

  • Reservation: one token is atomically deducted only when the confirmed request is created.

  • Daily guard: a second user request on the same UTC day is rejected and the existing request remains the reference.

  • Queue failure: the token is restored when PalSync cannot enqueue the new request.

  • Normal completion: the token is not restored merely because zero orders were found, some orders were already synced, or some item outcomes failed.

Annotated Historical Orders request details showing dispositions and reasons

Read results at two levels

The request row shows date range, total orders found, and overall status. Select the status badge to open the fulfillment outcomes:

  • SYNCED_SUCCESS: tracking synchronized successfully.

  • QUEUED_FOR_SYNC: the fulfillment entered the normal sync queue.

  • ALREADY_SYNCED: no duplicate update was necessary.

  • FOUND_ORDER_NO_FULFILLMENT: Shopify did not contain a fulfillment for the order.

  • SYNC_FAILED: use the reason column, such as no matching PayPal transaction, to choose recovery.

A completed request can contain mixed item outcomes. Always review the detail table before treating the historical job as fully successful.

Did this answer your question?