SEMA Data as a Source

July 20, 2026

Summary

SEMA Data is a pre-built automotive aftermarket product-data source in Flxpoint. It connects over FTP, SFTP, or FTPS and runs Get Inventory (Primary), importing part numbers, fitment attributes, and images, plus pricing and quantity if your SEMA export template includes them. SEMA Data is a catalog/data feed only; order operations are not part of this integration.

What this integration does

Get Inventory (Primary)

Imports SEMA's part, fitment, and image data from your export template.

How to connect: credentials you need

SEMA Data connects over FTP, SFTP, or FTPS, using the protocol your SEMA export is provisioned for. Add a SEMA Data source, start configuring Get Inventory Primary, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection.

Field	What to enter
ProtocolRequired	FTP, SFTP, or FTPS, as provisioned for your SEMA export.
HostRequired	The FTP/SFTP server where your SEMA Global/Custom Export is delivered.
PortRequired	The connection port.
UserRequired	Your FTP/SFTP username.
PasswordRequired	Your FTP/SFTP password.

Configure the SEMA Custom Export as Pipe Delimited (not comma-delimited), and schedule Get Inventory Primary to run about 30 minutes after the SEMA Global Export so the data has finalized before Flxpoint pulls it. Column names must match exactly (for example, Part Number, not PartNumber).

Important: read before configuring

Use Pipe Delimited, not comma

Configure the SEMA Custom Export as Pipe Delimited. Comma-delimited files are not recommended and cause parsing errors.

Stagger the export and the import

Schedule the SEMA Global Export first, then run Flxpoint Get Inventory Primary about 30 minutes later so SEMA's data has finalized before the pull.

Column names must match exactly

Flxpoint expects exact column names (for example, "Part Number", not "PartNumber"). Mislabeled columns break the import.

Files must arrive as zip archives

Flxpoint opens every file it downloads as a zip (or rar) archive and reads the pipe-delimited .txt brand files inside it. A plain .txt file left on the server is not read. By default only files updated in the last 5 days are downloaded.

Operations: fields to know

Get Inventory (Primary)

Imports SEMA's part, fitment, and image data from your export template.

Field	Maps To: Notes
Product Attributes (name:value pairs separated by ;)	→ Product → Attributes. Each attribute is a name and a value written as name:value, and attributes are separated by a semicolon (;). A pair that does not have exactly one colon is skipped.
Primary	→ Product / Variant → Images. Added as the first image.
Additional Image	→ Product / Variant → Images. Added as an additional image.
Logo	→ Product / Variant → Images. Added as an additional image.
Part Number and the other columns of your export template	→ Product / Variant. Mapped field-by-field from your SEMA Custom Export column names: exact column names are required (for example, "Part Number"). The SEMA export has no price, cost or quantity-on-hand columns.

Common issues

Missing or mislabeled columns in the feed

The import fails or fields come in blank because column names do not match what Flxpoint expects. Verify the names match exactly (for example, "Part Number" vs "PartNumber").

Connection issues pulling the file

Flxpoint cannot retrieve the export. Confirm the FTP credentials, ensure the correct remote directory (for example, /SEMA_Test/), and check firewall or SEMA access settings.

SKUs are archived despite being present in the SEMA feed?

This occurs when the SEMA feed has an inconsistent number of columns per row, often due to a variable count of asset columns like images or PDFs. This causes numeric fields (Weight, Height, Width, Length) to map to asset filenames instead of numbers, triggering a save failure and automatic archiving if Archive Missing Products is enabled. To resolve this, request a feed from SEMA with consistent delimiters (such as double quote string delimiters) or temporarily omit mapping these dimension fields in your Flxpoint mapping template.

FAQs

Which delimiter should the SEMA export use?

Pipe Delimited. Comma-delimited files are not recommended and cause parsing errors.

When should the Flxpoint import run?

Schedule the SEMA Global Export first, then run Get Inventory (Primary) about 30 minutes later so SEMA’s data has finalized before the pull.

Can SEMA deliver more than one file?

Yes. Flxpoint reads every archive it downloads, and each archive can hold several .txt brand files. Each downloaded file must be a .zip, or a rar archive. Plain text files are not read.

Back to Automotive Parts