How do I Prepare an Export for Custom Mapping?

Hailey Edge
  • Updated
Follow

This guide describes the requirements of a third party product data export provided to LBMX to create a custom map to be ingested into the LBMX OnePIM/OnePDX.

Quick Links

Custom Map Overview

The Custom Map is great for suppliers who have a SKU list that changes over time and already store their product data in a PIM or ERP. This is the least labour-intensive option for the supplier, however it requires the supplier to be able to provide an identically formatted export of their data at regular intervals. The Custom Map requires the supplier to export their data in a uniform manner and deposit it into a shared drive, the custom mapping tool then reworks the data, and inject it into the LBMX PIM.

 

Formatting Requirements & Recommendations

When creating an export template from a third party PIM or ERP it is important to ensure that the template is repeatable with ease.

For best results we recommend cleaning up the data within your PIM or ERP and implementing requirements in which new information is added, so that exports can be provided to LBMX in the cleanest and most optimal condition.

 

Product data exports are required to follow these principals:

  1. All SKUs must be included
  2. CSV format
  3. All product data is on one sheet/tab (no cross reference pages)
  4. Parameters within a column do not change
    • E.g. If measurement is always provided as a numeric input with 2 decimal places a new field is not added as a fraction, etc.
  5. Recurring loads must ensure all headers are exported in the same order and new headers are not added, duplicated, or removed
  6. Assets are provided by 

*Failure to follow any of these requirements could result in a remapping fee

 

Product data exports are recommended to follow these additional principals:

  1. Delimiters are consistent and delimiter is not used in marketing descriptions
    • E.g. comma (,), pipe (|), semicolon (;), etc.
  2. Null cells are left blank and not any combination of the following:
    • N/A, #NULL!, #VALUE!, FALSE, etc.
  3. Every measurement field has an accompanying Unit of Measure field
    • Consumer Item - Length "1.25" AND Consumer Item - Length UOM "IN"

 

Asset Requirements

File Format Requirements

OnePIM supports the following file formats:

Delivery Requirements

Assets are required to be provided by one of two methods:

  1. Assets URL 
  2. SFTP Delivery
    • Files provided are the supported file type (.
    • File names are cross referenced on the provided product data export

Screenshot 2023-09-05 104813.png

File Size Requirements

  • Files must be a maximum of 500mb, larger files are not supported

Naming Requirements

  • Assets must be named uniquely to other products with the same file extension
    • E.g. warranty.pdf and warranty.jpg will be two different assets
  • Assets uploaded with the same name and file extension as a previously provided asset will replace the old asset
    • warranty.pdf will replace all other assets on your account named warranty.pdf
  • Multiple products may share the same asset

Minimum/Maximum Assets Per Product

Each product must contain a minimum of 1 asset:

  • Primary Image File Name (

Each product may contain a maximum of 31 assets broken up as follows:

  • Primary Image File Name 1 (
  • Secondary Image File Name 1-10 (
  • Video File Name 1-10 (
  • Document File Name 1-10 (

 

Required and Recommended Fields

⚠️ All Product Fields

We recommend suppliers send all Product Fields/Attributes from their PIM or ERP. We will do our best to match your fields to a Product Field in LBMX's OnePIM. Fields we cannot match will be considered as an addition to our existing Product Field offerings.

 

The minimum required fields all products provided to LBMX OnePIM are:

  • Product ID (Product SKU or other unique identifier)
  • Product Description (Product name for ECommerce)
  • Brand Name
  • UPC
  • Consumer Product - Length
  • Consumer Product - Width
  • Consumer Product - Height
  • Consumer Product - Net Weight (Actual product weight, if multi-pack weight of single unit)
  • Consumer Product - Length UOM (What is Consumer Product - Length measured in?)
  • Consumer Product - Width UOM (What is Consumer Product - Width measured in?)
  • Consumer Product - Height UOM (What is Consumer Product - Height measured in?)
  • Consumer Product - Net Weight UOM (What is Consumer Product - Net Weight measured in?)
  • Short Marketing Description (Short description for ECommerce)
  • Primary Image File Name (Hero photo of product, if not photo then include brand logo image)

The recommended fields for all products provided to LBMX OnePIM are:

  • Unit of Measure (What is each product counted by? Each, Bag, Jar, Box etc.)
  • Consumer Package Quantity (How many units come in one consumer package?)
  • Consumer Package Unit of Measure (What is each unit in the consumer package contained in? Each, Bag, Jar, Box etc)
  • Consumer Package - Length
  • Consumer Package - Width
  • Consumer Package - Height
  • Consumer Package - Weight (Weight of product with packaging)
  • Consumer Package - Length UOM (What is Consumer Product - Length measured in?)
  • Consumer Package - Width UOM (What is Consumer Product - Width measured in?)
  • Consumer Package - Height UOM (What is Consumer Product - Height measured in?)
  • Consumer Package - Net Weight UOM (What is Consumer Product - Net Weight measured in?)
  • Supplier Hierarchy (Hierarchy exported from supplier ECommerce)
  • Colour Name
  • Material
  • Available Date (Date available to distributor)
  • Show Online Start Date (Products will only be eligible to show on eCommerce past this date)
  • MSRP
  • Long Product Name
  • Long Marketing Description
  • Features | Benefits
  • Key Words
  • Product Bullets 1-5
  • Country of Origin Code
  • Secondary Image File Name 1-10
  • Video File Name 1-10
  • Document File Name 1-10

🧩 Master Product Field List

Download the LBMX PIM PDX Master Product Field List to view all Product Fields available

 

Not Seeing a Necessary Product Field?

LBMX continues to research and create Product Fields as we represent new sectors and industries. If you do not see a Product Field you believe to be necessary to your product offerings please reach out to your PIM Analyst or emailing support@lbmx.com

 

Recurring Uploads

Updated product data must be uploaded to the assigned SFTP location at a regular interval as determined by LBMX. Updated data must be provided in a CSV export that is formatted identically to the export your Custom Map was created for. If providing assets via SFTP you may only upload new assets with recurring uploads.

*Failure to follow any of these requirements could result in a remapping fee

 

Support

If you have any questions about working with OnePIM or OnePDX, please contact the LBMX Support Team at support@lbmx.com.

Related articles

Comments

0 comments

Article is closed for comments.