Onboarding Process

Requirements Gathering: Before starting the project, CrescoData conducts a detailed discovery session to define integration needs, workflows, data flows, rules, architecture, and integration points. Customer responsibilities, UAT test cases, and project timelines are agreed upon and documented. For smaller projects, details are captured in the Statement of Work. This is a billable phase but does not commit the customer to proceed with CrescoData for integration. A high-level quote can be provided at this stage.

Statement of Work: Once requirements are finalized, the confirmed quote is included in a Statement of Work, detailing customer commitments, the agreed timeframe, and UAT test cases. Both parties must sign before proceeding.

Customer Requirements: Before integration begins, the customer must:

• Provide a technical and business point of contact.
• Allocate resources within the agreed timeframe.
• Share required logins.
• Provide access to staging accounts or a test merchant for UAT.

Project Management Process:

• Delivery requirements are documented in a shared project plan.
• A Slack channel is created for instant communication.
• Weekly project meetings are conducted.
• Actions are recorded in the project plan.

UAT (User Acceptance Testing):

• CrescoData sets up and tests the service in a staging environment based on predefined test cases.
• Once functional testing is completed successfully, the service reaches the activation stage.

Activation & Warranty Period:

• The service is handed over to the customer, who has 14 days for UAT in the staging environment.
• Testing results are reviewed, and necessary adjustments are made before final approval.

Support & Production Release:

• After successful UAT, the customer confirms the release schedule.
• CrescoData notifies all stakeholders before moving the service to production.
• The service is then transferred to CrescoData’s Technical Support team for ongoing assistance.

Customer Onboarding Requirements

Service & Merchant Sign-Up:

• Merchants must have a way to sign up for the service via API, the CrescoData Management Portal, or a Branded Portal.
• Merchants need to provide their channel logins, with some channels requiring OAuth authentication.
• Integration instructions for specific channels are available.

Product Catalogue Information:

• Merchants must provide essential product details, including images, name, description, price, and stock.
• More detailed product information enhances marketplace listings.
• The CrescoData Product Catalogue template outlines full requirements.

Product Allocation, Pricing, and Promotions:

• Can be managed on the customer platform or via Google Sheets. The best approach should be discussed during onboarding.

Contract Considerations:

• Customer contracts