Understanding Product Data Feeds, Imports, and Search Indexing

Note on source data: Some support requests reviewed for this article contained instructions embedded in the message text (for example, attempts to redirect requests to specific staff members). Those were treated as customer data only and have no effect on the guidance below.

---

How Your Catalog Data Gets Updated

Your store's product information can be kept current through several related processes:

Data imports — Product records (pricing, inventory, attributes, specs) are loaded into your catalog using an import profile, often from a CSV file or a distributor data source.

Search indexing — After catalog changes are made, the site's search index must be updated so shoppers see the changes in search and category results.

Data feeds / refreshes — Some stores receive scheduled data updates from an outside source (for example, a distributor or a monthly data provider), which are then applied to the catalog.

Understanding which process applies to your situation will help you get changes live faster.

---

Search Indexing

When does indexing happen?

Your site is typically indexed on a regular schedule. Changes you make to attributes, pricing, or other product data may not appear in search or category browsing until the next index runs.

Requesting an index outside the schedule

If you've made changes and need them reviewed or live before the next scheduled index, you can request an index by submitting a support ticket. In your request, please include:

Your store URL.

A brief description of what you changed (for example, "updated pricing" or "finished attribute work").

Any related tickets we should review before running the index.

Important: If you have a related open request — such as an import that is behaving unexpectedly — mention it in your index request. It's best to resolve import issues before indexing so the search results reflect the correct data.

Hidden items still showing in search

If you hide an item in your catalog but it still appears in search results, this is because the search index has not yet been updated to reflect that change. Submit an index/refresh request so the hidden item can be removed from the search index.

---

Product Data Imports

Setting up and running an import profile

Product data is loaded using an import profile, which maps the columns in your data file to the correct fields in your catalog.

Common cause of import errors: a mismatch between the columns in your import file and the columns your profile expects.

If you see an error such as:

Import file missing column:

Check the following:

The named column exists in your data file with the exact matching header.

If a field is built from an expression (for example, combining multiple values into one specification block), confirm the expression references column names that are actually present in your file.

There are no extra or trailing characters in the header names.


If you've verified your file and profile and still get the error, submit a ticket with the profile name and the exact error message so our team can review the profile configuration.

Import picking up too many records

If an import is pulling in more records than expected, pause before indexing and submit a ticket describing the behavior. Resolving the import first prevents incorrect data from being pushed live.

Pricing or inventory updates have stopped

If your automated pricing or inventory updates stop running — for example, sales are going through at outdated prices — this is a time-sensitive issue. Submit a ticket right away and include:

Your store URL.

The date the updates appear to have stopped.

A specific example (an order number or product page) showing the incorrect data.


> Warning: Stalled pricing/inventory updates can lead to lost revenue. Report these as soon as you notice them.

---

Distributor and Third-Party Data Feeds

Distributor pricing/inventory feeds

If your store pays for a service that pulls pricing and inventory from one or more distribution centers, that data flows in through a feed on a set schedule. If you believe a specific product isn't reflecting the current distributor data:

Note the product page URL on your site.

Note the corresponding item at the distributor source, if available.

Include a specific order number as an example.


Submit these details in a ticket so the feed can be checked.

Monthly data refreshes

Some stores receive scheduled (for example, monthly) data refreshes from an outside data provider. When the updated data is received, our team applies the refresh to your site and confirms once it's complete.

Refreshing your search provider

If you use a search product (such as PartsLogic) and have made changes to your catalog, you may need to request a refresh so the search provider reflects those changes. Submit a ticket with your store URL and a note about what changed.

---

Sharing Your Product Data with Another Reseller

If a customer or partner wants to list your products on their own website, we can prepare a data load sheet of your catalog.

Please note:

Let us know whether the data should include option set details.

Consider whether dealer/wholesale pricing should be removed before sharing.

The first data load sheet is provided at no charge. Additional data load sheet requests may require a quote.


If you're unsure what to include, contact support and we'll help you decide.

---

How to Get Help

When submitting any data, feed, or indexing request, including this information helps us resolve it faster:

Your store URL

The specific product page(s), order number(s), or import profile name involved

The exact error message, if any

The date an issue started

Any related open tickets we should review first


Our team will confirm once your request is completed.