Once your development and internal testing is completed, your stores can go live in a production environment.

1. Verify your integration with Grubtech
2. Set up your production integration configuration on Grubtech
3. Provision and launch pilot store(s)
4. Continue provisioning and launching stores

Verifying Your Integration with Grubtech

Once you have completed development and internal testing, submit a tech support request to schedule integration verification with Grubtech. We jointly run through full end-to-end testing to ensure everything has been configured correctly. After we confirm, we configure the integration on production.

Launching a Pilot Store

Pre-requisites

The following prerequisites should be satisfied for the Grubtech production team to arrange production access to the logistic partner account and set up the pilot store.

• Partners completed the signing of the NDA agreement
• Given the staging access to the partner user with relevant credentials
• Completed the UAT with full flow and confirm the successful verification of UAT
• Receive the credentials for production access

Basic Steps

Setting up a pilot store consists of:

1. Partner selects a suitable customer from their customer list to enable the as the pilot store:
   1. This could be further classified as an existing customer and new customer
2. Partner provides the pilot customer details to the Grubtech support team
3. Grubtech operations team set up the applications in production environment based on the pilot customer details
4. Grubtech provides required authentication and authorization to the pilot customer to continue the functionalities

Production Accounts

Before enabling the production account, the integration manager compiles the required documents and sends those to the partner. This document outlines the general facts about the production account such as payment products, processing currencies, additional services, and any account-specific items. After the approval by both parties, the integration manager enables the account on the Grubtech production platform. The production account undergoes a second and final check by an operation team member to ensure that the configuration reflects the scope of the project and that the products and services are set up as intended.

Scenarios based on Customer Type

When creating the pilot stores, a customer can be one of these scenarios :

Non-Existing Customer

In this scenario customer is not yet a Grubtech customer and the partner wants to use them as a Pilot Store.

• If the customer comes with new a partner, they will need to sign a contract first with Grubtech and have their partner account set up.
• Grubtech Sales Team will hand over the contract to the Customer Success Team.
• Customer Success team then contacts the customer (automatically through HubSpot, but also via call and/or email) requesting all details including menus, food aggregator IDs, etc...
• All the details collected are delivered to the Operations team
• Operations team sets up the pilot store
• Finally, Customer Success team trains the customer and deploys the pilot store on the customer's end

Existing Customer

In this case the Customer is already a Grubtech Customer, and the partner wants to use them as a Pilot Store.

• The Operations team connects the customer account to a partner that has finished the integration.
  • The process includes coordination with the FA for activation, taking the FA ID and including it in the Grubcenter Account, and other credential settings, etc...)
  • Next, the Operations team sets up the pilot store
• Finally, the Customer Success team trains the customer and deploys the pilot store on customer's end.

Notes

The customer will have limited services or expanded services based on their requirements and pilot store configurations may change according to that.

Continuing Launches

After successfully launching the pilot store, the customer starts trading using the configured pilot store. This process is monitored for a specific period of time before releasing the customer from the pilot phase.

Monitoring Pilot Phase

Pilot phase monitoring takes place two to four weeks after the go-live date depending on the nature of the customer setup. The Operations team members carefully monitor the success rate of the transactions to ensure the integration is established within our benchmarks.

During the monitoring period, it’s possible to make minor changes to the configuration. The Operations team will guide and recommend any changes in close cooperation with the partner users.

Completing the Pilot Phase

After the agreed period from the commercial live date, the account is officially handed over to the respective operational support team. This team takes care of operational relationship management and becomes the single point of contact for all operational queries.

Before the handover, the Operations team lead thoroughly checks the live account and its success rates; to validate the termination of the pilot phase.

After the handover, the Integration team lead sends an email, specifying the account and products/services that have been handed over. You are advised that the Operations team will be the single point of contact for any operational queries in the production environment.

Go-Live review

To pass the go-live review for the Grubtech API, you must:

• Run at least 20 API test calls in the Grubtech development environment using the pilot store.
• API calls must be completed without errors.
• Have a high rate of successful orders received from the online ordering platform down to their kitchen.

If there is no issue in the end-to-end flow, it’s confirmed that the integration with the logistics partner customer is successful and we can add more customers to that integration.