Requirements Coverage Tracker

Ability for customer to search for eBooks in the catalog using whole or partial match on Title, Author, ISBN, Topics, keywords, etc.

Native search (Elasticsearch-backed) covers title/author/keyword; ISBN and topic need custom field/property mapping.

Ability to sort search results as preferred (e.g. alphabetically, by pub date, author, subject area (e.g. Hematopathology), etc.)

Standard sort options are native; a few custom facets (e.g. subject area) need config.

Ability for external search engines (e.g. Google, Yahoo, Bing, Duck Duck Go, etc.) to read your website? Describe what functionality has been built into your pages to provide this capability.

Server-rendered storefront is inherently crawlable.

Ability to tag pages, products, and content (on webpage, within product description, meta tags, etc.) with crawlable key words (keyword optimization to attract searchers & engines)?

SEO/meta tag fields are native product and CMS attributes.

Ability to create and implement a link to a pre-defined search result (e.g. when user clicks on the link on client website or marketing/promotional communications, it will take them to the pre-defined search result in the ebook store that contains only products for a specific program or topic)?

Achievable via saved category/landing pages and URL parameters, but a true "pre-baked search result" deep link needs custom routing.

What search engine for your search functionality?

Informational/vendor question, not a build requirement.

Ability to define/group ebooks in the Catalog by different topics, diciplines, etc?

Categories and properties handle topic/discipline grouping.

Ability for ebook author information to be prominently displayed / readily visible.

Author fields as custom product attributes, surfaced via template.

Ability for the product to be included in multiple catalog groupings?

Products can belong to multiple categories natively.

Ability to provide sample pages, partial content of eBook to user before purchase (i.e. “View Inside” or download).

"View inside"/sample-page preview requires rendering ebook content, which sits outside Shopware and needs a reading/preview integration.

Multilingual support for titles, descriptions, custom fields.

Shopware supports multi-language sales channels for titles/descriptions/custom fields.

Ability for user to expand/collapse sections within the product description (e.g. short vs long description)

Expand/collapse is front-end template/theme work.

Ability for the appropriate price to be displayed based on the user's profile (e.g. Member vs Non-Member pricing)

Customer-group/rule-based pricing is native; tying it to CAP membership status depends on the SSO/membership integration.

Ability to make changes to bundles - what's included, pricing/discounts, date it applies.

Editing bundle contents, pricing, and effective dates is native.

Ability to bundle multiple eBooks and allow user to add to cart at once. Bundle print with eBook or multiple ebooks together.

Bundle/cross-sell functionality is native (Commercial edition for advanced bundling).

Ability to bundle an eBook with a print book both on print side (CAP) and on the eBook side.

Mixing a physical (print) and digital (ebook) item in one bundle needs custom fulfillment logic across systems.

Ability to diverge/transfer ebooks, order history, annotations, etc, from one user account to another user account? (eg, if user created duplicate accounts)

Merging/transferring a user’s order history, annotations, etc. across accounts is not a native capability.

Ability for administrator to view user account/profile details to support customer service issues / inquiries?

Admin can view customer account/profile details out of the box.

Ability for administrator to view order history, downloads, reading time, and email notifications sent to the customer?

Order history is native; download counts, reading time, and notification logs live outside Shopware (reading platform) and need integration.

Ability for administrator to reset the number of downloads, IP ranges or concurrent users for a specific product on a customer's account

Resetting download counts, IP ranges, or concurrent-user limits is DRM/entitlement functionality outside Shopware.

Availability of data elements to accommodate user data from client systems (e.g. Oracle EBS, Enterworks, D365)?

Custom fields support this; populating them from Oracle EBS/Enterworks/D365 needs middleware/API integration.

Ability for user to view a list of all products they have purchased

"My purchases" list is native via order history.

Ability for administrator to emulate a specific customer's experience to support customer issues / inquiries (e.g. shopping, reading, etc)?

Session emulation/impersonation of a customer is not native; needs custom admin tooling.

Ability to create and manage author profiles independent of their publications, eg, institional affiliation, credentials, biographical note.

Author-as-entity profiles independent of a product require a custom entity/content type beyond standard product data.

Ability to enter, store, and update book metadata: author, title, edition, ISBN, publication date, begin sales dates, release date, […more]

Book metadata fields are native custom product attributes.

Ability to support high resolution images, tables, and charts EITHER within the ebook file itself along with zoom in/out functionality OR host such images on an external site for the user to access outside the reading app via link or QR code.

High-res product imagery/zoom is native; zoom/pan inside the ebook file itself is reading-app functionality (custom/integration).

Ability to support hyphens, apostrophes, roman numerals, suffixes (e.g. Sr.) and credentials (e.g. M.D.) for attribute fields/name fields?

Standard text field support for special characters.

Ability to deactivate an eBook for future sale, but still allow those that have already purchased it to maintain access/continue to read or use it

Deactivating a SKU from sale is native; ensuring existing owners retain access requires entitlement logic tied to the reading/fulfillment layer.

Ability to modify configuration after a product is released? Describe which components can or cannot be modified and include impacts of those modifications to the user/reader and admin functions such as reporting.

Editing product configuration after release is native.

Ability to publish a product for automatic release on a defined release date?

Scheduled/active-from release dates are native.

Ability for admin to change pricing on product as of specific date.

Date-based price changes are native via price rules.

Ability to define member vs non-member pricing for B2C customers (Would require integration with CAP SSO as prerequisite)

Native pricing engine; requires the CAP SSO/membership integration to key off member status.

Ability to provide auto-notification when an old edition is sunsetted and a new one is available to trigger customer to purchase the new edition

Requires linking edition status to individual entitlements and triggering notifications — an entitlement/reading-platform capability, not core commerce.

Average amount of time before a newly published ebook is visible to the customers.

Informational vendor question.

Ability to upload and store eBooks on a secure server for authorized user to download/access. Describe how eBook content is added to and stored on the vendor system.

Secure ebook file storage/delivery sits with a dedicated content/DRM platform, not Shopware.

Ability for user to view titles they are authorized to access online (whether via purchase or subscription), with "download" and "read online" links for each title. (My Library or Order History page)

Order history is native; "download"/"read online" links depend entirely on the reading/DRM platform integration.

Ability to grant access to ebooks purchased on previous CAP eBooks platform (Impelsys) to authorized users.

Migrating and granting access to legacy (Impelsys) entitlements is a one-time custom migration/integration effort.

Ability to automatically push out major corrections or updates to a user who purchased a previous version of the eBook.

Pushing corrected/updated files to existing owners is a reading-platform capability.

Ability for user to download and read ebook on multiple platforms, eg: Android, iOS, MacOS, Windows, Kindle, Kobo…[others]

Multi-platform download/DRM (Kindle, Kobo, iOS, etc.) is entirely outside Shopware’s scope — owned by the reading/DRM vendor.

Ability to allow user to read book offline after purchase

Offline reading is a reading-app capability.

Ability to identify readers associated with an institution that purchased the product on a client eCommerce platform? Describe the different ways you have done this with other clients?

Shopware B2B/customer-group features can identify institutional accounts; linking that to reading access needs integration.

Ability to call a vendor webservice to provide user and item details for an order to enable download of the ebook. If vendor does not have a webservice for order integration, ability to call a similar CAP webservice to allow authorized user to download title.

Shopware’s API-first architecture (Store/Admin API) supports building the webhook, but the endpoint and DRM-side logic are custom integration work.

Ability to sell a chapter versus the entire book (also, subscription to chapters or book for a time-period verus perpetuity)

Chapter-level sale/entitlement granularity is not standard eCommerce SKU logic.

If reading app is available, ability for user to access via various apps same ebook multiple times for use on different platforms (eg, user may download ebook for Kindle and for iOS.)

Multi-app access to one entitlement is governed by the DRM/reading platform.

Ability to report/track which customer was provided a specific access code.

Promotion/discount code usage is tracked natively; tying redemption to a specific ebook access grant needs integration.

If a reader app is available, ability to support new versions or formats of epub in previously purchased ebooks while maintaining reader's annotations, highlights, and notes.

Preserving annotations across epub format/version changes is a reading-app capability.

Ability to generate/extract access reports (e.g. users accessing materials in a subscription or users accessing ebooks, # of access codes redeemed, etc) Describe your end user reporting capabilities and include report examples.

Order/promotion reporting is native; access-code redemption and subscription-access reporting need integration with the reading platform.

Availability of analytics functionality pertaining to the reader experience (i.e. % of books completed, time spent reading in different apps/platforms, etc)?

Reading-behavior analytics (% completed, time in app) come from the reading platform, not Shopware.

Ability to extract order data (or run a report of all orders) placed during a specific time period. Describe your eCommerce/sales order reporting capabilities and include report examples.

Order data extraction by date range is native.

Ability to generate reports on various sales metrics, including how many books sold, how many of each book sold, subscriptions, etc.

Sales metric reporting is native.

Ability to filter standard reports by various filters (e.g. date, product, user, etc)

Standard report filtering is native.

Ability to track free-trial data (customer, expired, etc)

Needs a custom field/flag plus reporting logic for free-trial status.

Ability to add/include custom fields in reports and as report parameters

Custom fields can be added to reports; more advanced custom reporting benefits from a BI layer.

Ability for administrator to create custom reports without need for coding nor vendor engagement

Admin reporting exists natively but no-code ad-hoc report building is limited; typically needs a BI tool (e.g., Tableau) layered on top.

Ability to export report data in the following data formats: xls, txt, xml, csv, pdf? List additional available formats.

CSV/XML export is native; XLS/TXT/PDF formats typically need custom export formatting.

Ability to send the report via email directly from the system?

Flow Builder can automate emailing reports, but this needs configuration/custom flow setup.

Ability to integrate with a BI analytics tool (e.g. Tableau)? List methods/options.

BI tool integration (e.g., Tableau) is done via API/DB connection — an integration effort, not native.

Ability to schedule a report to run per a predefined date/time and frequency (e.g. one time, weekly, monthly, etc.)

Scheduled report runs need Flow Builder automation or a custom job.

Ability to define data parameters for a report based on all available fields including standard & custom fields (e.g. program, course type, course name including wildcard functionality, date range, etc)

Parameterized reporting across custom+standard fields typically needs a BI layer.

Ability for version control on reports to determine what was changed, by who, and when

Report-level version control (who changed what, when) is not a native commerce-platform feature.

Ability for client admin to add additional email addresses to send reports to.

Achievable via Flow Builder configuration for additional recipients.

Ability to generate native and/or custom reports real-time

Admin dashboards are real-time.

If report generation is not available real-time, describe refresh schedule (e.g. nightly, 24hr, etc)?

Informational vendor question.

Ability to expose custom fields in the analytics tool you use

Exposing custom fields to an external analytics tool is an integration task.

Provide a list of the types of native analytics functionality/formats available (e.g. dashboards, aggregate/summary reporting, graphics, etc). Describe which types of native analytics functionality is available for the admin and/or for the user and in what format (e.g. by activity, by learner)?

Informational vendor question.

Availability of a custom report development tool or wizard? Provide what tool you are using.

Informational vendor question.

Upon successful purchase, ability to provide customer notification with order confirmation (for ebook download/access instructions)

Order confirmation emails are native (transactional emails / Flow Builder).

Ability for admin to turn off/disable product ratings and reviews either on specific products or globally.

Enabling/disabling reviews per product or globally is native.

Ability for administrator to monitor reviews for inappropriate messaging.

Admin review moderation queue is native.

Ability to highlight new releases, limited time offers on certain books, etc in the catalog. Describe available options in the tool to do this, who controls these settings (eg, admin configuration, algorithms), and who has access to them.

New-release/promo merchandising via CMS and promotions is native.

Ability to recommend content based on prior purchase or completion of another ebook.

Basic cross-sell/upsell is native; true purchase-history-based recommendations usually need a plugin or AI/recommendation service.

Ability for users to provide product ratings and reviews.

Product ratings and reviews are a native Shopware feature.

Ability for individual user to purchase eBook online

Standard checkout purchase flow is native.

Ability for individual user to purchase multiple eBook titles in one transaction.

Multi-item cart/checkout is native.

Ability to apply discount code on cart - percentage or dollar amount

Percentage/fixed discount codes are native (promotions).

Ability to update quantity of a single title on cart (buy more than one copy at a time)

Quantity field is native; multi-license logic for a single digital SKU typically needs custom entitlement handling.

Ability to support credit card and ACH/eCheck.

Supported via standard payment provider integrations (credit card and ACH/eCheck, e.g. via Stripe/PayPal).

Ability to define a timeframe for temporary product discounts (e.g. black Friday sale, end of year sale, etc.).

Time-boxed promotions/discounts are native.

Ability to limit number of times a discount code can be used (assuming discount codes are included).

Usage-limited discount codes are native.

Gift purchases of eBooks (eg, one person pays, another gets the download.)

No native "buy for someone else" digital gifting flow; needs custom checkout/fulfillment logic.

Ability to provide discounts on bulk purchases (eg, above a certain quantity, give [x] discount. Purchaser may be an individual or an organization.)

Quantity-based/bulk pricing rules are native.

Ability to report/track which customer redeemed a specific coupon code.

Coupon redemption tracking per customer is native.

Ability to award "gift card" aka account credit options to individual customers and track usage.

Gift card / account credit is a native (or Commercial-tier) feature.

What payment processers do you support out of the box? Which ones can you integrate with, and via what method? Does client need to have their own payment processor account, or does vendor manage this?

Informational vendor question.

Describe your capabilities surrounding refunds and returns on digital products.

Informational vendor question.

Ability for an institution to purchase an eBook subscription (single book or a prefefind collection of books) for a period of time.

Institutional/subscription purchasing needs the Subscriptions feature (Commercial) plus B2B company-account logic; not fully out of the box.

Ability to bill institution for subscription on a yearly basis

Recurring/annual billing is supported via the Subscriptions capability but needs configuration.

Ability to establish pricing tiers per collection based on number of users within subscribing organization

Seat-count-based tiered pricing per collection is not standard eCommerce pricing logic.

Ability to manage subscriptions; check out/in, limit # of days user can have checked out, etc based on subscription terms.

Check-in/check-out lending mechanics with day limits are a library/DRM feature, not commerce functionality.

Ability to grant access to subscribed ebooks to users within institution for the period of the subcription.

Granting institutional users access for a term needs integration between Shopware entitlements and the reading platform/identity system.

Ability for authorized user within a subscribing institution to download and read eBooks included in the subscription on any supported device(s) for the period of the subscription.

Multi-platform download/read within a subscription window is owned by the reading/DRM platform.

Ability to limit number of concurrent users that can access an ebook included in a subscription.

Concurrent-user limiting per title is a DRM/lending feature.

Ability to set an expiration date for access to an ebook or collection of ebooks that is included in a subscription. All access to ebooks will be cut off upon expiration if the subscription is not renewed.

Subscription expiration is native to billing; cutting off ebook access at expiration requires the reading-platform integration.

Ability to notify customer of upcoming subscription expriation?

Expiration reminder emails can be automated via Flow Builder with the right trigger data.

Ability to grant institution access to subscription materials for a predefined limited-time free trial.

Time-boxed free trial access needs a custom entitlement rule tied to subscription setup.

Ability for admin to set up collections of eBooks (aka product bundle) from CAP catalogue for institutional subscriptions.

Admin-curated collections/bundles are native.

Highlights, annotations and bookmarks are unique to the individual user for book that is part of an institutional subscription.

Per-user annotations/bookmarks within a shared institutional subscription are a reading-app capability.

Ability to use CAP branding, stylesheets, and color schemes on the retail website.

Theming/branding on the storefront is native (Shopware theme system).

Ability to use CAP branding, stylesheets, and color schemes on customer communications (email).

Branded transactional emails are native/configurable.

Ability for admin to customize home/landing page layout.

CMS page builder supports custom home/landing layouts.

Ability for admin to customize user interface header/footer to meet client standards?

Header/footer customization is native via CMS/theme.

Ability for admin to change/customize standard text and/or labels on the interface (e.g. button names, section headers on the page via configuration options) to align with client's taxonomy / vocabulary? Provide which elements on the UI are configurable vs require custom code development.

Labels/text are configurable via snippets/translations.

Ability to apply white label branding for your clients?

Multi-sales-channel architecture supports white-label branding per channel.

Ability to replicate the components outlined in the CAP style guide links provided below on your site. Describe and show how to apply these customizations in your software via video or screen shots. CAP Digital Style Kit https://capatholo.gy/cap-digital-style-kit Tabs https://www.cap.org/style-guide/tabs Icons https://www.cap.org/style-guide/shortcodes Refer to Font Awesome Icons section NOTE: Icons should be rendered in CAP Blue color (HEX #009BBF), unless they denote failure (red), success (green), or warning (orange). For red, green and orange colors refer to Colors link listed above.

Achievable through Shopware’s theme/template system, but matching CAP’s specific style-guide components (tabs, icon set, colors) is custom front-end development.

Ability to use CAP branding, stylesheets, and color schemes on the reading app.

The reading app is outside Shopware, so its branding is controlled by the reading/DRM vendor, not Shopware.

Ability for admin to customize dropdowns / menus.

Menu/dropdown customization is native via theme/CMS.

Ability for admin to customize login and logout screen/menus to follow client standards for consistency with their websites.

Login/logout screen customization is native.

Ability to remove/hide the platform vendor logo on the interface?

Removing vendor branding is a standard theming option.

Ability to add custom fields to the user interface?

Custom fields can be surfaced on the storefront via template changes.

Ability to give customer login options (e.g. SSO Client Login vs local account)?

Local account login is native; SSO login option requires an SSO integration (plugin or custom OIDC/SAML connector).

Ability to specify/force login method (e.g. SSO Client Login or Local Login) not giving the customer an option.

Forcing a single login method is configuration once SSO integration exists.

Ability to display user name in main banner upon login per client style specifications?

Displaying the logged-in user’s name is native/template-level.

Ability for user to read purchased eBook via online web reading app.

An in-browser ebook reading app is not part of Shopware and requires a dedicated reader integration.

Ability to provide certification to user that any apps included in solution are virus-free (eBook App Vetting Document)

Vendor attestation of the reading app, not a Shopware build item.

Ability to maintain reader's annotations, notes, and highlights when platform is upgraded

Preserving annotations across a platform upgrade is a reading-app/data-migration concern.

Ability to maintain reader's annotations, notes, progress, and highlights across different reading platforms.

Cross-platform annotation sync is a reading-app capability.

Ability for user to view a list of all ebooks and percent they've read

Reading-progress tracking (% read) comes from the reading app, not the storefront.

Is your platform WCAG-compliant? Please provide accessibility conformance report (ACR) based on VPAT.

An accessible, WCAG-conformant storefront is achievable with Shopware’s theming system but requires dedicated accessibility development and testing — not automatic.

Availability of loading indicator and/or message when something is taking longer than expected.

Loading indicators are front-end/theme implementation.

Multilingual support for the user interface.

Multi-language storefront is native.

Ability for learner to select preferred language and/or set preferred language in their profile for UI to reference.

Customer-selectable/stored language preference is native.

Ability to link to a chapter or related content to another CAP book, if needed.

Related-product links are native; deep-linking into another book’s specific chapter/content is a reading-app feature.

Ability to display the appropriate translated version of an ebook.

Language-variant products are native; serving the correct translated ebook file is a content/fulfillment concern.

Describe the standard user navigation experience in your product (screen shots or video clip of demo are welcome). Interest areas include profile page, dashboard, learning content, overall flow of registration through generation of course certificate.

Informational — request for vendor demo.

How is the user experience optimized for a mobile experience

Informational — request for vendor description.

Describe system error messages presented to end user (scenarios/types, wording, etc)?

Informational — request for vendor description.

How are accounts identified as institution vs individual? How is content access attributed based on institutional affiliation vs individual purchase?

Informational — request for vendor description.

How is linked content (e.g. images, URLs in ebook text, etc) optimized for mobile devices (tablets, phones)? Please provide demo recording.

Informational — request for vendor demo.

Benchmark response time to render pages?

Informational/benchmark request.

Average response time under 3 seconds.

Sub-3-second response times are achievable with proper Shopware hosting/caching configuration.

Availability of system monitoring tools/reporting?

System/infrastructure monitoring is available via hosting tooling.

Ability to provide a great user experience including a fast load speed and compelling UX? Provide average amount of time to return/load search results.

Informational vendor question.

Timing & Frequency of vendor software upgrades / scheduled outage and length of outage

Informational vendor question.

Describe your system timeout rules and processes.

Informational vendor question.

Does your platform work on any device (mobile responsive)? Please provide demo recording for desktop and mobile.

Shopware’s storefront is responsive by default.

Ability for platform to be supported across multiple browsers for current version and 2 back (e.g. Chrome, Firefox, Edge, Safari, Samsung)

Standard modern-browser support is native.

Ability/requirements for whitelisting IP Addresses (e.g. net IP range, etc).

IP whitelisting is a hosting/infrastructure-level configuration, not a core Shopware feature.

Ability to handle dynamic IP address ranges.

Dynamic IP range handling is an infrastructure-level configuration.

Ability to use client-defined domain name

Custom domain mapping is native/standard hosting configuration.

Ability to provide release notes for vendor software updates

Informational vendor question.

Access to test environment for CAP staff and CAP staff ability to test new functionality/features before releasing to end users

Informational — environment/process question.

Availability of non-production environment(s) that can connect to corresponding client non-prod environment(s) (e.g. UAT, DEV)?

Informational — environment/process question.

Are separate production and non-production environment(s)/tenant(s) available for each client?

Informational — environment/process question.

If separate non-production environments are available, describe any data refresh processes that occur in those environments. Please include frequency of each refresh process.

Informational — process question.

Describe your release management / migration process including frequency of updates in each environment (non-prod & prod).

Informational — process question.

Describe your unit, user and regression testing process for client specific and global releases.

Informational — process question.

Describe communications related to updates, releases, and fixes applied in each environment.

Informational — process question.

Describe your process for client verification of code and configuration updates, bug tracking and hot fixes.

Informational — process question.

What is your Header size limit?

Informational vendor question.

Describe the technical infrastructure and architecture on which your product resides. Provide a high level diagram of the product technology stack for both the UI and backend services.

Informational vendor question.

Describe measures to monitor and prevent bot traffic and spam account creation.

Informational vendor question.

Describe how data is stored and in what form.

Informational vendor question.

Ability to allow customer to renew a subscription

Subscription renewal flow depends on the Subscriptions capability/configuration described above.

Ability to accommodate custom data elements (including limitations to number of custom data elements)?

Custom fields/attributes are a core, extensible Shopware capability.

Ability to integrate with CAP's single sign on via OneLogin (OIDC).

OIDC SSO integration with OneLogin requires a connector (plugin or custom development), not out of the box.

Ability to interface with client ERP system (e.g. Financials, etc)? List of ERP systems/modules you have integrated with and integration method used (API, etc.)

ERP integration (D365, etc.) is done via API/middleware (e.g., Jitterbit), consistent with CAP’s existing integration pattern — not native.

Describe the processes/options available to notify customer subscription is ending with option to renew, and if selected, process for generating/triggering order creation on the eCommerce platform (internally vs externally hosted).

Informational vendor question.

Describe your interoperability capabilities to swap out eCommerce systems. Must the client solely use your eCommerce system or could they use a different eCommerce system (e.g. client eCommerce site)? Describe activities and effort involved to switch eCommerce systems?

Informational vendor question about platform flexibility.

Ability to integrate with third party eCommerce platforms (i.e. Shopify, Shopware, etc). Describe any OOB connections you have. Describe any eCommerce preferred vendors or third party vendors you have integrated with.

Informational vendor question.

Describe your SSO initiation capabilities, which do you support and which is the preferred option?

Informational vendor question.

Do the API's you provide follow industry standards such as REST, etc.? Describe.

Informational vendor question.

Ability to receive and apply full and/or change files for user and product data?

Bulk import/export of user and product data is supported via Admin API/import-export profiles; a full/change-file process needs configuration.

Ability to migrate data from client's legacy ebook sales platform into your environment? Provide brief description about types of data that can be migrated, method, limitations, format, or other key items to note. (user data, product data, order history, reading history, annotations, etc)

Migrating historical data (orders, reading history, annotations, entitlements) from the legacy platform is a one-time custom migration project regardless of target platform.

Ability to accept various data file formats for user and product data, delimited or fixed? Please list data file formats that can be used in migrating/importing data to the system.

Standard delimited formats (CSV) are native; other formats need custom import mapping.