Vmeasure App Multiple System Token

In today’s fast-paced e-commerce world, efficient warehouse management is crucial for ensuring seamless order fulfillment. Vmeasure is a powerful tool that helps businesses track and optimize their fulfillment operations. By integrating Vmeasure with Eshopbox Workspace, businesses can gain real-time visibility into their warehouses, monitor inventory movement, and enhance overall efficiency.

This guide walks you through the step-by-step process of integrating Vmeasure into your Eshopbox workspace—from authentication to enabling Vmeasure at specific fulfillment locations. Whether you’re setting it up for the first time or managing multiple fulfillment centers, this integration ensures smooth and accurate tracking of inventory using Vmeasure.

Step 1: Configuring Vmeasure

Emma, an e-commerce manager, wants to integrate Vmeasure with her Eshopbox workspace to enhance warehouse efficiency. To get started, she needs to configure Vmeasure.

She logs into the Eshopbox dashboard and navigates to the Vmeasure Integration section. The system prompts her to enter two critical credentials:

• User ID – A unique identifier provided by Vmeasure to authenticate her account.

• Secret ID – A confidential key required to authorize the integration securely.

Emma isn’t sure where to find these details, but a handy help article link appears, guiding her through the process. Within minutes, she retrieves her credentials from Vmeasure and enters them into the system.

With a deep breath, she clicks Authenticate. The system processes her request, and in a moment, a confirmation message appears:

✅ “Authentication successful! You are now connected to Vmeasure.”

With step one complete, Emma moves forward to configuring her fulfillment locations.

Step 2: Choosing Fulfillment Locations

Now that Vmeasure is configured, Emma must decide where she wants it to operate. The system presents her with a list of self-fulfillment locations—warehouses where her inventory is stored.

Since she is using the Eshopbox workspace, she also sees Eshopbox Fulfillment Centers (FCs) listed. She reviews the locations and selects the ones that should be monitored by Vmeasure.

But before activating Vmeasure at these locations, she needs to provide a System Token—a unique code from Vmeasure that authorizes tracking at each warehouse.

Step 3: Adding Vmeasure to Specific Locations

Emma clicks “Add Vmeasure” for her Mumbai Warehouse. Immediately, a popup appears prompting her to enter the System Token.

She copies the token from her Vmeasure account and pastes it into the field. But she realizes she has multiple tokens for different tracking systems within the warehouse. No problem—the system allows her to enter multiple tokens!

After adding the necessary tokens, she proceeds to the final step: managing their status.

Step 4: Managing System Tokens

Each System Token Emma enters has three possible actions:

1️⃣ Enable – Activates Vmeasure tracking at that location.
2️⃣ Disable – Temporarily pauses tracking without deleting the token.
3️⃣ Delete – Removes the token entirely, cutting off Vmeasure tracking.

For now, she enables all her tokens. The system confirms her selections:

✅ “Vmeasure successfully enabled for Mumbai Warehouse.”

Feeling accomplished, Emma moves on to repeat the process for her other fulfillment centers.

With everything set up, she knows Vmeasure is now working behind the scenes, providing insights into her warehouse operations.

Database Schema

Table: ConnectionOtherDetails

SQLQuery :

APIs & SQL Queries

1. Create Record API (POST)

• Endpoint: /connection-other-details

• Method: POST

• Request Body:

  { "connectionId": 2314, "otherDetails": { "650": [ { "token": "abc", "status": "active" }, { "token": "xyz", "status": "inactive" } ], "651": [ { "token": "def", "status": "active" } ] } }

   

• SQL Query:

  INSERT INTO ConnectionOtherDetails (connectionId, otherDetails) VALUES (2314, '{ "650": [ { "token": "abc", "status": "active" }, { "token": "xyz", "status": "inactive" } ], "651": [ { "token": "def", "status": "active" } ] }');

   

• Response:

  { "message": "Record created successfully", "id": 1 }

2. Get Record API (GET)

• Endpoint: /connection-other-details/{connectionId}

• Method: GET

• SQL Query:

  SELECT * FROM ConnectionOtherDetails WHERE connectionId = 2314;

• Response:

  { "id": 1, "connectionId": 2314, "otherDetails": { "650": [ { "token": "abc", "status": "active" }, { "token": "xyz", "status": "inactive" } ], "651": [ { "token": "def", "status": "active" } ] } }

   

3. Get API by Account Slug

• Endpoint: /connection-other-details/account/{accountSlug}

• Method: GET

• Logic:

  • accountSlug is mapped to a warehouseId.

  • Fetch records where warehouseId is part of otherDetails.

• SQL Query (Assuming accountSlug is within otherDetails JSON)

  SELECT * FROM ConnectionOtherDetails WHERE JSON_CONTAINS(otherDetails, '{"accountSlug": "aassqqwwdl123"}');

   

• Response:

  { "accountSlug": "some-account", "warehouseId": 650, "records": [ { "id": 1, "connectionId": 2314, "otherDetails": [ { "token": "abc", "status": "active" }, { "token": "xyz", "status": "inactive" } ] }