My apologies to everyone for re-posting my entry again since I was late to update the previous one. It is not for taking more attention, apologies once again.
Despite a long time since my first input in this thread which should have been already enough to design the required integration schema, I was just able to prepare only the one below and just decided to share it publicly with its all immatureness to ask you and the Square expert team and also the community on the forum first if it includes anything opposite to the Square’s mentality (working mindset), that might be something not possible for it to do.
And in order to make it clear if such a scenario (in the schema) is convenient (appropriate) for Square (in case I might miss some tricky/key/main points while exploring the “Square” through my own personal efforts), here are my first initial questions to be a start point:
1-) [The first stage in the schema]
Rather than converting the text-based “order->fulfillments->shipment_details->recipient->address” data into coordinates, we humbly consider working with the coordinates data taken directly from the end-user himself.
But in this method, we will probably need the information whether or not the customer uses his own address (which already recorded/exists in his “customer card” in the Square PoS) as the recipient address within the related order. Might there be any way to check it? Perhaps by using/adding some additional custom fields/attributes etc. if the standard (original) version of Square PoS doesn’t provide?
2-) [The third stage in the schema]
It is not a mandatory thing but, through “webhooks”, can Square notify us for new orders based on some additional conditions/filters? For example, just for those whose, “fulfilment” types are “SHIPMENT”.
3-) [Again the third stage in the schema]
The vice versa, - not a mandatory thing again but -, through “Orders API”, could we query Square orders based on some additional conditions/filters? For example, just for those whose, “fulfilment” types are “SHIPMENT”.
4-) // Not a question - Just aloud thinking //
If neither “2” nor “3” is possible, then we can already filter (sort) orders at our side. “2” and “3” are just in case, some Square clients might not want to share their all orders with us, however, as far as I guess, the data within the Orders API includes almost nothing in terms of “the privacy of the personal data” unless we don’t query anything with “customer ID”.
5-) [Still the third stage in the schema]
If a Square client (business) request not to use their all customers data through this integration scenario and want to restrict it for just the users benefiting (using) our solution (Internodz), can we use the “customer group” property/attribute for that purpose while querying/inserting or updating the customers through the Customers API?
6-) [The last thing about the third stage in the schema]
Might it be possible to sub-categorize/classify “SHIPMENT” orders more in detail using/adding by some additional custom fields/attributes/properties etc. as listed below?
- One group as “to be delivered by third-party (outsourced) logistics partners (couriers)”
- The other group as “to be delivered by the business’ own deliverers (employees)”
Would be so grateful for any kind of reply, comment, review and help from anyone.
Thanks so much.
The schema is also available at https://docs.google.com/drawings/d/1RjGK5B76oOmt6w8tAwAUBet1QnWKoeniUZ93QpFULqo/edit?usp=sharing