Most channels default newly created listings to a Draft or Hidden state. Check the channel's draft/inactive section first - if the listing is there, it published correctly and needs to be activated on the storefront side. If it doesn't appear at all, check the Publish Listings job log for per-listing errors (common cause: missing required attributes like GTIN or Brand that the channel enforces).

On Hold is the most common order issue in support tickets and has several causes. Check the order's status message for the specific reason - it appears on the order detail page. Common causes: (1) No matching shipping policy - the shipping method on the channel order doesn't map to a Flxpoint shipping policy. Add the mapping in the channel's Shipping Mappings settings. (2) Order routing rules - an Order Import Workflow rule is intentionally holding the order for review. (3) No eligible source - no source has the item in stock and in the routing configuration.

Three most common causes:
(1) Empty SKU - the incoming order line item has no SKU value at all. A SKU mismatch alone does not block import (it's brought in as not managed), but an empty SKU does. Open the order on the channel to confirm every line item has a SKU populated.
(2) Authentication failure - the API token or credentials have expired. Go to Channels → [Channel] → Integrations → Get Orders and check the integration status and recent log for auth errors.
(3) Order Import Status - Validate the Order Import Status configured in Flxpoint matches what is set on the store/channel side.
Mismatch between the financial or fulfillment status configured in Flxpoint's Get Orders integration and the actual order statuses used by the channel will result in orders not being imported.

Check in this order: (1) Is the listing linked to a Flxpoint product? Unlinked listings are skipped entirely. (2) Is the underlying source inventory syncing? A failed source import means Flxpoint has stale data to push. (3) Has the API token expired? Check the channel's Integrations tab and last Sync Listings log. (4) Is a quantity buffer rule zeroing out the displayed quantity? Check channel Pricing & Quantity rules. Note: if quantity shows as synced in Flxpoint but is wrong on the channel, the Location ID may be targeting the wrong warehouse.

Sync Orders pushes tracking on its next scheduled run - not in real time. First confirm the shipment exists in Flxpoint (check the order's Fulfillment Requests section). If the shipment is there but tracking hasn't synced after a Sync Orders run, open the Sync Orders job log - it will show whether the push was attempted and what error occurred. Common causes: channel API rejected the tracking format, the order is in a status the channel won't accept updates for, or Tracking Number is not mapped in the Sync Orders template.

Each channel enforces different required attributes. Amazon requires GTIN/UPC and a valid brand. Walmart requires item spec categories and specific attribute sets. Check the Publish Listings logs, or on the listing page, for the error - it will specify exactly which field is missing or invalid. Add the required value to the product in Flxpoint's Product Catalog, then re-publish the listing.

Channel Shipping Mappings allow orders imported from a sales channel to be mapped to a centralized shipping policy.
Once a Channel Shipping Mapping is configured, the process works as follows:

- An order is imported with the shipping method "4-7 business days"
- "4-7 business days" is recognized through a Channel Shipping Mapping
- Based on this mapping, the order is associated with the "Standard" shipping policy
- During order routing, any source shipping methods mapped to the "Standard" shipping policy are considered eligible and can be selected for fulfillment.

For sales channels that do not natively support a hidden or archived status (such as GunBroker), Flxpoint now automatically triggers a delist action when you move a product to the Hidden queue. This ensures the product is removed from the storefront and cannot be sold, rather than simply logging a sync error while the listing remains active.

Flxpoint automatically pauses or terminates integration jobs that fail repeatedly to prevent log flooding and redundant retries. This often occurs due to 403 Forbidden errors, store maintenance modes, or 503 service errors. To resolve this, update your credentials or reauthorize the integration, then manually reactivate the job schedule once the underlying error is cleared.

This can occur if the listing SKU and product SKU do not match and the external listing ID (listingVariantId) is missing. If the channel setting 'Flag Unmanaged Items as not Shippable' is enabled, Flxpoint may incorrectly mark these line items as unshippable and close the order prematurely. To resolve this, ensure SKUs are synchronized between the channel and Flxpoint, or disable the flag if you need the order to remain open for manual linking.

This error occurs when a product's variation structure or option names (e.g., Size, Color) are modified after an initial publishing attempt. Flxpoint may attempt to reuse existing option sets that no longer match the new data. To resolve this, unpublish or delist the product from the eBay channel, ensure the outdated Inventory Item Groups are cleared, and then republish the listing with the updated variation specifics.

Both - they serve different purposes. Sync Listings runs frequently (hourly or more) to keep price and quantity current. Publish Listings runs less often and pushes content changes - use it when you've updated titles, descriptions, or images. Running only Sync Listings means content edits never reach the storefront. Running only Publish is too slow to keep stock accurate.

Yes - they're separate operations that work together. Get Orders pulls new orders from the channel into Flxpoint. Sync Orders pushes tracking back to the channel after fulfillment. If you configure Get Orders but not Sync Orders, orders route and fulfill in Flxpoint but customers and the channel never receive tracking updates.

Yes - each store is its own channel in Flxpoint with its own credentials, integration settings, listing rules, and order import. Connect each separately. Use clear naming to distinguish them, e.g. Shopify – Brand A – US and Shopify – Brand B – EU.

It depends on inventory velocity and sync frequency. Fast-moving SKUs on high-volume channels need a larger buffer to account for the gap between a sale and the next sync run. A common starting point: show 0 on the channel when actual stock falls below 3–5 units. Monitor for oversells in the first two weeks and adjust upward if needed. For large-quantity SKUs, a percentage buffer (e.g. show 90% of actual stock) works better than a fixed number.

Change feed is the recommended option for the Product & Listing Management setting on the Import Listings integration, which is supported on Shopify, Amazon, WooCommerce, BigCommerce and Magento. It creates new products and listings and updates existing ones, and each run fetches only what changed on the channel since the last successful run, so runs stay fast. The alternatives are New products and listings, New listings, and Catalog refresh, which is not recommended. See Import Listings for the full comparison.