|
Current Problem
The Veeqo connector stores the Veeqo allocation ID (ExtraCode1) once, at order import. It does not re-read the order at despatch or on Resync Connect Action, and there is no import delay setting. On some orders, Veeqo's API returns the order without its allocation at the time Mintsoft imports it. Veeqo have confirmed this is stale cached order data on their side and are investigating. The allocation exists in Veeqo, but the order data Mintsoft receives does not include it. Result: ExtraCode1 is saved blank, with no warning. At despatch, Mintsoft sends CreateShipment with "allocation_id":"". Veeqo returns {"status":"404","error":"Not Found"} (UnableToDespatch). Tracking does not reach Veeqo or the marketplaces (WooCommerce, eBay, Etsy). Resync Connect Action sends the same blank value, so it cannot recover the order. Current workaround: the client marks each affected order as shipped in Veeqo by hand with the Mintsoft tracking number, then we complete the Connect action in Mintsoft. This happens on multiple orders every day. We only find out after despatch, when the customer is already missing tracking and marketplace performance is affected. |
|
| Idea to resolve Problem | 1) Flag a blank Veeqo allocation ID at import as a Connect error, so affected orders can be caught before despatch. 2) When the allocation ID is blank at despatch or resync, re-fetch the order from Veeqo (GET /orders/{id}, optionally after PUT /orders/{id} to refresh Veeqo's cache) and use the returned allocation ID in CreateShipment. |