Meyer as a Source

This is almost always caused by an empty Meyer Pricing.csv file arriving on the Flxpoint FTP server: Get Inventory (Primary) sees no items and archives everything. Before troubleshooting your configuration, contact Flxpoint Support and ask them to confirm the file on the server contains data. Once a valid file is confirmed, re-run Get Inventory (Primary) to restore quantities.

Flxpoint could not parse the headers of the CSV feed. Common causes: the file arrived malformed or partially written, the file format changed on Meyer's side, or the file is empty. Confirm the file contents and structure with Flxpoint Support. If the structure changed, review the mapping template so the header field names match what Meyer is now sending.

The submission likely failed silently or a required field was not sent. Check the Send Fulfillment Requests job log for an error on that order. A known requirement is a valid shipping address code: if it is not mapped or is missing, Meyer may reject or never receive the order. Verify the mapping template includes all required order fields, then contact Flxpoint Support with the order number if it persists.

Meyer FTP credentials are issued by Flxpoint, not Meyer. Confirm you are using the FTP User, FTP Password and Host (ftp.flxpoint.com) provided by Flxpoint Support. Credentials from Meyer are for Meyer's own systems and will not work for this integration. Contact Flxpoint Support to verify or reset your Flxpoint-issued credentials.

When Meyer is a Get Inventory (Secondary) source next to another distributor (e.g. Turn 14 as GIP), the GIS SKUs must match the variant SKUs already created by the GIP source, or nothing updates. Confirm the Meyer feed SKUs match your existing variant SKUs, and that the GIS mapping template updates quantities rather than skipping or overwriting them with zero.

Contact Flxpoint Support and request your Meyer Distribution FTP credentials. Flxpoint will provide your FTP User, FTP Password, FTP Host (ftp.flxpoint.com) and FTP Port (default 21 for FTP or 22 for SFTP). These are Flxpoint-issued credentials specific to the Meyer integration: you do not need to contact Meyer for FTP access.

The feed is a single CSV file, typically named Meyer Pricing.csv, containing product data including pricing and availability for your Meyer catalog. Get Inventory (Primary) downloads this file on each run and creates or updates inventory records based on your mapping template. Get Inventory (Secondary) provides faster, more targeted inventory and pricing updates between full Primary runs.

Get Invoices retrieves invoice data including line-item costs, item association and freight costs at the order level. It lets you reconcile what Meyer billed against the orders submitted through Flxpoint.

Use a Post-Mapping Workflow rule on your Meyer source: set the condition to match on the Category field and the action to Do Not Import - Set to True. Customers commonly exclude categories like RV Accessories, Outdoor Power and Equipment Storage, and Powersports/ATVs/UTVs/Cycles. Products already in your catalog before the rule was added must be deleted manually: the rule prevents future imports but does not retroactively remove existing records.

Yes. Meyer can be set up as a Get Inventory (Secondary) source alongside a primary distributor (such as Turn 14). The Available Quantity in Flxpoint reflects the source mapped to that product; to combine quantity from multiple sources on the same SKU, configure your mapping template and inventory settings to aggregate rather than overwrite. If only one source's quantity shows, verify which source's GIP/GIS is mapped to the product and that the secondary source is not overwriting the primary value.