## Summary To ensure the existing CustomerDot integration with Zuora does not break once Zuora Orders is enabled in a tenant, we will be enabling Orders Harmonization in Zuora first. Orders Harmonization is a feature that allows us to keep using existing Subscribe/Amend APIs and Subscription/Amendment Callouts. Per [Zuora Knowledge Center: Orders Harmonization - Notifications](https://knowledgecenter.zuora.com/Billing/Subscriptions/Orders/Orders_Harmonization/Orders_Harmonization#Notifications) > For any subscription creation or amendment created through Subscribe and Amend APIs, the existing Zuora Billing notifications configured in your tenant will continue to work. > > However, since for every subscription creation and amendment, if you configure Orders notifications then both order related notifications and amendment notifications will be triggered. Zuora recommends you to configure only the Orders notifications and turn off the existing Amendment related notifications if you do not want duplicate notifications. ## Project Plan Overview can be found here - [EntApps Project Plan and Timing spreadsheet](https://docs.google.com/spreadsheets/d/17Z2ouc32kTcx58WjHMmnsI7ddhdFTprT4iCewbQpczw/edit#gid=2123632446) Timeline for ~"group::license" is detailed here https://gitlab.com/groups/gitlab-org/-/epics/6641#timeline ## Resources - [Orders Harmonization Summary](https://gitlab.com/gitlab-com/business-ops/enterprise-apps/intake/-/issues/158) ## Knowledge Sharing Purchase Backend engineers should review [Orders Harmonization Summary](https://gitlab.com/gitlab-com/business-ops/enterprise-apps/intake/-/issues/158) prior to starting work on this epic. It will provide the necessary context to help plan and execute on Zuora Orders implementation. - [ ] @shreyasagarwal - [ ] @rcobb - [ ] @qzhaogitlab - [ ] @jhyson - [ ] @chris_baus (adding EM for full coverage, just in case) ## Related - [License Group] Order Harmonization https://gitlab.com/groups/gitlab-org/-/epics/6641