This document provides a project overview and “what”, “who”, and “why” guidance on project planning, execution, testing, go-live, and post go-live customer support (the “how” guidance is provided in the Catalog and Inventory and Order Management and other documents). It is targeted for a project lead and a technical lead but should be useful for anyone involved in implementation.
A typical Commerce Platform integration project for native checkout has a broad scope with multiple functional areas, such as product catalog, order fulfillment, finance, and customer service, and may involve stakeholders from various teams or from external organizations (such as third-party agencies). A successful integration requires all cross-functional cooperation with all key stakeholders.
This section should help the project lead to identify stakeholders within their organization such as e-comm development, OMS development, warehouse, customer service, IT, finance, and social media management, and onboard them and work with them to ensure in-time delivery. It provides a project overview and “what”, “who”, and “why” guidance on project planning, execution, testing, go-live, and post go-live customer support. After reading this section, the project lead should to have a sufficient understanding of the integration scope and steps to start engaging the technical team to implement product feed, inventory updates, and order management.
Before starting the integration, review the project documentation, work through prerequisites and technical requirements, and create a project plan with key milestones approved by stakeholders. Technical leads should design solutions and create a technical documentation (e.g. data flow diagrams). Project leads can engage identified stakeholders by training them on FB/IG tools, provide them with the “how-to” documentation, and facilitate them with completing project requirements and defining processes (e.g. reporting and customer service).