Shopify as a Source

The two most common causes are missing SKUs on Shopify variants and a wrong Location ID. Confirm every variant expected to sync has a SKU in Shopify, that the Location ID matches where inventory is stocked, and that your template maps Variant SKU → SKU and Available → Quantity. After bulk catalog changes, run a Force Full Inventory Fetch to catch up, then return to standard runs.

One or more variants had no SKU or the SKU field was not mapped. Open the mapping template and confirm Variant SKU is mapped to SKU, then add SKUs to any variants missing them in Shopify and re-run the job.

The fulfillment service name mapped in Send Fulfillment Requests does not exist in the vendor's Shopify store (Shopify returned an empty fulfillment_services: [] list). Ask the vendor whether they have a fulfillment service configured and use the exact name, or remove the fulfillment service field from the mapping template entirely.

Shopify requires both the shipping method title and the shipping price to build the shipping_lines block. If only the title is mapped and the price is blank, Shopify silently drops the line. Confirm both Shopify Order - Shipping Method Title and Shopify Order - Shipping Price are mapped.

Shopify's transaction block requires all three fields: Transaction Kind, Transaction Gateway and Transaction Amount. If any one is missing the whole block is silently skipped, and Amount must be greater than zero ("Amount must be greater than zero for sale transactions"). Map all three and confirm the Gateway matches a payment gateway configured in the vendor's store.

Get Shipments only retrieves fulfillments that exist in Shopify. Confirm the vendor has created fulfillments with tracking on their side. If fulfillments exist but aren't linking, verify the Location ID matches where the fulfillments were created and that the lookback window covers the age of your target fulfillment requests.

The Transactions field is Shopify's financial "source of truth" for an order (payment status, gateway and amount) and should be managed by the vendor to reflect whether the order is actually paid - not driven from Flxpoint. If the vendor needs to identify which marketplace or channel an order came from, use Tags or Order Note Attributes instead of mapping Transactions.

Shows when any Customer fields are mapped in the Send Fulfillment Requests template - once any Customer field is mapped, those values override Shopify's default find-or-create logic, so a partially mapped Customer section fails the job. Open the mapping template, review the Customer section, confirm all required customer fields are mapped (avoid partial mapping), then save and re-run Send Fulfillment Requests.

Shipments only exist once an order has a fulfillment created in Shopify. If the order isn't fulfilled yet (or hasn't synced into Shopify as expected), the shipment pull returns no results. Confirm the order has a fulfillment with tracking in Shopify; if you filter by Location ID, confirm it matches the fulfillment's location; and widen the lookback window if your job configuration includes a time range.

When using the Manage Exclusions modal to exclude specific categories, selections may appear to disappear if you use the search filter or scroll through a long list. This is a known UI behavior where the visible set changes; however, your selections are now maintained internally by a persistent state map. Ensure you complete your selections for the current source before switching to another source, as the saved state resets upon switching to prevent data leakage between different suppliers.

This typically occurs when order line items are missing custom attributes in the fulfillment request. Ensure that Custom Properties Direct Copy is enabled in your Send Fulfillment Requests mapping template. Flxpoint now processes these fields to appear under customAttributes in the Shopify order line items regardless of whether a Location ID is present. To verify the fix, place a test order and confirm the fields appear in the vendor's Shopify Admin.

Shopify as a channel is your storefront: where customer orders come in and products are published. Shopify as a source treats a Shopify store as your fulfillment supplier: you pull inventory from it, send fulfillment requests (purchase orders) to it, and retrieve tracking back. A common setup uses a vendor's Shopify store as the fulfillment source while a separate channel is where customers place orders.

OAuth2 is recommended when you can log into the Shopify store as owner or admin. If you're connecting a vendor's store and they can't complete OAuth2, have them install the Flxpoint Shopify App in their Shopify Admin and share their Store URL and API Key, then use Bearer Token and paste the API Key into the Token field. For legacy custom apps, Basic Auth uses the API Key and API Secret Key. Always use the .myshopify.com URL, not the store's custom domain.

No: each inventory or fulfillment job targets a single Location ID. To cover multiple locations, create a separate Get Inventory (Primary) job and a separate Get Inventory (Secondary) job per location, and one Send Fulfillment Requests job per location the vendor fulfills from.

Both Get Inventory (Primary) and Get Inventory (Secondary) have a maximum cadence of once per hour. Primary is for full catalog refreshes and is typically run daily; Secondary is the faster delta job for cost and quantity updates and suits hourly scheduling. Stagger the two so Secondary runs after Primary completes.

Use it as a one-time normalization step if inventory was imported from a file and quantities are missing or stale in the Global Inventory Pool, or after a major catalog change on the Shopify side. It pulls inventory for all products and variants at the selected Location ID regardless of recent change status, so expect longer runs on large catalogs. Return to standard runs after the catch-up completes.

No: this is a known platform limitation. Flxpoint syncs fulfillment and tracking data from Shopify sources automatically, but vendor-side refund and cancellation events do not surface in Flxpoint and must be coordinated manually. This affects multi-vendor marketplace setups in particular; if it's critical to your workflow, submit a feature request through the Flxpoint feedback channel.