Coreware is a firearms and outdoor-industry dealer-management and e-commerce platform. The Flxpoint integration imports your Coreware catalog with both dropship-eligible and owned (in-house) inventory, surfaces vendor lead-time data where Coreware provides it, sends dropship fulfillment requests, pushes purchase orders for special (non-dropship) orders, and imports shipment tracking back into Flxpoint. This guide walks you through connecting Coreware, configuring each operation, and troubleshooting common issues.
How to Connect
🧭 Phase 1: Launch the Source Wizard
+
Open Sources and start the Wizard
Go to Sources (building icon) → + Add Source → Configure Single Source. This opens the Source Wizard.
Step 1 — Create Source
Enter a clear name (e.g., Coreware). Then choose the Source Type that best fits how this Source will be used.
After selecting the Source Type, click Save & Next.
Choose the right Source Type
Coreware is a dealer-management and e-commerce platform for the firearms and outdoor industry. The integration can import both dropship-eligible SKUs and your owned (in-house) inventory.
- Vendor Warehouse (Recommended): You send Fulfillment Requests to Coreware so dropship vendors ship directly to your customers.
- Internal Warehouse: You stock items and ship from your own facility.
- External Warehouse: A 3PL or external partner ships your owned inventory.
- Product Data Source: Content-only source to enrich product details (no fulfillment).
For Coreware: select Vendor Warehouse for the dropship flow. Owned (in-house) stock pulled from your Coreware location codes is still imported alongside dropship availability, so routing rules can compare both for every order.
Step 2 — Vendor Set-Up
Choose Yes (Recommended) to Assign Vendor → Confirm. You'll enable Vendor reporting and optional portal access.
Step 3 — Order Fulfillment
Decide if this source is eligible to fulfill orders:
- Yes (Recommended): You can route orders here.
- No: Routing/Shipping steps won't apply.
Step 4 — Order Fulfillment Settings
Use Defaults or No, Customize. You'll see:
- Override: Auto Processing (Use Global / Auto Process / Do NOT Auto Process).
- Commit Stock + Inventory Management Options.
- Allow Backorders / Cancel Unacknowledged Items.
Step 5 — Shipping Cost Estimations
Pick one:
- Yes, Use Rate Shopping (Real-Time Estimates).
- No, Set Up via Rules.
Step 6 — Order Routing Groups
Enable on all routing groups? Select Yes or No, Customize. Optionally mark Default Order Routing Group. Save & Next.
Reminder: Complete Step 1 — Shipping Methods and Step 2 — Source Location in Phase 2 below, then return (if needed) to finalize.
🚚 Phase 2: Shipping Methods & Source Location (Finish the Wizard)
+
Goal
Finish the Source Wizard by confirming your Ship From location and reviewing shipping behavior for Coreware.
Step 1 — Shipping Methods
When the wizard opens the Shipping Methods step for this Source:
- Skip if you do not need to configure shipping methods at this time.
- Or Add Method to configure shipping methods if required for your setup.
Step 2 — Source Location (Ship From)
Enter the Ship From address:
- Address, City, State/Code, Postal Code, Country/Code
- Optional: Contact Name, Phone, Email
Finish the Wizard
Review Steps 1–2, then click Save and Complete. The wizard is now finished.
Next: Proceed to Phase 3 to create your Coreware connection.
🔑 Phase 3: Create Your Coreware Connection
+
Goal
Coreware uses a single connection for every operation — Get Inventory (Primary & Secondary) imports dropship and owned stock, Send Fulfillment Requests submits dropship orders, special orders are pushed as purchase orders, and Get Shipments imports tracking. You create that one connection here and reuse it across all operations.
Step 1 — Open Get Inventory [Primary] and start
Inside your Coreware source, open Integrations → Get Inventory [Primary] and click Start Creating Integrations.
In the connector gallery, choose Coreware. If you don't see it, use Not Listed? → Request a custom integration.
Step 2 — Enter your Coreware API credentials
Fill the form with the API credentials issued by Coreware for your dealer account:
- Connection Name (required) — a friendly label for this connection (e.g., Coreware)
- API credentials (required) — issued by Coreware for your dealer account
Where do these come from? Coreware issues your API credentials for your dealer account. If you don't have them yet, request them from your Coreware contact before starting this step. Flxpoint stores them encrypted and never exposes them in the catalog.
Step 3 — Configure your inventory scope and location codes
Decide whether you want to import dropship-eligible SKUs, owned (in-house) inventory, or both. Owned inventory is pulled using your Coreware location codes so each physical warehouse's stock can be shown alongside dropship availability for order routing.
Confirm your location codes first: owned-inventory quantities are tied to the Coreware location codes you configure here. If a code is missing or wrong, that warehouse's stock won't appear in Flxpoint.
Step 4 — Test Connection and Save
Click Test Connection to confirm Flxpoint can authenticate with Coreware using the credentials you supplied. When the test succeeds, click Save Connection.
If the test fails: double-check the API credentials — they are case-sensitive. If they are correct but the connection still fails, confirm with your Coreware contact that the credentials are active for your dealer account.
Step 5 — How Flxpoint uses this connection
A single Coreware connection powers every Coreware operation:
- Get Inventory (Primary) — full catalog import: dropship-eligible and owned SKUs, with vendor lead time where Coreware provides it
- Get Inventory (Secondary) — high-frequency quantity refresh
- Send Fulfillment Requests — dropship orders sent to Coreware for fulfillment
- Special Orders — purchase orders pushed for non-dropship items
- Get Shipments — tracking and status updates imported back into Flxpoint
One connection, every operation: when configuring each operation later, you'll select this same Coreware connection. You do not need to recreate it.
Next
Configure Product & Order Operations 🚀
Now that your Coreware connection is saved, go to the Operations sections of this doc to set up the Coreware
integrations you need. Start with Get Inventory (Primary) to import the catalog, then enable the order operations
(Send Fulfillment Requests, Special Orders, Get Shipments) as you need them.
Product Operations
Get Inventory (Primary) imports your full Coreware catalog — dropship-eligible and owned SKUs — with quantities, cost, and vendor lead time where available. Get Inventory (Secondary) is a lean, high-frequency quantity refresh that keeps stock levels current between full catalog runs.
Get Inventory (Primary)
Get Inventory (Secondary)
Supported
Introduction
Coreware — Get Inventory [Primary] imports your full Coreware catalog into Flxpoint, including both dropship-eligible SKUs and owned (in-house) inventory. It transforms the data into Flxpoint's standard product and variant structure and saves it to your Source Inventory so each SKU can participate in order routing.
Setup Steps
- 1Connect Coreware: Select your saved Coreware connection. Confirm the location codes you want owned inventory pulled from are configured on the source. Click Save and Proceed.
-
2Choose what to import:
- Dropship-eligible SKUs — products Coreware can dropship to your customer on your behalf.
- Owned (in-house) inventory — stock physically held at your locations, pulled using your Coreware location codes.
- 3Select a Mapping Template: Choose the Coreware Get Source Product template and click Save and Complete.
What happens on each run
- Authenticate securely with Coreware using your stored credentials.
- Retrieve the catalog — dropship-eligible products and owned-inventory items.
- Apply location codes to attribute owned stock to the correct warehouse(s).
- Capture vendor lead time where Coreware provides it, so it can be displayed and used by routing.
- Transform & save into Flxpoint's product/variant structure in your Source Inventory.
Field Mapping
| Coreware Field | Flxpoint Field | Notes |
|---|---|---|
| SKU / Item Number | Product → SKU | Primary identifier used to match and route. |
| Title / Description | Product → Title / Description | Direct mapping. |
| Brand / Manufacturer | Attributes → Brand | Used by brand-based routing rules. |
| Dropship Availability | Inventory → Quantity (dropship) | Stock Coreware can dropship on your behalf. |
| Owned Inventory (per location code) | Inventory → Quantity (owned) | Attributed to the warehouse(s) tied to your configured location codes. |
| Vendor Lead Time | Lead Time field | Imported where Coreware provides it; see the note below for unavailable values. |
| Cost / Price | Pricing → Cost | Used for pricing rules downstream. |
⏱️ Vendor lead time visibility: When Coreware supplies a lead-time value for a SKU or vendor, Flxpoint displays it as a data field on the product. Lead time is not guaranteed for every vendor or SKU — when Coreware does not provide a value, the lead-time field is simply left blank for that item rather than estimated.
🏭 Owned vs. dropship inventory: Owned stock pulled from your Coreware location codes is stored alongside dropship availability for the same catalog. This lets your routing rules compare in-house stock against dropship options for every order.
Quick Checks
- Coreware credentials are entered and the connection test passed.
- The location codes for your owned inventory are configured on the source.
- You selected whether to import dropship, owned, or both.
- A Coreware mapping template is selected and saved.
Troubleshooting
- Owned inventory missing: confirm the correct Coreware location codes are configured — owned stock is attributed to those locations.
- Lead time blank for some items: expected — Flxpoint only shows lead time where Coreware provides it; blanks mean Coreware returned no value for that vendor/SKU.
- A SKU shows only dropship (or only owned): verify your import scope includes both inventory types.
- Catalog incomplete: re-run the Primary job; if items are still missing, confirm they are active and visible to your dealer account in Coreware.
Operation Details
| Feature | Availability | What to Expect |
|---|---|---|
| Dropship Inventory | Supported | Dropship-eligible quantity imported into Source Inventory. |
| Owned Inventory | Supported | Pulled by location code; shown alongside dropship. |
| Vendor Lead Time | Supported (when provided) | Displayed as a data field; blank when unavailable. |
| Multiple Locations | Supported | Owned stock attributed per configured location code. |
Supported
Introduction
Coreware — Get Inventory [Secondary] is the high-frequency inventory refresh. It updates quantity (and cost where mapped) for SKUs already imported by the Primary job — keeping both dropship and owned stock current between full catalog runs without re-importing catalog details.
Setup Steps
- 1Connect Coreware: Re-use the same connection from Primary. Click Save and Proceed.
- 2Confirm scope: Keep the same location codes you imported from in Primary so owned-inventory quantities stay aligned. Click Save and Proceed.
- 3Select a Mapping Template: Choose the Coreware Get Inventory (Secondary) template and click Save and Complete.
What it refreshes
- Quantity for dropship and owned SKUs.
- Cost when mapped.
- Catalog details (titles, descriptions, attributes) are not refreshed here — those come from Primary.
Field Mapping (Secondary)
| Coreware Inventory Field | Flxpoint Field | Notes |
|---|---|---|
| SKU / Item Number | Variant → SKU | Matches the SKU imported by Primary. |
| Location Code | (internal — warehouse routing) | Attributes owned quantity to the correct location. |
| Quantity (dropship / owned) | Inventory → Quantity | Refreshed each run. |
| Cost | Pricing → Cost | Optional mapping. |
Keep Secondary lean. Run Primary for full catalog imports and Secondary on a higher frequency for fast stock-level updates across both dropship and owned inventory.
Quick Checks
- Location codes match the Primary import.
- The Secondary mapping template is selected.
- Primary has run at least once so SKUs exist to refresh.
Troubleshooting
- Quantities not updating: confirm Secondary is scheduled and the SKUs were first imported by Primary.
- Owned stock looks off: verify the location codes match what Primary used.
- New products not appearing: Secondary only refreshes existing SKUs — run Primary to add new catalog items.
Order Operations
Flxpoint can send dropship fulfillment requests to Coreware, push purchase orders for special (non-dropship) orders, and import shipment tracking back to update your orders. Routing rules decide which path each order takes based on data sourced from Coreware.
Send Fulfillment Requests
Special Orders (Purchase Orders)
Get Shipments
Supported
Introduction
Coreware — Send Fulfillment Requests sends dropship orders to Coreware for fulfillment on your behalf. When routing rules select Coreware as the dropship vendor for an order, Flxpoint submits the fulfillment request automatically.
Setup Steps
- 1Enable Send Fulfillment Requests on your Coreware source.
- 2Configure routing rules so Coreware is selected for dropship-eligible orders — you can route by brand, availability, and lead time.
- 3Save and activate. Once routing assigns an order to Coreware, Flxpoint sends the fulfillment request automatically.
How rule-based vendor selection works
- Brand — route specific brands to Coreware.
- Availability — route only when Coreware has dropship stock.
- Lead time — prefer Coreware when its lead time meets your threshold (where lead-time data is available).
What Flxpoint sends
| Flxpoint Order Data | Sent to Coreware as | Notes |
|---|---|---|
| Line items (SKU + quantity) | Fulfillment request line items | Only dropship-eligible SKUs. |
| Ship-to address | Customer shipping address | Coreware ships directly to your customer. |
| Order reference | External order reference | Used to match the shipment/tracking back. |
Dropship vs. special orders: Fulfillment requests cover dropship orders. Non-dropship items are handled separately as special orders (see the Special Orders tab).
Quick Checks
- Send Fulfillment Requests is enabled on the source.
- Routing rules assign dropship-eligible orders to Coreware.
- The order's SKUs are dropship-eligible in your Coreware catalog.
Troubleshooting
- Order not sent to Coreware: check that routing selected Coreware and the SKU is dropship-eligible.
- Order routed to special orders instead: non-dropship items are pushed as purchase orders — see the Special Orders tab.
- Request rejected: verify the ship-to address and that the item is still available for dropship in Coreware.
Supported
Introduction
Coreware — Special Orders covers non-dropship items. For these, Flxpoint pushes a purchase order to Coreware with the order's line items. You can then view outstanding special orders and their statuses inside Flxpoint, separate from the dropship fulfillment flow.
Setup Steps
- 1Enable special-order purchase orders on your Coreware source.
- 2Set routing rules so non-dropship items are directed to the special-order (purchase order) path instead of dropship fulfillment.
- 3Review outstanding special orders in Flxpoint, where each shows its current status.
Dropship vs. special orders
- Dropship — sent as a fulfillment request; Coreware ships to your customer.
- Special order — pushed as a purchase order with line items for non-dropship items.
- Routing distinguishes the two based on data sourced and configured from Coreware (e.g., dropship eligibility).
Purchase order contents
| Flxpoint Data | Pushed to Coreware as | Notes |
|---|---|---|
| Line items (SKU + quantity) | Purchase order line items | For non-dropship / special-order items. |
| Order reference | PO reference | Used to track the special order in Flxpoint. |
| Status | Special-order status | Outstanding special orders and their statuses are visible in Flxpoint. |
Visibility: Outstanding special orders and their statuses are tracked in Flxpoint so you can monitor non-dropship items separately from dropship fulfillment.
Quick Checks
- Special-order purchase orders are enabled on the source.
- Routing directs non-dropship items to the special-order path.
- You can see outstanding special orders and statuses in Flxpoint.
Troubleshooting
- Special order not created: confirm the item is non-dropship and routing directed it to the purchase-order path.
- Item dropshipped instead of special-ordered: review the dropship-eligibility data and routing rules.
- Status not updating: statuses reflect what Coreware reports for the special order; re-check after the next sync.
Supported
Introduction
Coreware — Get Shipments pulls shipment tracking and status updates from Coreware back into Flxpoint. As tracking arrives, Flxpoint updates the related order and can trigger Sync Orders to push the update to your sales channels.
Setup Steps
- 1Enable Get Shipments on your Coreware source.
- 2Schedule the job so tracking and status updates are pulled on a regular cadence.
- 3Enable Sync Orders on your sales channels so tracking flows out to customers automatically.
What happens on each run
- Pull tracking + status for fulfilled orders from Coreware.
- Match to the order in Flxpoint using the order reference.
- Update the order with tracking and shipment status.
- Trigger Sync Orders so the update is pushed to your sales channels.
Shipment data
| Coreware Field | Flxpoint Field | Notes |
|---|---|---|
| Tracking number | Shipment → Tracking | Applied to the matched order. |
| Carrier | Shipment → Carrier | When provided. |
| Shipment status | Order status update | Marks the order shipped / fulfilled. |
| Order reference | (match key) | Links the shipment back to the Flxpoint order. |
📧 Customer tracking notifications: Flxpoint updates the order and triggers Sync Orders. The customer-facing tracking email is typically sent by your sales channel when it receives the Sync Orders push — not by Coreware directly.
Quick Checks
- Get Shipments is enabled and scheduled.
- Sync Orders is enabled on the relevant sales channels.
- The originating order has a matching reference in Coreware.
Troubleshooting
- Tracking not appearing on the order: confirm the order reference matches between Flxpoint and Coreware.
- Customer didn't get a tracking email: the notification is sent by the sales channel on Sync Orders — check that Sync Orders is enabled and ran.
- Status stuck: shipment status reflects what Coreware reports; re-run Get Shipments after the next update.
Troubleshooting
Common issues and solutions for Coreware. Click any card to expand.
!Owned inventory not importing
What's happening
Owned (in-house) stock is pulled using your Coreware location codes. If the codes aren't configured, owned inventory won't appear — only dropship availability will.
How to fix it
- Open your Coreware source → Configuration.
- Enter the correct location codes for the warehouses you want to import.
- Re-run Get Inventory (Primary).
!Vendor lead time is blank for some items
What's happening
Flxpoint displays vendor lead time only where Coreware provides it. Lead time is not guaranteed for every vendor or SKU.
How to fix it
- This is expected when Coreware returns no lead-time value — the field is left blank rather than estimated.
- If you believe a value should exist, confirm it is populated for that vendor/SKU in Coreware.
!Order went dropship instead of special order (or vice versa)
What's happening
Routing distinguishes dropship from special (non-dropship) orders using data sourced and configured from Coreware. If an order took the wrong path, the routing rules or dropship-eligibility data need review.
How to fix it
- Check the item's dropship eligibility as imported from Coreware.
- Review your routing rules so dropship items go to fulfillment requests and non-dropship items go to special-order purchase orders.
!Fulfillment request not sent to Coreware
What's happening
Dropship orders are sent only when routing selects Coreware and the SKU is dropship-eligible.
How to fix it
- Confirm routing assigned the order to Coreware (by brand, availability, or lead time).
- Verify the SKU is dropship-eligible and the ship-to address is valid.
!Special order status not updating
What's happening
Outstanding special orders and their statuses are shown in Flxpoint based on what Coreware reports for the purchase order.
How to fix it
- Confirm the purchase order was created in Coreware for the special order.
- Re-check the status after the next sync; statuses reflect Coreware's latest update.
!Tracking imported but customer wasn't notified
What's happening
Flxpoint imports tracking from Coreware and triggers Sync Orders. The customer-facing tracking email is typically sent by your sales channel when it receives the Sync Orders push.
How to fix it
- Confirm Sync Orders is enabled on the sales channel and ran after the shipment was imported.
- Verify the channel's own notification settings are configured to email tracking to customers.