Skip to main content

Connect Gearfire / AXIS to AIQ Marketing + Loyalty

About the AIQ <> Gearfire AXIS Integration

Review our Integration Grid for supported features.

This article covers connection for AIQ Marketing + Loyalty.


How to Connect AIQ to Gearfire / AXIS

AIQ Steps

This step is only required to sync waiver data from AIQ to Gearfire. Inventory, customer and order data is processed from Gearfire to AIQ and only requires that you enable the AIQ integration in Gearfire.

  1. For Owner level users, navigate to Settings > Integrations, use the search bar to locate Gearfire, then click on it to open the Integration Card.

  2. Fill out the credentials:

  3. Username and Password — API credentials issued by Gearfire.

  4. Base URL — the retailer's Gearfire Azure endpoint (e.g. https://yoursite.azurewebsites.net).

  5. Source Name — must exactly match the source bound to those API credentials.

  6. After these are filled in, click the Add Credential button.

  7. Lastly, click the purple Connect button in the top right. You have now completed the minimum settings needed to connect your integration!

Gearfire Steps

  1. In AIQ, navigate to Settings > API & Tracking

  2. Copy the API Key and UID from this page

Add these credentials inside your Gearfire AXIS POS to enable the integration.

How to Map a Store

  1. Navigate to Settings -> Company Account > Retail Store

  2. Click Edit on the store you wish you map

  3. Under Store Mappings you'll see the AIQ REST API symbol

  4. Click on the empty field to the right of the symbol and a dropdown will appear to "map" the key

  5. Click Save settings and you are done mapping the store. Keep in mind this must be repeated for any additional stores that you add to the account.


Gearfire Waiver Sync

Waiver setup in Gearfire

You don't need to create anything on the Gearfire side. The first time a shopper signs a given waiver form, AIQ creates the matching waiver record in Gearfire automatically and names it after the form — so a form numbered 2 shows up in Gearfire as RANGE-WAIVER-002.

The waiver applies across all of your stores rather than being set up location by location. After that first setup, AIQ remembers it's done and doesn't repeat it, so there's no duplicate clutter in AXIS.


How signed waivers sync to Gearfire

When a shopper fills out one of your signup forms and that form has waivers turned on for their store, their signed waiver is sent to Gearfire within moments — no exporting, no manual entry, no staff step at the counter.

The following information is sent along with the signature:

  • Full name

  • Date of birth

  • Address (sent exactly as the shopper typed it, including out-of-country addresses)

  • Email address

  • Phone number

  • Exact date and time of signing

If the same shopper signs again later, AIQ updates their existing Gearfire record instead of creating a second one. Because this happens in the background, a slow or unavailable Gearfire connection never holds up the shopper at signup — the form still submits normally.

Waivers must be enabled in your form's store settings for this to happen. Signup forms without waivers enabled are not sent to Gearfire.


Minors on a waiver

If a parent or guardian lists minors on the waiver, each minor is sent to Gearfire as their own participant on that same waiver — with their name and date of birth — and flagged as a minor. The adult who signed is sent as a separate participant, flagged as an adult.

For example, a family of four signing one waiver shows up in Gearfire as four distinct participants tied to that waiver, rather than one combined record.


Re-sending waivers

If Gearfire was down, credentials expired, or the connection was misconfigured during a stretch of time, waivers signed in that window may not have made it over. Our support team has a tool to go back and re-send them for a specific form or date range — you don't need to re-enter anything by hand.

  • This is an internal tool — reach out to AIQ Support rather than running it yourself.

  • It currently re-sends minors only, not the adult signers, so a full catch-up for a missed window will need assistance from our team.


AIQ <> Gearfire / AXIS: User Guide

All discounts/rewards you want to offer in the wallet to shoppers must be created in AIQ.

Configuring Discounts

Discounts are configured entirely in AIQ, there's nothing to set up on the AXIS side. Once you build a discount in AIQ, it automatically starts appearing at the AXIS register. No linking or manual sync step is required.

Redeeming Discounts

When a shopper is selected at the register, AXIS pulls their AIQ loyalty wallet automatically and displays their current point balance. When ready to process payment, click the Rewards button. Select a discount from the dropdown and confirm the payment. If the reward is cleared before submitting, the shopper's points are immediately restored.

Creating Loyalty Customers

Loyalty enrollment happens through AIQ, not Gearfire. Customers sign up through an AIQ signup form or are imported and processed overnight, not at the register. Once a customer is looked up in Gearfire, a loyalty checkbox indicates whether they're already a member.

Timing depends on whether the customer already exists in Gearfire: an existing customer who newly enrolls in loyalty will show as a member the next time they're looked up.


FAQs

I am having issues with data coming over, who should I contact?

This integration was built out by the Gearfire/AXIS team. They send there data through our REST API endpoints throughout the day and AIQ processes the data overnight.


How long does it take before I start to see my POS data in AIQ?

Within 24-48 hours, you should see data populating in AIQ


How can I confirm that the integration is active and signups are being sent?

Look under your Personas page in AIQ. The integration is functioning properly if you see new personas being added via Rest API. You can also see inventory appearing in your analytics.


I am getting an account notification that I have unmapped stores, how can I fix this?

Once you see data coming through AIQ, you must "map" the API key to the store(s) to assign a "favorite store" to the shopper. See How to Map a Store above for directions on how to accomplish this.


Need Help?

If you need assistance, reach out to AIQ Support anytime via chat widget within your AIQ Dashboard.

Did this answer your question?