Customizations

đź§© What Are Customizations?

The Customizations feature lets you upload a spreadsheet to apply updates across large groups of products or listings at once.

This is the fastest way to:

  • Modify product or listing data in bulk
  • Improve or enhance supplier feed data
  • Apply channel-specific changes
  • Lock or override pricing and quantity fields
     

 

 

 

 

Customizing Products vs. Listings

Use the table below to quickly determine which type of customization is the best fit for your use case.

Product Customizations vs Listing Customizations
Quick guide to help you choose the correct customization type.
Use Case Guidance Product Customizations Global scope Listing Customizations Per channel
What it updates Product catalog (core catalog) data Listing data for a specific sales channel
Affects all channels? ✓ Yes — applies to every channel ✕ No — selected channel only
Best for Universal data like titles, MAP, core attributes Channel-specific formatting, pricing, or rules
Common use cases Set MAP, fix weight, normalize options, clean descriptions Add ASINs, meet Walmart rules, lock prices per channel
Pricing & quantity Can update and lock globally Can update and lock per channel
Requires channel selection? âś• No âś“ Yes
Identifier fields Parent SKU / Master SKU Parent SKU or Variant SKU
Great for merchants who… Want consistent catalog data everywhere Need per-channel control
Tip: Global changes → Product Customizations. Channel-specific changes → Listing Customizations.



Why Use Customizations?

Customizations let you:

  • Improve supplier product data or fill missing item fields
  • Add MAP price when it’s not available in a supplier feed
  • Enrich product metadata (titles, descriptions, brand, materials, etc.)
  • Tailor listing data for specific channels without affecting all listings
  • Lock pricing or quantity fields to prevent them from updating from feed imports
  • Update SKUs for existing products or listings
  • Apply bulk updates after data QA and catalog cleanup initiatives
  • Implement flash sale or promo pricing
  • Standardize and apply your business's  product data rules across supplier feeds

     

 

 

 

🛠️ How-to Guides

 

 

How to Create a Customization

The steps below apply to both Product and Listing Customizations. If you're customizing Listings: You must also select the channel the customization applies to. See our comparison table above for help choosing  between Product vs. Listing Customizations.

Follow these steps to access the Customizations tool:

  • Navigate to the Products icon (listed under the Home icon on the left-hand panel).
  • Select the Channel Listings tab at the top of the page.
  • In the upper-right corner, open the Actions menu.
  • Click Customizations under the Import section.
Navigate to Customizations

This opens the Listing Customizations page where all customization uploads are performed.

Once you’re on the Customizations page, you’ll need to choose or create a template. Templates define:

  • Which identifier you’ll match items by
  • Which fields you want to update
  • Whether you're updating Parent or Variant fields
Template selection

How to Create a Template

  • Select your Channel (Listing Customizations only).
  • Select an existing Template, OR click Create New Mapping Template.
  • Click the arrow icon next to the template to open and edit it in a new tab.
  • In the template editor:
  • Add identifier fields such as SKU, UPC, ASIN, or EAN.
  • Add fields you want to change (e.g., List Price, Descriptions, Title, etc.).
  • Pay attention to Parent vs Variant “To Listing” fields and map correctly.

Enter a Template Name.

Click Save Template.

Save template
Important: A Unique Identifier Is Required

Your file must include one unique identifier that matches your Flxpoint data exactly:

  • SKU
  • UPC
  • ASIN
  • EAN

These identifiers must match the values in Flxpoint exactly, including:

  • Spelling
  • Hyphens & spaces
  • Capitalization

⚠️ Critical Note: Be sure to include the right identifier based on the data you want to update:

  • Parent-level fields → use Parent SKU
  • Variant-level fields → use Variant SKU, UPC, etc.

If the identifier or level doesn’t match, the update will not run for that row.

Now that your template is ready, you can upload the file that contains your updates.

Upload customization file

How to Run a Customization

  • Select your Channel (Listings only).
  • Select your Template.
  • Upload your file containing the customization data.
  • Review optional fields (you may leave them blank unless needed).
  • Ensure the File Format matches your file type:
  • .csv
  • .xlsx
  • .tsv

Click Run Listing Customization (or Product Customization).

After submitting the job:
A notification will appear in the top-right corner (đź””) when the run is complete.

You should always verify the customization worked as expected.

Check the Logs

Customization logs
  • Open the Notifications (đź””) icon OR
  • Visit your Logs page from the navigation
  • Locate your customization run
  • Confirm it shows a Success / Completed status

After the customization has successfully completed, go to either Products or Channel Listings (based on the type of customization you performed) and search for the SKU you updated.

You will typically see:

  • The Product or Listing is now Out of Sync, because a customization overrides feed-controlled data
  • Updated values such as Title, List Price, or any other customized fields

For customized fields:

  • Updated Title → Compare against the original value in Source Inventory
  • Updated List Price → Open the Product or Listing to view original vs. customized pricing side-by-side

Tips

🔍 Not Seeing Your Changes?

  • Customizations, never update Source Inventory.
    The Source Inventory always displays original supplier data.
  • Product Customizations update the Product Catalog only.
    To push the updated values to your listings, you may need to Rebuild Listings.
  • Channel Listing Customizations update Channel Listings only and do not affect Products or Source Inventory.

     

🛠️ Ensure Updates Apply Downstream

Depending on your catalog workflow, you may need to perform a:

  • Rebuild — Reprocesses listing data using the updated Product values
  • Overwrite — Forces the updated values onto the connected channel


This ensures that the changes flow correctly to downstream systems.

 

 

 

Locking/Unlocking Pricing and Quantity Fields

 

Customizations can be used to lock certain dynamic fields so they do not update when source feed data changes. Only Pricing and Quantity fields can be locked:

  • List Price
  • Estimated Cost
  • Quantity
  • Shipping Cost

When a dynamic field is locked via Customization, future feed updates will not update that specific field until you explicitly change or unlock it (via another customization or manual edit).

 

Example Use Cases

  • Flash sale on a subset of SKUs
    Lock the list price at a promotional value for specific SKUs while supplier costs continue to update in the background.

     
  • Protecting MAP pricing
    If MAP isn’t reliably provided by the supplier, set and lock MAP values so they stay compliant.

     
  • Holding fixed inventory for a sale or bundle
    Lock quantity for certain SKUs so automatic feed changes don’t disrupt specific marketing campaigns.

     

How to Unlock Quantity Using a Customization

If a listing or product has become locked due to a previous customization (for example, a quantity override), you can unlock it using a simple Customization update.

There are two ways to unlock the quantity, and the easiest is to run a new Customization using only the SKU field.

 

Use this option when you want to unlock quantity for many SKUs at once.

Steps:

  1. Go to Products → Channel Listings.
  2. Open Actions → Customizations.
  3. Select your Channel (if customizing listings).
  4. Choose your existing Mapping Template, OR create a new one for unlocking.
  5. In the Mapping Template:
    1. Include only the Master SKU Variant SKU field as the identifier
    2. Set the Quantity field to Set to Empty.
    3. Leave the all other fields set to Don't Map
  6. Save the template.
  7. Upload a file that contains only the SKUs you want to unlock (no quantity values).
  8. Ensure the file format matches your upload (.csv, .xlsx, or .tsv).
  9. Click Run Listing Customization (or Product Customization).
  10. Wait for the success notification in the top-right bell icon (🔔).

     

When the customization completes, the system removes the quantity lock and shows the quantity derived for linked source inventory.

 

 

Unlock Quantity with a Manual Edit (Single SKU Only)

Use this option when you only need to unlock one product/listing.

Steps:

  • Go to Channel Listings.
  • Search for the SKU.
  • Click into the listing.
  • Locate the Quantity field.
  • Remove or reset the overridden quantity.
  • Save the listing.

     

Manual edits are useful for one-off changes, but bulk unlocking should be done through a Customization file.

⚠️ Important: Only Pricing and Quantity) can be locked using Customizations.
Non-PQS fields (e.g., titles, descriptions, attributes) cannot be locked in this way.

 

 

 

 

Customizations for Large Catalogs

For very large catalogs, Customizations are powerful but should be used thoughtfully.

Recommended approach:

  • Break large customization projects into batches of 100,000 SKUs or fewer.
  • Start with a small test set to validate your:
    • Template mappings
    • File format
    • Logs and results

 

Additional tips:

  • Use meaningful file names that describe the purpose and date (e.g., 2025-12-09_map-update-usa-channel.csv).
  • Keep a record of:
    • Which templates were used
    • What fields were updated
    • Which SKUs were included

 

 

 

Best Practices & Final Tips

  • Decide first: Product vs Listing level based on the table above.
  • Standardize your templates: Reuse consistent templates for recurring operational tasks.
  • Log everything: Keep a documented history of major Customizations for audit and rollback planning.
  • Test before scaling: Always test with a small subset before running changes on your full catalog.

Review logs after every run: Confirm success and handle errors early, rather than discovering issues days later.

 

 

🔍 Troubleshooting & Common Errors

If your customization didn’t behave as expected, review these common issues. Expand each item to learn more.

Troubleshooting Tip: Save a copy of your file with only a few test SKUs and run a small customization first. Once you achieve the desired results with the test SKUs, run the full file.

Â