When I create a new order via the API and specify the customer_id and deliver_to_id correctly for a wholesale customer, the order is created but the customer’s shipping address is deleted. This is unexpected - am I doing something wrong?
This is the API body I’m sending (minus the real IDs):
Just to add, I’ve tried the same call now with a “Retail” type customer and that works as expected - the order is created and the customer retains the shipping address, so this appears to be related to the “Wholesale” customer type.
This looks to be the correct request (and obviously not intended behaviour!) so I’m just in the process of investigating this and will attempt to recreate on my own account.
Can you send an email to helpme@veeqo.com and request Sam for API support and we can communicate on there.
I know this is an old issue… But we have come across the exact same issue…
Sending json (Pretty much the same fields in the payload)…
The order is created (and seems to have the correct Billing and Shipping address)
However the Retail Customer no longer has that Delivery address in its record.
Did you find a solution? And Ideally how to create an order so it appears in the Wholesale section of Veeqo given that its a customer with a customer_type of business.
Hello @DanHalpin, In this case this is related to a system limitation with the business customers in which in this specific case this type of behavior would be expected.
For this please create the deliver_to by sending the deliver_to_attributes instead of sending the customer shipping address as the deliver_to_id, here I’ll be leaving an example:
That works nicely (And the Order appears in the Wholesale section of Veeqo which is ideal.
However now there is a further issue…
As part of the payload I am sending
payment_attributes : {
‘payment_type’: ‘bank_transfer’,
‘reference_number’: ‘INVOICE’
}
But the order remains in a status of awaiting_payment.
I have also tried a payment_type of ‘paypal’ given most examples (including yours) seem to use this… But same result.
If I use the ID from the result and immediately try a PUT with a payload of just
Hey @DanHalpin, I am glad to hear that it worked, regarding the other issue, can you share the whole payload and maybe an ID of an order just to verify cause I used the next payload and it worked as expected: