Bug Fixes
- Fixed fatal error in Repricer when getItemOffers returns invalid response – Merchants accessing the Repricing page encountered a fatal error when Amazon’s getItemOffers API returned a null or invalid response. The error “Call to a member function getSummary() on null” prevented the page from loading. Added proper null checking and error handling to gracefully manage invalid API responses. (Ticket #68110)
- Fixed missing API class files in Repricing page – Amazon orders were not syncing to WooCommerce when using the Repricing feature because required API class files weren’t being loaded on the Repricing page. Ensured all necessary API classes are properly initialized when accessing repricing functionality. (Ticket #68128)
- Improved support for Amazon’s beta custom feed templates – Amazon made format changes to their beta custom feed templates, which broke the template parser. Merchants uploading beta templates found that attribute names weren’t displaying correctly. Updated the feed template parser to handle the new beta format. Note: We continue to recommend using non-beta templates when possible as Amazon may make additional changes. (Ticket #68211)
- Fixed “Undefined variable $success” warning – PHP warning appeared in logs: “Undefined variable $success in WPLA_AjaxHandler.php on line 1016”. While not affecting functionality, this warning cluttered error logs. Properly initialized the variable before use. (Ticket #68078)
- Fixed promotional discount handling in order imports – When Tax Mode was set to “Import from Amazon”, promotional discounts were being incorrectly added to line item prices instead of being applied as separate deductions. This caused WooCommerce order totals to be inflated and prevented merchants from properly refunding orders, as the refundable amount in WooCommerce didn’t match what was actually charged on Amazon. Promotional discounts are now correctly handled as separate line items, maintaining accurate order totals and enabling full refunds. (Ticket #68406)
- Added throttling detection for getOrderItems API call – When Amazon’s API returns a throttling error (HTTP 429 or 400) for order item requests, the system now properly detects this and sets a flag to skip further order processing until the next scheduled run. This prevents cascading errors during high-volume order imports and ensures imports resume smoothly once throttling ends.
- Fixed fatal error when generating FBA Shipping Methods – Merchants using FBA with custom shipping methods encountered a fatal error during checkout when WooCommerce’s cart and session objects weren’t properly initialized. Added proper initialization of WC_Cart and WC_Session objects before generating FBA shipping methods to prevent crashes.
Technical Changes
- Enhanced logging for third-party tracking plugins – Added detailed logging to the process_third_party_tracking_plugins() method to help diagnose issues when tracking information from plugins like YITH WC Order Tracking or WooForce Shipment Tracking isn’t syncing properly to Amazon. Logs now include carrier names and tracking numbers for easier troubleshooting.