Thank you for your response, Justin.
The integration is meant to be a one-way flow of data from our fulfillment house into Keap. Orders flow into the fulfillment house, are shipped from there, and customer updates occur there as well. It is desired that we “update the picture in Keap” with this same data. Our plan is to wake up once a day, identify records whose statuses have changed, and push them up to Keap via API. We plan to do this by first searching in Keap for a customer, grabbing the relevant data (which we believe is contact information, product information, order information, and order product information. Then we plan to identify what needs to change based on what we identified in our system, and then push up the necessary API calls to make that happen.
This will involve add/update to contacts, add/update to items, add/update to orders, and add/update to order products.
It is our understanding that there would not be a need to process payments on the Keap side of things. We would want the order to bear the best replica we could muster of how that order appears in our system. Payment information is probably not critical, but we have that available if it can be uploaded. Other things would be order status, order shipments, possibly tracking information - just whatever is relevant (and we need to identify that yet.)
Orders consist of “product” and “subscription”, both, but I think it may be safe to say we would treat subscriptions as a “product” in your system - it is a purchase made here but not necessarily needing to be tracked on your side. One thing that might be nice would be to identify an order item as a subscription and simply update status and expiration information.
We would not want the complexity of a two-way sync.
I hope I’ve answered the excellent questions you posed. Again, thank you very much.