The Ordergroove Launch Process: Stages, Steps, and Timeline

It can seem daunting, to launch a new subscription program for your store. With this guide on the Ordergroove launch process, you'll be able to take the stress and worry out of it and rest assured that you'll be able to soon begin your steps in relationship commerce. 

 


Overview: The Launch Stages, Steps, and Timeline

The image below will give you a detailed overview of the top-level launch stages you'll be progressing through as well as the specific tasks your business and technical teams will need to complete as you integrate with Ordergroove’s Relationship Commerce Solution. 

Note: The timeframes provided are a general estimate, and should not be taken at face value. There are a number of factors that could affect your program launch such as project resources, custom add-ons, and the scope of the project. 

 

Launch_Steps.jpg

Further below that, we've provided additional instruction and links to articles throughout our Knowledge Center that will explain in greater detail how to complete the tasks within each stage of the integration. 

Lastly, at the end of this article, we've provided some loose estimates for the level of effort (LOE) in hours that will be required for implementing Ordergroove. These estimates will vary depending on your familiarity with Ordergroove and the e-commerce platform. These are ballpark estimates only, and merchants should consult with their project teams to get a more precise estimate.


Stage 1: Introduction and Kickoff

Before jumping into the integration, we highly recommend that you review the articles in this first section to make sure you're fully up to speed and ready to begin bringing your program online. You'll also learn about the various places where you can find and get help.

Team

Tasks / Documentation

Client Business and Technical Teams

What does success look like at this stage?

  • You know what Ordergroove help sources are available to you and where to find them.
  • You know how Ordergroove features work.
  • You have a general grasp of how the integration with Ordergroove will work.


Stage 2: Design and Installation

Once you're up to speed on our offering, how it works, the general integration process, and where you can find help, it is time to dive into stage 2. In this stage, we'll focus on designing/marketing your program, as well as integrating Ordergroove with your e-commerce platform by installing our cartridge, application, or module.

Team

Tasks / Documentation

Client Business Teams

Client Technical Teams

  • Install the cartridge, application, or module
  • Depending on your e-commerce platform, this may also include:
    • Setting up payment gateways
    • Modifying front-end code to inject OG content
    • Blocking guest checkout
    • Blocking unsupported payment methods

What does success look like at this stage?

  • Your business teams have decided how your program will be designed and how it will be marketed.
  • Your technical teams/partners have successfully installed and tested the "base integration" of the Ordergroove cartridge, application, or module.
      • "Base integration" implies the underlying integration works but may not yet be configured, customized, or styled for your needs.


Stage 3: Configuring and Styling Your Program

Now that you've designed your program and have successfully installed the cartridge, it's time to further configure and style your program to match your brand and needs.

Team

Tasks / Documentation

Client Business Teams

Client Technical Teams

What does success look like at this stage?

  • Your business teams have decided which products will be subscription-eligible.
  • Your business teams have decided which promotions you will use to entice customers to sign up for a subscription to them.
  • Your business teams have agreed to designs and copy for your front-end customer experiences should be designed and with what copy (IU, opt-in enrollment, email, Subscription Manager).
  • Your technical teams have configured, developed, and tested your front-end customer experiences (IU, opt-in enrollment, email, Subscription Manager).


Stage 4: QA & UAT

Now that you've integrated Ordergroove as well as configured and styled it with your preferences, it's time to conduct full end-to-end QA and UAT. This will ensure that all features and functionality are working as expected so that you can move on to launching your program!

Team

Tasks / Documentation

Client Business and Technical Teams

What does success look like at this stage?

  • Your business and technical teams have tested and confirmed that your integration is successfully working and ready to go live.


Stage 5: Program Migration Day

Note: This stage is only applicable if you're importing an existing program into Ordergroove. 

While listed as stage 5 in this article, migration planning should start on Day 1 and be done in parallel with all of the other stages listed. There are many different types and flavors of program migration, and the link below will guide you to the migration article suited to your specific scenario.

Team

Tasks / Documentation

Client Business and Technical Teams

What does success look like at this stage?

  • You've completed a dry run of extracting (E) your customer records from your previous provider/platform, transformed (T) them as required, and have loaded (L) them into the Ordergroove.
  • If applicable, you've addressed any issues uncovered during the migration dry run.
  • You've now successfully loaded your final customer subscription records into the Ordergroove production environment.


Step 6: Launch Day

You're now ready to launch your program! Please review the launch day checklist to ensure you're prepared to handle each step.

Team

Tasks / Documentation

Client Business and Technical Teams

What does success look like at this stage?

  • Your program is now live, new subscription sign-ups are coming in, transactional emails are being sent, and recurring orders are being placed.


Post-Launch: What's Next?

Congratulations, your relationship commerce program is now live!

Let's walk through how you'll manage your customers and review the performance of your program. Included below are also some tips and tricks to improve program acquisition, increase retention, and integrate with your loyalty program.

Team

Tasks / Documentation

Client Business and Technical Teams

Our Knowledge Center is full of additional information that will help you before and after your integration. Please make sure to browse around it to find helpful information.


Ordergroove Support During Integration

If you have questions at any stage of the integration, please do not hesitate to look in our Knowledge Center for articles that might help answer your question.
If you still need additional help, please submit a ticket for our support team!


Client and Technology Partners Estimated Level of Effort (LOE)

The level of effort and hours required for implementation will vary depending on familiarity with Ordergroove and the e-commerce platform. The following are ballparks only, and merchants should consult with their project teams to get a more precise estimate.

Team

Tasks

Business Team

[35-70 Hours]

Make Decisions On Program Requirements: 2-5 hours

  • Such as program name, incentive, frequency, etc.

Prepare Assets To Power Program: 5-10 hours

  • Content designs, email templates, etc.

Configure Within Ordergroove: 25-50 hours

  • Emails
  • Enrollment/Upsell
  • Subscription Manager
  • Products
  • Promotions

UAT and Signoff: 2-5 hours

Client Technical Team

[30-60 Hours]

  • Install Platform Plugin: 2-5 hours
  • Setup Payment Gateway: 2-5 hours
  • Modify Site Frontend To Inject Ordergroove Content: 5-10 hours
  • Apply Initial Order Incentives: 5-10 hours
  • Block Unsupported Payment Methods: 2-5 hours
  • Block Guest Checkout: 2-5 hours
  • QA and Bug Resolution: 10-20 hours

Client Technical Team

Program Import
(If Applicable)

[25-50 Hours]

Export From Legacy Systems

  • Customers
  • Subscriptions
  • Payment Tokens

Import Into e-commerce Platform

  • Customers

Import Into Ordergroove*

  • Subscriptions
  • Payment Tokens
  • *Import format must match the format outlined here

Comments

0 comments

Article is closed for comments.