GunBroker as a Channel

Your GunBroker account password has changed since the connection was set up. Go to the channel's connection settings, re-enter the current GunBroker username and password, and click Test Connection & Continue. All scheduled jobs will resume on their next run once the connection is re-authenticated.

The Category ID mapped is a parent node, not a leaf. Open the GunBroker category CSV, find the lowest-level sub-category for your product, and replace the mapped ID with that leaf ID. All SKUs must use the same category depth - mixed levels will also trigger this error.

Quantity is not mapped in the Publish Listings template, or cost and list price are both zero/missing for the affected SKUs - the built-in rule sets quantity to 0 to prevent low-price publishing, which causes the listing to end immediately. Go to Sales Channels → GunBroker → Templates → Publish Listings → Field Mapping, confirm Quantity and Price are mapped, then check that cost and list price are populated on the source inventory records.

This is the most-reported GunBroker issue in support tickets. Two causes: (1) Both Price and Quantity must be mapped in the Sync Listings template - mapping only one of them causes the job to error silently. Go to Templates → Sync Listings → Field Mapping and confirm both are mapped. (2) The listing ended due to zero quantity - once ended, a listing needs to be republished rather than synced. Add stock and run Publish to bring it back.

GunBroker ends listings when quantity hits zero. Restocking alone doesn't relist them - you need to re-run Publish Listings after adding stock. Sync Listings only updates active listings; it cannot relist ended ones. If auto-relist is important for your workflow, consider a Pricing & Quantity rule in Flxpoint that queues a Publish action when quantity rises above zero.

This is not a missing template setting - GunBroker's Items API doesn't expose a brand/manufacturer field, so there is nothing for Flxpoint to map to. This is a documented integration limitation. The only workaround is to include the brand in a field GunBroker does accept - most commonly the Title (or Description) - using the Publish Mapping Template's prefix or postfix options.

FFL rules are configured at the source level, not the channel level. If all orders from a source are being flagged for FFL - including items that don't require it - check the FFL rules in the source's settings. A rule that applies to all SKUs rather than specific categories or product types will flag everything. Narrow the rule to match only the item types (e.g. handguns, rifles) that actually require FFL transfers.

Sync Orders skips orders with FFL items unless the order is marked FFL Received. For non-FFL orders still not closing, confirm Tracking Number and Carrier are both mapped in the Sync Orders template and that the order is fully shipped - partial shipments are not supported. Check the job log for the specific error on any stuck orders.

If an order item's price comes in empty - for example the SKU is not managed in Flxpoint and Order Item Price is set to Don't Map in the Get Orders template - Flxpoint resolves the missing price to the matched listing/variant price, or zero when there is no match. The invoice subtotal is then always recalculated from the resolved item prices, overwriting whatever subtotal GunBroker sent. Keep Order Item Price mapped in the Get Orders template so imported orders keep their real prices.

The SKU in Flxpoint doesn't match the existing GunBroker listing SKU - Flxpoint created a new listing instead of updating. Correct the SKU mismatch on one side, delete the duplicate on GunBroker, and republish.

Enabling AI Category Mapping overwrites the Category 1 field with the GunBroker category ID and sets Category 2 and 3 to null. If you have mapping rules or shipping profile overrides that depend on your original category names, those rules will stop matching. To fix this, export your categories using the fail-safe link in the AI enablement modal, save these values into custom fields at the listing level, and update your rules to reference the custom field instead of Category 1, 2, or 3.

This occurs when a listing SKU does not match the product SKU and the external listing ID is missing. If the channel setting 'Flag Unmanaged Items as not Shippable' is enabled, Flxpoint incorrectly marks these line items as unshippable, causing the order to auto-close. To resolve this, ensure your SKUs match between Flxpoint and GunBroker, or disable the 'Flag Unmanaged Items as not Shippable' setting in your channel configuration.

The most common cause is that the listing ended due to zero quantity before the price update ran - ended listings don't receive price updates. Check whether the affected listings show as Active or Ended on GunBroker. If ended, add stock and run Publish to relist them. If still active, check the Sync Listings template to confirm both Price and Quantity are mapped - mapping only one causes the sync to fail without a clear error.

Yes. Both listing types are supported. Auction listings are always quantity 1 with a required starting price and optional reserve/buy-now prices. Fixed-price listings support any quantity. Use separate mapping templates if your auction and fixed-price products need different field configurations.

GunBroker does not support hiding - only delisting. When you move a product to the Hidden Queue in Flxpoint it is automatically delisted on GunBroker. To bring it back, add stock and run Sync Listings. There is no way to hide a GunBroker listing without removing it from sale.

Download the official GunBroker category CSV and locate the lowest-level sub-category that matches your product. Use only that leaf-node ID in your mapping template - parent category IDs cause a "terminal categories" error. You can also use Flxpoint's AI category mapping feature in the GunBroker channel settings to auto-suggest leaf IDs.

When Get Orders imports an FFL order, it brings in the FFL dealer details. Orders requiring FFL processing appear as "Needs Attention" and require manual approval before routing. Sync Orders will not push tracking for FFL items until the order is marked FFL Received. Configure FFL rules at the source level to automate flagging - apply rules only to item types that genuinely require FFL transfers (e.g. handguns, rifles) to avoid non-FFL items being incorrectly held.

No - Sync Listings is price and quantity only. To update descriptions, images, or other content on existing GunBroker listings, use Publish Listings with the overwrite option enabled (non-auction listings only). This is a common point of confusion: clients run Sync expecting content changes to appear, but only Publish pushes content.