Magento as a Source
July 2, 2026
Summary
Magento as a Source connects your Magento store to Flxpoint over Magento's REST API, treating the store as a supplier you pull products and inventory from. You authenticate with an Access Token generated in Magento Admin under System → Integrations, plus your Store URL, and all four operations reuse that same connection to import the catalog and inventory, submit orders, and pull back shipment tracking.
What this integration does
Get Inventory (Primary)
Imports the full Magento catalog – SKU, title, description, brand, quantity, price, UPC, weight, images and categories
Get Inventory (Secondary)
Enriches products with secondary data – dimensions, shipping cost, GTIN and up to 100 custom fields
Send Fulfillment Requests
Submits fulfillment requests to Magento, creating purchase orders with billing, shipping and item details
Get Shipments
Pulls shipment tracking numbers, carrier and ship dates back into Flxpoint
How to connect - credentials you need
Add a source, start a Get Inventory (Primary) job, then click + New Connection and enter your Access Token and Store URL. Click Test Connection → Save Connection. All four operations reuse this one connection.
Access TokenRequired
The API access token from your Magento store. Generate it in Magento Admin under System → Integrations: add a new integration, open the API tab, set Resource Access, then click Save → Activate to reveal the token.
The token is shown only once on activation — copy it immediately. If it is lost, deactivate and reactivate the integration to generate a new one.
Store URLRequired
The full base URL of your Magento store, including the protocol and with no trailing slash — e.g.
A missing https://yourstore.com. It must match your Magento admin login URL base.https:// or a trailing slash will cause Test Connection to fail.
API Page SizeSetting
How many records Magento returns per API request for Get Inventory (Primary) and (Secondary). Lower it (e.g. to 100) if runs return partial data or time out under Magento's rate limits.
Reduce this first if you see HTTP 429 or timeout errors.
If Test Connection fails with a 401, the token is wrong, expired, or the integration was deactivated — regenerate it. A 403 means the token is valid but its API scope is missing a resource; add the required Catalog or Sales permission in Magento Admin → API tab, save, and reactivate.
Important - read before configuring
Access Token must include the correct Magento API scope
Generate the token in Magento Admin → System → Integrations. You can grant Resource Access = All (simplest) or restrict to the minimum: Catalog (Products, Categories, Attributes) and Sales (Orders and Shipments). If Send Fulfillment Requests fails with a 403, confirm Sales → Operations → Orders is included; if Get Shipments fails, confirm Sales → Operations → Shipments is included.
Store URL must include https:// with no trailing slash
The Store URL field requires the full URL with the protocol: https://yourstore.com — not yourstore.com or https://yourstore.com/. A missing protocol or a trailing slash will cause Test Connection to fail. Confirm it exactly matches your Magento admin login URL base.
Archive/Un-Archive can only be enabled on one of GIP or GIS
Flxpoint enforces this at the setting level – Archive/Un-Archive Inventory can be turned on for Get Inventory (Primary) or Get Inventory (Secondary), never both at once. In Get Inventory (Primary), also configure the field values to submit for Manufacturer Code, UPC Code, Image URL, Website ID and Store View Code so the correct catalog and storefront data is pulled.
Send Fulfillment Requests requires FR Number, SKU, and a complete billing/shipping address
Map every required billing and shipping field — Address Line 1, City, Country Code, First Name, Last Name, Postal Code — plus Fulfillment Request Number and SKU. Missing any of these makes Magento reject the order creation via API.
Mapping - fields to know
| Magento Field | Maps To – Notes |
|---|---|
| SKU | → SKU. Required — uniquely identifies the product (e.g. ABC123). |
| Name | → Title. Required — the product title. |
| Description | → Description. Required — the product description. |
| Manufacturer | → Brand. Required — the product brand. |
| Quantity | → Quantity. Required — on-hand stock level from the variant. |
| Price | → Source List Price. Optional — the product price. |
| UPC | → UPC. Required — universal product code from the variant. |
| Weight | → Weight. Optional — product weight. |
Required fields are SKU and Quantity. GIP also imports images, categories (up to 3 levels) and product attributes via
/V1/products, /V1/categories and /V1/products/attributes. Enable Fetch All Attributes if fields like manufacturer code or UPC are storefront-hidden. Recommended schedule: daily.| Magento Field | Maps To – Notes |
|---|---|
| Height | → Height. Optional — product height. |
| Width | → Width. Optional — product width. |
| Length | → Length. Optional — product length. |
| Dimension Unit | → Dimension Unit. Optional — map this whenever you sync dimensions so values display in the correct unit (e.g. inch, centimeter). |
| Shipping Cost | → Shipping Cost. Optional — per-item shipping fee. |
| GTIN | → GTIN. Optional — global trade item number. |
| Custom Field 1 / 2 … | → Custom Field 1 / 2 …. Optional — one row per custom attribute (e.g. Color, Size). |
No required fields. Enable Fetch Custom Fields to pull up to 100 custom attributes defined in Magento. Run GIS after GIP on a more frequent schedule to keep enriched data fresh, and leave Archive/Un-Archive off on GIS.
| Your Field | Maps To (Magento) – Notes |
|---|---|
| Address Line 1 | → Address Line 1. Required — for both the billing and shipping address blocks. |
| City | → City. Required — billing and shipping. |
| Country Code | → Country Code. Required — e.g. US. |
| First Name | → First Name. Required — billing and shipping. |
| Last Name | → Last Name. Required — billing and shipping. |
| Postal Code | → Postal Code. Required — billing and shipping. |
| SKU | → SKU. Required — product identifier on the fulfillment item. |
| Quantity | → Quantity Ordered. Required — quantity to fulfill. |
| Title | → Name. Optional — product name. |
| UPC | → UPC. Optional — universal product code. |
Also map Fulfillment Request Number (required) so each request is identified in Magento. The address rows apply to both the Billing and Shipping blocks. Flxpoint creates the purchase order via
POST /V1/orders. Use the Order Status Filter to avoid re-sending already-processed requests.| Magento Field | Maps To – Notes |
|---|---|
| Carrier Code | → Carrier. Optional — the shipping carrier (e.g. UPS). |
| Comment | → Note. Optional — the shipment comment. |
| Shipment Created At | → Shipped At. Optional — the shipment creation date. |
| Title | → Method. Optional — the shipping method title. |
| Tracking Number | → Tracking Number. Required — without it, shipments are retrieved but not attached to orders. |
Only Tracking Number is required. Pulls from
GET /V1/shipments. Use the Shipment Status Filter to sync only relevant records, and confirm the Sales → Operations → Shipments permission is enabled on the Access Token.Common issues
Test Connection fails with a 401 or 403 error
A 401 means the Access Token is wrong, expired, or the integration was deactivated in Magento Admin — regenerate it by deactivating and reactivating the integration, then update the token in Flxpoint. A 403 means the token is valid but its API scope is missing the resource — edit the integration in Magento Admin → API tab, add the missing permission, save, and reactivate. Also confirm the Store URL includes
https:// with no trailing slash.GIP runs but imports no products or is missing catalog data
Confirm SKU and Quantity are mapped (both required). If title, description, or manufacturer are missing, enable Fetch All Attributes — those fields may not be storefront-visible. If products are being removed, check that no Website ID restriction is narrowing the result set. If only partial data returns, increase the API Page Size to 100.
GIS custom fields or dimensions not syncing
Confirm Fetch Custom Fields is enabled in the GIS settings. When syncing dimensions, also map Dimension Unit or the values may not display correctly. Verify the custom attributes actually exist on the product in Magento Admin → Catalog → Products. Make sure Archive/Un-Archive is not enabled on both GIP and GIS — if it is, disable it on GIS.
Send Fulfillment Requests failing — order rejected or request not processing
Usual causes: Fulfillment Request Number or SKU not mapped (both required); missing or incomplete address fields (map Address Line 1, City, Country Code, First Name, Last Name and Postal Code for billing and shipping); the Sales → Operations → Orders permission missing on the token; or duplicate requests — use the Order Status Filter. Check the run log for the exact Magento API error to pinpoint the missing field.
Get Shipments not returning tracking or shipments not linking
Confirm Tracking Number is mapped — without it, shipments are retrieved but not attached to orders. A Shipment Status Filter may be excluding the ones you need — adjust or remove it. Confirm the Sales → Operations → Shipments permission is enabled. If a shipment exists in Magento but still will not link, verify the Magento order IDs match what was sent during Send Fulfillment Requests.
Job pauses mid-sync or returns partial records (HTTP 429 / timeouts)
Magento enforces API rate limits. Reduce the API Page Size (try 100 or lower — large responses cause timeouts), stagger GIP and GIS so they do not run simultaneously, and widen the gap between scheduled runs. Check the run log for HTTP 429 or timeout errors to confirm rate limiting is the cause.
FAQs
How do I generate the Access Token in Magento?▸
In Magento Admin, go to System → Integrations → Add New Integration. Enter a name (e.g. "Flxpoint Integration"), open the API tab, set Resource Access to All (or the minimum permission set), click Save, then Activate. The Access Token is generated on activation — copy it immediately and store it securely. It is shown only once; if lost, deactivate and reactivate the integration to generate a new one.
What does Get Inventory (Primary) import versus Get Inventory (Secondary)?▸
GIP pulls the full catalog: SKU, Title/Name, Description, Manufacturer/Brand, plus variant Quantity, Price, UPC and Weight, as well as images, categories (up to 3 levels) and product attributes — via
/V1/products, /V1/categories and /V1/products/attributes. GIS pulls supplementary data: Height, Width, Length, Dimension Unit, Shipping Cost, GTIN and up to 100 custom fields (when Fetch Custom Fields is enabled). Run GIS after GIP on a more frequent schedule.What does the Fetch All Attributes setting control in GIP?▸
When Fetch All Attributes is enabled, GIP retrieves all product attributes regardless of storefront visibility; when disabled, only storefront-visible attributes are fetched. If fields like manufacturer code, UPC, or custom attributes are missing after a GIP run, enable it to pull the full attribute set. Note this can increase import time for large catalogs.
Which Magento endpoints does each operation use?▸
GIP and GIS:
GET /V1/products, GET /V1/categories, GET /V1/products/attributes. Send Fulfillment Requests: POST /V1/orders plus the fulfillment-request acknowledgement call. Get Shipments: GET /V1/shipments. If any of these return a 403, confirm the Magento integration has the matching Sales or Catalog permission enabled.