Magento as a Channel
June 28, 2026
Summary
Connect Magento as a sales channel over the Magento REST API. Flxpoint imports and publishes listings, syncs price and inventory, pulls orders, and writes shipment tracking back. Connection uses your Store URL plus an Access Token you generate from an integration created in your Magento admin. Both simple and configurable products are supported, along with partial shipments.
What this integration does
Import Listings
Pulls existing Magento products and variants into Flxpoint and links them by SKU for centralized management
Sync & Link Listings
Links Flxpoint listings to Magento products by SKU and pushes price, quantity and status updates back
Publish Listings
Creates new Magento products or updates existing ones from Flxpoint listing data
Get Orders
Retrieves Magento orders by status, custom status code and date range into Flxpoint
Sync Orders
Writes shipment tracking and carrier details back to Magento, with partial-shipment support
How to connect - credentials you need
In Flxpoint go to Sales Channels › Create Channel, search for Magento and name the channel. On the Connect Channel screen enter the values below, then click Test Connection & Continue.
Access TokenRequired
Generated in your Magento admin under System › Integrations: click Add New Integration, name it (e.g. "Flxpoint"), and on the API tab grant at least Sales, Catalog, Customers, Stores and System. Click Save, then Activate to reveal the token. Treat it like a password.
Open Magento admin
Store URLRequired
Your Magento store's base URL. Flxpoint calls the REST API (e.g.
Enter the full store URL exactly as your Magento instance is reached.
/rest/V1/products) under this host.API Page SizeSetting
How many records Flxpoint fetches per API call.
Lower it if your Magento server times out on large pages.
250 is a common starting value.Connection NameSetting
A label for this connection in Flxpoint (e.g. "Magento Store").
One connection can be reused across Import, Publish, Get Orders and Sync jobs.
Can't find the token? In Magento the token only appears after you click Activate (not just Save) on the integration. If Test Connection passes but individual jobs fail, your Magento server is most likely blocking Flxpoint's IPs — contact Flxpoint support for the current IP list to whitelist.
Important - read before configuring
Whitelist Flxpoint's IPs if your Magento server restricts by IP
If your Magento host has a firewall or IP allowlist, Flxpoint's outbound IPs must be explicitly whitelisted or API calls will be blocked. Connection tests may pass while individual jobs fail. Get the current IP list from Flxpoint support before troubleshooting other connectivity issues.
"Don't Map" now omits the field from the sync payload entirely
As of June 2025, setting a field to Don't Map in Sync & Link Listings excludes it from the API payload, preserving the existing Magento value (previously it could send an empty or default value). If Magento fields change unexpectedly during a sync, confirm those fields are set to Don't Map.
Image handling depends on the "Override or Delete Existing Images" channel setting
When you map images with Direct Copy in Publish Listings, the default false adds new images without removing existing Magento images; setting it to true replaces all Magento images with whatever is in Flxpoint. Review this channel setting before any bulk publish.
Custom order status codes are case-sensitive Magento status_code values
The Custom Order Status field in Get Orders uses Magento's internal status_code values, not display labels — e.g. unverified, not "Unverified." Values are case-sensitive and comma-separated with no spaces. When transitioning codes, include both the old and new value so no orders are missed.
Mapping - fields to know
| Magento Field | Maps To – Notes |
|---|---|
| SKU | → Listing SKU. Required. Product identifier (Magento sku). |
| Master SKU | → Master SKU. Required. Primary key Flxpoint links on. |
| Name | → Name. Required. Product title (Magento name). |
| Description | → Description. From Magento custom_attributes.description. |
| Price | → Price. Regular price (Magento price). |
| Quantity | → Quantity. On-hand stock (Magento stock_item.qty). |
| Images | → Images. Image URLs from media_gallery_entries. |
| Category One / Two / Three | → Category One–Three. Up to three levels from category_ids. |
| Variant SKU / UPC / Quantity / Price | → matching Variant fields, populated for configurable products from configurable_product_options. |
| Flxpoint Field | Maps To – Notes |
|---|---|
| SKU | → Magento SKU. Required — the only mandatory field; it is the key Flxpoint matches on via PUT /rest/V1/products/{sku}. |
| Price / Special Price | → Magento Price / Special Price (regular and promotional). |
| Stock Quantity | → Magento Stock Quantity. Flxpoint also sends is_in_stock: true whenever quantity is above 0. |
| In Stock | → Magento In Stock status. |
| Status / Visibility | → Magento Status and Visibility (e.g. Enabled; Catalog, Search). |
| Weight | → Magento Weight. |
| Name / Description / Images | Mappable, but not updated by a standard Sync job — use an Overwrite job to change content fields. Set any field to Don't Map to omit it from the payload and keep Magento's value. |
| Flxpoint Field | Maps To – Notes |
|---|---|
| SKU | → Magento SKU. Required. Existing SKU → PUT update; new SKU → POST /rest/V1/products create. |
| Name | → Magento Name. Required. |
| Description / Short Description | → Magento Description / Short Description. |
| Price / Special Price | → Magento Price / Special Price. |
| Stock Quantity / In Stock | → Magento Stock Quantity and In Stock status. |
| Categories | → Magento Categories (e.g. Apparel > T-Shirts). |
| Status / Visibility | → Magento Status (Enabled/Disabled) and Visibility. |
| Images | → Magento Images. With Direct Copy, whether existing Magento images are kept or replaced depends on the Override or Delete Existing Images channel setting. Don't Map preserves existing images; Set to Empty clears them. |
| Variant SKU / UPC / Quantity / Price | → matching Variant fields for configurable products. |
| Magento Field | Maps To – Notes |
|---|---|
| Order ID | → Flxpoint Order ID. Required. |
| Status | → Flxpoint Status. Required. Magento internal status_code (e.g. unverified). |
| Grand Total / Shipping Amount | → Flxpoint Grand Total / Shipping Amount. |
| Coupon Code / Customer Note | → Flxpoint Coupon Code / Customer Note. |
| Date Created | → Flxpoint Date Created. |
| Order Item SKU | → Flxpoint Order Item SKU. Required. |
| Quantity Ordered | → Flxpoint Quantity Ordered. Required. |
| Order Item Name / Price / Item ID / Weight / Discount | → matching Flxpoint Order Item fields. |
| Billing & Shipping Address | Address Line 1–2, City, State, Post Code, Country Code, Telephone, Email, First/Last Name, Company → matching Flxpoint address fields. |
| FFL custom fields | Magento has no native FFL fields; when present they live under extension_attributes. Map each with the cf_ prefix to pull the custom value onto the imported order. |
| Flxpoint Field | Maps To – Notes |
|---|---|
| Carrier | → Magento Carrier Code. Required. |
| Tracking Number | → Magento Track Number. Required. |
| Method | → Magento shipment Method (e.g. Ground). |
| Fulfillment Request Number | → Magento Order ID. Must match the Magento order to avoid an "External Order Item ID Mismatch" error. |
| Shipped At | → Magento shipment Created At. |
| Shipping Cost | → Magento shipment Shipping Cost. |
| Comment | → Magento Shipment Comment. Shown to the customer when Is Visible on Front / Notify Customer are enabled. Partial shipments are supported — only shipped items sync each run. |
Common issues
Sync Listings or Publish Listings job failing with no detailed error message
First check the job's View Logs for item-level API errors. If the connection tests OK but jobs still fail, the most common cause is Flxpoint's IP being blocked by a server-side firewall on your Magento host — connection tests can succeed while data calls are blocked. This also applies after a hosting migration, server reconfiguration or firewall change. Ask your host/IT to whitelist Flxpoint's IPs (get the current list from Flxpoint support).
Publish job overwriting Magento fields that should not change (e.g. url_key)
Magento can auto-populate custom attributes like
url_key in the API response, which Flxpoint may then re-send. Set that specific custom attribute to Don't Map in your mapping template — since June 2025, Don't Map reliably omits it from the payload. If the field isn't visible in your template, ask Flxpoint support to add it as an excludable attribute."Don't Map" for images is removing existing alternative images from Magento
This was a known bug where Don't Map still sent
"media_gallery_entries": [], which Magento read as "clear all non-base images." It has been addressed — Don't Map should now omit the media gallery field entirely. If images are still cleared, confirm you're on the latest integration version and raise a ticket with example SKUs.Orders not importing — order exists in Magento but not in Flxpoint
Check, in order: the order's Magento status code matches one of your Get Orders status filters (Custom Order Status is case-sensitive); the Get Orders Created Within the Last X Days window covers the order's date. If it still doesn't import, use View Logs and contact Flxpoint support with the Magento order number.
Configurable product SKU mismatch causing Sync Orders to fail on line items
Magento configurable products generate order line items using the parent product's item ID rather than the simple variant SKU. Enable Use Parent Item ID Instead of Item ID in Get Orders so the external order item ID matches during Sync Orders. Orders imported before enabling this may need to be re-imported.
Publish job stuck at a percentage or showing "pending action" and not progressing
A job stuck for hours usually means Magento is returning 500 errors on individual items without clear messages. Check View Logs — 500s typically indicate a Magento-side issue (missing attribute sets, invalid category IDs, or a plugin conflict). Publish a single known-good SKU to isolate it, and confirm no Flxpoint IP blocks are active on the Magento server.
FAQs
How do I generate the Access Token needed to connect Magento to Flxpoint?▸
In your Magento admin go to System › Integrations and click Add New Integration. Name it (e.g. "Flxpoint"), enter your admin password, and on the API tab grant at least Sales, Catalog, Customers, Stores and System. Click Save, then Activate to generate the Access Token. Copy it into Flxpoint's Magento channel setup along with your Store URL and a page size (
250 is a common starting value).How do I import only specific order statuses from Magento?▸
Use the Custom Order Status field in Get Orders. Enter Magento's internal
status_code values (not display labels), comma-separated with no spaces — e.g. pending,unverified. It uses logical OR, so an order matching any listed code is imported. Leave it blank to fall back to the multi-select status filter; if both are populated, both apply as a logical OR.Does Sync Orders support partial shipments?▸
Yes. Only the portion of order items that have shipped is synced to Magento in a given run, so you can fulfill an order incrementally. The mapping template requires at minimum Carrier Code and Track Number for shipment sync to work.
How do I control whether customers are notified when a shipment is synced back?▸
In Sync Orders settings, enable Notify Customer to have Magento email the buyer when tracking is synced. You can also enable Is Visible on Front to show the shipment comment on the order status page in your storefront, and Append Comment to attach a note alongside the tracking notification.
Import Listings cannot be scheduled — how should I run it?▸
Import Listings must be triggered manually; it cannot be put on an automated schedule. Run it when you need a fresh batch of products from Magento, such as after adding new products in your store. Use the Set New Listings to Paused option on first import to review and verify products before they go live in Flxpoint.