1. Metapack
  2. Shipping
  3. Integrations
  4. Integrating with Peoplevox WMS

Mapping Attributes in Peoplevox to Fields in Delivery Manager

The following specific Item Attributes in Peoplevox can be mapped to fields in Metapack Delivery Manager.

Note

In order to have these fields mapped, raise a ticket with the Peoplevox help desk and confirm the Attribute number for each of the available lines you intend to use.

Mapping of fields other than those listed below has to be raised with the help desk via the "I want to raise a feature request" option.

  • The Attribute number for the harmonised product code. Refer to the equivalent Delivery Manager Field in Product-Level Information.

  • The Attribute number for the fabric content. Refer to the equivalent Delivery Manager Field in Product-Level Information.

  • The Attribute number for the country of origin. Refer to the equivalent Delivery Manager Field in Product-Level Information.

  • The Attribute number for the product type description (e.g. the item name in MetapackPeoplevox). Refer to the equivalent Delivery Manager Field in Product-Level Information.

  • The Sales order Attribute number for the carrier service code. This maps to a carrier 'service group' in Metapack Delivery Manager (refer to Creating your Carrier 'Service Groups').

  • The Sales order Attribute number for the currency: a Sales order Attribute that will store data for the Currency Field in Metapack Delivery Manager (refer to Shipping in different currencies).

  • The Sales order Attribute number for the Company name: a Sales order Attribute that will store data for the Company Field in Metapack, generated when Creating an Account.

The fields sent from Peoplevox to Delivery Manager

Depending on the above mappings, the following fields are sent to Metapack Delivery Manager:

  • The Company name (taken from the equivalent Peoplevox Sales order Attribute, if mapped as above).

  • The Sales order number.

  • Your Company address (taken from the Metapack integration data configuration).

  • The Recipient address (taken from the Peoplevox Sales order shipping address).

  • The Recipient's email address (taken from the Peoplevox Sales order).

  • The Recipient's phone number (taken from one of the Sales order Attributes, if mapped following an approach to the Peoplevox help desk). Otherwise, it can be generated from the customer data.

  • The Recipient Contact phone number (taken from one of the Sales order Attributes, if mapped following an approach to the Peoplevox help desk). Otherwise, it can be generated from the customer data.

  • The Parcel number (taken from the despatch package ID automatically created in Peoplevox).

  • The Parcel dimensions (taken from the despatch package dimensions in Peoplevox).

  • The Country of origin (taken from the equivalent Peoplevox Attribute, if mapped as above).

  • Product type description (taken from the equivalent Peoplevox Attribute, if mapped as above).

  • Fabric content description (taken from the equivalent Peoplevox Attribute, if mapped as above).

  • The Harmonised Product Code (taken from the equivalent Peoplevox Attribute, if mapped as above).

  • Information about the despatched items, such as item name, item code, quantity, etc. (taken from the Peoplevox Sales order).

  • Information about the label (taken from the Metapack integration data configuration).

  • The Carrier Service code (taken from the equivalent Peoplevox Sales order Attribute, if mapped as above).

  • The Currency (taken from the equivalent Peoplevox Sales order Attribute, if mapped as above).