Deferred Delivery for Paazl Checkout Widget: How It Works

1. The customer adds items to their cart and proceeds to checkout.
2. At the shipping step, the Paazl widget displays available shipping options.
3. Some shipping options include a scheduled carrier pickup date (this depends on the carrier and Paazl configuration).
4. The customer selects a shipping option with a deferred pickup date and completes the order.
5. From the customer's perspective, the order is placed as normal.

Once the order is placed, the following automated process takes over:

Order Placed
    |
    v
Order gets "Deferred Delivery" status (instead of going straight to Processing)
    |
    v
Order appears in the Deferred Queue in the admin panel
    |
    v
[Time passes until the scheduled pickup date approaches]
    |
    v
Automatic hourly check detects that the pickup date is approaching
    |
    v
Order transitions to "Processing" status automatically
    |
    v
Order is sent to Paazl (within 5 minutes of transitioning)
    |
    v
Carrier receives the order and prepares for pickup

Navigate to: Stores > Configuration > Sales > Shipping Methods > Paazl Checkout Widget

Under the Deferred Delivery section, you will find two settings:

Note: These settings apply globally (system-wide), not per store view or website.

If you set "Days Before Scheduled Pickup" to 1 and a customer places an order with a carrier pickup date of April 20:

• The order stays in "Deferred Delivery" status from the moment it is placed.
• On April 19, the hourly cron job detects the order is within 1 day of the pickup date.
• The order automatically transitions to "Processing" and is sent to Paazl.
• The carrier receives the shipment details in time to prepare for the April 20 pickup.

If you set it to 2, the order would transition on April 18 instead.

Navigate to: Paazl > Deferred Queue in the admin menu.

This page shows all orders that have been flagged for deferred delivery.

• Search: Use the search bar to find specific orders.
• Filter: Filter by any column (date ranges, status, etc.).
• Delete: Remove individual queue entries.
• Mass Delete: Select and delete multiple entries at once.
• Inline Edit: Update the status field directly in the grid.

• Runs every hour at the top of the hour.
• Checks all pending deferred queue entries.
• If the scheduled pickup date is within the configured "Days Before" window, transitions the order from "Deferred Delivery" to "Processing" status.
• Adds a comment to the order: "Order automatically transitioned from Deferred Delivery to Processing status."

• This is the existing order sending cron that runs every 5 minutes.
• Once an order is in "Processing" status, it becomes eligible to be sent to Paazl.
• The order is sent to the Paazl API on the next run.

Important: No manual action is needed. The transition from Deferred Delivery to Processing to Sent happens fully automatically.

Orders already in the "Deferred Delivery" status will remain in that status. The hourly cron job checks if the feature is enabled before processing, so pending deferred orders will not be automatically transitioned while the feature is disabled. You would need to manually change these orders to "Processing" status, or re-enable the feature.

Yes. You can change the order status from "Deferred Delivery" to "Processing" manually in the Magento admin. Once in Processing status, the order will be picked up by the regular Send Orders cron and sent to Paazl within 5 minutes.

No. Only shipping options that include a carrier pickup date from the Paazl widget trigger the deferred delivery flow. Standard shipping options without a pickup date are processed immediately as usual.

Two ways:

1. Check the order status in the Orders grid - deferred orders show "Deferred Delivery" status.
2. Check the Paazl > Deferred Queue page for a dedicated overview with scheduled dates and processing status.

If the Magento cron is not running, deferred orders will not be automatically transitioned. Make sure your Magento cron is properly configured and running. You can verify cron execution in System > Cron Schedule or by checking the cron_schedule database table.