Flxpoint Help Center
All DocsContact support

Customizations

June 26, 2026

Summary

Customizations let you upload a spreadsheet (.csv, .xlsx, or .tsv) to bulk-update products or listings, enhance supplier feed data, apply channel-specific changes, and lock pricing or quantity fields so they stop updating from feeds. Covers Product vs Listing scope, mapping templates, running a job, locking PQS fields, and common errors.

Customizations let you upload a spreadsheet (.csv, .xlsx, or .tsv) to apply updates across large groups of products or listings at once. Use them to modify product or listing data in bulk, enhance supplier feed data, apply channel-specific changes, and lock or override pricing and quantity fields.

Bulk update by spreadsheet
Match items by a unique identifier and update the fields you map in a template - across many SKUs in one run.
Product vs Listing scope
Product Customizations apply globally (core catalog); Listing Customizations apply to one selected channel only.
Lock pricing & quantity
Lock List Price, Estimated Cost, Quantity, or Shipping Cost so feed imports stop overwriting them.
Out of Sync after run
A customized item shows Out of Sync because the customization overrides feed-controlled data.

Decide which scope you need before building a template. The rule of thumb: global changes use Product Customizations; channel-specific changes use Listing Customizations.

 Product CustomizationsListing Customizations
ScopeGlobalPer channel
What it updatesProduct catalog (core catalog) dataListing data for a specific sales channel
Affects all channels?Yes - applies to every channelNo - selected channel only
Best forUniversal data like titles, MAP, core attributesChannel-specific formatting, pricing, or rules
Common use casesSet MAP, fix weight, normalize options, clean descriptionsAdd ASINs, meet Walmart rules, lock prices per channel
Pricing & quantityUpdate and lock globallyUpdate and lock per channel
Requires channel selection?NoYes
Identifier fieldsParent SKU / Master SKUParent SKU or Variant SKU

These steps apply to both Product and Listing Customizations. For Listing Customizations, you must also select the channel the customization applies to.

1
Navigate to Customizations
  1. Go to the Products icon (under the Home icon on the left-hand panel).
  2. Select the Product Catalog or Channel Listings tab at the top of the page, depending on whether you're customizing products or listings.
  3. In the upper-right corner, open the Actions menu.
  4. Click Customizations under the Import section.
2
Create or select a template
  1. Select your Channel (Listing Customizations only).
  2. Select an existing template, or click Create New Mapping Template.
  3. Click the arrow icon next to the template to open and edit it in a new tab.
  4. In the editor: add identifier fields (SKU, UPC, ASIN, or EAN), add the fields you want to change (e.g. List Price, Descriptions, Title), and map Parent vs Variant "To Listing" fields correctly.
  5. Enter a Template Name and click Save Template.
3
Upload & execute your file
  1. Select your Channel (Listings only) and your Template.
  2. Upload the file containing your updates.
  3. Ensure the File Format matches your file type:
.csv.xlsx.tsv
  1. Click Run Listing Customization (or Product Customization). A notification appears in the top-right bell icon when the run completes.
4
Verify the run completed
  1. Open the Notifications bell icon, or visit your Logs page.
  2. Locate your customization run and confirm it shows a Success / Completed status.
5
Review the updated product or listing
  1. Go to Products or Channel Listings (based on the type you ran) and search for an updated SKU.
  2. The item is now Out of Sync (a customization overrides feed-controlled data), and you should see your updated values such as Title or List Price.
  3. Compare updated Title against the original value in Source Inventory; open the item to view original vs. customized pricing side-by-side.

Your file must include one unique identifier that matches your Flxpoint data exactly - including spelling, hyphens, spaces, and capitalization. Eligible identifiers:

SKUUPCASINEAN
Match the identifier to the field level you are changing: Parent-level fields use the Parent SKU, and Variant-level fields use the Variant SKU, UPC, etc. If the identifier or level doesn't match, the update will not run for that row.

Customizations can lock certain dynamic fields so they do not update when source feed data changes. Once locked, future feed updates will not touch that field until you explicitly change or unlock it. Only these Pricing and Quantity (PQS) fields can be locked:

List PriceEstimated CostQuantityShipping Cost
Use caseHow locking helps
Flash sale on a subset of SKUsLock the list price at a promotional value while supplier costs keep updating in the background.
Protecting MAP pricingWhen MAP isn't reliably supplied, set and lock MAP values so they stay compliant.
Holding fixed inventoryLock quantity for certain SKUs so automatic feed changes don't disrupt a sale or bundle campaign.

To unlock quantity in bulk (recommended): open Actions → Customizations, select your channel and template, include only the Master/Variant SKU field as the identifier, set the Quantity field to Set to Empty, leave all other fields as Don't Map, then upload a file with only the SKUs to unlock and run it. When it completes, the system removes the quantity lock and shows the quantity derived from linked source inventory.

To unlock a single SKU manually: go to Channel Listings, search the SKU, open the listing, remove or reset the overridden Quantity value, and save. Use manual edits only for one-off changes - bulk unlocking should go through a Customization file.

Customizations never touch Source Inventory
Source Inventory always displays the original supplier data. If you don't see your changes there, that's expected - check the Product Catalog (for Product Customizations) or Channel Listings (for Listing Customizations) instead.
Product changes may not reach listings automatically
Product Customizations update the Product Catalog only. To push those values to your listings you may need a Rebuild (reprocesses listing data using the updated Product values) or an Overwrite (forces values onto the connected channel).
Only PQS fields can be locked
Locking works only on Pricing and Quantity fields (List Price, Estimated Cost, Quantity, Shipping Cost). Non-PQS fields like titles, descriptions, and attributes cannot be locked this way.
Large catalogs need batching
Break large projects into batches of 100,000 SKUs or fewer, and always validate template mappings, file format, and logs against a small test set before running the full file.
1
"Nothing updated" or fewer rows updated than expected
  • Check that identifiers (SKU/UPC/ASIN/EAN) in your file match Flxpoint exactly.
  • Confirm the template is mapped to the correct fields.
  • Verify the correct level (Product vs Listing) and the correct Channel for Listing Customizations.
2
"Wrong field changed" or no visible change
  • Double-check whether the field is parent or variant level.
  • Confirm you used the appropriate Parent SKU or Variant SKU in the file.
  • Verify the change in the right place - Product page vs Channel Listing page.
3
Pricing or quantity values still changing after a customization
  • Confirm the field you expected to lock is actually a PQS field and is configured to lock.
  • If feeds keep overriding, re-run a Customization with the correct locking settings or manually review the item's PQS configuration.
4
Errors in the customization job logs
Open the Logs view for that customization and review error messages for an invalid file format, missing required headers, or mismatched field names.
When should I use Product vs Listing Customizations?
Use Product Customizations for global changes that should apply across every channel (titles, MAP, weight, core attributes). Use Listing Customizations when you need per-channel control such as adding ASINs, meeting a specific channel's rules, or locking prices on one channel only - these require selecting the channel.
Why is my item now "Out of Sync" after a customization?
That's expected. A customization overrides feed-controlled data, so the product or listing shows Out of Sync to indicate it no longer matches the raw feed values.
I ran a customization but don't see my changes in Source Inventory.
Customizations never update Source Inventory - it always shows the original supplier data. Product Customizations update the Product Catalog only, and Listing Customizations update Channel Listings only. You may also need a Rebuild or Overwrite for changes to flow downstream.
Which fields can I lock?
Only Pricing and Quantity (PQS) fields: List Price, Estimated Cost, Quantity, and Shipping Cost. Non-PQS fields like titles, descriptions, and attributes cannot be locked through a customization.
How do I unlock a quantity that a previous customization locked?
Run a new customization that includes only the SKU field as the identifier, set the Quantity field to Set to Empty, and leave everything else as Don't Map. Upload a file with only the SKUs to unlock. For a single item you can instead open the listing and remove the overridden quantity manually.
How big can a customization file be?
For very large catalogs, break the work into batches of 100,000 SKUs or fewer. Always test with a small subset first to validate your template mappings, file format, and results before scaling to the full file.
Β© 2026 Flxpoint. All rights reserved.