Guns.com as a Channel
July 2, 2026
Summary
Guns.com is an online marketplace for firearms, ammunition, and accessories. Connect it as a channel with your Guns.com API Username, API Password, and Environment to publish listings, keep price and quantity in sync, and import orders. Note that Sync Orders (tracking writeback) is not supported for this channel.
What this integration does
Publish Listings
Create new UPC-based Guns.com listings and publish used firearms into Guns.com's predefined categories
Sync & Link Listings
Link Flxpoint listings to approved Guns.com listings and keep price and quantity in sync
Get Orders
Import Guns.com orders with payment status, shipping/FFL destination, and customer PII
How to connect - credentials you need
In the Connect Channel step of the setup wizard, enter your API Username and API Password and select the Environment, then click Test Connection → Save Connection.
API UsernameRequired
The API username issued for your Guns.com seller account. Request it from your Guns.com account representative or the seller onboarding team.
Provided by Guns.com; API access must be approved and enabled for your seller account.
API PasswordRequired
The API password paired with your Guns.com API Username.
Provided by Guns.com.
EnvironmentSetting
Selects which Guns.com API environment to connect to — Production (
Use the Guns.com API production environment for live listings and orders.
auth.guns.com) for live selling, or Sandbox (auth-sandbox.guns.com) for testing.Can't find your credentials or is Test Connection failing? Request API access from your Guns.com account representative or the seller onboarding team, and confirm API access has been approved and enabled for your seller account. If the integration doesn't appear in your Flxpoint channel list, that approval is usually the missing step.
Important - read before configuring
Sync Orders is not supported — manage tracking in the Guns.com portal
Flxpoint cannot push shipment tracking back to Guns.com. After fulfilling a Guns.com order in Flxpoint, enter tracking and shipment status updates directly in the Guns.com seller portal. Plan your fulfillment workflow around this — there is no automated tracking writeback for this channel.
Sync & Link only connects to approved (active) Guns.com listings
When linking by UPC, Flxpoint only matches to approved (active) listings on Guns.com. Inactive listings are skipped even if they share the same UPC as an active listing. If a listing won't link, confirm the matching Guns.com listing is in an active/approved state before re-running.
New items require a valid UPC — publish is blocked without one
For new-item publishing, UPC is required. If the listing variant has no UPC, Flxpoint silently skips it and sends no API request. Guns.com treats UPC as the unique product key and matches the offer to its existing catalog entry, so the UPC must correspond to a product already in the Guns.com catalog.
Used items have strict category requirements — image can't be sent via mapping
Publishing a used firearm requires a Main Category (handguns, shotguns, or rifles), a Subcategory (bolt action, lever action, over under, pump action, semi auto, single shot, side by side, derringer, or revolver), and a quantity of 1. Missing any of these fails the publish for that item. Guns.com's own listing requirements expect an image on used firearms, but the Publish Listings mapping template has no image field — Flxpoint can't send one on publish, so plan to add the image directly on the Guns.com side after the listing is created.
Mapping - fields to know
| Flxpoint Field | Maps To – Notes |
|---|---|
| Title | → Title. Required. e.g. Smith & Wesson M&P 9. |
| Description | → Description. Recommended. |
| Brand | → Brand. Recommended. |
| List Price / MSRP / MAP | → Price. Required. |
| Quantity | → Quantity. Required — any value ≥ 0 for new items; always 1 for used items. |
| UPC | → UPC. Required for new items — Guns.com's unique product key (SKU is internal to Guns.com). |
| Condition | → Condition (New / Used). Required. |
| Category 1 / 2 / 3 | → Main / Sub Category. Required for used items (e.g. Rifles → Bolt Action). |
| Image | No image mapping is available in the Publish Listings mapping template. Variations, attributes/tags, custom fields, and weights & dimensions are also not supported on publish. |
Offerings vs. Creation: New items are created via an existing UPC offering when available; used or custom items without a UPC can still be created, but must fit one of Guns.com's predefined categories.
| Flxpoint Field | Maps To – Notes |
|---|---|
| Quantity | → Guns.com Quantity. Required — if it isn't mapped, syncs can fail for active items without a clear error. |
| List Price (or MSRP) | → Guns.com Price. Recommended. Matching uses your Linking Priority (SKU → UPC) and links only to approved (active) Guns.com listings. |
| Order Field Group | Key Fields – Notes |
|---|---|
| Guns.com Order | Order ID, Order Date, Status, Payment. Order and payment statuses are supported; currency is USD. Orders are fetched in batches of up to 100 using a Since date filter and the selected status(es). |
| Billing Address | First/Last Name, Street, City, State, Zip, Phone, Email. Subject to your PII retention setting. |
| Shipping Address | First/Last Name, Street, City, State, Zip, Phone, License. Includes destination FFL details when applicable. |
| Order Item | Order Item ID, Listing ID, Amount, Serial Number. Serial Number appears on firearm items when provided. |
| FFL | FFL ID, Name, Business Name, Street, City, State, Zip, Phone, Expiration Date. Captures the receiving dealer's information for compliance and fulfillment. |
Common issues
Publish failing for new items — UPC missing or not being sent
A new item with no UPC is blocked entirely — it's silently skipped and nothing is sent to Guns.com. Check the Publish job logs for skipped SKUs, add a valid 12-digit UPC to each affected listing variant, and re-run Publish. If the UPC exists but the item still fails, confirm it matches an active product already in the Guns.com catalog — new offers are created against existing catalog entries.
Used item publish rejected — category or quantity missing
Used items need three things from the Publish mapping: Main Category (handguns, shotguns, or rifles), Subcategory (one of the nine valid values), and Quantity = 1. In the Publish mapping template, confirm Condition maps to Used, Category 1 maps to the Main Category, Category 2/3 maps to the Subcategory, and Quantity is a fixed value of 1 (not a dynamic field). Note that Publish Listings has no image mapping field, so an image requirement on Guns.com's side for used listings can't be satisfied through Flxpoint mapping — add the image directly on Guns.com after the listing is created.
Listings not linking — no match found despite matching UPC on both sides
Link jobs only connect to approved (active) Guns.com listings, so an inactive listing is skipped even when the UPC matches. Confirm the target listing is active/approved (not pending, suspended, or deactivated) in your Guns.com seller account. If it is active and the UPC matches, check that Linking Priority is ordered as expected (SKU first if applicable, then UPC) and re-run the link job.
Quantity or price not updating on Guns.com after Sync Listings runs
First confirm the listing is linked — Sync Listings cannot update an unlinked item. Open the Sync mapping template and verify Quantity (required) and Price are mapped; an unmapped Quantity fails syncs for active items without a clear error. Check the job's last-run timestamp to confirm it is still running, and allow a few minutes for Guns.com to reflect the update on their end.
Orders not importing from Guns.com
Run Test Connection to confirm credentials are still valid. Make sure at least one Order Status is selected in Get Orders settings — with none selected, no orders pull. Widen the Since date range to cover the orders you expect. If a status is selected and orders still don't appear, verify in the Guns.com seller portal that orders exist in that status. Guns.com's API allows one status per call, so Flxpoint pulls multiple selected statuses in sequence.
FAQs
How do I get API credentials to connect Guns.com to Flxpoint?▸
Your API Username and API Password come from your Guns.com seller account. Contact your Guns.com account representative or the seller onboarding team to request API access, and set Environment to the Guns.com API production environment. If the integration doesn't appear in your Flxpoint channel list, confirm API access has been approved and enabled for your seller account.
What linking identifiers does Sync & Link Listings support?▸
Linking by SKU and UPC. Set the Linking Priority during setup — SKU first when your Flxpoint SKUs match Guns.com, with UPC as a fallback if SKU isn't present on both sides — and Flxpoint tries each identifier from top to bottom until it finds a match. Only approved (active) Guns.com listings are eligible; inactive listings are skipped even if the UPC matches.
What FFL information does Get Orders capture for firearm orders?▸
Get Orders can capture full FFL details for the receiving dealer: FFL ID, Name, Business Name, Street, City, State, Zip, Phone, and Expiration Date, available under the FFL group in the Get Order mapping template. The Shipping Address group also includes a License field for the destination FFL. Map these to your order fields for compliance and fulfillment workflows.
Can I use a Custom Aggregate Field for quantity in Sync Listings?▸
Custom Aggregate Fields (CAFs) are not available in the Publish Listings mapping template, and they also do not appear in the Sync Listings template, which uses a different field set. If you need a CAF as the quantity source for ongoing sync, contact Flxpoint support — making it available there may require a configuration adjustment.
What order statuses can I filter in Get Orders?▸
Get Orders supports multi-select status filtering: All, Awaiting Confirmation, GDC Processing Order, Shipped, Delivered, and Cancelled. Guns.com's API accepts only one status per call, so Flxpoint runs separate calls per selected status.