Hi!
We have discovered a few orders with state = null that, as expected, are not showing in the list when pulling data from https://api.clover.com/v3/merchants/{mId}/orders endpoint.
However, I wonder if it's possible to update the state on the front-end in clover.com portal?
Or is API call is the only option?
I'm not aware how those orders were created and why their state is null but for sure they were NOT created through the API.
Thanks
The merchant can update the order state by accessing the order and saving, adding items, or adding a payment. You can also do an update order API and update it or make a payments. Please make sure the orders are syncing.
Thanks for the answer!
> The merchant can update the order state by accessing the order and saving, adding items, or adding a payment.
I checked one of the orders with null state in Clover front-end - and it appears to have subitems and payment. So basically there is nothing to edit in terms of subitems or payment.
In that case, what could be changed to trigger state update from null to open or locked (I'm not sure what's the expected state in that case, I guess locked)?
Thanks for the answer!
> The merchant can update the order state by accessing the order and saving, adding items, or adding a payment.
I checked one of the orders with null state in Clover front-end - and it appears to have subitems and payment. So basically there is nothing to edit in terms of subitems or payment.
In that case, what could be changed to trigger state update from null to open or locked (I'm not sure what's the expected state in that case, I guess locked)? 
Can you email developer-relations@devrel.clover.com with your developer information and the merchant ID in question for them to look further at the logs. normally if orders are not syncing properly, the state will be null. When you create the order you should be passing the state as "open"
7 People are following this question.
