@jib87 

> Is it what we are expecting?

pSM] Yes, when you delete data you have quite some problems with data consistency. For instance, orders are left without customer record. You won’t see history of the orders and so on.

Furthermore, I would encourage to not delete customers in Acumatica too. Better to make then inactive.

> Do we have some indication in BC if a Customer was deleted from it's Acu source?

pSM] As far as I know, BigCommerce does not have Active/Inactive for customers.

> Can we forbid them to log-in and place order in BC? 

As @smarenich said, it’s not easy to implement a deletion process in the integrated solution. However, I think it could be achieved.

First, BigCommerce doesn’t have data integrity concerns. If you delete a customer who has orders, those orders become Guest Customer orders.

Second, there is an option to use https://developer.bigcommerce.com/api-reference/82f91b58d0c98-get-all-orders before sending the DELETE request. That is, when a customer is deleted in Acumatica, before deleting it in BigCommerce, query BigCommerce, if there are any orders for this customer. And if there are none, delete the record. Otherwise, throw an error.

The only reason I’m expanding on this here, is that it might really be beneficial in situations when a website was maliciously injected with multiple new customer records, or as the author said, when you genuinely need to clean up your data.

Thank you!

Thank you @smarenich and @Yuri Karpenko. I agree. Appreciate you expanding these scenarios, and providing tips. Great help!