Axis as a Source
Summary
Axis is a point-of-sale and inventory management platform that connects to Flxpoint over a token-based API. Flxpoint authenticates against your Axis /token endpoint with your username, password and subdomain, then imports the full product catalog and submits orders back to Axis. Receiving shipment/tracking data is not supported through the source integration.
Create a source named Axis (type Vendor Warehouse), start a Get Inventory (Primary) job, then choose Connect an Integration → Axis → New Connection and enter the values below. Click Test Connection, then Save Connection.
/token endpoint.grant_type=password to obtain the token.https://XYZ.azurewebsites.net/, enter XYZ – do not include https://, the .azurewebsites.net suffix, or a trailing slash. Example: capitolrangefirearms1486.https://, no path, no trailing slash), confirm your Axis site is reachable over HTTPS, and make sure your Axis account is enabled for API access. You can also POST directly to https://yoursubdomain.azurewebsites.net/token with grant_type=password in a tool like Postman to confirm credentials.Enter only the subdomain in the Subdomain field – never the full URL
The Subdomain (Domain) field accepts only the subdomain portion of your Axis URL. For https://XYZ.azurewebsites.net/, enter XYZ – not the full URL. Flxpoint builds the complete API URLs internally, so including https://, the .azurewebsites.net suffix, or a trailing slash will cause authentication failures.
Get Shipments is not supported for Axis as a Source
Axis as a Source supports Get Inventory (Primary) and Send Fulfillment Requests only. Tracking and shipment data does not flow back from Axis through the source integration. If you need shipment writeback, use the separate Axis as a Channel integration, which does support importing orders and syncing shipments.
FFL fields are required for firearm shipments in Send Fulfillment Requests
Axis is commonly used by firearms retailers. When routing orders for firearm products, the Send FR mapping must include the FFL address fields – FFL Address1, FFL Address2, FFL City, FFL Phone and related fields. Firearm orders submitted without them fail Axis validation, so configure FFL mapping before going live with firearm routing.
Get Inventory (Primary) is a full feed in batches of 250 – there is no delta mode
Every GIP run retrieves the complete Axis catalog from /api/Ecomm/GetProducts in batches of 250 items – there is no partial or delta update. For large catalogs, schedule GIP during off-peak hours to avoid API rate limiting. Do not also enable Archive/Un-Archive on a second inventory job for the same source.
| Flxpoint Field | Maps From (Axis) – Notes |
|---|---|
| SKU | ← Axis Item Nmbr (or Item). Primary unique identifier – pick the field your team uses as the SKU. |
| Title | ← Product Description (fallback Short Description). Human-readable product name. |
| Brand | ← Manufacturer. Normalized brand label. |
| Quantity | ← Qoh. Quantity on hand reported by Axis. |
| Price (Retail) | ← Retail Price. Optionally also map Web Price. |
| Weight | ← Weight. The unit is not defined in the Axis feed – confirm it in your shipping settings. |
| Category 1 | ← Department. Imported as Category Level 1. |
| Category 2 | ← Item. Imported as Category Level 2. |
| Images | ← Axis images list. Multiple images are supported. |
| UPC | ← Product UPC. Barcode where present. |
| Flxpoint Field | Maps To (Axis Sales Order) – Notes |
|---|---|
| Customer PO | → Customer PO. Order reference passed from the channel order. |
| Shipping Address | → ShipTo* fields – Name, Address1, City, State, Postal Code and Country. |
| Billing Address | → BillTo* fields – full billing details for invoicing. |
| FFL Address / City / Phone | → FFL* fields. Required for firearm shipments. |
| SKU | → SKU. Must match the SKU in the Axis catalog. |
| Quantity | → Quantity. Units to ship. |
| Price | → Price. Line-item price. |
| Subtotal | → Subtotal. Calculated per-line subtotal. |
| Shipping Method | → Carrier/Method/Code. Map to your Axis shipping code values. |
| Total | → Total. Order total including shipping and tax. On success Axis returns a Fulfillment Request Number that Flxpoint saves to the FR. |
https://...) instead of just the subdomain – remove the protocol, suffix and any trailing slash. Otherwise verify the User Name and Password, and confirm your Axis account has API access enabled (contact your Axis administrator). You can test the token endpoint directly by POSTing to https://yoursubdomain.azurewebsites.net/token with grant_type=password and your credentials in Postman.Qoh field is unmapped or returning 0 from Axis. Check the GIP mapping template and confirm Qoh is mapped to Quantity. If the mapping is correct, verify in Axis that inventory tracking is enabled and quantities are entered – items with no inventory tracking return 0 from /api/Ecomm/GetProducts.What fields does Get Inventory (Primary) return from Axis?▸
ProductAttribute list is also available as custom attributes. Variations/Options and multiple warehouses are not supported, and the weight unit is not defined in the feed – set it manually in your shipping settings.How does Send Fulfillment Requests work with Axis?▸
/api/Ecomm/SubmitOrder endpoint to create a sales order. Required fields include Customer PO, the full ShipTo address (Name, Address1, City, State, Postal Code, Country), BillTo address, SKU, Quantity, Price, Subtotal, Total and Shipping Method (Carrier/Method/Code). For firearm products the FFL fields (Address, City, Phone) are also required. On success Axis returns a Fulfillment Request Number, which Flxpoint stores on the FR as the auto-acknowledgement.How do I find my Axis subdomain?▸
.azurewebsites.net. For example, if your store is at https://capitolrangefirearms1486.azurewebsites.net/, your subdomain is capitolrangefirearms1486. Enter only this value in the Subdomain field – not the full URL. If you're unsure, check the address bar in your Axis dashboard or ask your Axis account administrator.