Created orders do not appear in the merchant's Square dashboard

allendav commented 5 years ago

During testing of v2, in the Square dashboard ( https://squareup.com/dashboard/orders/overview?orderGroups=%5B1%2C4%5D ), I noticed I did not see orders I’ve created (and payments captured) in testing.

According to @matthewlent of Square:

If you want the orders to appear there, you have to add a Fulfillment object - see https://developer.squareup.com/reference/square/objects/OrderFulfillment/

You would need to:

Create the Fulfillment when the order is created

Send updates to Square when Order changes within Woo

Receive updates from Square when Order changes within Square (webhook)

allendav commented 5 years ago

Note: At least they appear under Transactions (props @dechov )

https://squareup.com/dashboard/sales/transactions

bmccotter commented 5 years ago

@bekarice @ChaseWiseman any insight as to why this wasn't included in the original release?

bekarice commented 5 years ago

The fulfillments API wasn’t usable in building v2 so it wasn’t included in scope of work as a result. Order fulfillments in Square can't line up to Woo without the order updates API, which is now in beta and was not available during the v2 build (hence why Send updates to Square when Order changes within Woo as also not possible). With that API endpoint which is now available, if the transaction is successful, you can send a fulfillment to it in Square now as an update.

Since we needed to create a Square order before we could take the payment for it (transactions need to be associated with an order), we couldn’t reasonably create a fulfillment for that order at the same time -- the payment can fail and it might not be a real “order”. It is a transaction, though, which is why you see it in the transactions dashboard.
The shipping method in Woo could also change between failure and success, and you’d have no way to update it in Square in v2 (wasn't possible without the new beta updates API).
Square also supports only one fulfillment per order, while Woo supports multiple shipments per order by default, so these paradigms may not line up.

I’d recommend more user research around what folks expect to see for these fulfillments before proceeding: do they just want the orders to show up in that list in Square (so a fulfillment would be pushed up for any Woo order immediately), or do they expect to be able to manage a fulfillment and order within Square and push those changes to Woo (which would require additional polling infrastructure for Square orders)? Do they expect the order in Square to match the paid / shipped states within Woo? How would a fulfillment be managed in Woo without the concept of fulfillment status / shipment status?

Just to clarify one point: webhook listeners for Square were proposed as a change order and rejected; Square webhooks don't let you register a delivery URL, that URL can only be specified at the OAuth application level. So this means that any Woo store would need to register webhooks via a single proxy (probably connect.woocommerce.com), then Square would send the webhooks to this proxy, which is now responsible for relaying them to individual sites based on the site ID. Given that infrastructure, I don't think webhook listeners would be appropriate until Square adds delivery URL registry for webhooks.