The order import script via scheduled task runs when all ideal conditions have been met, the incoming order processed by Amazon, the payment confirmed.
However, there are exceptions, such as the request of supporting documents by Amazon to the customer, which will result in a delay in processing the order.
This is why this automation do not exempt you from regular checks of your order feeds, such as the daily confrontation of orders imported on PrestaShop and those on Amazon.
The module also imports FBA orders, for these orders, the module extends the two-day observation period because Amazon “waits” before sending orders that are not ordered by express delivery.
There is no need to increase the frequency of scheduled tasks, first because the observation period would remain the same so no more orders would be imported and second because Amazon imposes use quotas of its API, therefore the imports would become inoperative.
So, on one hand Amazon API quotas prevent to expand the observation period, second some orders can sometimes be processed with a certain delay, so orders pass through the automaton observation period; there is loss of order imports.
A catch-up cron session is however possible;
- For FBA orders, deemed shipped, it’s appropriate to conduct a catch-up session per day, for that add &recheck=1 to the URL of the order import scheduled task, then ask the addition of this new scheduled task to your webmaster (version 4, any version).
- For regular orders, non-shipped, it is appropriate to conduct a catch-up session per day, for that add &doublecheck=1 to the URL of the order import scheduled task, then ask your webmaster to add this new scheduled task (version 4.1.090 and >).
Note that the recommended settings are developed for stores generating a hundred orders per day and up to 500 orders, however if your order volume is over 100 orders per day, it would be appropriate to contact us for fine adjustments , see in this case Support page.
