diff --git a/help/implementation-playbook/architecture/extensibility-strategy.md b/help/implementation-playbook/architecture/extensibility-strategy.md index b66199921..85fb0968b 100644 --- a/help/implementation-playbook/architecture/extensibility-strategy.md +++ b/help/implementation-playbook/architecture/extensibility-strategy.md @@ -1,6 +1,6 @@ --- title: Adobe Commerce Extensibility Strategy -description: Learn how Adobe Commerce's exttensibility model empowers you to customize your implementation. +description: Learn how Adobe Commerce's extensibility model empowers you to customize your implementation. exl-id: fac4630d-8a41-40dc-899a-01eabceaa61e --- # Extensibility strategy diff --git a/help/implementation-playbook/architecture/global-reference.md b/help/implementation-playbook/architecture/global-reference.md index 815b80b8f..c42a801ec 100644 --- a/help/implementation-playbook/architecture/global-reference.md +++ b/help/implementation-playbook/architecture/global-reference.md @@ -1,6 +1,6 @@ --- title: Adobe Commerce Global Reference Architecture -description: Get the most our of your Adobe Commerce implementaiton by leveraging a global reference architecture. +description: Get the most our of your Adobe Commerce implementation by leveraging a global reference architecture. exl-id: a18529a3-da9b-4e1b-8048-0a906e65c740 --- # Global Reference Architecture (GRA) diff --git a/help/implementation-playbook/architecture/headless/adobe-commerce.md b/help/implementation-playbook/architecture/headless/adobe-commerce.md index d05338966..546910f10 100644 --- a/help/implementation-playbook/architecture/headless/adobe-commerce.md +++ b/help/implementation-playbook/architecture/headless/adobe-commerce.md @@ -5,7 +5,7 @@ exl-id: eac9d5b1-4917-4d2a-a8af-7f85c825fa0d --- # Headless Adobe Commerce Architecture -The benefit of Adobe Commerce’s architecture is that it’s not an all-or-nothing proposition and a merchant can find the right mix of solutions for their business. They can build a PWA Studio-powered PWA for their primary site experience or use Adobe Experience Manaager as the layer in complex customer journeys, all while building out a custom frontend to experiment with new touchpoints. No other platform can match the time to market benefits and the flexibility that Adobe Commerce offers with its headless architecture. +The benefit of Adobe Commerce’s architecture is that it’s not an all-or-nothing proposition and a merchant can find the right mix of solutions for their business. They can build a PWA Studio-powered PWA for their primary site experience or use Adobe Experience Manager as the layer in complex customer journeys, all while building out a custom frontend to experiment with new touchpoints. No other platform can match the time to market benefits and the flexibility that Adobe Commerce offers with its headless architecture. ![Diagram showing a headless Adobe Commerce storefront architecture](../../../assets/playbooks/headless-storefront-architecture.svg) @@ -25,7 +25,7 @@ The first is a progressive web application built with PWA Studio. Part of this i Most merchants understand the direction that the industry is heading toward with regards to PWAs and many potential blockers are being removed rapidly. -Week over week, the number of partners building expertise in PWA Studio grows and we have an accelerating number of customer launches. The most recent update to PWA Studio included extensibility that will help make significant progress in compatibility with ADobe Commerce Marketplace extensions. +Week over week, the number of partners building expertise in PWA Studio grows and we have an accelerating number of customer launches. The most recent update to PWA Studio included extensibility that will help make significant progress in compatibility with Adobe Commerce Marketplace extensions. Many merchants may feel they aren’t ready for headless and PWAs because they require heavy reliance on developers. One of the huge benefits of having both the commerce application and the head developed by Adobe Commerce is that it helps ensure compatibility across commerce capabilities. @@ -33,9 +33,9 @@ In order to make PWAs more accessible and easier to manage for our merchants, we ## Adobe Experience Manager -A powerhouse combination for your content and digital asset management needs,Adobe Exeprience Manager helps merchants get personalized, content-led experiences into market faster, combining digital asset management with the power of machine learning, Adobe Sensei-powered content, and customer journey management. +A powerhouse combination for your content and digital asset management needs, Adobe Experience Manager helps merchants get personalized, content-led experiences into market faster, combining digital asset management with the power of machine learning, Adobe Sensei-powered content, and customer journey management. -Adobe Commerce plus Adobe Exeprience Manager is a powerful story in that the commerce engine allows businesses to enable commerce though customer interfaces that are powered by Adobe Experience Manager. +Adobe Commerce plus Adobe Experience Manager is a powerful story in that the commerce engine allows businesses to enable commerce though customer interfaces that are powered by Adobe Experience Manager. ## Custom Heads diff --git a/help/implementation-playbook/architecture/headless/journey-to-headless.md b/help/implementation-playbook/architecture/headless/journey-to-headless.md index f820e2402..28bc95f99 100644 --- a/help/implementation-playbook/architecture/headless/journey-to-headless.md +++ b/help/implementation-playbook/architecture/headless/journey-to-headless.md @@ -1,8 +1,8 @@ --- title: Journey to Headless -description: Review a timeline of Adobe Commerce's jouirney to support headless architectures. +description: Review a timeline of Adobe Commerce's journey to support headless architectures. exl-id: 9286e6b3-3c29-4428-b353-f66eb4bc382d --- # Adobe Commerce’s Journey to Headless -![Timeline of Adobe Commerce's hjourney to a headless architecture](../../../assets/playbooks/journey-to-headless.svg) +![Timeline of Adobe Commerce's journey to a headless architecture](../../../assets/playbooks/journey-to-headless.svg) diff --git a/help/implementation-playbook/architecture/headless/microservices.md b/help/implementation-playbook/architecture/headless/microservices.md index 89127c065..5cd1bb0bc 100644 --- a/help/implementation-playbook/architecture/headless/microservices.md +++ b/help/implementation-playbook/architecture/headless/microservices.md @@ -1,6 +1,6 @@ --- title: Adobe Commerce Microservices -description: Be able to differentiate between healdess and microservices as it pertains to Adobe Commerce. +description: Be able to differentiate between headless and microservices as it pertains to Adobe Commerce. exl-id: 078e0e8e-7acc-4913-8b78-585a950f3f5e --- # Headless and microservices @@ -9,7 +9,7 @@ It is important not to confuse headless with microservices. A lot of the time, w A microservices architecture is a term used to describe the practice of breaking up an application into a collection of smaller, loosely coupled services. Microservices enable individual backend services to be: -- **Isolated from one another**—For exmaple, the pricing service has no dependency on the catalog service. +- **Isolated from one another**—For example, the pricing service has no dependency on the catalog service. - **Deployed a la carte**—Customers deploy only the parts of the application that they need. diff --git a/help/implementation-playbook/architecture/integration-options.md b/help/implementation-playbook/architecture/integration-options.md index 463ef7915..ce809587b 100644 --- a/help/implementation-playbook/architecture/integration-options.md +++ b/help/implementation-playbook/architecture/integration-options.md @@ -15,7 +15,7 @@ The following diagram describes a monolithic approach that uses Adobe Commerce a ## Headless -The following diagram describes a headless approach that uses Adobe Commerce as the backend systenm integrated with a DXP/CMS/custom application as the storefront application: +The following diagram describes a headless approach that uses Adobe Commerce as the backend system integrated with a DXP/CMS/custom application as the storefront application: ![Adobe Commerce headless diagram](../../assets/playbooks/integration-headless.svg) diff --git a/help/implementation-playbook/architecture/integration-strategy.md b/help/implementation-playbook/architecture/integration-strategy.md index 0d819840d..ce9681af9 100644 --- a/help/implementation-playbook/architecture/integration-strategy.md +++ b/help/implementation-playbook/architecture/integration-strategy.md @@ -9,7 +9,7 @@ The ability to integrate your platform is “non-negotiable.” Companies want t A holistic integration approach for both storefront and backend systems are supported by performant GraphQL APIs, comprehensive REST APIs, and batch-file import between Adobe Commerce and other systems or services. -The Adobe Commerce GraphQL API provides comprehesnive storefront coverage that you can use to integrate with other storefronts, including: +The Adobe Commerce GraphQL API provides comprehensive storefront coverage that you can use to integrate with other storefronts, including: - Digital experience platforms (DXPs) like Adobe Exeprience Manaber and Bloomreach - Content management systems (CMS) like Drupal and WordPress diff --git a/help/implementation-playbook/development/platform-tools.md b/help/implementation-playbook/development/platform-tools.md index 651715997..aa5c3b113 100644 --- a/help/implementation-playbook/development/platform-tools.md +++ b/help/implementation-playbook/development/platform-tools.md @@ -22,7 +22,7 @@ The following table includes solutions that we recommend and can be used within | Message queue services | RabbitMQ | | Security scan tool | SonarQube, ZAP | -## Datbase +## Database There are three different tools that we use depending on the needs of the brand. MySQL is a great baseline solution as the Adobe Commerce database if you don’t expect your store to handle extreme loads. diff --git a/help/implementation-playbook/infrastructure/cloud/managed-services.md b/help/implementation-playbook/infrastructure/cloud/managed-services.md index c0ebcf72c..311a13455 100644 --- a/help/implementation-playbook/infrastructure/cloud/managed-services.md +++ b/help/implementation-playbook/infrastructure/cloud/managed-services.md @@ -1,11 +1,11 @@ --- title: Managed Services -description: Review the responsibilities of Adobe Managed Services, customers, and cloud service providers for your Adobe Commerce on cloud infrastructure implementaiton. +description: Review the responsibilities of Adobe Managed Services, customers, and cloud service providers for your Adobe Commerce on cloud infrastructure implementation. exl-id: b1442e31-06f4-4aa6-b24a-b6cda630d52f --- # Managed services -Adobe Commerce on cloud infrastructure manged services are secure by default. +Adobe Commerce on cloud infrastructure managed services are secure by default. ![Diagram showing Adobe Commerce managed services](../../../assets/playbooks/managed-services.svg) @@ -15,7 +15,7 @@ Adobe Commerce Pro plans rely on a shared responsibility security model. In this ![Diagram showing Adobe Commerce shared responsibility model](../../../assets/playbooks/shared-responsibility.svg) -### Adobe Manged Services responsibilities +### Adobe Managed Services responsibilities Adobe Managed Services is responsible for the security and availability of the Adobe Commerce Pro cloud environment, the core Adobe Commerce Pro application code, and internal commerce systems. This includes, but is not limited to: diff --git a/help/implementation-playbook/infrastructure/cloud/overview.md b/help/implementation-playbook/infrastructure/cloud/overview.md index b5e1e3fd7..712e25afe 100644 --- a/help/implementation-playbook/infrastructure/cloud/overview.md +++ b/help/implementation-playbook/infrastructure/cloud/overview.md @@ -1,6 +1,6 @@ --- title: Cloud Infrastructure Overview -description: Learn about Adobe Commerce on cloud infrastucture. +description: Learn about Adobe Commerce on cloud infrastructure. exl-id: 94cf1505-0853-4e01-ba55-befc1117fbdb --- # Overview diff --git a/help/implementation-playbook/infrastructure/cloud/security.md b/help/implementation-playbook/infrastructure/cloud/security.md index a243d6058..571752ec4 100644 --- a/help/implementation-playbook/infrastructure/cloud/security.md +++ b/help/implementation-playbook/infrastructure/cloud/security.md @@ -1,5 +1,5 @@ --- -title: Cloud Infrasrtructure Security +title: Cloud Infrastructure Security description: Learn about how we keep Adobe Commerce on cloud infrastructure secure. exl-id: cd5d1106-c8db-4b70-b1c7-12378d7d77a7 --- diff --git a/help/implementation-playbook/infrastructure/on-premises.md b/help/implementation-playbook/infrastructure/on-premises.md index cc5ba2d3c..116d72adf 100644 --- a/help/implementation-playbook/infrastructure/on-premises.md +++ b/help/implementation-playbook/infrastructure/on-premises.md @@ -1,6 +1,6 @@ --- title: On-premises Infrastructure -description: Learn about Adobe Commerce on-premises infrastucture and third-party cloud services. +description: Learn about Adobe Commerce on-premises infrastructure and third-party cloud services. exl-id: de1467be-acec-4a0d-8229-e7e87614bc55 --- # Adobe Commerce on-premises infrastructure @@ -43,7 +43,7 @@ In addition to providing a supporting technology platform for the enablement of ## Cloud migration -The value proposition for migrating Adobe Commerce to AWS is further enhanced by the availability of several services that provide operational insight and agility. What we mean is operational insight into the platform from not only a technical perspective (for exmaple, requests per hour) but also a business operational perspective (for example, orders per hour), particularly when the two sets of data can be married. This provides a near-real-time look into campaign performance, platform operations costs, and a near infinite number of other indicators. +The value proposition for migrating Adobe Commerce to AWS is further enhanced by the availability of several services that provide operational insight and agility. What we mean is operational insight into the platform from not only a technical perspective (for example, requests per hour) but also a business operational perspective (for example, orders per hour), particularly when the two sets of data can be married. This provides a near-real-time look into campaign performance, platform operations costs, and a near infinite number of other indicators. Adobe Commerce setup to AWS can replace specific application dependencies with fully managed alternatives available in the cloud. For example, rather than directly hosting a relational database on EC2 instances, the database for many applications can be easily replaced by Amazon Relational Database Service (AmazonRDS). The benefit to this strategy is that the operating responsibility of undifferentiated components can be offloaded to AWS without requiring significant changes to the core application. diff --git a/help/implementation-playbook/infrastructure/overview.md b/help/implementation-playbook/infrastructure/overview.md index 73590e0ff..30288695e 100644 --- a/help/implementation-playbook/infrastructure/overview.md +++ b/help/implementation-playbook/infrastructure/overview.md @@ -1,6 +1,6 @@ --- title: Infrastructure and Deployment Overview -description: Get an overview of what we've taught you about the Adobe Commerce soluion so far. +description: Get an overview of what we've taught you about the Adobe Commerce solution so far. exl-id: 8767bb83-9175-4a54-8c5c-c6af0931917c --- # Overview diff --git a/help/implementation-playbook/infrastructure/performance/recommendations.md b/help/implementation-playbook/infrastructure/performance/recommendations.md index fd42d6fff..3a1187051 100644 --- a/help/implementation-playbook/infrastructure/performance/recommendations.md +++ b/help/implementation-playbook/infrastructure/performance/recommendations.md @@ -17,7 +17,7 @@ DNS lookup is the process of finding which IP address that the domain name belon ### Content delivery network (CDN) -Use a CDN to optimize asset downloading performance. Adobe Commerce uses Fastly. If have an on-premises implementaiton of Adobe Commerce, you should also consider adding a CDN layer. +Use a CDN to optimize asset downloading performance. Adobe Commerce uses Fastly. If have an on-premises implementation of Adobe Commerce, you should also consider adding a CDN layer. ### Web latency @@ -97,7 +97,7 @@ Performance testing before each production release is always recommend to get an >[!NOTE] > -> Adobe Commerce on cloud infrastrucrure already applies all of the above infrastructure and architecture optimizations, except for the DNS lookup because it's out of scope. +> Adobe Commerce on cloud infrastructure already applies all of the above infrastructure and architecture optimizations, except for the DNS lookup because it's out of scope. ### Search @@ -105,11 +105,11 @@ Elasticsearch is required as of Adobe Commerce version 2.4, but it’s also a be ## Operating models -Apart from the previoiusly mentioend common infrastructure optimization recommendations, there are also approaches to enhance the performance for specific business modes and scales. This document does not provide in-depth tuning instructions for all of them because each scenario is different, but we can provide a few high-level options for your reference. +Apart from the previously mentioned common infrastructure optimization recommendations, there are also approaches to enhance the performance for specific business modes and scales. This document does not provide in-depth tuning instructions for all of them because each scenario is different, but we can provide a few high-level options for your reference. ### Headless architecture -We have a seperate section dedicated to detailing what [headless](../../architecture/headless/adobe-commerce.md) is and different options. In summary, it separates the storefront layer from the platform itself. It is still the same backend, but Adobe Commerce no longer processes requests directly and instead only supports custom storefronts through the GraphQL API. +We have a separate section dedicated to detailing what [headless](../../architecture/headless/adobe-commerce.md) is and different options. In summary, it separates the storefront layer from the platform itself. It is still the same backend, but Adobe Commerce no longer processes requests directly and instead only supports custom storefronts through the GraphQL API. ### Keep Adobe Commerce updated diff --git a/help/implementation-playbook/intro/platform-development.md b/help/implementation-playbook/intro/platform-development.md index af2e76692..fa8e4f0f1 100644 --- a/help/implementation-playbook/intro/platform-development.md +++ b/help/implementation-playbook/intro/platform-development.md @@ -18,14 +18,14 @@ In this playbook, we dive deeper into some of the main standards of Adobe Commer While some solution implementers may have their own preferences when it comes to the methodologies, processes, and tools used throughout an implementation project, this playbook focuses on generally accepted best practices and methodologies that can be shared across the majority of implementations. -Like any large IT project, Adobe Commerce is built on coding standards that leverage best practices and standardizations of the underlying technologies (for example, PHP/Zend,Symfony, JavaScript, jQuery, and HTML), as well as standards that have been established within the Adobe Commerce Coding Standard. Following these standards is an absolute must to eliminate bugs and improve the quality and maintainability of custom-built code. +Like any large IT project, Adobe Commerce is built on coding standards that leverage best practices and standardizations of the underlying technologies (for example, PHP/Zend, Symfony, JavaScript, jQuery, and HTML), as well as standards that have been established within the Adobe Commerce Coding Standard. Following these standards is an absolute must to eliminate bugs and improve the quality and maintainability of custom-built code. ## Adobe Commerce on cloud infrastructure Adobe Commerce on cloud infrastructure is a managed, automated hosting platform for the Adobe Commerce software. Adobe Commerce on cloud infrastructure comes with a variety of additional features that sets it apart from on-premises Adobe Commerce and Magento Open Source implementations: -![Adobe Commerce component infgraphics](../../assets/playbooks/commerce-cloud.svg) +![Adobe Commerce component infographics](../../assets/playbooks/commerce-cloud.svg) Adobe Commerce on cloud infrastructure provides a pre-provisioned infrastructure that includes PHP, MySQL, Redis, RabbitMQ, and Elasticsearch technologies; a Git-based workflow with automatic build and deploy operations for efficient rapid development and continuous deployment every time code changes are pushed in a Platform as a Service (PaaS) environment; highly customizable environment-configuration files and tools; and AWS hosting that offers a scalable and secure environment for online sales and retailing. -![Adobe Commerce component infgraphics](../../assets/playbooks/cloud-tech-stack.svg) +![Adobe Commerce component infographics](../../assets/playbooks/cloud-tech-stack.svg) diff --git a/help/implementation-playbook/maintenance/adobe-managed-services.md b/help/implementation-playbook/maintenance/adobe-managed-services.md index dc4a369ba..04d08efcb 100644 --- a/help/implementation-playbook/maintenance/adobe-managed-services.md +++ b/help/implementation-playbook/maintenance/adobe-managed-services.md @@ -1,6 +1,6 @@ --- title: Adobe Managed Services -description: Learn how ADobe Managed Services can help support and maintain your Adobe Commerce implementation. +description: Learn how Adobe Managed Services can help support and maintain your Adobe Commerce implementation. exl-id: b600b0e3-c6fd-4b86-ad2a-a445e599f1bd --- # Adobe Managed Services @@ -21,4 +21,4 @@ Platform partners such as Amazon Web Services and Microsoft Azure ensures maximu The following diagram shows Adobe Managed Service's security technology stack: -![Diagram showing ADobe Managed Services security stack](../../assets/playbooks/managed-services-security-stack.svg) +![Diagram showing Adobe Managed Services security stack](../../assets/playbooks/managed-services-security-stack.svg) diff --git a/help/implementation-playbook/maintenance/models.md b/help/implementation-playbook/maintenance/models.md index c13d1723b..c6b473c51 100644 --- a/help/implementation-playbook/maintenance/models.md +++ b/help/implementation-playbook/maintenance/models.md @@ -1,6 +1,6 @@ --- title: Maintenance and Support Models -description: Use these common maintenance and support models to keep your ADobe Commerce implementation running smoothly. +description: Use these common maintenance and support models to keep your Adobe Commerce implementation running smoothly. exl-id: 44469b83-a10b-44c2-8721-9a7daa2733d3 --- # Maintenance and support models diff --git a/help/implementation-playbook/planning/ownership.md b/help/implementation-playbook/planning/ownership.md index a7378e915..be5fb9ac9 100644 --- a/help/implementation-playbook/planning/ownership.md +++ b/help/implementation-playbook/planning/ownership.md @@ -1,6 +1,6 @@ --- title: Responsibility and Ownership -description: Define project roles and responsibilities to ensure a succesful Adobe Commerce implementation. +description: Define project roles and responsibilities to ensure a successful Adobe Commerce implementation. exl-id: 206b6e3b-6dee-442e-a2ba-7867b2494b75 --- # Responsibility and ownership diff --git a/help/implementation-playbook/project-scope/knowledge.md b/help/implementation-playbook/project-scope/knowledge.md index c3d73a9f5..256235877 100644 --- a/help/implementation-playbook/project-scope/knowledge.md +++ b/help/implementation-playbook/project-scope/knowledge.md @@ -1,6 +1,6 @@ --- title: Knowledge is Power -description: Learn why it's so important that everyone in your organizationinvests in your Adobe Commerce implementation. +description: Learn why it's so important that everyone in your organization invests in your Adobe Commerce implementation. exl-id: a3929586-5ad2-4b30-8bc4-84da8f8b9eb5 --- # Knowledge is power diff --git a/help/implementation-playbook/project-scope/process-timeline.md b/help/implementation-playbook/project-scope/process-timeline.md index f0ff6bfbd..668c3d2af 100644 --- a/help/implementation-playbook/project-scope/process-timeline.md +++ b/help/implementation-playbook/project-scope/process-timeline.md @@ -1,11 +1,11 @@ --- title: Process and Timeline -description: See examples of typical Adobe Commerce imeplmentation timelines and timeline activities. +description: See examples of typical Adobe Commerce implementation timelines and timeline activities. exl-id: 73e38098-db2b-4ad3-9f2d-ac8a377f2525 --- # Typical process and timeline -Many organizations prepare for a commerce transformation by creating a request for proposal (RFP). This includes detailed requirements, current systems of record, a business case, and specific goals (for example, revenue, conversion, average order value) to define success. The brand then approaches two to three different commerce systems integrators or digital agencies to evaluate, review estimates and proposals, select a company, and begin working towarda projected timeline to launch. +Many organizations prepare for a commerce transformation by creating a request for proposal (RFP). This includes detailed requirements, current systems of record, a business case, and specific goals (for example, revenue, conversion, average order value) to define success. The brand then approaches two to three different commerce systems integrators or digital agencies to evaluate, review estimates and proposals, select a company, and begin working towards projected timeline to launch. This can be a successful approach. However, one recommendation that mitigates risk (before committing to a full implementation) is to work with an organization on a requirements assessment or discovery process that can confirm organizational preparedness, project scope, timeline, budget, business requirements, and technical approach. On average, this process should take between four to six weeks, but varies depending on the size of the project. diff --git a/help/implementation-playbook/project-scope/requirement-checklists.md b/help/implementation-playbook/project-scope/requirement-checklists.md index fad1f5e6b..38c4daf28 100644 --- a/help/implementation-playbook/project-scope/requirement-checklists.md +++ b/help/implementation-playbook/project-scope/requirement-checklists.md @@ -49,11 +49,11 @@ The following questions can serve as a starting point to see which information s - Where do you see future growth coming from in your business? -- What role does digital commerce play in your business strategy? What are your primary objectives for setting up thisecommerceplatform? +- What role does digital commerce play in your business strategy? What are your primary objectives for setting up this ecommerce platform? - Do you have any brands/companies that you take as a reference on how you grow your omnichannel business? -- Which teams or individuals are driving theecommercestrategy? Describe the relevant positions. +- Which teams or individuals are driving the ecommerce strategy? Describe the relevant positions. ## Current platform @@ -97,7 +97,7 @@ The following questions can serve as a starting point to see which information s - Will it be a high-availability system architecture? -- How manyAdobe Commerceadministrators will you have? +- How many Adobe Commerce administrators will you have? - Expected catalog size (number of SKUs)? @@ -133,7 +133,7 @@ The following questions can serve as a starting point to see which information s - Is this primarily a B2C or B2B site? Is there any B2B2B or B2B2C element? -- Is there an existing design that is adapted,or will the platform be designed from scratch? +- Is there an existing design that is adapted or will the platform be designed from scratch? - Is there a requirement for headless commerce (separate frontend and backend layers)? @@ -143,9 +143,9 @@ The following questions can serve as a starting point to see which information s - Any specific browsers that should be tested (except for the standard browsers IE9+, Firefox, Chrome, Safari)? -- What are the language(s) for eachfront end? Is the translated content available or is support needed? +- What are the language(s) for each frontend? Is the translated content available or is support needed? -- Are there multiple websites? If so,cancustomers use their credentials across all sites? +- Are there multiple websites? If so, can customers use their credentials across all sites? - Is product data shared across all sites? @@ -157,31 +157,31 @@ The following questions can serve as a starting point to see which information s ## Integrations -- Which CMS system will be integrated withAdobe Commerce? (Examples: WordPress, Drupal, Concrete5) +- Which CMS system will be integrated with Adobe Commerce? (Examples: WordPress, Drupal, Concrete5) Are there existing APIs that can be used? - Has system-error handling been designed and developed for this third-party-system integration? -- Which ERP system will be integrated withAdobe Commerce? (Examples: SAP, MS Dynamics NAV) +- Which ERP system will be integrated with Adobe Commerce? (Examples: SAP, MS Dynamics NAV) -- Which shipping carrier system will be integrated withAdobe Commerce? +- Which shipping carrier system will be integrated with Adobe Commerce? -- Which tax-software system will be integrated withAdobe Commerce? (Example:Taxware) +- Which tax-software system will be integrated with Adobe Commerce? (Example: Taxware) -- From which system will product data be imported intoAdobe Commerce? +- From which system will product data be imported into Adobe Commerce? - Frequency of imported product data loads? -- Into which system willAdobe Commerceexport product data? +- Into which system will Adobe Commerce export product data? - Frequency of exported product data loads? -- From which system will order data be imported intoAdobe Commerce? +- From which system will order data be imported into Adobe Commerce? - Frequency of imported order data loads? -- Into which system willAdobe Commerceexport order data? +- Into which system will Adobe Commerce export order data? - Frequency of exported order data loads? @@ -197,11 +197,11 @@ Are there existing APIs that can be used? - Which payment gateway do you want your site to have? -- Which order management system will be integrated withAdobe Commerce? (Examples: Microsoft Dynamics, SAP, Retail Pro) +- Which order management system will be integrated with Adobe Commerce? (Examples: Microsoft Dynamics, SAP, Retail Pro) -- Which product inventory management system will be integrated withAdobe Commerce? (Examples: Akeneo, InRiver, Bluestone) +- Which product inventory management system will be integrated with Adobe Commerce? (Examples: Akeneo, InRiver, Bluestone) -- Which customer relationship management system will be integrated withAdobe Commerce? (Examples: Hubspot, Salesforce, Klaviyo) +- Which customer relationship management system will be integrated with Adobe Commerce? (Examples: Hubspot, Salesforce, Klaviyo) ## Adobe Commerce-specific features @@ -225,7 +225,7 @@ Are there existing APIs that can be used? - Will you require a content staging website? -- Should customers be allowed to create a website account +- Should customers be allowed to create a website account? - Will you use unique discount coupons for promotions? @@ -243,7 +243,7 @@ Are there existing APIs that can be used? - Allow a customer to view past orders and select items to be exchanged? -- Will you allow a customer to initiate the cancelling of an order from the website? +- Will you allow a customer to initiate the canceling of an order from the website? - Will you allow a customer to initiate the exchange of items from the website? @@ -253,7 +253,7 @@ Are there existing APIs that can be used? - Will Adobe Commerce issue a return RMA? -- Capture refund information inAdobe Commerce? +- Capture refund information in Adobe Commerce? - Will you require online order tracking for a registered customer? @@ -279,7 +279,7 @@ Are there existing APIs that can be used? - Reward points -- "Bill Me Later”– more commonly knownas“Buy Now, Pay Later”as it's immediately billed but not paid yet +- "Bill Me Later” – more commonly known as “Buy Now, Pay Later” as it's immediately billed but not paid yet - Will there be different product pricing on different websites? @@ -301,9 +301,9 @@ Are there existing APIs that can be used? - Shopping cart: Products in carts, abandoned arts -- Products: Bestsellers, products ordered, most viewed, lowstock, downloads +- Products: Bestsellers, products ordered, most viewed, low stock, downloads -- Customers: Newaccounts,customersby orders total,customersby number of orders,customer segments,customer reviews +- Customers: New accounts, customers by orders total, customers by number of orders, customer segments, customer reviews - Products reviews @@ -317,7 +317,7 @@ Are there existing APIs that can be used? - Will you need Adobe Commerce to generate reports based on sales data? -- Will you need custom Adobe Commercere ports? +- Will you need custom Adobe Commerce reports? - What is your current SEO strategy? @@ -329,7 +329,7 @@ Are there existing APIs that can be used? - Allow partial shipping? -- Should shipment tracking information be stored inAdobe Commerce? +- Should shipment tracking information be stored in Adobe Commerce? - Will you require tax-calculation rules for your domestic regions?