Coreware as a Source
Summary
How to connect Coreware as a source: the credentials it needs, why the inventory location code is required, how cost and quantity are read across locations, and what happens to FFL orders.
Invoices are not imported. Coreware's invoices bill the end customer on the dealer's behalf, not the dealer for wholesale purchases, so there is nothing there to reconcile against a purchase order.
| Field | What to enter |
|---|---|
API Domain NameRequired | The domain Coreware assigns to your store for API access. |
Connection KeyRequired | The key that identifies your account to Coreware. |
UsernameRequired | The API user Coreware issues you. This is not your storefront login. |
PasswordRequired | The password for that API user. |
Inventory Location Code is required, and without it you get nothing
Set it in the integration config before the first inventory run. Coreware answers with an empty inventory response when no location code is supplied, so the job completes and imports zero quantities rather than failing with an error you would notice.
One code per warehouse, or a comma-separated list
The field accepts several codes. Flxpoint queries each location and sums the quantity per product across them, so a product stocked in two listed warehouses shows the combined figure. List only the locations you actually sell from.
FFL orders are checked against Coreware before they are sent
When a fulfillment request carries a Federal Firearms Licence, Flxpoint asks Coreware whether that licence is on file first. If it is not, the request fails with that reason instead of being submitted and rejected later. The integration config has a setting to skip the check when you need to send anyway.
A test account may not return an order number
Production returns the Coreware order number as soon as the order is created and Flxpoint stores it as the confirmation number. A purchase order without one is skipped by Get Shipments and Get PO Acknowledgements, because there is no order to look up.
Imports the full Coreware catalog: products, options and product groups, with grouped variants merged under one parent.
| Field | Maps To: Notes |
|---|---|
| Product code | → Variant → SKU. The per-record identifier. Required. |
| Product group code | → Product → Parent SKU, so every variant in a group lands on the same parent. A group with no code falls back to a generated parent SKU. |
| Description | → Product → Title. Grouped variants take the group's description as the parent title; an ungrouped product uses its own. |
| Detailed description | → Product → Description. The row's own HTML wins; the group's is the fallback. |
| Product manufacturer | → Product → Brand. |
| Base cost | → Variant → Cost, available as an alternate source. The default cost comes from the location, see the next tab. |
| Weight and dimensions | Imported as pounds and inches. Coreware does not send units, so those are assumed. |
Lightweight refresh of quantity and cost only, so stock stays current between full imports.
| Field | Maps To: Notes |
|---|---|
| Quantity | → Variant → Quantity, summed across every location code you listed. A zero is imported as zero, not skipped: the zero is what marks the variant out of stock. |
| Location cost | → Variant → Cost. This is the default. When a location carries no cost of its own, the row's plain cost is used instead. |
| Cost location code | Optional. Set it when you want quantity from one set of locations and cost from another. |
Submits purchase orders and records the Coreware order number as the confirmation number.
| Field | Maps To: Notes |
|---|---|
| PO number | → sent on every order. Always required, and set before any mapping runs so a template cannot overwrite it. |
| Line item SKU | Resolved to Coreware's product id by product code, falling back to UPC. A line whose code matches neither fails with that reason rather than being sent. |
| Ship-to address | Mapped values win, the purchase order's own address is the fallback. US addresses must carry a 2-letter state code. |
| FFL licence number | Sent only on orders flagged as requiring an FFL, and checked against Coreware first. See the warning above. |
Reads order status back from Coreware.
| Field | Maps To: Notes |
|---|---|
| Order status | → Fulfillment request → Status, read from the order Coreware returns for the stored confirmation number. |
| Confirmation number | The key used to find the order. An order without one cannot be checked, exactly as with Get Shipments. |
Retrieves tracking for submitted orders and marks them shipped.
| Field | Maps To: Notes |
|---|---|
| Confirmation number | The Coreware order number stored when the order was submitted. A purchase order without one is skipped and listed in the run warnings. |
| Tracking number and carrier | → Shipment, read from the shipments attached to the order. |
| Product code | Matches each shipped line back to its purchase order item. |
Dimension Unit and Weight Unit are not populated in the parent section of these templates, and item-level mappings are not available in the shipment templates.