• Publish new product listings from Flxpoint to Magento, creating new products as needed.
• Update existing Magento products with the latest data from Flxpoint (e.g., price, stock quantity).
• Ensure your Magento store reflects accurate and up-to-date product information for sales.
• Support both simple and configurable products for comprehensive catalog management.

• Product Check: Checks if the product exists in Magento using the SKU. If it exists, the integration updates the product; if not, it creates a new one.
• Data Mapping: Maps Flxpoint listing fields to Magento product fields using a configurable mapping template (e.g., Flxpoint’s "Name" to Magento’s "name").
• Publishing: Sends a POST request to /rest/V1/products to create a new product, or a PUT request to /rest/V1/products/{sku} to update an existing product.
• Handle Variants: For configurable products, publishes variant details like SKU, UPC, quantity, and price using the same SKU-based linking.
• Error Handling: Logs errors if the publish fails due to validation issues (e.g., missing required fields) or duplicate SKUs.
• Publishing Schedule: Listings can be published manually or on a schedule (e.g., daily at 8 AM UTC).

• Fields to Publish: Choose which fields to publish (e.g., Name, Price, Stock Quantity) via the mapping template.
• Update Existing Products: Enable or disable updates for existing products (options: Yes/No in job settings).
• Create New Products: Enable or disable creation of new products if they don’t exist in Magento (options: Yes/No in job settings).
• Scheduling: Run the integration manually or schedule it (e.g., daily at 8 AM UTC).
• Mapping Template: Define how Flxpoint listing fields map to Magento product fields for accurate publishing. This is crucial for controlling the data sent.

• 1 Add the Integration: Navigate to the Integrations section, select Magento as the integration type, and choose “Publish Listings.”
• 2 Connect to Magento: Select an existing Magento connection or set up a new one using your Magento API credentials. This involves configuring your Magento store URL, access token, and other necessary authentication details.
• 3 Configure Publish Job Settings: Set options like whether to update existing products, create new products, and define the publishing schedule.
• 4 Create/Configure Mapping Template: Define how Flxpoint listing fields map to Magento product fields (see Mapping Templates section below). Pay close attention to image mapping options.
• 5 Configure Advanced Channel Settings (if applicable): For specific behaviors like image overwriting, check the main Magento Channel Configuration for advanced settings (see Magento Channel: Advanced Image Publishing Configuration section below).
• 6 Run the Integration: Start the integration manually with Run Sync or let it run on your configured schedule.

• The mapping screen is labeled “Magento - Publish Listings” with sections for field mappings.
• Common Actions: Buttons for Delete, Duplicate, and Save the publish job or mapping template.
• Key Areas in the Publish Job configuration:
  • Settings: Options like Update Existing Products, Create New Products, and Scheduling.
  • Mapping Template Area: Access to define how Flxpoint fields (e.g., Listing fields like SKU, Name) map to Magento Product Fields (e.g., sku, name).

• Current Date and Time: Information as of May 20, 2025. This integration is fully operational for publishing listings to Magento.
• Magento Integration: Connects to your Magento store via the /rest/V1/products endpoint to create or update product listings. Connection settings are configured through your Magento channel setup in Flxpoint.
• Publishing Process: Creates new products with a POST request or updates existing ones with a PUT request, based on the SKU.
• Data Validation: Ensures that required fields (e.g., SKU, Name) are provided and meet Magento’s validation rules to avoid publishing errors.
• Variant Support: Supports publishing configurable product variants, ensuring variant-specific fields like SKU, UPC, and price are correctly mapped.

• The mapping screen is typically labeled “Flxpoint → Magento” within the “Publish Listings” job configuration.
• Actions: Buttons like Cancel and Save Mapping.
• Structure: Usually a two-column layout showing Flxpoint source fields and corresponding Magento destination fields.

• Don’t Map: Flxpoint will not send any data for this Magento field.
• Set To Empty: Flxpoint will send a request to clear any existing data in this Magento field.
• Field: Map a specific Flxpoint field (e.g., Listing’s “Name”) to a Magento field. This is the most common option.
• Value: Set a fixed, constant value to be sent for this Magento field for all listings processed by this template.
• Mapping Set: Apply a predefined transformation, lookup table, or rule-based mapping.

• From Listing: SKU, Name, Price, Special Price, Stock Quantity, In Stock Status, Visibility, Description, Short Description, Images (URLs), Categories, Weight, Product Type, Created At, Updated At, and any custom attributes.
• From Variant (if applicable): SKU, UPC, Quantity, Price, and variant-specific attributes.

A specific configuration option in your Magento channel settings controls how images are handled when you use the "Direct Copy" image mapping option (or map your image source field) in your Publish Listings mapping template for Magento.

• Location of Setting in Flxpoint: This setting is found within the main configuration area for your Magento sales channel integration (often under an "Advanced Settings" or "Configuration" tab or section specific to the Magento channel itself).
• Available Options:
  • False (This is the Default Setting)
  • True

When "Direct Copy" (or your image source field) is used for images in your mapping template:

• If "Override or Delete Existing Images" is set to False (Default):
  • Flxpoint will add the images from your product data to the Magento listing.
  • Any images already existing on the Magento product listing will be preserved. New images from Flxpoint are added alongside these existing ones.
  • Use this setting if: You want to add new images from Flxpoint to your Magento listings without affecting images already present on Magento.
  • Note: If a product is unlinked from Flxpoint and then re-linked, and this option is False, Flxpoint may add images again if it cannot match them to existing Magento image IDs, potentially leading to duplicate images on the storefront.
• If "Override or Delete Existing Images" is set to True:
  • Flxpoint will replace the entire set of images on the Magento product listing with the images currently available in your Flxpoint product data for that item.
  • Any images existing on the Magento product that are not present in the current Flxpoint data for that product will be deleted from the Magento listing.
  • Use this setting if: You want Flxpoint to be the definitive source for your product images on Magento, ensuring the Magento listing exactly mirrors the image set defined in Flxpoint with each update.

• Publish Failure:
  • Check the mapping template for missing required fields (e.g., SKU, Name) or invalid data (e.g., duplicate SKUs).
  • Ensure that image mappings and related advanced channel settings (like "Override or Delete Existing Images") are configured correctly for your intended outcome.
• Validation Errors:
  • Ensure that the data being published (e.g., Price, Stock Quantity) meets Magento’s validation rules (e.g., numeric values for price).
  • Verify that image URLs are valid if using "Direct Copy" for image mapping.
• Connection Issues:
  • Ensure your Magento API credentials (e.g., access token) in the Magento Channel configuration are valid and have the necessary permissions.
  • Test the connection using any "Test Connection" feature available in the Magento Channel settings.
• Check Logs:
  • Use the "View Logs" option for the Publish Listings job to identify any API errors (e.g., 400 for invalid data, 409 for duplicate SKU) or mapping issues.
  • Contact Flxpoint support if problems persist, providing log details and the affected SKU for investigation.