PeopleVox Warehouse Inventory Transfers

Overview

Inventory transfers help you move products between different warehouse locations and accurately track stock levels in real time. This feature is typically used to manage seasonal demand, scale operations, and optimize warehouse space.

Sellercloud’s PeopleVox Account Integration allows you to export transfer requests, import receiving details, and sync inventory information between the two platforms.


Prerequisites

Before you can submit transfer requests from Sellercloud to PeopleVox, you must complete the following requirements.

  • Account Configuration – The PeopleVox Account Integration must be set up.
  • Warehouse Mapping – PeopleVox locations must be mapped to their corresponding Sellercloud warehouses on the PeopleVox Warehouse Mapping page.
  • SKU Mapping – If the PeopleVox SKU (also referred to as Item Code) differs from the Sellercloud SKU, the corresponding values must be populated in the Peoplevox_MerchantSKU field of the PeopleVox Product Properties page.
The products you intend to send in your transfer requests must be PeopleVox-enabled and Posted.
To transfer inventory between a PeopleVox location and an external or Skustack-managed warehouse, be sure to familiarize yourself with the inventory movement scenarios below.

PeopleVox Warehouse Inventory Transfers

Sellercloud sends WITRs to PeopleVox in the form of Sales Orders, allowing you to manage the transfer process (picking, shipping, and receiving) within PeopleVox. Once the transfer is shipped, PeopleVox sends fulfillment details back to Sellercloud, which then marks the request as shipped and creates a Purchase Order (PO) to complete the receiving process.

  1. Navigate to Inventory > Tools > Warehouse Inventory Transfer.
  2. Access the Actions menu and select Create New Transfer Request.
  3. Complete the transfer creation as described in the Warehouse Inventory Transfers article.PVXWITR
  4. Once the request is successfully created in Sellercloud, it can be sent to PeopleVox either manually or automatically:
    1. To send the WITR manually, use the Submit to Peoplevox action on the WITR Details page. This action only becomes available if:
      • The WITR’s company is PeopleVox Enabled.
      • The WITR has not already been submitted to PeopleVox.
      • The To or From warehouse is a mapped PeopleVox location.PVXSubmit
    2. To send the WITR automatically, the WITR status must be Requested, and the above conditions must also be met. Any transfers that fit that criteria will be exported from Sellercloud to PeopleVox approximately every 15 minutes.
  5. The request is sent to PeopleVox as a Sales Order, containing the transfer details and item information.
Once a WITR is sent to PeopleVox, the Submit to PeopleVox action will no longer be available, and additional products cannot be added.

Receiving Details

After the WITR is submitted to PeopleVox, the inventory is processed based on the From and To warehouses as follows:

Scenario 1

From and To are mapped to PeopleVox warehouses:

  1. The WITR is created in Sellercloud.
  2. Sellercloud sends a Sales Order with transfer details to PeopleVox.
  3. PeopleVox picks and ships the items.
  4. Sellercloud receives a fulfillment notice from PeopleVox → WITR is marked as Shipped and moved to Interim.
  5. Sellercloud then creates a Purchase Order (PO) for the same items using the To warehouse and sends it to PeopleVox.
  6. When PeopleVox receives the PO, Sellercloud marks the WITR as Received.
This is the full transfer workflow using PeopleVox for both shipping and receiving.

Scenario 2

From is a PeopleVox-mapped warehouse; To is a Skustack warehouse:

  1. The WITR is created in Sellercloud.
  2. Sellercloud sends a Sales Order with transfer details to PeopleVox.
  3. PeopleVox picks and ships the items.
  4. Sellercloud receives a fulfillment notice from PeopleVox → WITR is marked as Shipped.
No PO or receiving steps are required for this workflow because the receiving warehouse is managed outside of PeopleVox.

Scenario 3

From is a PeopleVox-mapped warehouse; To is not a Skustack or PeopleVox-mapped warehouse:

  1. The WITR is created in Sellercloud.
  2. Sellercloud sends a Sales Order with transfer details to PeopleVox.
  3. PeopleVox picks and ships the items.
  4. Sellercloud receives a fulfillment notice from PeopleVox → WITR is marked as Shipped.
No PO or receiving steps are required for this workflow because the receiving warehouse is managed outside of PeopleVox.

Scenario 4

From is a Skustack warehouse; To is PeopleVox-mapped:

  1. The WITR is created in Sellercloud.
  2. The WITR is manually marked as Shipped and moved to Interim using Sellercloud.
  3. Sellercloud then creates a Purchase Order (PO) using the To warehouse and sends it to PeopleVox.
  4. When PeopleVox fulfills the PO, Sellercloud marks the WITR as Received.
This workflow skips PeopleVox shipping steps and focuses on PeopleVox receiving.

If there’s a difference between the WITR quantity and the quantity in the Fulfillment Notice (Example: WITR has 100 qty, Fulfillment Notice has 50 qty):

  • Sellercloud generates a PO for the shipped quantity (e.g., 50 units).
  • Once the second Fulfillment Notice is received, Sellercloud creates a second PO with the rest of the quantity (e.g., the remaining 50 units).

You can review all documents related to PeopleVox WITRs in Settings > Company > Toolbox > Peoplevox Settings > Documents.
PVXDocs


Was this article helpful?

Need Support?
Can't find the answer you're looking for?
Contact Support