• 1Connect Shopify
  New to this? Click Create Connection, choose Shopify (OAuth), and approve the app on your store. If you already connected your store, just pick it from the list.
• 2Configure Settings
  • Set New Listings to Paused — Start new imports as Paused so you can review and link to sources first.
  • Master SKU — Choose which Shopify field becomes your unique ID in Flxpoint (usually Variant SKU or Barcode).
  • Product & Listing Management — Decide whether we only create new items or also update existing ones when a match is found.
  Why “Paused” helps: It gives you a safe review step to catch errors before activating listings.
• 3Run the Import
  Click Run Sync. This runs on demand (no scheduler).
  After completion, check Recent Notifications for created/updated counts and any errors.

• Don’t have Variant SKUs? Add SKUs in Shopify first. Missing SKUs often cause “SKU must be provided” errors.
• Unsure about Master SKU? Pick the field that’s unique per variant. If in doubt, use Variant SKU.

• Review Paused Items: Go to Channel Listings, open the Paused items, verify data, and connect to sources if needed.
• Unpause Listings: Select the listings → Actions → Edit → Unpause.
• Product & Listing Management modes:
  • Create Products & Listings Only: Import & link by SKU; create new when no match exists.
  • Create New Products Only: Build new products in Flxpoint without touching existing ones.
  • Create and Update Products & Listings: Import & link by SKU and overwrite matches with Shopify data; create when no match exists.

Parents and variants from Shopify, including core details, images, and metafields.

Shopify Field	Maps To	Example	Purpose	Status
externalListingId	Flxpoint externalListingId	123456789	Identifies the parent listing	Supported
SKU (Handle)	Flxpoint SKU	product-handle	Identifier for the product	Supported
Title	Flxpoint Title	Blue T-Shirt	Product name	Supported
Description	Flxpoint Description	Comfortable cotton t-shirt	Product description	Supported
Manufacturer	Flxpoint Manufacturer	BrandX	Product manufacturer	Supported
Images	Flxpoint Images	image_url.jpg	Product images	Supported
customField (Product Metafields)	Flxpoint customField	color: blue	Additional product metadata	Supported
Attributes (Tags)	Flxpoint Attributes	tag: summer	Product attributes	Supported
Category1/2/3 (CustomCollections)	Flxpoint Categories 1–3	Apparel / T-Shirts / Casual	Category context	Supported

Shopify Field	Maps To	Example	Purpose	Status
externalListingId	Flxpoint externalListingId	987654321	Identifies the variant	Supported
SKU	Flxpoint SKU	variant-sku-001	Unique identifier	Supported
UPC (Barcode)	Flxpoint UPC	012345678905	Universal product code	Supported
Title	Flxpoint Title	Blue T-Shirt – Medium	Variant name	Supported
Price / MSRP / SalePrice	Flxpoint Price / MSRP / SalePrice	29.99 / 39.99 / 24.99	Pricing	Supported
Quantity	Flxpoint Quantity	100	Available stock	Supported
customFields (Variant Metafields)	Flxpoint customFields	size: medium	Additional metadata	Supported
Options	Flxpoint Options	Medium, Blue	Variant options	Supported
Weight / Unit	Flxpoint Weight / Weight Unit	0.5 / lbs	Weight & unit	Supported

• “SKU must be provided…” — Add Variant SKUs in Shopify, then re-run the import.
• Connection errors — Re-authorize the Shopify app or confirm the correct store connection.
• Unexpected overwrites — If you chose “Create and Update…”, Shopify data will overwrite matched items. Pick the mode that fits your workflow.

• Manual Execution: Import Listings doesn’t support scheduling.
• Master SKU: Choose a unique field (Variant SKU or Barcode) to ensure clean linking and updates.
• Results: Check Recent Notifications after each run for counts and error messages.

• 1Connect Shopify: Choose (or create) your Shopify connection via OAuth and click Save and Proceed.
  Note: If you manage multiple stores, double-check you authorized the correct shop domain before proceeding.
• 2Configure Settings:
  • Location ID — Inventory location to update. Must match a valid Shopify location or quantities won’t move.
  • Linking Priority — Add rows like Listing Variant → SKU ↔ Shopify Variant → SKU. We try from top to bottom until a match is found.
  • Scheduling — Optional. Enable a cadence (e.g., hourly/daily) if you want automatic sync.
  Click Save and Proceed.
• 3Define a Mapping Template: Select your Sync Listings template (e.g., Shopify Sync Listings 1) so we know which fields to send to Shopify (Quantity, Price, SKU, etc.). Save, then Run Sync or let the schedule take over.

• Wizard steps: Connect an Integration, Configure Settings, Define a Mapping Template — each shows a check mark when complete.
• Tooltips that explain Linking Priority (“rows are tried top to bottom”).
• A scheduling toggle on the Configure screen if you want automation.

Template	Use Case	What it Covers	Availability
Shopify Sync Listings 1	Keep Shopify price/qty in sync	Maps List Price → Price, Quantity → Quantity, SKU → SKU.	Available

How your Flxpoint listing fields flow to Shopify.

Flxpoint Field (From)	Shopify Variant Field (To)	Type	Required?	Notes
Listing Variant → Quantity	Quantity	Number	Yes	Inventory updates occur at the selected Location ID.
Listing Variant → List Price	Price	Number	Recommended	Use rules if you need markups/rounding.
Listing Variant → SKU	SKU	Text	Recommended	Primary match key for Linking Priority.

Rule	Type	When it Helps	What it Does
Markup price by %	Number	Create Shopify selling price from cost or list price	Applies a percentage increase and can round to .99.
Clamp min/max quantity	Number	Prevent over-listing or under-listing	Forces the sent qty within your safe range (e.g., 1–50).
When SKU starts with … then set value	String	Account for vendor prefixes	Outputs a different field or flag when the pattern matches.

Utility	Availability	How You Might Use It
Mapping Sets	Optional — available	Combine inputs (e.g., base price + fee) into one output.
Lists	Optional — available	Reusable value lists (approved brands, restricted SKUs).
Builders	Optional — available	Create custom outputs if your Shopify workflow needs them.

• Shopify connection is authorized and saved.
• Location ID is set to a valid Shopify inventory location.
• Linking Priority includes at least one reliable pair (usually SKU ↔ SKU).
• A Sync Listings mapping template is selected and saved.
• Scheduling is enabled if you want automation; otherwise run manually.

• Quantity didn’t change — Confirm the template maps Quantity → Quantity and that the location matches your Shopify Location ID. Ensure “Track inventory” is enabled on the variant in Shopify.
• Nothing linked — Review Linking Priority; start with SKU ↔ SKU. Make sure your Shopify variants actually have SKUs.
• Price not updating — Verify List Price → Price is mapped and that no other app overrides price after our sync.
• API throttling — Shopify may rate-limit. Space your schedule (e.g., hourly) and reduce batch sizes if available.
• Hidden vs Delisted — “Hide” (set to out-of-stock / remove sales channel visibility) is reversible; “Delist” requires publishing again.

Feature	Availability	What to Expect
Hiding	Supported	Use rules to hide when qty ≤ 0 or based on flags.
Delisting	Supported	Removes item from sale; re-publish to restore.
Custom Fields	Not primary	Sync focuses on price/qty/SKU; other attributes depend on your template.
Multiple Locations	Supported (single target)	Sync applies to the chosen Location ID for this integration.
Scheduling	Supported	Run on demand or enable a recurring schedule.

• 1Connect Shopify: Add Shopify — Publish Listings and select your Shopify connection (API credentials or OAuth2). Click Save and Proceed.
• 2Configure Settings:
  • Location ID — set the Shopify inventory location ID used for publishing.
  • Publication IDs (optional) — publish to one or more Shopify publications using a comma-separated list. Use either numeric IDs or full GIDs consistently, and do not include spaces.
    Numeric: 1234567890,9876543210

    GID: gid://shopify/Publication/1234567890,gid://shopify/Publication/9876543210

    Invalid: 1234567890, 9876543210 (spaces)  |  1234567890; (semicolon)
  • Truncate Title to 255 — prevents publish failures when titles exceed Shopify limits.
  • Additional Variant Images — uploads variant-specific images when a parent image exists (useful for color-based variants).
  • Namespace & Use Underscore in Meta Fields Name — controls how metafields are named when sending custom data.
  • Auto-Create Smart Collection — optionally create Smart Collections based on mapped Product Types.
  • Advanced Image Duplication Logic — helps prevent duplicate image uploads by caching checksums.
  • Sort Variants by Option Position — sorts variants by option order when creating new parent products.
  • Automate (optional) — schedule publishing jobs (runs in UTC).
  Click Save and Proceed.
• 3Define a Mapping Template: Select your Publish Listings mapping template (e.g., Publish Listings 1) to control which fields are sent to Shopify (Title, Description, Tags, Category, SKU, Price, images, metafields, etc.). Then run manually or set a schedule.

• Wizard steps: Connect an Integration, Configure Settings, Define a Mapping Template.
• Settings include Location ID, optional Publication IDs, image behavior, title truncation, metafield namespace options, and scheduling.
• Mapping template grid with Flxpoint fields (left) → Shopify fields (right), plus options like Don’t Map, Set to Empty, Value, and Rules.

Template	Use Case	What it Covers	Availability
Publish Listings 1	Create/update Shopify products & variants	Parent fields (Title, Description, Product Type, Tags, Category) + Variant fields (SKU, Price, Compare at Price/MSRP, Weight/Unit) + Images + Metafields (when configured).	Available

Quick snapshot of how Flxpoint listing fields commonly map into Shopify for publishing.

Flxpoint Field (From)	Shopify Field (To)	Type	Required?	Notes
Listing Parent → Title	Title	Text	Recommended	Enable Truncate Title to 255 if needed.
Listing Parent → Description	Description	Text/HTML	Optional	Use your content rules to standardize formatting.
Listing Variant → SKU	Variant SKU	Text	Yes	SKU uniquely identifies variants; must be mapped.
Listing Variant → List Price	Variant Price	Number	Recommended	Primary sell price in Shopify.
Listing Variant → MSRP	Compare at Price	Number	Optional	Should be greater than or equal to Price.
Listing Parent → Attributes	Tags	List/Text	Optional	Sent as comma-separated tags.
Listing Parent → Category 1	Category	Text	Optional	Use Shopify taxonomy IDs (GID format) when applicable.
Images (Parent/Variant)	Images	List	Recommended	Use duplication logic to prevent repeated uploads.

Flxpoint now supports publishing all Shopify metafield types from a Publish Listings mapping template. This allows you to send correctly typed data into Shopify metafields instead of relying only on plain text values.

Supported metafield types include (but are not limited to):

• single_line_text_field, multi_line_text_field
• number_integer, number_decimal
• boolean
• json
• rich_text_field
• date, date_time
• weight and other Shopify typed fields

In the Publish Listings mapping template, you can map a Flxpoint field to a Shopify metafield target and select the target metafield data type in the mapping UI.

• Flxpoint validates the mapped value against the selected metafield type before sending it to Shopify.
• If the value does not match the selected type, the Publish run returns a mapping warning/error and the field will not be sent until fixed.
• The Publish template shows a sample preview of the value and a quick type validation status (Valid / Invalid) next to used metafield rows.

Mapping templates now include a Metafield Type selector when you map to a customField / customFields target. Select the Shopify metafield type you intend to write (for example, json or rich_text_field).

Common validation rules:

• json — value must be valid JSON (object or array)
• rich_text_field — value must be valid Shopify rich text JSON (see Developer Appendix example)
• number_integer / number_decimal — must be parseable numbers (no extra characters)
• boolean — true or false (case-insensitive)
• date / date_time — ISO 8601 format

If validation fails, the mapping shows a warning and the Publish run will skip that metafield (Publish run logs include detailed error messages).

Use this in the Mapping Template / sample preview when writing to a rich_text_field.

• Metafield value rejected / validation error — confirm the selected Metafield Type in your mapping template matches the value format. For json and rich_text_field, confirm the value is valid JSON; use Postman to simulate the payload if needed.
• Rich text appears as escaped string in Shopify — this means Flxpoint sent a string rather than structured JSON. Ensure your mapping value is a JSON object (not a string blob). The mapping preview will show Invalid if Flxpoint detects this.
• Unexpected publish failures after enabling metafield types — check the publish logs for the specific metafield error. Common causes: invalid numeric formats (e.g., 2.5 kg instead of 2.5 for number types) or incorrect ISO date formats.
• User mistakenly maps wrong type — the mapping UI displays a prominent warning and the Publish run will skip the invalid mappings; instruct users to correct the mapping type or value before retry.

Rule	Type	When it Helps	What it Does
Title normalization	String	Inconsistent parent titles	Standardizes capitalization/formatting; pairs well with title truncation.
Tag builder	String/List	You want consistent tagging	Creates Shopify tags from attributes, brands, categories, or static values.
Category mapping	Rule/Lookup	You use Shopify taxonomy IDs	Maps Flxpoint category values to Shopify taxonomy category GIDs.
Price guardrails	Number	Prevent bad pricing	Blocks prices below a threshold or rounds to a preferred ending.

If your mapping template exposes a Publication IDs field, enter a comma-separated list with no spaces. Use either all numeric IDs or all GIDs.

• Shopify connection saved on Step 1.
• Location ID set correctly for your Shopify store.
• SKU is mapped in the Publish Listings template.
• Variant options stay within Shopify limits (max 3 options, max 100 variants).
• If using Publication IDs, the list is comma-separated with no spaces and a single consistent format (all numeric or all GIDs).

• Title length failures — enable Truncate Title to 255.
• Invalid Publication IDs — use commas only, no spaces; keep all IDs in the same format (all numeric or all GIDs).
• Change not applied to existing products — publication targeting applies on create/unhide. Use hide → unhide to re-apply publications.
• Variant option limit — ensure no more than 3 options and no more than 100 variants per product.
• Metafield issues — verify Namespace/Key conventions and that the metafield type matches what Shopify expects.
• Image upload issues — confirm image size/format requirements and enable Advanced Image Duplication Logic to reduce duplicates.
• Category mapping issues — ensure the taxonomy category ID (GID) is valid and matches Shopify’s taxonomy.
• Product/variant mismatches — if a product or variant was deleted in Shopify, unlink/re-link in Flxpoint before re-publishing.

Feature	Availability	Notes
Products & Variants	Supported	Creates/updates Shopify parent products and variants based on your mapping template.
Variants / Options	Supported	Max 3 options per product; max 100 variants per product.
Metafields	Supported	Requires correct namespace/key behavior as configured in settings/templates.
Tags (from attributes)	Supported	Attributes can be published as Shopify tags (comma-separated).
Categories	Supported	Map to Shopify taxonomy category IDs where applicable.
Images	Supported	Supports parent and (optionally) variant images; duplication logic helps prevent re-uploads.
Multiple Publications	Supported	Set via Publication IDs (comma-separated). Applied on create/unhide, not every routine sync.
Scheduling	Supported	Optional automation runs in UTC.

• 1Connect: Authorize your Shopify store and click Save and Proceed.
• 2Filters & Statuses:
  • Where: Get Orders → Step 2: Filters
  • Fulfillment status: select unfulfilled and/or partial.
  • Financial status: include the statuses you need (e.g., paid, authorized).
  Why this works: Shopify tracks production at the fulfillment-order level. Using unfulfilled/partial reliably brings in those jobs while they’re in progress.
  Quantity note: Map line Quantity from line_items.quantity. Using fulfillable quantity can cause orders to import “On Hold”.


• 3Advanced options (optional):
  • Import Already Fulfilled Order Items — bring in lines with fulfillable_quantity = 0 for accounting/reporting.
  • Allow Zero Fulfillable Shipment — marks those lines as shippable so you can create Fulfillment Requests and Purchase Orders. Use this with the option above.
  • Import Items from Configured Location Only — include only the line items that belong to the Shopify fulfillment order for the Location ID you entered in the channel. Default: Off. Turn this on if you route by location and don’t want items from other Shopify locations (e.g. “LA” warehouse) to be imported.
  • Import Order Risk Rating — When enabled, Flxpoint will import risk ratings from Shopify for each order, if risk assessment is enabled in Shopify or provided via a third-party app in Shopify.

  
  How it Works

  When enabled, orders will import with a risk rating tag:
  High, Medium, Low, Pending, or None

  • Order import can be delayed up to 30 minutes for an order if fraud risk evaluation has not yet completed.
  • If a risk rating is not assigned after 30 minutes, the next Get Orders job will import the order with a risk rating of Pending or None.
  • PENDING → Shopify had not added a risk rating at the time Flxpoint imported the order.
  • NONE → Shopify did not run fraud analysis for this order.

  You can build Order Import Workflow rules using these tags to automatically hold orders.

  Example Rule:

  If Order → Tags → Contains → High OR Medium
  → Then set Order Status → On Hold

  This allows you to review potential high-risk orders before routing or fulfillment to your suppliers.

  
  • 4Run or Schedule: Test with a manual run, then enable a schedule if you want automation.

Choose which Shopify identifier becomes your Flxpoint Order Reference Number to keep reporting consistent.

Flxpoint Field	Shopify Property	Looks Like	When to Use
Order Reference Number	order.name	#1001	Matches the label seen in Shopify UI.
Order Reference Number	order.order_number	1001	Numeric only; ideal when downstream systems expect digits.
Order Reference Number	order.id (Shopify orderId)	gid or numeric ID	Best for cross-system joins and shipment lookups.

• Shopify connection is authorized and saved.
• Filters include unfulfilled/partial (and the needed financial statuses).
• Quantity mapping uses line_items.quantity.
• Advanced options are enabled if you need fulfilled lines (and set to shippable).

• 1Connect Shopify: Create/select your OAuth connection and click Save and Proceed.
• 2Configure Settings:
  • Location ID — Required. Fulfillments post to this Shopify location.
  • Sync “Closed” Order Status — Optional. Sends a Closed status for orders with partial/no fulfillment (common for in-store orders).
  • Shipping Mappings — Map Shopify rates (e.g., Free, Expedited) to your Flxpoint policies (Ground, Two Day, etc.).
  • Channel Shipping Text (In-Store) — Map text such as “In-Store”/“POS” so your In-Store workflow rules can identify these orders.
• 3Run the Sync: Use Run Sync to post fulfillments. If a shipment spans multiple locations, lines from the selected Location ID post now; others retry on the next run.

Align your Shopify rate names with Flxpoint shipping policies.

Shopify Rate	Flxpoint Policy	Example Use
Free	Ground	Free economy shipments
Standard	Two Day Shipping	Guaranteed 2-day delivery
Expedited	Expedited	Paid faster option

• Location ID is required. Verify the numeric ID in Shopify and enter it here so fulfillments hit the right location.
• Mixed-location orders: Lines for your selected Location ID post now; other locations are retried on subsequent runs.

• Template type: Sync Orders (e.g., “Shopify Sync Orders 1”).
• UI has columns for Flxpoint Shipment (left) → Shopify Fulfillment (right).
• Common actions: Save Mapping, Duplicate, Delete.

Flxpoint Field	Shopify Field	Required?	Notes
Shipment → Tracking Number	Tracking Number	Required	Primary identifier for the fulfillment.
Shipment → Carrier	Tracking Company	Recommended	Carrier name (UPS, USPS, FedEx, etc.).
Shipment → Tracking URL	Tracking URL	Optional	Deep link to carrier tracking.
Notify Customer (value/rule)	Notify Customer	Optional	Set to true to email customers on post.
Location (integration)	Location ID	Required (via config)	Usually set by the integration using your Location ID.

• Don’t Map — field not sent.
• Set to Empty — clears destination value.
• Field — map a Flxpoint field (e.g., Tracking Number → Tracking Number).
• Value — static value (e.g., true for Notify Customer).
• Rules — conditional outputs (e.g., notify only when Carrier = UPS/FedEx).

• Shopify OAuth connection is saved.
• Location ID is correct and active in Shopify.
• Template maps Tracking Number (and preferably Carrier + Notify Customer).
• Shipping Mappings cover your live rate names.
• Sync “Closed” is only enabled if you truly want that status posted.

• Shipment didn’t post — If the product was deleted in Shopify after order creation, Shopify can’t attach the fulfillment. Re-link the product/variant in Shopify & Flxpoint, then re-run.
• Wrong location — Verify the numeric Location ID matches the items being fulfilled.
• No customer email — Set Notify Customer to true (value or rule) in the template.
• Mixed-location orders — Only lines for your Location ID post in the current run; others retry next run.
• API rate limits — Stagger runs or reduce batch size if available.

• Required: Tracking Number mapping and a valid Location ID.
• In-Store/POS: Use Channel Shipping Text mapping and consider posting Closed to mirror your POS behavior.
• Scope: Sync Orders pushes fulfillments/status; it does not re-price or re-publish products.