Axis as a Source

Table of Contents

How to Connect Product Operations Order Operations

Axis as a Source supports most of our core source operations, such as retrieving product data and sending orders, but not receiving order shipping information.

How to Connect

📋 Phase 1: Create Your Axis Source +

Create Source in Flxpoint

Go to Sources → + Add Source. Name it Axis and choose Vendor Warehouse. Click Save & Next.

Tip: Assigning a Vendor enables vendor-level reporting and optional Vendor Portal access.

Enable Order Fulfillment

When prompted, select Yes (Recommended) for “Eligible for Order Fulfillment” so you can route orders to this source, then click Confirm.

Choose Integrations

In Integration Set-Up, click Start Creating Integrations and add what you need:

Get Inventory (Primary)
Send Fulfillment Requests
Get Shipments
Get Invoices (optional)

🔐 Phase 2: Set Up the Axis Connection +

Gather Credentials

You’ll need your Axis User Name, Password, and the Axis Subdomain.

Tooltip: Enter only the subdomain part of your site URL (e.g., for https://XYZ.azurewebsites.net/, enter XYZ). Do not include https:// or .azurewebsites.net.
Example of a valid subdomain: capitolrangefirearms1486.

Create “New Axis Connection”

In Get Inventory (Primary) select Connect an Integration → Axis → New Connection, then fill:

Connection Name — e.g., “Axis Connection”.
User Name — Axis username.
Password — Axis password.
Subdomain — subdomain only, e.g., XYZ if your URL is https://XYZ.azurewebsites.net/.

Click Test Connection, then Save Connection.

If the test fails: Recheck credentials and subdomain format, confirm HTTPS accessibility, and ensure your Axis account is enabled for API access.

🛒 Phase 3: Configure Order Processing +

Use the Axis Connection

Attach your Axis connection to:

Send Fulfillment Requests — sends orders to Axis.
Get Shipments — retrieves tracking and shipment updates.

Automation Settings

Enable Automatically Send Orders if you want Flxpoint to transmit orders without manual review.
Add any routing rules (minimums, categories, etc.) as needed.

✅ Phase 4: Mapping & Activation +

Field Mapping for Inventory

Create or select a mapping for Get Inventory (Primary):

Map SKU, Quantity, Price, Title/Description, Images.
Apply transformations (markup rules, qty adjustments) as needed.

Note: Include both product attributes and on-hand quantity fields.

Master SKU Strategy

In Master SKU, map Inventory SKU → Master SKU. Consider a prefix to identify Axis items.

Activate & Verify

Click Save & Complete. Monitor the initial sync in Fulfillment Sources → Integrations. Run a test order and confirm shipments return with tracking.

Product Operations

Get Inventory (Primary)

Supported | Axis — Get Inventory (Primary)

Introduction

In Flxpoint, Get Inventory (Primary) (GIP) is the main import job for bringing Axis catalog data (products and quantities) into your Global Inventory Pool.

      Note: GIP refers to the job that imports data. The Global Inventory Pool is where that data lives after each run.
    

Use this job to keep your Axis inventory synced in Flxpoint:

Import the complete product list with key details (title, brand, categories, images, weight).
Keep quantities current using Axis quantity-on-hand.
Maintain basic catalog structure using Axis department (Category 1) and item (Category 2).

Each run follows this workflow:

1Token Generation — Flxpoint makes a POST request to https://<your-domain>.azurewebsites.net/token with grant_type=password and your Axis credentials to obtain a bearer token.
2Domain Setting — The domain you enter in the connection settings is used for all requests (e.g., myaxis.azurewebsites.net).
3Product Fetch — Products are retrieved from /api/Ecomm/GetProducts in batches of 250.
4Map Fields — Axis fields are matched to your Mapping Template.
5Save Inventory — Data is written to the Global Inventory Pool for downstream channel sync.

Example: If Axis reports QOH = 18 for ITEM 12345, after GIP runs, Flxpoint will also show 18 available units for that SKU.

Follow these steps in the Axis source → Get Inventory (Primary):

1Connect Integration — Choose Axis and enter your connection details.
- Domain — Enter only the base host, e.g., myaxis.azurewebsites.net. Why? Do not include https:// or paths. Flxpoint builds the full URL under the hood for /token and /api calls.
- Credentials / Token — Provide the Axis username/password used for token generation (or your pre-issued API token if applicable).
2Configure Settings
- Archive/Un-Archive Inventory — Enable to archive items missing from the feed and automatically restore them if they return. Recommendation: don’t also enable archive on the Secondary job for the same source.
3Create a Mapping Template — Use the recommended fields below and adjust to your catalog.
4Save & Schedule — Run manually or enable scheduling (UTC time).

Suggested starting point for Axis:

Flxpoint Field	Axis Field	Notes
SKU	`Item Nmbr` (or `Item`)	Primary identifier. Choose the field your team uses as the unique SKU.
Title	`Product Description` (fallback: `Short Description`)	Human‑readable product name.
Brand	`Manufacturer`	Normalized brand label.
Quantity	`Qoh`	Quantity on hand provided by Axis.
Price (Retail)	`Retail Price`	Standard retail; optionally also map `Web Price`.
Weight	`Weight`	Unit may not be defined by Axis; confirm in shipping settings.
Category 1	`Department`	Imported as Category Level 1.
Category 2	`Item`	Imported as Category Level 2.
Images	Images list	Axis supports multiple images.
UPC	`Product UPC`	Barcode if present.

Tip: If Axis exposes Qty Committed and Qty On Order, you can bring them in as custom attributes for downstream rules and reporting.

Custom Fields: Supported — Axis ProductAttribute list is copied to attributes.
Variations/Options: Not supported.
Generic Pricing: Supported — single pricing available.
Client Pricing: Not supported.
Quantity: Supported via Axis feed.
Multiple Warehouses: Not supported.
Weights & Dimensions: Weight only (unit not defined in feed).
Images: Supported — multiple images.
Categories: Supported — department → Category 1, item → Category 2.
Delta vs Full Feed: Full feed.
Archive Support: Supported.

Auth error? Verify Axis username/password and that the domain is correct. Use the token POST in a tool like Postman to confirm.
Missing products? Confirm your Axis account exposes the catalog to the API and that your Mapping Template includes Item/Item Nmbr.
Zero quantities? Check that Qoh is present in the Axis response for the items in question.
Rate limiting / slowness? Keep batch size at 250 and schedule off‑peak hours.

Enable a schedule so this job runs automatically and keeps your Axis data fresh. Schedules run in UTC.

Order Operations

Send Fulfillment Requests

Supported | Axis — Send Fulfillment Requests

Introduction

The Send Fulfillment Requests operation sends purchase orders from Flxpoint to Axis, generating sales orders in your Axis system.

      Note: All fulfillment requests in Flxpoint must be properly mapped to Axis order fields for the request to succeed.
    

Use this job to:

Create purchase orders in Axis when a channel order is routed to the Axis source.
Pass along required shipping, billing, and customer information.
Ensure FFL and compliance fields are included for firearm-related products.

1Trigger — A fulfillment request is generated in Flxpoint.
2API Call — Flxpoint sends the request via Axis API /api/Ecomm/SubmitOrder.
3Field Mapping — Data is mapped according to your configuration (see Mapping Template below).
4Order Creation — Axis validates and creates the order in its sales system.
5Response — Axis returns a Fulfillment Request Number which Flxpoint saves to the FR.

Example: A Shopify order for SKU AX12345 routes to Axis, Flxpoint calls /SubmitOrder, and Axis responds with FRN: 9988123 confirming creation.

To configure Send Fulfillment Requests for Axis:

1Connect Axis — Ensure your Axis credentials and domain are configured in the source.
2Open Mapping Template — Map Flxpoint Fulfillment Request fields to Axis order fields.
3Include Shipping and Billing — Map address lines, city, state, postal code, country, phone, and email.
4Map Compliance Fields — Map FFL Address1/2, FFL City, FFL Phone, etc. for firearm shipments.
5Save & Test — Send a test order to confirm successful order creation in Axis.

Flxpoint Field	Axis Sales Order Field	Notes
Customer PO	`Customer PO`	Reference for the order, passed from channel order.
Shipping Address	`ShipTo*` fields	All address fields including Name, Address1, City, State, Postal Code, Country.
Billing Address	`BillTo*` fields	All billing details for invoicing.
FFL Address / City / Phone	`FFL*` fields	Required for firearm shipments.
SKU	`SKU`	Must match SKU in Axis catalog.
Quantity	`Quantity`	Units to ship.
Price	`Price`	Line item price.
Subtotal	`Subtotal`	Calculated subtotal per line item.
Shipping Method	`Carrier/Method/Code`	Map to Axis shipping code values.
Total	`Total`	Order total including shipping and tax.

Orders are submitted in real-time via API call.
Axis returns a Fulfillment Request Number and status.
Compliance fields (FFL) are mandatory when shipping firearms.
Errors in mapping or credentials will cause request failures.

Authentication error? Verify Axis domain and credentials (token must be valid).
Missing FFL data? Ensure FFL Address and Phone fields are mapped for firearm shipments.
Order not created? Review Axis response message in Flxpoint job logs.

Flxpoint Knowledge