Subscribed 2019 - Current and Future State: Zuora Functional Architecture
1 like503 views
The document outlines Zuora's product architecture and related disclaimers, focusing on the importance of functional architecture to ensure comprehensive system coverage while developing new functionalities. It describes various components of their platform, including offer catalogs, order management, billing, and rating processes, emphasizing their centralized approach to enhance efficiency. Forward-looking statements regarding product features are provided, warning that actual results may differ due to uncertainties.
Subscribed 2019 - Current and Future State: Zuora Functional Architecture
- 5. SAFE HARBOR DISCLAIMER The following presentation is intended for information purposes only. The development, release, and timing of any features or functionality described for Zuora’s products remains at the sole discretion of Zuora and is subject to change. Any unreleased services or features referenced in this presentation are not currently available and may not be delivered on time or at all. Customers should make purchase decisions based upon product features that are currently available. In addition, statements in this presentation that refer to forecasts, future plans and expectations are forward-looking statements that involve risks, uncertainties, and assumptions, many of which involve factors or circumstances that are beyond our control. If any such uncertainties materialize, if any of the assumptions prove incorrect, or if priorities or resourcing changes, actual results could differ materially from such forward-looking statements. You are cautioned not to place undue reliance on these forward- looking statements as they reflect Zuora’s expectations as of the date of this presentation. In addition, actual results could differ materially from those expressed or implied in the forward-looking statements due to a number of factors, including but not limited to, risks detailed in our Annual Report on Form 10-K filed with the Securities and Exchange Commission (SEC) on April 18, 2019, as well as other documents that may be filed by us from time to time with the SEC. Copies of Annual Report on Form 10-K and other filings with the SEC may be obtained by visiting our Investor Relations website at investor.zuora.com or the SEC's website at www.sec.gov. Zuora assumes no obligation and does not intend to update these forward looking statements after the date of this presentation to conform these statements to actual results or to changes in our expectations. We encourage customers requiring specific functionality to file requests on our Zuora Community Ideas Board, even if a feature potentially addressing their needs has been previously discussed. These cases will be tracked by Zuora product management and every effort will be made to proactively communicate Zuora’s triage and status of incoming requests.
- 7. • ENSURE FUNCTIONAL COVERAGE ACROSS THE PLATFORM As new functionality is developed, otherareasof the systemcannotbe negatively impacted. • FOCUS ON DESIGN, NOT TECHNOLOGY OR INDUSTRY Prioritize whatneeds to be done over how it should be accomplished • PROVIDE A UNIFYING LAYER BETWEEN PRODUCT AND ENGINEERING With ourend to end view of the entire solution stack,we ensurethatnothing gets lostin translation between the productand engineering organizations. FUNCTIONAL ARCHITECTURE
- 10. Offer Catalog Arepresentation of‘How you sell it’.Itwill allow the reuse ofRatePlans and allow forbundling, price overrides, rules etc.Offersarecentralized into asingle location, which is usedtofeedeachofyour Ordering channels, whether itbeCPQ,aWebPortal, orthe Zuora UI Product Catalog BREAKING UP THE CATALOG TheProduct Catalog will contain non-pricing information related totheactual products. Itwill truly represent ‘Whatyou sell’. Clear delineation makes it easier todefine, createandroll outnewproducts and getthem intotesting without having todefine complicated pricing structures.
- 11. Order Management Onceand Order getsplaced, all ofthedownstream actions thatneed tooccur arehandled byOrder Management. Each Order line Itemcantrigger a separate workflow tocomplete tasks,activateservice, update statusetc. Order Entry ENTRY VS MANAGEMENT Functionally speaking, thepurpose ofOrder Entryisto getOrder Data intothe system.All Order Entry channels (Commerce, CPQ,WebPortal, UI)and the rules thatgovern themwill bedriven fromacentralized location.
- 12. Billing Billing will focuson Document Generation andTax calculation.All Document templates, presentation rules, lifecycle management and import/export functionality will bemaintained within theBilling module Rating & Charging RATE, CHARGE AND BILL Processes that calculate and produce debit/credit charges will be separated into adistinct module. Further submodules thatfocus on specific charge types (OneTime/Recurring, Usage, etc)canalsobe defined further optimizing the rating and charging process.
- 13. ZUORA CENTRAL A single platform to monetize and orchestrate subscription services MONETIZE • price & package • bill & collect payments • recognize revenue • measure results ORCHESTRATE • send communications • design acquisition, expansion, billing, dunning, & renewal flows • trigger provisioning • sync external data